From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Agenda - Council meeting 2021-11-14
Date: Sun, 14 Nov 2021 02:53:01 +0100 [thread overview]
Message-ID: <12846119.CDJkKcVGEf@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
The next Council meeting will be on Sunday 2021-11-14, 19:00 UTC in the
#gentoo-council channel on Libera Chat.
Agenda:
1. Roll call
2. Dropping hppa, ppc, sparc and x86 to ~arch-only status [1]
3. Opening the range 60001..60999 (with possible later extension to
higher IDs) for allocation of additional UIDs and GIDs [2]
3. Open bugs with Council participation [3]
4. Open floor
[1] https://archives.gentoo.org/gentoo-project/message/253dc6b0b980133305f8661d4093f664
[2] https://archives.gentoo.org/gentoo-project/message/87bd3e5f66e034e8fb54d71c97254681
[3] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
reply other threads:[~2021-11-14 1:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=12846119.CDJkKcVGEf@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev-announce@lists.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