[gentoo-project] [PATCH 0/6] Some updates for GLEP 39

[gentoo-project] [PATCH 0/6] Some updates for GLEP 39

[Ulrich Müller]

We recently saw a proposal by ajak for updating GLEP 39, which would
require an all-developers vote. If we do that, we could use it to get
some other changes in. Some of them are pending since many years;
I have collected them from bugzilla, council meeting logs, and mailing
list postings.

The patches in this series should be independent of each other (and of
ajak's patch), so each of them can be discussed separately.

Ulrich Müller (6):
  glep-0039: Update title
  glep-0039: Updating GLEP 39 requires an all-developers vote
  glep-0039: Replace leaving council members by next in line
  glep-0039: Council members must be developers
  glep-0039: A meeting must dissolve if not quorate
  glep-0039: Projects need not have a lead

 glep-0039.rst | 30 ++++++++++++++++++++----------
 1 file changed, 20 insertions(+), 10 deletions(-)

-- 
2.38.1

[gentoo-project] [PATCH 1/6] glep-0039: Update title

[Ulrich Müller]

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/glep-0039.rst b/glep-0039.rst
index 82bf1d9..d6caf28 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -1,13 +1,13 @@
 ---
 GLEP: 39
-Title: An "old-school" metastructure proposal with "boot for being a slacker"
+Title: Gentoo metastructure
 Author: Grant Goodyear <g2boojum@gentoo.org>,
         Ciaran McCreesh <ciaranm@gentoo.org>
 Type: Informational
 Status: Final
 Version: 2
 Created: 2005-09-01
-Last-Modified: 2019-11-07
+Last-Modified: 2022-11-10
 Post-History: 2005-09-01, 2006-02-09, 2007-10-12, 2008-01-19
 Content-Type: text/x-rst
 Replaces: 4
-- 
2.38.1

[gentoo-project] [PATCH 2/6] glep-0039: Updating GLEP 39 requires an all-developers vote

[Ulrich Müller]

See council decision of 2009-07-20, confirmed again on 2011-07-15.

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/glep-0039.rst b/glep-0039.rst
index d6caf28..e2fe477 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -21,6 +21,9 @@ Gentoo developers on 2005-06-14 [#Metastructure_vote]_.
 GLEP amended on 2006-02-09 to add the final bullet point to list B in
 `Specification`_.
 
+Updates to this GLEP (other than editorial changes) require a vote of
+all developers.
+
 Abstract
 ========
 
-- 
2.38.1

[gentoo-project] [PATCH 3/6] glep-0039: Replace leaving council members by next in line

[Ulrich Müller]

Accepted in the 2007-02-08 council meeting. Wording slightly updated,
in order to clarify that even after an election the new council member
will get a reduced term.

This is already current practice and was followed by the council
several times in the past: 2007-03-08 (uberlord), 2007-06-14 (jaervosz),
2008-09-11 (cardoe), 2009-02-26 (leio), 2009-05-28 (ulm),
2011-01-11 (patrick).

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/glep-0039.rst b/glep-0039.rst
index e2fe477..7443ae1 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -148,9 +148,15 @@ B. Global issues will be decided by an elected Gentoo council.
       two consecutive meetings, they are marked as a slacker.
    *  If a council member who has been marked a slacker misses any further
       meeting (or their appointed proxy doesn't show up), they lose their
-      position and a new election is held to replace that person. The newly
-      elected council member gets a 'reduced' term so that the yearly
-      elections still elect a full group.
+      position.
+   *  Whenever a member of the council loses their position (the reason
+      is irrelevant; e.g. they resign or they are booted for slacking),
+      then the next person in line from the previous council election
+      is offered the position.  If they accept and the current council
+      unanimously accepts the new person, they get the position.
+      Otherwise, it is offered to the next person in line, and so forth.
+      The new member gets a 'reduced' term so that the yearly elections
+      still elect a full group.
    *  Council members who have previously been booted for excessive slacking
       may stand for future elections, including the election for their
       replacement. They should, however, justify their slackerness, and
-- 
2.38.1

Re: [gentoo-project] [PATCH 3/6] glep-0039: Replace leaving council members by next in line

[Ulrich Mueller]

>>>>> On Fri, 25 Nov 2022, Ulrich Müller wrote:

>     *  If a council member who has been marked a slacker misses any further
>        meeting (or their appointed proxy doesn't show up), they lose their
> -      position and a new election is held to replace that person. The newly
> -      elected council member gets a 'reduced' term so that the yearly
> -      elections still elect a full group.
> +      position.
> +   *  Whenever a member of the council loses their position (the reason
> +      is irrelevant; e.g. they resign or they are booted for slacking),
> +      then the next person in line from the previous council election
> +      is offered the position.  If they accept and the current council
> +      unanimously accepts the new person, they get the position.
> +      Otherwise, it is offered to the next person in line, and so forth.

Hm, apparently I have dropped a sentence here. The following should be
inserted:

         If the Council does not accept that person, then a new election is
         held to choose a new member.

> +      The new member gets a 'reduced' term so that the yearly elections
> +      still elect a full group.

[gentoo-project] [PATCH 4/6] glep-0039: Council members must be developers

[Ulrich Müller]

Discussed in 2013-02-12 council meeting.

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/glep-0039.rst b/glep-0039.rst
index 7443ae1..87c9535 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -141,6 +141,7 @@ B. Global issues will be decided by an elected Gentoo council.
       first election that number was set to 7 by acclamation.)
    *  Council members will be chosen by a general election of all
       devs once per year.
+   *  Council members (and their proxies) must be Gentoo developers.
    *  The council must hold an open meeting at least once per month.
    *  Council decisions are by majority vote of those who show up (or
       their proxies).
-- 
2.38.1

[gentoo-project] [PATCH 5/6] glep-0039: A meeting must dissolve if not quorate

[Ulrich Müller]

Bug: https://bugs.gentoo.org/520074
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/glep-0039.rst b/glep-0039.rst
index 87c9535..ad723b2 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -165,7 +165,8 @@ B. Global issues will be decided by an elected Gentoo council.
    *  The 'slacker' marker is reset when a member is elected.
    *  If any meeting has less than 50% attendance by council members, a new
       election for *all* places must be held within a month. The 'one year'
-      is then reset from that point.
+      is then reset from that point.  Any such meeting must dissolve
+      immediately after the short roll call.
    *  Disciplinary actions may be appealed to the council.
    *  A proxy must not be an existing council member, and any single person
       may not be a proxy for more than one council member at any given
-- 
2.38.1

Re: [gentoo-project] [PATCH 5/6] glep-0039: A meeting must dissolve if not quorate

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 561 bytes --]

>>>>> On Fri, 25 Nov 2022, Ulrich Müller wrote:

>     *  If any meeting has less than 50% attendance by council members, a new
>        election for *all* places must be held within a month. The 'one year'

Also, does this need clarification whether proxies are included in the
count? For example, is a new election required if a meeting is attended
by 3 council members and 2 proxies?

> -      is then reset from that point.
> +      is then reset from that point.  Any such meeting must dissolve
> +      immediately after the short roll call.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

[gentoo-project] [PATCH 6/6] glep-0039: Projects need not have a lead

[Ulrich Müller]

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/glep-0039.rst b/glep-0039.rst
index ad723b2..f456f04 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -119,10 +119,9 @@ A. A project is a group of developers working towards a goal (or a set
       that the information on the page is factually correct and not
       out-of-date.)  If the Wiki page isn't maintained, it is presumed
       dead.
-   *  It may have one or many leads, and the leads are
-      selected by the members of the project.  This selection must
-      occur at least once every 12 months, and may occur at any
-      time.
+   *  It should have at least one lead, and the leads are selected by
+      the members of the project.  This selection must occur at least
+      once every 12 months, and may occur at any time.
    *  It may have zero or more sub-projects.  Sub-projects are
       just projects that provide some additional structure, and their
       Wiki pages are defined as sub-projects of the parent project.
-- 
2.38.1

Re: [gentoo-project] [PATCH 6/6] glep-0039: Projects need not have a lead

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Fri, Nov 25, 2022 at 07:20:32PM +0100, Ulrich Müller wrote:
> -   *  It may have one or many leads, and the leads are
> -      selected by the members of the project.  This selection must
> -      occur at least once every 12 months, and may occur at any
> -      time.
> +   *  It should have at least one lead, and the leads are selected by
> +      the members of the project.  This selection must occur at least
> +      once every 12 months, and may occur at any time.

The subject line buries the lede here ;-).

If the GLEPs are trying to follow RFC 2119 language semantics.

"SHOULD" is "recommended"
"MAY" is "truly optional"

How about this, again in line with RFC 2119 (formatted for ease of discussion):
==
It is recommended that projects have at least one lead. 
It is recommended that leads are selected by members of the project.
Lead selection may occur at any time.
Lead selection is required to occur least once every 12 months.
==

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]

Re: [gentoo-project] [PATCH 6/6] glep-0039: Projects need not have a lead

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

>>>>> On Sun, 27 Nov 2022, Robin H Johnson wrote:

> On Fri, Nov 25, 2022 at 07:20:32PM +0100, Ulrich Müller wrote:
>> -   *  It may have one or many leads, and the leads are
>> -      selected by the members of the project.  This selection must
>> -      occur at least once every 12 months, and may occur at any
>> -      time.
>> +   *  It should have at least one lead, and the leads are selected by
>> +      the members of the project.  This selection must occur at least
>> +      once every 12 months, and may occur at any time.

> The subject line buries the lede here ;-).

> If the GLEPs are trying to follow RFC 2119 language semantics.

> "SHOULD" is "recommended"
> "MAY" is "truly optional"

I don't think they do. The last item in the list says:

"... any single person *may* not be a proxy for more than one council
member at any given meeting." (my emphasis)

Obviously this isn't an optional "MAY" but a requirement. (And IMHO the
meaning is clear, so no need to reword it.)

> How about this, again in line with RFC 2119 (formatted for ease of discussion):
> ==
> It is recommended that projects have at least one lead. 
> It is recommended that leads are selected by members of the project.

This would imply that leads could also be selected by somebody else?

> Lead selection may occur at any time.
> Lead selection is required to occur least once every 12 months.
> ==

Not sure. I have tried to do minimal changes, i.e. clarify things where
it's necessary, but leave the rest of the wording alone.

How about this then:

| * It is recommended that a project has at least one lead.  The leads
|   are selected by the members of the project.  This selection must
|   occur at least once every 12 months, and may occur at any time.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

[gentoo-project] [PATCH 7/6] glep-0039: Update Post-History

[Ulrich Müller]

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0039.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/glep-0039.rst b/glep-0039.rst
index f456f04..bc40edb 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -7,8 +7,8 @@ Type: Informational
 Status: Final
 Version: 2
 Created: 2005-09-01
-Last-Modified: 2022-11-10
-Post-History: 2005-09-01, 2006-02-09, 2007-10-12, 2008-01-19
+Last-Modified: 2022-11-25
+Post-History: 2005-09-01, 2006-02-09, 2007-10-12, 2008-01-19, 2022-11-25
 Content-Type: text/x-rst
 Replaces: 4
 ---
-- 
2.38.1

Re: [gentoo-project] [PATCH 0/6] Some updates for GLEP 39

[John Helmert III]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Could you add references to the relevant council decisions for these?

On Fri, Nov 25, 2022 at 07:20:26PM +0100, Ulrich Müller wrote:
> We recently saw a proposal by ajak for updating GLEP 39, which would
> require an all-developers vote. If we do that, we could use it to get
> some other changes in. Some of them are pending since many years;
> I have collected them from bugzilla, council meeting logs, and mailing
> list postings.
> 
> The patches in this series should be independent of each other (and of
> ajak's patch), so each of them can be discussed separately.
> 
> Ulrich Müller (6):
>   glep-0039: Update title
>   glep-0039: Updating GLEP 39 requires an all-developers vote
>   glep-0039: Replace leaving council members by next in line
>   glep-0039: Council members must be developers
>   glep-0039: A meeting must dissolve if not quorate
>   glep-0039: Projects need not have a lead
> 
>  glep-0039.rst | 30 ++++++++++++++++++++----------
>  1 file changed, 20 insertions(+), 10 deletions(-)
> 
> -- 
> 2.38.1
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [gentoo-project] [PATCH 0/6] Some updates for GLEP 39

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

>>>>> On Tue, 29 Nov 2022, John Helmert wrote:

> Could you add references to the relevant council decisions for these?

>> glep-0039: Update title
>> glep-0039: Updating GLEP 39 requires an all-developers vote
>> glep-0039: Replace leaving council members by next in line
>> glep-0039: Council members must be developers
>> glep-0039: A meeting must dissolve if not quorate
>> glep-0039: Projects need not have a lead

References to council meetings and bugs are in the commit messages?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

Re: [gentoo-project] [PATCH 0/6] Some updates for GLEP 39

[John Helmert III]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On Tue, Nov 29, 2022 at 09:12:22PM +0100, Ulrich Mueller wrote:
> >>>>> On Tue, 29 Nov 2022, John Helmert wrote:
> 
> > Could you add references to the relevant council decisions for these?
> 
> >> glep-0039: Update title
> >> glep-0039: Updating GLEP 39 requires an all-developers vote
> >> glep-0039: Replace leaving council members by next in line
> >> glep-0039: Council members must be developers
> >> glep-0039: A meeting must dissolve if not quorate
> >> glep-0039: Projects need not have a lead
> 
> References to council meetings and bugs are in the commit messages?

Is it typical for background references to not be included in the
document itself?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]