From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-07-21
Date: Sun, 07 Jul 2019 22:51:37 +0200 [thread overview]
Message-ID: <64ca8f0d73011af497a7d1b286d1aaea289b3d09.camel@gentoo.org> (raw)
In-Reply-To: <w6gzhlptzf0.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
On Sun, 2019-07-07 at 21:30 +0200, Ulrich Mueller wrote:
> In two weeks from now, the newly elected Council will have its
> constituent meeting. This is the time to raise and prepare items that
> the Council should put on the agenda to discuss or vote on.
>
> Please respond to this message with agenda items. Do not hesitate to
> repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).
>
I would like to request the Council to vote on GLEP 81 (user/group
packages) approval. The main purpose of the GLEP is to provide
replacement for GLEP 27, and to set review policies.
Draft:
https://gentoo.org/glep/glep-0081.html
Mailing list reviews:
https://archives.gentoo.org/gentoo-dev/message/2ca74142fa1d160f7573303d88b185b4
https://archives.gentoo.org/gentoo-dev/message/a3e94f10441bba9800b93b7cc90ded97
https://archives.gentoo.org/gentoo-dev/message/92289b159fb07599cfc8a215ee5163b5
The reference implementation is already in ::gentoo (I need to update
this section of the GLEP, I'll do it soonish), and so far the only
complaints were about obligatory pre-commit review.
We also have a wiki page with current mapping/progress:
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/UID_GID_Assignment
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-07-07 20:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 19:30 [gentoo-project] Call for agenda items - Council meeting 2019-07-21 Ulrich Mueller
2019-07-07 20:51 ` Michał Górny [this message]
2019-07-07 21:00 ` Michał Górny
2019-07-08 4:43 ` Ulrich Mueller
2019-07-08 5:36 ` Michał Górny
2019-07-08 13:50 ` Rich Freeman
2019-07-09 9:58 ` Ulrich Mueller
2019-07-12 19:56 ` Andreas K. Huettel
2019-07-21 0:22 ` Andrew Savchenko
2019-07-09 9:28 ` Lars Wendler
2019-07-10 13:55 ` William Hubbs
2019-07-10 14:07 ` Michael Everitt
2019-07-10 15:48 ` William Hubbs
2019-07-20 23:57 ` Andrew Savchenko
2019-07-20 23:48 ` Andrew Savchenko
2019-07-21 1:11 ` Raymond Jennings
2019-07-21 6:28 ` Michał Górny
2019-07-21 11:25 ` Andrew Savchenko
2019-07-21 11:52 ` Raymond Jennings
2019-07-21 13:33 ` Michael Orlitzky
2019-07-09 9:02 ` Haelwenn (lanodan) Monnier
2019-07-13 7:39 ` Ulrich Mueller
2019-07-13 10:53 ` Haelwenn (lanodan) Monnier
2019-07-13 3:28 ` desultory
2019-07-13 4:11 ` Matthew Thode
2019-07-13 6:56 ` Michał Górny
2019-07-13 7:09 ` Ulrich Mueller
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=64ca8f0d73011af497a7d1b286d1aaea289b3d09.camel@gentoo.org \
--to=mgorny@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