You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@corinthia.apache.org by jan i <ja...@apache.org> on 2014/12/19 17:57:52 UTC
[DISCUSS] committers == PPMC
Hi.
*Preamble:*
Sorry about the fuzz, but we have to do things right, and I started this
discussion from a wrong perspective.
In my opinion it is the community as a whole who decide (within the limits
of the bylaws) how our PPMC shall operate, therefore this discussion is an
open discussion.
As initial committers we are all PPMC, so this discussion is solely about
new people coming to the project.
*Discussion starting point:*
For a small project like ours, there are no logical reason to make a
difference between being committer and PPMC. I believe it can be directly
harmful to the project.
Example (another project): In budapest we were 6 people gathered around a
table discussion the future of the project. 3 PMC, 1 committer (but ASF
member) and 2 committers.....We had to stop the discussion several times,
due to the fact "oooh this happened on the private list", I still wonder
how the 2 committers felt...I know I would have felt being held out.
What is the downside of this rule, with time we might get a big PMC (after
graduation) and lots of discussions, some see this as negative, I see it as
healthy...Apache is not about a few ruling the project, but the whole
community doing it together.
I must emphasize, I am NOT suggesting to bend or change any voting rules
but simply to implement a procedure !!
My suggestion is, that we as community, ask the PPMC to always vote if a
candidate should be PPMC+committer using the strictest voting rules (right
now 3 PPMC +1 and no -1).
The invitation letter, should be an invitation to join both as committer
and PPMC, but give an option so the candidate can choose only to be a
committer.
If we want this, it can be implemented in 2 ways:
1) A convention, where we simply ask the PPMC to always do it like this
- here a vote is not really needed, because the PPMC can decide to follow
it or not.
2) A Rule, where the PPMC have to do it.
- here a vote is really needed (and one with a clear majority and NONE
against it).
Thoughts ?
rgds
jan i.
Re: [DISCUSS] committers == PPMC
Posted by jan i <ja...@apache.org>.
On 22 December 2014 at 17:56, Dennis E. Hamilton <de...@acm.org>
wrote:
> +1
>
> -- in reply to --
> From: jan i [mailto:jani@apache.org]
> Sent: Monday, December 22, 2014 06:55
> To: dev@corinthia.incubator.apache.org
> Subject: Re: [DISCUSS] committers == PPMC
>
> Hi.
>
> I hope we have turned all the stones we want to turn in this discussion.
>
> It seems we agree to do it while we are small and in incubator, but it
> needs to discussed again once we graduate to TLP.
>
> Based on the above, I expect the PPMC to use the guideline PPMC==committers
> until we graduate. Doing this means we dont need to vote.
>
> <orcnote>
> I have to think what it means about "don't need to vote."
> I take it that "by lazy consensus the PPMC is going to
> employ PPMC == committers until graduation."
> </orcnote>
>
It does not mean "lazy consensus" for me since that implies we have had a
vote. To me It means that the PPMC can in each single case choose what it
want to do, but the community recommend (the community cannot demand)
PPMC==Committer or otherwise formulated, it is the individual proposer, who
decides how to call the vote knowing this discussion.
rgds
jan i.
>
> rgds
> jan I.
>
>
> [ ... ]
>
>
RE: [DISCUSS] committers == PPMC
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1
-- in reply to --
From: jan i [mailto:jani@apache.org]
Sent: Monday, December 22, 2014 06:55
To: dev@corinthia.incubator.apache.org
Subject: Re: [DISCUSS] committers == PPMC
Hi.
I hope we have turned all the stones we want to turn in this discussion.
It seems we agree to do it while we are small and in incubator, but it
needs to discussed again once we graduate to TLP.
Based on the above, I expect the PPMC to use the guideline PPMC==committers
until we graduate. Doing this means we dont need to vote.
<orcnote>
I have to think what it means about "don't need to vote."
I take it that "by lazy consensus the PPMC is going to
employ PPMC == committers until graduation."
</orcnote>
rgds
jan I.
[ ... ]
Re: [DISCUSS] committers == PPMC
Posted by jan i <ja...@apache.org>.
Hi.
I hope we have turned all the stones we want to turn in this discussion.
It seems we agree to do it while we are small and in incubator, but it
needs to discussed again once we graduate to TLP.
Based on the above, I expect the PPMC to use the guideline PPMC==committers
until we graduate. Doing this means we dont need to vote.
rgds
jan I.
On 20 December 2014 at 15:38, Louis Suárez-Potts <lu...@gmail.com> wrote:
>
> > On 20 Dec 2014, at 00:02, Peter Kelly <pm...@apache.org> wrote:
> >
> > Well as someone new to Apache I’m still not yet entirely sure of the
> rationale between having a distinction between the two :)
>
>
> Depending on the nature of the project and what is wanted the two can be
> identical or not. Duh. (Not unlike principles of agile development.)
> Usually, social, and also code government—bureaucracy and the differences
> it imposes—becomes important as more people and code (as in modules
> expressing different intentionalities and evidencing diverging styles)
> intervene in the project. At that point, we can articulate the distinctions
> and codify them. Usually, “that point” is reached when someone demands it.
> The there is discussion, which can be mercifully brief, and so on.
>
> But until then, why make a distinction?
>
>
> >
> > I think for a small project like Corinthia is right now, it makes sense
> to have Committer == PPMC. We want to build up the project community, and I
> see welcoming people and being inclusive as being important pre-requisites
> to that.
> >
> > If and when (hopefully when) the project gets larger and moves into a
> TLP, it may be appropriate to have only a subset of participants on the
> PPC, depending on the number of committers and their level of involvement
> with the project. As an open source project, I think we should try to be as
> open and democratic as possible, and I’m in favour of using private lists
> only where absolutely necessary.
>
>
> >
> > I propose that during the incubation period, we have Committer == PPMC,
> and then we revisit this discussion if & when we prepare to become a TLP.
> >
> Yes; had I bothered to read Peter’s point, before I inflated myself and
> then shared with others a lot of tepid air, I’d have seen he anticipated
> me. :-) But I would still keep it as flexible and basically anarchic as
> feasible. (Anarchic doesn’t mean, “do as you like,” which is just solipsism
> run amok. It means, rather, something closer to a direct democracy
> predicated on merit, where “merit” is proved by code and other relevant
> works others can use. Fwiw, David Graeber, the great contemporary
> anarchist, has a new book on bureaucracy, a field I studied early in
> graduate school and of which I’m particularly fond.)
>
> louis
> > —
> > Dr Peter M. Kelly
> > pmkelly@apache.org
> >
> > PGP key: http://www.kellypmk.net/pgp-key <
> http://www.kellypmk.net/pgp-key>
> > (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
> >
> >> On 19 Dec 2014, at 11:57 pm, jan i <ja...@apache.org> wrote:
> >>
> >> Hi.
> >>
> >> *Preamble:*
> >>
> >> Sorry about the fuzz, but we have to do things right, and I started this
> >> discussion from a wrong perspective.
> >>
> >> In my opinion it is the community as a whole who decide (within the
> limits
> >> of the bylaws) how our PPMC shall operate, therefore this discussion is
> an
> >> open discussion.
> >>
> >> As initial committers we are all PPMC, so this discussion is solely
> about
> >> new people coming to the project.
> >>
> >>
> >>
> >> *Discussion starting point:*
> >> For a small project like ours, there are no logical reason to make a
> >> difference between being committer and PPMC. I believe it can be
> directly
> >> harmful to the project.
> >>
> >> Example (another project): In budapest we were 6 people gathered around
> a
> >> table discussion the future of the project. 3 PMC, 1 committer (but ASF
> >> member) and 2 committers.....We had to stop the discussion several
> times,
> >> due to the fact "oooh this happened on the private list", I still wonder
> >> how the 2 committers felt...I know I would have felt being held out.
> >>
> >> What is the downside of this rule, with time we might get a big PMC
> (after
> >> graduation) and lots of discussions, some see this as negative, I see
> it as
> >> healthy...Apache is not about a few ruling the project, but the whole
> >> community doing it together.
> >>
> >> I must emphasize, I am NOT suggesting to bend or change any voting rules
> >> but simply to implement a procedure !!
> >>
> >> My suggestion is, that we as community, ask the PPMC to always vote if a
> >> candidate should be PPMC+committer using the strictest voting rules
> (right
> >> now 3 PPMC +1 and no -1).
> >>
> >> The invitation letter, should be an invitation to join both as committer
> >> and PPMC, but give an option so the candidate can choose only to be a
> >> committer.
> >>
> >> If we want this, it can be implemented in 2 ways:
> >> 1) A convention, where we simply ask the PPMC to always do it like this
> >> - here a vote is not really needed, because the PPMC can decide to
> follow
> >> it or not.
> >> 2) A Rule, where the PPMC have to do it.
> >> - here a vote is really needed (and one with a clear majority and NONE
> >> against it).
> >>
> >> Thoughts ?
> >>
> >>
> >> rgds
> >> jan i.
> >
>
>
Re: [DISCUSS] committers == PPMC
Posted by Louis Suárez-Potts <lu...@gmail.com>.
> On 20 Dec 2014, at 00:02, Peter Kelly <pm...@apache.org> wrote:
>
> Well as someone new to Apache I’m still not yet entirely sure of the rationale between having a distinction between the two :)
Depending on the nature of the project and what is wanted the two can be identical or not. Duh. (Not unlike principles of agile development.) Usually, social, and also code government—bureaucracy and the differences it imposes—becomes important as more people and code (as in modules expressing different intentionalities and evidencing diverging styles) intervene in the project. At that point, we can articulate the distinctions and codify them. Usually, “that point” is reached when someone demands it. The there is discussion, which can be mercifully brief, and so on.
But until then, why make a distinction?
>
> I think for a small project like Corinthia is right now, it makes sense to have Committer == PPMC. We want to build up the project community, and I see welcoming people and being inclusive as being important pre-requisites to that.
>
> If and when (hopefully when) the project gets larger and moves into a TLP, it may be appropriate to have only a subset of participants on the PPC, depending on the number of committers and their level of involvement with the project. As an open source project, I think we should try to be as open and democratic as possible, and I’m in favour of using private lists only where absolutely necessary.
>
> I propose that during the incubation period, we have Committer == PPMC, and then we revisit this discussion if & when we prepare to become a TLP.
>
Yes; had I bothered to read Peter’s point, before I inflated myself and then shared with others a lot of tepid air, I’d have seen he anticipated me. :-) But I would still keep it as flexible and basically anarchic as feasible. (Anarchic doesn’t mean, “do as you like,” which is just solipsism run amok. It means, rather, something closer to a direct democracy predicated on merit, where “merit” is proved by code and other relevant works others can use. Fwiw, David Graeber, the great contemporary anarchist, has a new book on bureaucracy, a field I studied early in graduate school and of which I’m particularly fond.)
louis
> —
> Dr Peter M. Kelly
> pmkelly@apache.org
>
> PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key>
> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
>
>> On 19 Dec 2014, at 11:57 pm, jan i <ja...@apache.org> wrote:
>>
>> Hi.
>>
>> *Preamble:*
>>
>> Sorry about the fuzz, but we have to do things right, and I started this
>> discussion from a wrong perspective.
>>
>> In my opinion it is the community as a whole who decide (within the limits
>> of the bylaws) how our PPMC shall operate, therefore this discussion is an
>> open discussion.
>>
>> As initial committers we are all PPMC, so this discussion is solely about
>> new people coming to the project.
>>
>>
>>
>> *Discussion starting point:*
>> For a small project like ours, there are no logical reason to make a
>> difference between being committer and PPMC. I believe it can be directly
>> harmful to the project.
>>
>> Example (another project): In budapest we were 6 people gathered around a
>> table discussion the future of the project. 3 PMC, 1 committer (but ASF
>> member) and 2 committers.....We had to stop the discussion several times,
>> due to the fact "oooh this happened on the private list", I still wonder
>> how the 2 committers felt...I know I would have felt being held out.
>>
>> What is the downside of this rule, with time we might get a big PMC (after
>> graduation) and lots of discussions, some see this as negative, I see it as
>> healthy...Apache is not about a few ruling the project, but the whole
>> community doing it together.
>>
>> I must emphasize, I am NOT suggesting to bend or change any voting rules
>> but simply to implement a procedure !!
>>
>> My suggestion is, that we as community, ask the PPMC to always vote if a
>> candidate should be PPMC+committer using the strictest voting rules (right
>> now 3 PPMC +1 and no -1).
>>
>> The invitation letter, should be an invitation to join both as committer
>> and PPMC, but give an option so the candidate can choose only to be a
>> committer.
>>
>> If we want this, it can be implemented in 2 ways:
>> 1) A convention, where we simply ask the PPMC to always do it like this
>> - here a vote is not really needed, because the PPMC can decide to follow
>> it or not.
>> 2) A Rule, where the PPMC have to do it.
>> - here a vote is really needed (and one with a clear majority and NONE
>> against it).
>>
>> Thoughts ?
>>
>>
>> rgds
>> jan i.
>
Re: [DISCUSS] committers == PPMC
Posted by Peter Kelly <pm...@apache.org>.
Well as someone new to Apache I’m still not yet entirely sure of the rationale between having a distinction between the two :)
I think for a small project like Corinthia is right now, it makes sense to have Committer == PPMC. We want to build up the project community, and I see welcoming people and being inclusive as being important pre-requisites to that.
If and when (hopefully when) the project gets larger and moves into a TLP, it may be appropriate to have only a subset of participants on the PPC, depending on the number of committers and their level of involvement with the project. As an open source project, I think we should try to be as open and democratic as possible, and I’m in favour of using private lists only where absolutely necessary.
I propose that during the incubation period, we have Committer == PPMC, and then we revisit this discussion if & when we prepare to become a TLP.
—
Dr Peter M. Kelly
pmkelly@apache.org
PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key>
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
> On 19 Dec 2014, at 11:57 pm, jan i <ja...@apache.org> wrote:
>
> Hi.
>
> *Preamble:*
>
> Sorry about the fuzz, but we have to do things right, and I started this
> discussion from a wrong perspective.
>
> In my opinion it is the community as a whole who decide (within the limits
> of the bylaws) how our PPMC shall operate, therefore this discussion is an
> open discussion.
>
> As initial committers we are all PPMC, so this discussion is solely about
> new people coming to the project.
>
>
>
> *Discussion starting point:*
> For a small project like ours, there are no logical reason to make a
> difference between being committer and PPMC. I believe it can be directly
> harmful to the project.
>
> Example (another project): In budapest we were 6 people gathered around a
> table discussion the future of the project. 3 PMC, 1 committer (but ASF
> member) and 2 committers.....We had to stop the discussion several times,
> due to the fact "oooh this happened on the private list", I still wonder
> how the 2 committers felt...I know I would have felt being held out.
>
> What is the downside of this rule, with time we might get a big PMC (after
> graduation) and lots of discussions, some see this as negative, I see it as
> healthy...Apache is not about a few ruling the project, but the whole
> community doing it together.
>
> I must emphasize, I am NOT suggesting to bend or change any voting rules
> but simply to implement a procedure !!
>
> My suggestion is, that we as community, ask the PPMC to always vote if a
> candidate should be PPMC+committer using the strictest voting rules (right
> now 3 PPMC +1 and no -1).
>
> The invitation letter, should be an invitation to join both as committer
> and PPMC, but give an option so the candidate can choose only to be a
> committer.
>
> If we want this, it can be implemented in 2 ways:
> 1) A convention, where we simply ask the PPMC to always do it like this
> - here a vote is not really needed, because the PPMC can decide to follow
> it or not.
> 2) A Rule, where the PPMC have to do it.
> - here a vote is really needed (and one with a clear majority and NONE
> against it).
>
> Thoughts ?
>
>
> rgds
> jan i.
RE: [DISCUSS] committers == PPMC
Posted by "Dennis E. Hamilton" <de...@acm.org>.
-- in reply to --
From: Andrea Pescetti [mailto:pescetti@apache.org]
Sent: Friday, December 19, 2014 16:01
To: dev@corinthia.incubator.apache.org
Subject: Re: [DISCUSS] committers == PPMC
jan i wrote:
[ ... ]
> Example (another project): In budapest we were 6 people gathered around a
> table discussion the future of the project. 3 PMC, 1 committer (but ASF
> member) and 2 committers.....We had to stop the discussion several times,
> due to the fact "oooh this happened on the private list", I still wonder
> how the 2 committers felt...I know I would have felt being held out.
A complex example. It refers to the biggest project at Apache in terms
of number of committers (it's called OpenOffice, for those who don't
know it). And we had to stop the discussion many more times to explain
things that had been posted to PUBLIC lists but that nobody had read...
The two projects are too different to compare (by the way, OpenOffice
used "committer==PPMC member" during incubation, if I recall correctly;
but if I do not recall correctly, this is still a different project!).
<orcnote>
Andrea recalls correctly. You can see the list of *86* initial
committers, all of whom were automatically invited to be PPMC
members (and were all self-selected) at
<http://wiki.apache.org/incubator/OpenOfficeProposal>. As
graduation approached, PPMC invitation was a bit
more selective. Some initial committers declined to complete
the formalities for establishing an Apache ID, others, including
ones invited after formation of the project, declined to be on
the PPMC. There are currently 26 members of the AOO PMC, with
over 140 committers (not all active, but still ...).
</orcnote>
Regards,
Andrea.
Re: [DISCUSS] committers == PPMC
Posted by Andrea Pescetti <pe...@apache.org>.
jan i wrote:
> For a small project like ours, there are no logical reason to make a
> difference between being committer and PPMC. I believe it can be directly
> harmful to the project.
The PPMC has the role of bringing the project to Apache and building a
community. With graduation, things change. It may have some value,
especially for new people, to admit them to the PPMC and expose them to
the private list just to show them that there is (hopefully!) no
discussion there, contrary to popular myths. When Corinthia graduates,
reduce the PMC to the really active people (upon some kind of vote).
And remember that every time one has to count votes, something went
wrong: all decisions should be taken by an overwhelming majority, be it
of committers or PMC members. So, ultimately, if the private list is
used with sanity and the project is not split into factions, being a
committer or a PMC member should not make a big difference.
> Example (another project): In budapest we were 6 people gathered around a
> table discussion the future of the project. 3 PMC, 1 committer (but ASF
> member) and 2 committers.....We had to stop the discussion several times,
> due to the fact "oooh this happened on the private list", I still wonder
> how the 2 committers felt...I know I would have felt being held out.
A complex example. It refers to the biggest project at Apache in terms
of number of committers (it's called OpenOffice, for those who don't
know it). And we had to stop the discussion many more times to explain
things that had been posted to PUBLIC lists but that nobody had read...
The two projects are too different to compare (by the way, OpenOffice
used "committer==PPMC member" during incubation, if I recall correctly;
but if I do not recall correctly, this is still a different project!).
Regards,
Andrea.
RE: [DISCUSS] committers == PPMC
Posted by "Dennis E. Hamilton" <or...@apache.org>.
+1 on having new committers invited to the podling also be invited to be on the PPMC.
I have no preference how this is established so long as there is a clear record of it.
-- in reply to --
From: jan i [mailto:jani@apache.org]
Sent: Friday, December 19, 2014 08:58
To: dev@corinthia.incubator.apache.org
Subject: [DISCUSS] committers == PPMC
[ ... ]
<orcnote>
Those who are interested in what that entails need to look at
<http://incubator.apache.org/guides/ppmc.html> down at the two
sections, "Adding new committers" and "Voting in a new PPMC
member."
Because the addition of a PPMC member requires more ceremony,
that level of ceremony is required when the two are combined
in single [DISCUSS] and following [VOTE].
<orcnote>
My suggestion is, that we as community, ask the PPMC to always vote if a
candidate should be PPMC+committer using the strictest voting rules (right
now 3 PPMC +1 and no -1).
<orcnote>
Where is the 3x+1, 0x-1 voting rule described, so folks can confirm
how that works?
</orcnote>
The invitation letter, should be an invitation to join both as committer
and PPMC, but give an option so the candidate can choose only to be a
committer.
If we want this, it can be implemented in 2 ways:
1) A convention, where we simply ask the PPMC to always do it like this
- here a vote is not really needed, because the PPMC can decide to follow
it or not.
2) A Rule, where the PPMC have to do it.
- here a vote is really needed (and one with a clear majority and NONE
against it).
Thoughts ?
rgds
jan i.