I'm one of the developers on the Subversion project that has full commit rights
and I'm thinking that to help portions of Rails move a little faster, say in the
database adapters, that the core Rails team look at offering partial commit
rights to people for small portions of the code base. This would be a half-way
step between no access and somebody who clearly understands the direction and
the entire code base.
Our current list is in svn at:
http://svn.collab.net/repos/svn/trunk/COMMITTERS
It would be nice if the people like Michael Schoen who have shown a commitment
to the Oracle bindings could work on that portion without the overhead of a full
time committer reviewing each commit, as long as only that file or file(s) is
modified.
On the Subversion team, we have a private mailing list to discuss invitations
and other issues (which is not archived if somebody does become a full committer
later on, so they can't see the discussion that took place around them.)
We don't actually enforce the protections on the partial committers via an
authorization method, as people are pretty good not to do commits where they
were not offered commit access, and an email and a svn reverse merge is enough
to undo a change.
Finally, we have the "obvious fix" rule:
"Any committer, whether full or partial, may commit fixes for obvious typos,
grammar mistakes, and formatting problems wherever they may be — in the web
pages, API documentation, code comments, commit messages, etc. We rely on the
committers judgement to determine what is "obvious"; if you're not sure, just ask."
http://subversion.tigris.org/hacking.html
Some ideas to consider.
Regards,
Blair
--
Blair Zajac, Ph.D.
<[EMAIL PROTECTED]>
Subversion training, consulting and support
http://www.orcaware.com/svn/
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
