Todd Lipcon wrote:
As for the community impact of SVN vs git, I find as a contributor (not committer) that git opens things up substantially for me. I am essentially on the same playing field as the committers when it comes to new feature development
On every Apache project that I'm involved with (all RTC) committers and contributors follow exactly the same procedures: patches are submitted, reviewed and committed. A project that does not provide a level playing field for contributors and committers is not a healthy community. One of Lucene's most prolific contributors is (by choice) not a committer. Becoming a committer should not grant privileges, but rather add responsibilities.
My assumption is that the long-running-patch-series type projects (e.g. C bindings, new Erlang bindings, Ruby rewrite, etc) are primarily undertaken by a group of core developers who have no problem learning to use and using git. The majority of contributions from non-core contributors are more likely to be the one-diff JIRA submissions.
Things are often not so clear cut. I have seen many major changes instigated by non-committers.
Doug
