public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: John Helmert III <ajak@gentoo.org>
Cc: gentoo-project@lists.gentoo.org,  council@gentoo.org
Subject: Re: [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items
Date: Wed, 29 Mar 2023 07:29:41 +0200	[thread overview]
Message-ID: <uh6u4m8fu@gentoo.org> (raw)
In-Reply-To: <ZCOz9Hd1/ciHPWMp@gentoo.org> (John Helmert, III's message of "Tue, 28 Mar 2023 20:43:48 -0700")

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

>>>>> On Wed, 29 Mar 2023, John Helmert wrote:

> Please reply with any topics you wish to be discussed during the next
> council meeting (2023-04-09).

Some time ago ajak and I had proposed a series of changes for GLEP 39 in
[1] and [2]. These will require an all-developers vote, but I think the
council should discuss the changes first and maybe pre-approve them.

In particular, the changes are:

- Update title [3]
- Updating GLEP 39 requires an all-developers vote [4]
- Replace leaving council members by next in line [5]
- Council members must be developers [6]
- A meeting must dissolve if not quorate [7]
- Projects need not have a lead [8]
- Drop hard requirement of yearly lead elections [9]
- Add summary of changes [10]

Most of them were discussed previously in council meetings or
on the mailing lists. See the commit messages for pointers to these
discussions.

Ulrich

[1] https://archives.gentoo.org/gentoo-project/message/c23c228ac508d19c671da4e4d23c4880
[2] https://archives.gentoo.org/gentoo-project/message/60ca5dac5336b30d71abadaa28bc90ad
[3] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=5ddb7140a90543185dbf05731cdedad83e412fc9
[4] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=50a99510a47016ab0ecadd46dca4f604984c6f13
[5] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=16cc239ad8f68e1d8218409b2aa17c148155d0a3
[6] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=7077c51ad626c2ead5ed95497a54cf78e311f14b
[7] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=0a8d6ae35dea6f7f4a32d3fbc2b6404935660be2
[8] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=fc4d512dba8e4502eec244511f1974e119c56fec
[9] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=52bdf9a83a72e137c148fb4c86a9fa8602649fa1
[10] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep39&id=0ecd972919c8489070a79746eefa4b3e50b4cbc4

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

  parent reply	other threads:[~2023-03-29  5:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  3:43 [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items John Helmert III
2023-03-29  5:14 ` Ulrich Mueller
2023-03-29  5:29 ` Ulrich Mueller [this message]
2023-03-29 14:41   ` Rich Freeman
2023-03-29 16:11     ` Ulrich Mueller
2023-04-10 17:37   ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 (was: Re: Council Meeting 2023-04-09: Call for Agenda Items) Ulrich Mueller
2023-04-10 18:48     ` Robin H. Johnson
2023-04-10 21:28       ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 Ulrich Mueller
2023-04-11 16:24         ` Ulrich Mueller
2023-04-15  9:33           ` Roy Bamford
2023-04-16  8:24     ` [gentoo-project] " Ulrich Mueller
2023-04-24  9:18       ` [gentoo-project] Gentoo metastructure update (GLEP 39) voting now open Ulrich Mueller
2023-04-25  7:15         ` Ulrich Mueller
2023-04-30 16:30         ` [gentoo-project] Re: [gentoo-dev-announce] Gentoo metastructure update (GLEP 39) voting now open - 7 days left Jorge Manuel B. S. Vicetto
     [not found]           ` <d43987ddf5371b1b883cfe0b712e683baec62379.camel@gentoo.org>
2023-05-03  6:58             ` Ulrich Mueller
2023-05-03 11:59               ` Michael Orlitzky
2023-03-31 17:02 ` [gentoo-project] Re: Council Meeting 2023-04-09: Call for Agenda Items Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uh6u4m8fu@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=ajak@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox