For the last several months, individuals from all over the world have been able to contribute to the improvement of the PrestaShop software on GitHub. Since our short existence on GitHub, 45 contributors have proposed 62 adjustments, changes and additions that have been included and assisted in improving various versions of PrestaShop. Thank you all for your feedback to help PrestaShop strengthen its position as the best e-commerce solution. PrestaShop can count on GitHub.

Among this group, we would like to acknowledge some that have been predominantly helpful at providing fundamental contributions to the solution:

  1. PrestaEdit : 45 contributions
  2. Damonsk : 9 contributions
  3. Caleydon : 8 contributions
  4. DrySs : 6 contributions
  5. Shagshag : 5 contributions

We would also like to send a big thanks to MrManchot, kluevandrew, prestarocket, doekia… who participate in the evolution of PrestaShop!

Our team had the pleasure of meeting PrestaEdit, our greatest contributor on GitHub. Here’s how it went:

You are the best PrestaShop contributor on Github, how do you feel about that?

When I first heard it, I thought, being labeled as the best does not mean I’m the only one who has contributed. For me, helping PrestaShop isn’t a race where you have to finish at the top, it’s just a positive contribution to the solution. To me every person who participates is a contribution to the solution, no matter the amount.

What motivates you to be active and contribute as much as you do on GitHub?

When I like a project, I invest myself into it. Now it’s almost three years since I discovered PrestaShop and I work on it daily, it’s my specialization.
I discovered a rich solution, which has features that I wanted to help improve. This is why it is useful and necessary to contribute to the solution on GitHub. It allows me to share a correction and then I know that the next store I develop, the correction will be taken into account.

What are the positive and negatives to contributing on GitHub?

In my perspective, the positive is clearly the fact that we share our developments and corrections to a solution that is widely used. With the input of each contributor, we all share each other’s corrections.
In terms of negatives, that’s hard to say. However, if I had to say something it would be the lack of tools to know what to prioritize and focus on.

Do you think PrestaShop contributors on GitHub could offer additional features for PrestaShop and why?

I’m actually sure of it, having done it myself and having seen other contributors bring new features, I’m sure it’s possible.
Of course some suggested features could be available as add-ons, sold by their respective developer so a lot of good ideas for features aren’t shared on GitHub for that reason. With that said, it’s still always nice to know that you contributed to a solution used by so many merchants.

Do you think GitHub provides a real advantage for PrestaShop?

When PrestaShop joined GitHub, the PrestaShop community welcomed the idea to contribute to the solution, including fixing bugs which is a real advantage for PrestaShop.
We are developers of online shops and we are merchants and consumers so sometimes we have a more holistic vision and we see issues that we can easily fix. This way, we allow PrestaShop to focus on developing new tools, fixing larger issues and continuing to improve the software.


Thank you again to contributors who have and continue to contribute. Please do not hesitate to join us on the adventure to enhance our widely used open-source software. We are waiting for you!

Receive articles like this in your inbox!

Subscribe to get the latest ecommerce news and tips sent directly to your email. Subscribe

ShareTweet about this on TwitterShare on Facebook0Share on LinkedIn0Share on Google+0

Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>