Re: Radical proposal: no initial list of committers

I like the idea, but isn't the initial list primarily a question for the Secretary. Is the Secretary ok with 1000 additional ICLAs arriving en masse from an even larger project? If so, then I think the solution is much simpler; *Let the podling decide* if it is only Mentors, every user who has

Re: Radical proposal: no initial list of committers

In all honesty: What would I as a mentor do, to get the project rolling? Obvious: Ask the mailing list for an "Initial committer list". So, what's the point? Jochen On Tue, Sep 27, 2016 at 1:25 PM, Greg Stein wrote: > The NetBeans proposal (among many others in the past) has

Re: Radical proposal: no initial list of committers

On Tue, Sep 27, 2016 at 4:39 PM, Bertrand Delacretaz wrote: > On Tue, Sep 27, 2016 at 11:01 PM, Roman Shaposhnik > wrote: > >... Greg's proposal, as far as I can see, is predicated on mentors being > fully > > aware of an increased load... > > And

Re: Radical proposal: no initial list of committers

On Tue, Sep 27, 2016 at 11:01 PM, Roman Shaposhnik wrote: >... Greg's proposal, as far as I can see, is predicated on mentors being fully > aware of an increased load... And as such might be an interesting filter to make sure mentors are actually going to engage. -Bertrand

Re: Radical proposal: no initial list of committers

On Tue, Sep 27, 2016 at 12:22 PM, Geertjan Wielenga wrote: > On Tue, Sep 27, 2016 at 8:56 PM, Roman Shaposhnik wrote: > > >> For example, I'm really curious whether the current cast of NetBeans >> mentors are really aware of the IP review workload that is going

Re: Radical proposal: no initial list of committers

On Tue, Sep 27, 2016 at 8:56 PM, Roman Shaposhnik wrote: > For example, I'm really curious whether the current cast of NetBeans > mentors are really aware of the IP review workload that is going to hit > them > once NetBeans tries to produce its first official Apache Release. In that regard,

Re: Radical proposal: no initial list of committers

On Tue, Sep 27, 2016 at 4:25 AM, Greg Stein wrote: > The NetBeans proposal (among many others in the past) has demonstrated a > significant "problem" with trying to establish an appropriate list of > initial committers. There are many people that want to be on, for various >

Re: Radical proposal: no initial list of committers

On 9/27/16, 8:38 AM, "gch...@gmail.com on behalf of Greg Chase" wrote: >In Apache Geode, we are trying to be liberal about bringing in new >committers. Anyone who shows an interest, and a series of well formatted >pull requests that follow are

Re: Radical proposal: no initial list of committers

On Sep 27, 2016 10:44 AM, "Gregory Chase" wrote: > > Having been through this with Apache Geode, I like the idea of paying > homage to emeritus committers in the proposal and history of the > technology. If you start with a rule of providing committer privileges to > those who

Re: Radical proposal: no initial list of committers

It's a radical proposal - but I think it would only work well where the champion/mentors are also from same community - e.g. the kind of "Already lots of Apache folks" projects that we previously suggested for the straight-to-PLP mode. There's also the danger of the project to seem hostile to

Re: Radical proposal: no initial list of committers

+0.5 I like this idea a lot (but there are governance problems to be solved). I have long been frustrated at folks who jump on the bandwagon and become initial committers then play no further part in the project. Do inactive committers harm the project? No, of course they don’t. But it isn’t

Re: Radical proposal: no initial list of committers

In Apache Geode, we are trying to be liberal about bringing in new committers. Anyone who shows an interest, and a series of well formatted pull requests that follow are code guidelines are pretty quickly nominated to become committers. This would make it very easy for emeritus contributors to

Re: Radical proposal: no initial list of committers

It is an interesting idea. I thought that the initial committers list provided the set of people who could define the merit to approve other new committers. The mentors may not be familiar enough with the technology and people to make the decision with the "Flavor" the community wants. The only

Re: Radical proposal: no initial list of committers

Having been through this with Apache Geode, I like the idea of paying homage to emeritus committers in the proposal and history of the technology. If you start with a rule of providing committer privileges to those who have directly committed to the project in the last two or three years, and a

Re: Radical proposal: no initial list of committers

Le 27/09/16 à 13:25, Greg Stein a écrit : > The NetBeans proposal (among many others in the past) has demonstrated a > significant "problem" with trying to establish an appropriate list of > initial committers. There are many people that want to be on, for various > reasons. Because they are

Re: Radical proposal: no initial list of committers

Its not a bad idea at all, except you're now relying on already stretched too thin mentors to help bootstrap the podling. And since we've agreed that champion can roll off once the podling has been accepted (since they don't have to be a mentor) you're limiting that a bit further. John On Tue,

Re: Radical proposal: no initial list of committers

Considering the effort that went into this and the fact that we had just reached a point where we could move on past this list, I hope you start using this new rule for the next project submitted. Pe marți, 27 septembrie 2016, Greg Stein a scris: > The NetBeans proposal (among

Radical proposal: no initial list of committers

The NetBeans proposal (among many others in the past) has demonstrated a significant "problem" with trying to establish an appropriate list of initial committers. There are many people that want to be on, for various reasons. Because they are committers, recent or historic. Or they want the