Tiki is the Free/Libre/Open Source Software Web Application with the most contributors with direct commit access to the whole code base.
Tiki has over 500: http://info.tiki.org/article188-Tiki-reaches-500-contributors-with-commit-access
The second place seems to be Plone, with 450 core contributors (but do they all have commit access to the core and whole code base?)
Some other projects have overall more committers if you count extensions, but they are not direct committers to the core. For example, in Drupal, there are core maintainers, who approve the commits.
Why is direct commit access important?
Direct access to the whole code base is important because it makes it easier to refactor the code and not be limited to what the core provides (say you are developing an extension and can't modify the core code)
While the idea of each commit (code contribution) being reviewed is appealing, you need a lot of active reviewers and it adds complexity and delays. In large projects, you end up with hundreds or thousands of yet-to-be-accepted commits. And because these unaccepted commits can be in a queue for several weeks or months, they can, at one point become invalid because another commit breaks them.
But no gatekeeper doesn't mean there is no review. Since
We want the "The Simplest Thing that Could Possibly Work" and avoid this dependency-hell between unapproved commits. Besides, since the vast majority of commits are just fine, reviewing each commit is taking resources away from regular development. We do feel however that it's worth it to have code review by the Quality Team during the Quality and Security phases of our LTS versions, as per our version lifecycle.
1) |
15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
2) |
19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
3) |
Tiki birthday |
4) |
17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
5) |
21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
6) |
19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting |