On 10/10/11 - 05:35:36PM, Matt Wagner wrote:
Hi all,
After a bit of discussion this morning, we decided to consolidate
permissions for commit access on GitHub across our projects. I think
this was a great decision, because it makes management easier,
recognizes that many contributors contribute to multiple projects, and
makes us feel more like an integrated family of projects.
However, as I've been going through adding existing contributors that
were overlooked earlier in the day, I'm starting to wonder what our
policy is on handing out commit access. It was never terribly clear to
me, at least for Conductor. Now that it affects multiple projects, I
think we should develop a concrete policy. (Once we do so, I'll document
it somewhere.)
For the sake of getting the conversation moving, here is what I propose:
We grant commit access to anyone who has (a) sent at least one patch
that has passed on-list code review, or (b) is vouched for by an
existing contributor. If someone has met (a) or (b), any of the existing
project admins can add them without further input.
My thinking with the above is that:
a.) Having more people with commit rights is a good thing.
b.) The policy above is simple. There's no nomination process that will
drag on on the mailing lists, and no, "So-and-so is out of the office so
we have to wait until next week for them to vote" nonsense.
c.) It's not as if we have had problems with accidentally permitted
crazed lunatics to contribute code, or that we're trying to change an
onerous process that scares away contributors. It's just that as I get
asked to add people to the project, I want to make sure I'm acting on
behalf of the community.
Yeah, agreed. You can always revoke access to crazy lunatics later :).
--
Chris Lalancette