From contributor to maintainer: Krystian Podemski's experience with the PrestaShop project
Discover the faces behind the commits
A few years ago, a series of contributor interviews was published on the blog. It was a nice way of putting faces to names and getting to know the people who participate in the PrestaShop project. And this year, we wanted to do it again. So here we go: this section is back on the blog!
For the first interview of the year 2022, let’s meet Krystian Podemski.
Krystian is 31. He comes from Bydgoszcz, Poland, and has been coding for over 15 years. From contributor to maintainer, Krystian has always been a very active member of the community. In July 2021, he even joined the PrestaShop company, as Tech Evangelist in Poland… without ever giving up his role as a maintainer of the open source project!
So, what does it mean to be a maintainer? What skills do you need to become one, and what can you get out of it?
Krystian answered these questions and many more.
Dear readers, meet Krystian!
Hi Krystian, can you tell us more about yourself?
Of course, yes. I’m 31. I’m from Poland, Bydgoszcz - which is very hard to spell! I’m just a normal guy, who is very passionate about his job. I call myself a developer, even though I’m more of a consultant at the moment, which is a bit different. About my hobbies, I like F1, Netflix, and I’m a big fan of La Liga.
When did you get involved in contributing to the PrestaShop project?
I think it was in 2008, about 14 years ago. I started by getting involved in the Polish PrestaShop community. I contributed to the translation of the software into Polish and shared some tutorials on how to use PrestaShop. I was also a very active member of the Polish forum that was created at the time. After that, I started contributing on SVN, until PrestaShop migrated to GitHub, which made contributing much easier!
What motivated you to contribute?
Everyone has their own reasons for contributing to an open source project. In my case, I had just migrated a store to PrestaShop, and I found that the Polish translations needed to be improved. So, I contributed to the translations because, well, I had to! I wanted these translations to be available in the Core, so I did it.
Do you have any advice for first-time contributors?
Yes! Don’t be afraid to try, but first, do some research. We have very good documentation about how to start contributing. I’d highly recommend that you take a look at it. Then, when you feel ready, start with a small contribution, something that you need. I think translation and documentation are a great way to start. I’m pretty sure we have typos in the translations or some parts of the documentation that could be clarified. You just have to start with something.
Now that we’ve talked about your role as a contributor, I’d like to ask you about your role as a maintainer. But first, for the newer people out there, could you please explain the difference between the two?
Maintainers are contributors with merge rights. They are responsible for keeping the software stable, clean, and safe. We are the last door to open before a contributor’s code can be merged into the project (before QA, of course). So I’d say that the main difference is that, as a maintainer, you have much more responsibility… and maybe a bit more stress.
Do you have any advice for contributors who’d like to become maintainers?
First of all, there are about 10 maintainers right now and sometimes we disagree. So to be a maintainer, you need to be patient and open-minded. Being consistent is also important. It’s easier to be a maintainer if you are up-to-date with the software and aware of the latest changes. Also, make sure you don’t become a maintainer for the wrong reasons. I applied because I wanted to work closely with the team and have more impact on decisions. But don’t get me wrong, being a maintainer doesn’t mean that all your suggestions will be merged into the project, nor that your pull requests will be given priority. In the end, it’s really important that you care about the software and the community.
Do you think the PrestaShop project needs more maintainers?
Yes, I think it’s crucial. We need more maintainers. We need people with experience in DevOps, for example, or Docker, and server stuff. I think we could also have maintainers dedicated to documentation, tests, etc. It’s not only about coding. There are a lot of possibilities!
Finally, as we enter a new year, how do you hope to see the PrestaShop project evolve in 2022?
Those are very exciting times for the PrestaShop project, and I’m very much looking forward to seeing the V8. I hope this version will be a new start for PrestaShop. The project has a lot of momentum and I hope that it will continue to grow.
Thank you, Krystian!
In addition to learning more about an iconic figure of the PrestaShop community, this interview provides a better understanding of the role of contributor and maintainer. If Krystian’s experience has inspired you and you want to get more involved in the project, don’t hesitate to contribute… and, if you are a regular, why not apply for a maintainer position?