From: John Helmert III <ajak@gentoo.org>
To: gentoo-project@lists.gentoo.org, council@gentoo.org
Subject: [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items
Date: Tue, 28 Mar 2023 20:43:48 -0700 [thread overview]
Message-ID: <ZCOz9Hd1/ciHPWMp@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
Hello,
Please reply with any topics you wish to be discussed during the next
council meeting (2023-04-09).
Current default agenda:
1. Roll call
2. Open bugs with council participation
3. Open floor
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2023-03-29 3:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 3:43 John Helmert III [this message]
2023-03-29 5:14 ` [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items Ulrich Mueller
2023-03-29 5:29 ` Ulrich Mueller
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=ZCOz9Hd1/ciHPWMp@gentoo.org \
--to=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