On Nov 18, 2007 12:46 AM, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...Here's an attempt to summarize our recent discussions, and suggest
some actions. Comments are welcome, of course
Just want to note that I have not forgotten about these discussions,
just didn't have time yet to
On Nov 23, 2007, at 3:10 AM, ant elder wrote:
Ask people to self nominate - I imagine often inactive commiters
won't
put themselves forward, removing any issue. Then maybe a review of
the
list by the the mentors and proposed PMC Chair. If there are issues
it
can be discussed in the
On Nov 22, 2007 7:09 PM, Niall Pemberton [EMAIL PROTECTED] wrote:
On Nov 20, 2007 9:14 PM, Eelco Hillenius [EMAIL PROTECTED]
wrote:
I would agree with reviewing committers at graduation, but how do we
implement that?
I would say that this depends on the judgment of the mentors, and it
On Nov 23, 2007 9:10 AM, ant elder [EMAIL PROTECTED] wrote:
On Nov 22, 2007 7:09 PM, Niall Pemberton [EMAIL PROTECTED] wrote:
Ask people to self nominate
That sounds reasonable but is it ok to do that? Its quite hard to remove a
committer from a real Apache project, are incubating
On Nov 20, 2007 9:14 PM, Eelco Hillenius [EMAIL PROTECTED] wrote:
I would agree with reviewing committers at graduation, but how do we
implement that?
I would say that this depends on the judgment of the mentors, and it
is probably more important to evaluate the role they would be playing
Ask people to self nominate - I imagine often inactive commiters won't
put themselves forward, removing any issue. Then maybe a review of the
list by the the mentors and proposed PMC Chair. If there are issues it
can be discussed in the community and if theres disagreement then
vote. I
Btw would people have interest in a small script that would analyze a
given
project history and give stats on commits and who committed? I've built
something similar for infra [1] and such reports could be useful to the
IPMC
when a podling starts talking about graduation. I'm not sure how
On Nov 22, 2007 8:09 PM, Niall Pemberton [EMAIL PROTECTED] wrote:
...Or re-elect all committers before graduation?...
...Ask people to self nominate...
Good idea, that's probably the easiest way of addressing that concern.
-Bertrand
On Nov 19, 2007 8:05 PM, Craig L Russell [EMAIL PROTECTED] wrote:
...Some of the discussion here to me seems to be backward: adding
constraints to the entry of a podling to the incubator...
Agreed, we shouldn't add more constraints than needed.
...A couple of additional comments below...
I would agree with reviewing committers at graduation, but how do we
implement that?
I would say that this depends on the judgment of the mentors, and it
is probably more important to evaluate the role they would be playing
in the project once it is over to Apache, than what happened before
On Nov 18, 2007 12:45 PM, Martijn Dashorst [EMAIL PROTECTED] wrote:
On Nov 18, 2007 12:46 AM, Bertrand Delacretaz [EMAIL PROTECTED]
wrote:
3) Limit the number of new non-ASF initial committers for incubating
projects...
...I think this throws a too wide a net. Wicket would not be an
On 11/19/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
I like the idea: discuss initial diversity among the Incubator PMC,
when a new project comes in, with the option of limiting the number of
initial non-ASF committers. But no hard rules on that.
This might be easier to implement than
Hi,
On Nov 18, 2007 1:46 AM, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
3) Limit the number of new non-ASF initial committers for incubating projects
People who were not ASF committers but come in via a newly incubating
project do not get their commit rights via the normal ASF meritocracy
Same here. I think a good way to address the short way to committership
problem is to make sure people really committed consistently during the
lifetime of the poddling when the project effectively graduates.
There's something to say for that, though I think you should take
activity on the
On Nov 19, 2007 10:23 AM, Eelco Hillenius [EMAIL PROTECTED] wrote:
Same here. I think a good way to address the short way to
committership
problem is to make sure people really committed consistently during the
lifetime of the poddling when the project effectively graduates.
There's
Hi,
Some of the discussion here to me seems to be backward: adding
constraints to the entry of a podling to the incubator.
I'd hope that we could get podlings, including all of their current
community, into the incubator and then actively mentor/monitor its
activities to promote
Craig L Russell wrote:
Some of the discussion here to me seems to be backward: adding
constraints to the entry of a podling to the incubator.
I'd hope that we could get podlings, including all of their current
community, into the incubator and then actively mentor/monitor its
activities to
On Nov 18, 2007 12:46 AM, Bertrand Delacretaz [EMAIL PROTECTED]
wrote:
3) Limit the number of new non-ASF initial committers for incubating
projects
People who were not ASF committers but come in via a newly incubating
project do not get their commit rights via the normal ASF meritocracy
Hi,
Here's an attempt to summarize our recent discussions, and suggest
some actions. Comments are welcome, of course.
1) We need better tools for Incubator PMC members to measure the
community diversity of incubating projects, especially before
graduation.
Suggestion:
-Require a community
3) Limit the number of new non-ASF initial committers for incubating projects
People who were not ASF committers but come in via a newly incubating
project do not get their commit rights via the normal ASF meritocracy
rules.
We might want to limit the number of such commiters, to limit the
@incubator.apache.org
To
general@incubator.apache.org
cc
Subject
Re: [DISCUSS] Community diversity: current concerns and suggestions for
improvement
3) Limit the number of new non-ASF initial committers for incubating
projects
People who were not ASF committers but come in via a newly
21 matches
Mail list logo
