-
Notifications
You must be signed in to change notification settings - Fork 42
Description
Prerequisites
- I understand and accept the project's code of conduct.
- I have already searched in existing issues and found no previous report of this bug.
Describe the bug and add attachments
Applicant: Jonathan Danse
GitHub: prestaedit
Scope: Modules (initially), then Core, as I think it's the best to process.
Who I am
I’m Jonathan Danse, better known as PrestaEdit.
I’ve been developing with PrestaShop since 2010 and have been contributing to the project ever since.
I’m also the author of a book on PrestaShop development and a regular speaker at events like the PrestaShop Developer Conference and Friends Of Presta Days.
My contribution history
I've been an active contributor since 2012, with over 600 contributions merged into the core and modules repositories. I'm in the top 3 of the companies involved into contributions, 16 as contibutor (or 41, based on commits contributions).
You can check my full story with PrestaShop on my profile.
Also there.
Why today and how ?
As you all know, PrestaShop (the brand) is now part of another group and I believe in the open source part of this project.
The "how" part will be made on my part time, when I'm available : not much, maybe, but every time with the time to read and analyze the contribution, even if it's one a time.
Steps to reproduce
n/d
Expected behavior
No response
Actual Result
No response
PrestaShop version where the bug happens
Bugs inside PrestaShop ? Maybe, it's why we are here, :)
Module version where the bug happens
Every modules, of course. :D
PHP version(s) where the bug happened
The oldest.
Your company or customer's name goes here (if applicable).
No response