Just to be clear...
A project can have as many committers as makes sense for the
project.
A prospective new committer needs to demonstrate merit in a
transparent manner. This normally takes the form of establishing a
pattern of contributing high-quality patches that get accepted by
the project. The actual number of contributions, and amount of time
varies by project and the nature of the contributions. It's more of
an art than a science.
In the case of a significant code contribution, the contribution
itself is a good demonstration of merit. It is generally accepted
that if a project chooses to pull in a big chunk of code, they must
trust it and--by extension--trust the developers who created it.
This assumes, of course, that the prospective new committers
actually authored the contribution.
HTH
Wayne
On 04/23/2013 01:49 PM, Wayne Beaton
wrote:
I'll go one stronger.
I recommend against accepting significant code contributions
without adding committers.
I'm curious to know if that guidance came from me or any of our
documentation? If so, then I may need to make some revisions.
Wayne
On 04/23/2013 01:33 PM, Ian Skerrett
wrote:
Not
sure who provided the guidance but I would assume Roger
and John would need direct access to support their code
contributions. Therefore, I’d recommend nominating them
as committers.
From:
paho-dev-bounces@xxxxxxxxxxx
[mailto:paho-dev-bounces@xxxxxxxxxxx]
On Behalf Of andypiperuk@xxxxxxxxx
Sent: April-23-13 12:01 PM
To: General development discussions for paho
project
Subject: Re: [paho-dev] New committers for Python
and Objective-C clients
The previous guidance was that
committer elections were limited given the low activity on
the project.
I'm certainly personally happy to
work with both Roger and John to bring changes in to the
repositories, but it would make it easier if they had
direct access to maintain their contributions!
I believe we need to have an election
for a new project leader now that Scott is stepping
aside, and also potentially to bring these new
committers on-board once the CQs are closed (I know the
Python one is tentatively OK aside from the naming
discussions).
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
|
