[TYPO3-dev] Contribution to community extensions
Dominique Feyer
dfeyer at ttree.ch
Sat Aug 16 17:09:56 CEST 2014
HI Xavier and other,
Just my two cents, two week ago I've done some consulting for a TYPO3 Neos project. This project has been started by developer not currently part of the TYPO3 community. And as Neos is a young boy, they tackle some bugs or strange parts in documentation. They are really open to contribute, but the gerrit wall is was to high. That's not a wall, that's a mountain.
I'm used to Gerrit, but the workflow is to complexe. Many big opensource projet work with github and so many developper are used to the PR workflow. I don't want a Gerrit vs Github discussion. The discussion must be focus on how friendly, as a community, we are to external contribution. Gerrit UI is terrible and the workflow too complexe.
That's a key point for an opensource community. We are alive because we have contributors. So we need to take a lots of care to ease the contribution wall that we have currenty. I speak about Gerrit but also the CLA.
About the CLA why enforcing a CLA for submitting a patch ? When we can per exemple require a CLA is that patch can be merged after review. That's less frustration for the new contributor.
Yes Gerrit is opensource and Github is not ... but is that a real point ?
Contributing to documentation is a important example, where the online edition on github rock a lots. Even for small bugfixe it work nicely. The new issue on github solve a lots of problem.
More information about the TYPO3-dev
mailing list