incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Newcomer, Eric" <>
Subject RE: Policy on Initial Committership
Date Tue, 03 Oct 2006 14:08:39 GMT
Dan -

As you have no doubt seen by now the issue is not how to contribute to
an open source project, since as you said there are indeed many ways to
accomplish that.  

The issue is whether or not to carry out the agreement implicit in the
approval of a project, including the list of initial committers.  I
believe we have consensus on this point, meaning that the list of
initial committers for CXF stands as originally included in the project

Mark and Kevin were justifiably confused and concerned when they tried
to confirm the status they believed they had as initial committers.  

Can we please now ensure this is fixed for them and anyone else who may
have been questioned during the process, for whatever good reasons?  

As we have also seen in the discussions on this topic it is natural for
a project to review and revise the committers list as it progresses.
But let's at least get CXF off to a good start!



-----Original Message-----
From: Kulp, John Daniel 
Sent: Monday, October 02, 2006 11:31 AM
Subject: Re: Policy on Initial Committership

On Monday October 02 2006 10:54 am, Newcomer, Eric wrote:
> How could they contribute when they were not given access? 

The same way any non-commiter contributor contributes to a project:

1) JIRA - creating JIRA items, submitting patches, etc... I admit, the
JIRA was not setup to allow patches to be attached for the first couple 
weeks.   Once that was discovered, we did get it fixed as quickly as
and it's been ok for several weeks now.  (One note: I did send a request
for JIRA ids to be added so I could create a master list for
rather than bombard them with "one at a time" requests.  I didn't get a 
response from everyone, although I don't know if Jason or the other
did get a response.)

2) Dev lists - participate in discussions, start discussions with new
ask questions, etc...

3) Wiki - help out with the wiki if the wiki is publicly editable.    If
definitely try to document ideas and findings in some form or another so
can be added to the wiki.

All three of those are very valuable contributions to a project, but
don't require commit access (other than maybe the wiki depending on how 
that's setup).   All three are generally how someone earns commit



> These guys 
> have been asking for two weeks or more to be allowed to contribute,
> in some cases did not even receive a reply.
> Eric
> -----Original Message-----
> From: Kulp, John Daniel
> Sent: Sunday, October 01, 2006 4:17 PM
> To:
> Cc: Justin Erenkrantz
> Subject: Re: Policy on Initial Committership
> Justin,
> On Sunday October 01 2006 3:22 pm, Justin Erenkrantz wrote:
> > We've seen an example of this with Celtixfire.  So far, we're
> for
> > an explanation (as those discussions did not occur in a place where
> the
> > Incubator PMC could provide any oversight), but the aggrieved
> > believe they have been barred access to a project they felt they
> > contributed to.
> That's not it.   The issue is they have been barred access to a
> they
> have only expressed interest in contributed to.   They have not yet
> contributed anything (no code, no patches, little to no communication
> the
> dev list, etc...).   That is why the CXF mentors decided it was
> in-appropriate to give them commit access.   There name was on the
> initial
> proposal, but after two months, there was still no contributions.
> individuals are basically stating that since there name was on the
> proposal,
> that is enough to get the commit rights.
> Basically, Jason and the other mentors thought the initial commiters
> should
> actually be those who contribute/commit stuff.   Those who don't meet
> that
> barrier haven't earned the commit rights, so why should they have
> rights?

J. Daniel Kulp
Principal Engineer
P: 781-902-8727    C: 508-380-7194   F:781-902-8001

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message