Garrett Rooney wrote:
On 3/15/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
Do these really have to be "Apache" credits accumulated? Let's do a
hypothetical situation. Let's say that some guy puts in a few years of
his life into a CodeHaus project. Then, he has a kid. At that time the
project moves to ASF and he's MIA. Is it fair that he doesn't get
commit karma when it graduates? IMO, no, it is not fair. Is it fair
that he does not make it into the project PMC? Yes, it is fair, IMO.
Not providing commit karma seems to be a bit like forced retirement
because of inactivity. Something that ASF frowns upon.
Let's do another scenario. Someone works very long and hard on one
component of the project. That component becomes very mature and rock
solid so, we really don't hear from him very often. Is it fair that he
doesn't get commit karma when it graduates? IMO, no, it is not fair.
Is it fair that he does not make it into the project PMC? Yes, it is
fair, IMO.
Not providing commit karma seems to be a bit like forced retirement
because he completed the task that he set out to do.
I agree with Alan that it is only fair that significant contributions
prior to incubation should be recognized.
IMO, only active participants during incubation should be invited to an
existing project's PMC when graduating.
For those that are offered commit access it should be explained that
commit access is a privilege, not a right and they should be pointed to
the community rules.
I like Ken's words on the "commit access is a privilege, not a right"
topic in the last two paragraphs of the following mail in 2002:
http://marc2.theaimsgroup.com/?l=incubator-general&m=104217311311925&w=4
What do we have to lose giving past contributors commit access
considering the ability to veto commits or as a last resort have their
commit access suspended or revoked if they don't respect the
community/rules?
I agree that keeping the barrier low to past contributors as Garrett
says below is beneficial to the project.
John
This isn't from an ASF project, but I think it's relevant. In the
subversion project we've got a number of people who have full commit
access, something around 30 at this point. Not all of them are active
at any given time (heck, most of them aren't active at any given time
for that matter), but having them out there with commit rights is
still valuable, because it means the barrier is lowered for that day
somewhere down the road when they find some bug, dig into the code and
fix it, and want to commit the patch. Making it more difficult for
experienced developers to come back to the project and contribute
seems like a bad thing to me.
Now on the other hand there's the argument that if they come back some
day and express interest in committing something we could set them up
with commit access then, but let's be fair, getting all the paperwork
settled takes time, and if they want to do that now and make it that
much easier when they do find the time for the project, what's the
real harm? If the community around the project has truly learned how
to work in the way apache projects tend to work, I'm sure they'll be
able to teach these dormant committers what they need to know on the
fly as they come back.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
