You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by "Claude Warren, Jr" <cl...@aiven.io.INVALID> on 2022/10/28 07:22:44 UTC
[DISCUSS] new committers - Pekko process
The other discussion has rightly concentrated on how contributions will be
made. I wanted to split out a new conversation about committers.
There are a number of committer requests on the github discussion [1] that
were not included in the original pekko proposal. This conversation
probably should have been closed to new comments a while ago. Is there a
way to close a conversation?
We need a section in the process for electing new committers. I propose
the following section for the process documentation: (the X to be replaced
with the next section number)
X Committers
1. New committers will be nominated on the private mailing list.
2. New committers will be accepted after a 24 hour vote if there are
more positive than negative votes.
3. New committers must demonstrate sustained contribution to the project
in either code, documentation, or community building.
4. Once accepted, committer candidates will be given the opportunity to
reject the committer mantle.
5. Only after the committer accepts will they be added to the committer
list.
Claude
[1] https://github.com/mdedetrich/akka-apache-project/discussions/3
Re: [DISCUSS] new committers - Pekko process
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Claude
Ok my bad, I misunderstood. Sorry about that.
Regards
JB
Le ven. 28 oct. 2022 à 16:46, Claude Warren, Jr
<cl...@aiven.io.invalid> a écrit :
> This is not about the Pekko Incubation proposal which was already accepted
> but about the process proposal:
> https://cwiki.apache.org/confluence/display/PEKKO/Processes
>
> Looking back I can see how this was confusing.
>
>
> On Fri, Oct 28, 2022 at 1:47 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi,
> >
> > I don't think the discussion should be in the proposal. The proposal
> > is really about the project (defintion, objectives, community), not
> > development process on its own as each project decides, assuming
> > following basic Apache rules.
> >
> > Committer-ship (and PPMC) is basically well described at Apache
> > (Justin already shared the link afair).
> >
> > We will find a consensus/balance between Apache rules and willing from
> > Pekko community. Clearly, Pekko seems to be already a mature project
> > with existing rules. So, with slight adjustment, we will have
> > something.
> >
> > Now, I'm more a little concerned about the way too long discussion.
> > For instance, the discussion between Commit-Then-Review or
> > Review-Then-Commit is required betweens committers, but doesn't impact
> > the incubation process.
> >
> > Using existing projects as template is not super interesting because
> > each project is unique somehow.
> > Let's be pragmatic and move forward on the code push adjusted with
> > Apache requirements. Then, step by step we can adjust.
> >
> > Too much information kills the information :)
> >
> > Regards
> > JB
> >
> > On Fri, Oct 28, 2022 at 9:22 AM Claude Warren, Jr
> > <cl...@aiven.io.invalid> wrote:
> > >
> > > The other discussion has rightly concentrated on how contributions will
> > be
> > > made. I wanted to split out a new conversation about committers.
> > >
> > > There are a number of committer requests on the github discussion [1]
> > that
> > > were not included in the original pekko proposal. This conversation
> > > probably should have been closed to new comments a while ago. Is
> there a
> > > way to close a conversation?
> > >
> > > We need a section in the process for electing new committers. I
> propose
> > > the following section for the process documentation: (the X to be
> > replaced
> > > with the next section number)
> > >
> > > X Committers
> > >
> > > 1. New committers will be nominated on the private mailing list.
> > > 2. New committers will be accepted after a 24 hour vote if there are
> > > more positive than negative votes.
> > > 3. New committers must demonstrate sustained contribution to the
> > project
> > > in either code, documentation, or community building.
> > > 4. Once accepted, committer candidates will be given the opportunity
> > to
> > > reject the committer mantle.
> > > 5. Only after the committer accepts will they be added to the
> > committer
> > > list.
> > >
> > > Claude
> > >
> > > [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
Re: [DISCUSS] new committers - Pekko process
Posted by "Claude Warren, Jr" <cl...@aiven.io.INVALID>.
This is not about the Pekko Incubation proposal which was already accepted
but about the process proposal:
https://cwiki.apache.org/confluence/display/PEKKO/Processes
Looking back I can see how this was confusing.
On Fri, Oct 28, 2022 at 1:47 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi,
>
> I don't think the discussion should be in the proposal. The proposal
> is really about the project (defintion, objectives, community), not
> development process on its own as each project decides, assuming
> following basic Apache rules.
>
> Committer-ship (and PPMC) is basically well described at Apache
> (Justin already shared the link afair).
>
> We will find a consensus/balance between Apache rules and willing from
> Pekko community. Clearly, Pekko seems to be already a mature project
> with existing rules. So, with slight adjustment, we will have
> something.
>
> Now, I'm more a little concerned about the way too long discussion.
> For instance, the discussion between Commit-Then-Review or
> Review-Then-Commit is required betweens committers, but doesn't impact
> the incubation process.
>
> Using existing projects as template is not super interesting because
> each project is unique somehow.
> Let's be pragmatic and move forward on the code push adjusted with
> Apache requirements. Then, step by step we can adjust.
>
> Too much information kills the information :)
>
> Regards
> JB
>
> On Fri, Oct 28, 2022 at 9:22 AM Claude Warren, Jr
> <cl...@aiven.io.invalid> wrote:
> >
> > The other discussion has rightly concentrated on how contributions will
> be
> > made. I wanted to split out a new conversation about committers.
> >
> > There are a number of committer requests on the github discussion [1]
> that
> > were not included in the original pekko proposal. This conversation
> > probably should have been closed to new comments a while ago. Is there a
> > way to close a conversation?
> >
> > We need a section in the process for electing new committers. I propose
> > the following section for the process documentation: (the X to be
> replaced
> > with the next section number)
> >
> > X Committers
> >
> > 1. New committers will be nominated on the private mailing list.
> > 2. New committers will be accepted after a 24 hour vote if there are
> > more positive than negative votes.
> > 3. New committers must demonstrate sustained contribution to the
> project
> > in either code, documentation, or community building.
> > 4. Once accepted, committer candidates will be given the opportunity
> to
> > reject the committer mantle.
> > 5. Only after the committer accepts will they be added to the
> committer
> > list.
> >
> > Claude
> >
> > [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [DISCUSS] new committers - Pekko process
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
I don't think the discussion should be in the proposal. The proposal
is really about the project (defintion, objectives, community), not
development process on its own as each project decides, assuming
following basic Apache rules.
Committer-ship (and PPMC) is basically well described at Apache
(Justin already shared the link afair).
We will find a consensus/balance between Apache rules and willing from
Pekko community. Clearly, Pekko seems to be already a mature project
with existing rules. So, with slight adjustment, we will have
something.
Now, I'm more a little concerned about the way too long discussion.
For instance, the discussion between Commit-Then-Review or
Review-Then-Commit is required betweens committers, but doesn't impact
the incubation process.
Using existing projects as template is not super interesting because
each project is unique somehow.
Let's be pragmatic and move forward on the code push adjusted with
Apache requirements. Then, step by step we can adjust.
Too much information kills the information :)
Regards
JB
On Fri, Oct 28, 2022 at 9:22 AM Claude Warren, Jr
<cl...@aiven.io.invalid> wrote:
>
> The other discussion has rightly concentrated on how contributions will be
> made. I wanted to split out a new conversation about committers.
>
> There are a number of committer requests on the github discussion [1] that
> were not included in the original pekko proposal. This conversation
> probably should have been closed to new comments a while ago. Is there a
> way to close a conversation?
>
> We need a section in the process for electing new committers. I propose
> the following section for the process documentation: (the X to be replaced
> with the next section number)
>
> X Committers
>
> 1. New committers will be nominated on the private mailing list.
> 2. New committers will be accepted after a 24 hour vote if there are
> more positive than negative votes.
> 3. New committers must demonstrate sustained contribution to the project
> in either code, documentation, or community building.
> 4. Once accepted, committer candidates will be given the opportunity to
> reject the committer mantle.
> 5. Only after the committer accepts will they be added to the committer
> list.
>
> Claude
>
> [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] new committers - Pekko process
Posted by Josep Prat <jo...@prat.tech>.
Hi all,
I like the proposal. Good point on the GitHub discussion Fanning!
Best,
On October 28, 2022 6:33:47 PM GMT+02:00, PJ Fanning <fa...@apache.org> wrote:
>I think this is a reasonable place to start.
>
>We'll need to come up a diplomatic message to put on the Github discussion calling for new committers that explains the path to becoming a committer - and that highlights that contributions (issues, PRs, input to discussions, etc.) are welcome from everyone.
>
>On 2022/10/28 08:19:44 "Claude Warren, Jr" wrote:
>> I'd like to change my proposal to read 72 hours so it is now.
>>
>>
>> X Committers
>>
>> 1. New committers will be nominated on the private mailing list.
>> 2. New committers will be accepted after a 72 hour vote if there are
>> more positive than negative votes.
>> 3. New committers must demonstrate sustained contribution to the project
>> in either code, documentation, or community building.
>> 4. Once accepted, committer candidates will be given the opportunity to
>> reject the committer mantle.
>> 5. Only after the committer accepts will they be added to the committer
>> list.
>>
>>
>>
>> On Fri, Oct 28, 2022 at 9:15 AM Justin Mclean <ju...@classsoftware.com>
>> wrote:
>>
>> > Hi,
>> >
>> > In general votes should be open for a minimum of 72 hours to be allow
>> > people in different timezones and different involvement to take part. This
>> > however is just a guideline.
>> >
>> > Kind Regards,
>> > Justin
>> >
>> > On Fri, 28 Oct 2022, 6:23 pm Claude Warren, Jr,
>> > <cl...@aiven.io.invalid> wrote:
>> >
>> > > The other discussion has rightly concentrated on how contributions will
>> > be
>> > > made. I wanted to split out a new conversation about committers.
>> > >
>> > > There are a number of committer requests on the github discussion [1]
>> > that
>> > > were not included in the original pekko proposal. This conversation
>> > > probably should have been closed to new comments a while ago. Is there a
>> > > way to close a conversation?
>> > >
>> > > We need a section in the process for electing new committers. I propose
>> > > the following section for the process documentation: (the X to be
>> > replaced
>> > > with the next section number)
>> > >
>> > > X Committers
>> > >
>> > > 1. New committers will be nominated on the private mailing list.
>> > > 2. New committers will be accepted after a 24 hour vote if there are
>> > > more positive than negative votes.
>> > > 3. New committers must demonstrate sustained contribution to the
>> > project
>> > > in either code, documentation, or community building.
>> > > 4. Once accepted, committer candidates will be given the opportunity
>> > to
>> > > reject the committer mantle.
>> > > 5. Only after the committer accepts will they be added to the
>> > committer
>> > > list.
>> > >
>> > > Claude
>> > >
>> > > [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
>> > >
>> >
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>For additional commands, e-mail: dev-help@pekko.apache.org
>
Re: [DISCUSS] new committers - Pekko process
Posted by PJ Fanning <fa...@apache.org>.
I think this is a reasonable place to start.
We'll need to come up a diplomatic message to put on the Github discussion calling for new committers that explains the path to becoming a committer - and that highlights that contributions (issues, PRs, input to discussions, etc.) are welcome from everyone.
On 2022/10/28 08:19:44 "Claude Warren, Jr" wrote:
> I'd like to change my proposal to read 72 hours so it is now.
>
>
> X Committers
>
> 1. New committers will be nominated on the private mailing list.
> 2. New committers will be accepted after a 72 hour vote if there are
> more positive than negative votes.
> 3. New committers must demonstrate sustained contribution to the project
> in either code, documentation, or community building.
> 4. Once accepted, committer candidates will be given the opportunity to
> reject the committer mantle.
> 5. Only after the committer accepts will they be added to the committer
> list.
>
>
>
> On Fri, Oct 28, 2022 at 9:15 AM Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > In general votes should be open for a minimum of 72 hours to be allow
> > people in different timezones and different involvement to take part. This
> > however is just a guideline.
> >
> > Kind Regards,
> > Justin
> >
> > On Fri, 28 Oct 2022, 6:23 pm Claude Warren, Jr,
> > <cl...@aiven.io.invalid> wrote:
> >
> > > The other discussion has rightly concentrated on how contributions will
> > be
> > > made. I wanted to split out a new conversation about committers.
> > >
> > > There are a number of committer requests on the github discussion [1]
> > that
> > > were not included in the original pekko proposal. This conversation
> > > probably should have been closed to new comments a while ago. Is there a
> > > way to close a conversation?
> > >
> > > We need a section in the process for electing new committers. I propose
> > > the following section for the process documentation: (the X to be
> > replaced
> > > with the next section number)
> > >
> > > X Committers
> > >
> > > 1. New committers will be nominated on the private mailing list.
> > > 2. New committers will be accepted after a 24 hour vote if there are
> > > more positive than negative votes.
> > > 3. New committers must demonstrate sustained contribution to the
> > project
> > > in either code, documentation, or community building.
> > > 4. Once accepted, committer candidates will be given the opportunity
> > to
> > > reject the committer mantle.
> > > 5. Only after the committer accepts will they be added to the
> > committer
> > > list.
> > >
> > > Claude
> > >
> > > [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] new committers - Pekko process
Posted by "Claude Warren, Jr" <cl...@aiven.io.INVALID>.
I'd like to change my proposal to read 72 hours so it is now.
X Committers
1. New committers will be nominated on the private mailing list.
2. New committers will be accepted after a 72 hour vote if there are
more positive than negative votes.
3. New committers must demonstrate sustained contribution to the project
in either code, documentation, or community building.
4. Once accepted, committer candidates will be given the opportunity to
reject the committer mantle.
5. Only after the committer accepts will they be added to the committer
list.
On Fri, Oct 28, 2022 at 9:15 AM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> In general votes should be open for a minimum of 72 hours to be allow
> people in different timezones and different involvement to take part. This
> however is just a guideline.
>
> Kind Regards,
> Justin
>
> On Fri, 28 Oct 2022, 6:23 pm Claude Warren, Jr,
> <cl...@aiven.io.invalid> wrote:
>
> > The other discussion has rightly concentrated on how contributions will
> be
> > made. I wanted to split out a new conversation about committers.
> >
> > There are a number of committer requests on the github discussion [1]
> that
> > were not included in the original pekko proposal. This conversation
> > probably should have been closed to new comments a while ago. Is there a
> > way to close a conversation?
> >
> > We need a section in the process for electing new committers. I propose
> > the following section for the process documentation: (the X to be
> replaced
> > with the next section number)
> >
> > X Committers
> >
> > 1. New committers will be nominated on the private mailing list.
> > 2. New committers will be accepted after a 24 hour vote if there are
> > more positive than negative votes.
> > 3. New committers must demonstrate sustained contribution to the
> project
> > in either code, documentation, or community building.
> > 4. Once accepted, committer candidates will be given the opportunity
> to
> > reject the committer mantle.
> > 5. Only after the committer accepts will they be added to the
> committer
> > list.
> >
> > Claude
> >
> > [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
> >
>
Re: [DISCUSS] new committers - Pekko process
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
In general votes should be open for a minimum of 72 hours to be allow
people in different timezones and different involvement to take part. This
however is just a guideline.
Kind Regards,
Justin
On Fri, 28 Oct 2022, 6:23 pm Claude Warren, Jr,
<cl...@aiven.io.invalid> wrote:
> The other discussion has rightly concentrated on how contributions will be
> made. I wanted to split out a new conversation about committers.
>
> There are a number of committer requests on the github discussion [1] that
> were not included in the original pekko proposal. This conversation
> probably should have been closed to new comments a while ago. Is there a
> way to close a conversation?
>
> We need a section in the process for electing new committers. I propose
> the following section for the process documentation: (the X to be replaced
> with the next section number)
>
> X Committers
>
> 1. New committers will be nominated on the private mailing list.
> 2. New committers will be accepted after a 24 hour vote if there are
> more positive than negative votes.
> 3. New committers must demonstrate sustained contribution to the project
> in either code, documentation, or community building.
> 4. Once accepted, committer candidates will be given the opportunity to
> reject the committer mantle.
> 5. Only after the committer accepts will they be added to the committer
> list.
>
> Claude
>
> [1] https://github.com/mdedetrich/akka-apache-project/discussions/3
>