A few days ago I posted a link to a very tiny survey on source control I made to prepare myself for the eZ Systems Developer Conference in Barcelona in two weeks.
Until now, 28 people took the survey. The unscientific results are:
- The second most used and preferred VCS after SVN is GIT.
- 13 of 28 participants declare to use feature branches with SVN. This number is quite higher then I expected given the pain involved with branching in SVN.
- 16 people declare to use a patched version of eZ Publish.
Some choosen responses from the free text field: Would you like to get more involved in the development of eZ Publish? Is there anything that holds you back from getting more involved?
- Funding
- Source code access, eZ is not seen as a Community development project. It is eZ who decides the direction & completes the work.
- Ez systems being less and less willing to accept anything from the community.
- not any more

- Missing a cleary community focused process (comparing to typo3)
- long process of approval of patches
- I can't ever see eZ allowing community development of the core product, but the use of GIT would allow much better patching options.
Some of the above statements are rather pessimistic in regard to community involvment in eZ Publish development. However I'd like to point out some more optimistic personal views on this topic:
- eZ Systems manages to keep the quality of it's products very high, compared to other PHP products. This of course has the drawback of high barriers for involvement.
- Good tools for patch review workflows start to appear only since some months.
- The eZ Components project is a model for open decision making and documentation.
The survey data:
gitforez.ods,
gitforez.csv
BTW.: Want to enter yourself in the participants list of the Barcelona conference on
upcoming?