Posted by drak
on Friday, April 22, 2011 (2157 reads)
A few months ago, the core development team made a group decision which changes the dynamics of Zikula development to create a more open and community friendly development process. Until now, the title core developers were meant someone with commit access to our source repositories. This is a historical fact born from having used Subversion for source control.
Traditionally, projects that use centralised permission based source control like Subversion or CVS, if you want to contribute you either have to make manual patches or request commit access to the source control repository. Both of these ways are barriers because manual patches are slow to verify, and to get commit access usually requires a great deal of trust which has to be earned. Not only that, commit access is usually reserved for those who make a commitment to the project. This makes casual participation difficult.
Now that we use GIT source control we thought it was time to really take advantage of the open and collaborative qualities GIT brings to us by adopting the "contributor/collaborator workflow".