From: John Helmert III <ajak@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-project] Agenda for 2022-12-11 council meeting
Date: Sun, 4 Dec 2022 15:00:07 -0600 [thread overview]
Message-ID: <Y40KV8ITmbYxSwi4@gentoo.org> (raw)
In-Reply-To: <20221204202153.qpdjwtvy6xca3i3b@framework>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Sun, Dec 04, 2022 at 03:21:53PM -0500, Matt Turner wrote:
> Hello,
>
> This is the agenda for the council meeting (2022-12-11) at 19:00 UTC:
>
> 1. Roll call
> 2. GLEP76 update [0] (discussion at [1])
Please don't take this as me doing bureaucratic nonsense, but I think
having this on the agenda for the next meeting should be contigent on
us actually having further discussion on the mailing lists. Without
that discussion, it's probably inevitable that it yields the same
result as the last meeting (ie, nothing):
19:29 <@mattst88> motion to table this and continue discussion on the mailing list?
[snip]
19:34 <@mattst88> I think we have yes votes from mattst88, ajak, dilfridge, gyakovlev
19:35 <@mattst88> moving on...
> 3. Open bugs with council participation
> 4. Open floor
>
> One can observe the meeting in #gentoo-council on IRC (libera.chat).
>
> Matt
>
> [0] https://gitweb.gentoo.org/data/glep.git/commit/?h=glep76&id=139198d2e8560f8dfb32c8f4c34a3e49d628b184
> [1] https://archives.gentoo.org/gentoo-project/message/c85b78ca69802522534ee8ab0804f665
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-04 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 20:21 [gentoo-project] Agenda for 2022-12-11 council meeting Matt Turner
2022-12-04 21:00 ` John Helmert III [this message]
2022-12-10 18:41 ` [gentoo-project] " John Helmert III
2022-12-11 3:34 ` Michał Górny
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=Y40KV8ITmbYxSwi4@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