The bugtracker and git
From LimeSurvey Manual
This article should help developers on the LimeSurvey when resolving issues.
General process outline.
1. Bug reported by user.
2. Bug assigned to developer (by the developer himself or someone else)
3. Bug fixed in fork on github.com (each developer has his own fork?)
4. Pull request generated on github.com
5. Issue assigned to LimeSurvey repository owner (c_schmitz), status set to resolved.
6. Pull request fulfilled and bug status set to closed (done by c_schmitz)
This method of working should allow for efficient bug fixing with multiple developers without getting c_schmitz overworked..?
Please respond on what you think of this process, or what should be changed.