From: kuzetsa CatSwarm <kuzetsa@searh.us>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items for upcoming council meeting (2022-11-13)
Date: Mon, 7 Nov 2022 07:58:38 -0500 [thread overview]
Message-ID: <90a4c069-fecd-92f6-6e99-51132c2159d1@searh.us> (raw)
In-Reply-To: <Y2GEwUNtIHlKi5fJ@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1126 bytes --]
re: GLEP 76
~ I'll set time aside on the 13th to be available for comment if anyone
has questions or wants insights into the wording adjustment, social
conventions for contributor inclusivity, smoother recruiting paths, or
just developer relations regarding dignity as a broader topic.
though hopefully, just to quietly attend, sign off, and ACK that
everyone is on the same page.
(confident everything still LGTM)
- kuza
P.S. thank you to everyone involved
On 11/1/22 16:42, John Helmert III wrote:
> On Sun, Oct 30, 2022 at 11:45:32AM -0400, Matt Turner wrote:
>> Hello,
>>
>> Please reply with any topics you wish to be discussed during the next
>> council meeting (2022-11-13).
>>
>> Current default agenda:
>> 1. Roll call
>> 2. Open bugs with council participation
>> 3. Open floor
>>
>> Matt
>
> I'd like to seek approval of Robin's GLEP 76 update:
>
> https://gitweb.gentoo.org/data/glep.git/commit/?h=glep76&id=139198d2e8560f8dfb32c8f4c34a3e49d628b184
>
> With discussion at:
>
> https://archives.gentoo.org/gentoo-project/message/c85b78ca69802522534ee8ab0804f665
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-11-07 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 15:45 [gentoo-project] Call for agenda items for upcoming council meeting (2022-11-13) Matt Turner
2022-10-30 16:17 ` Michał Górny
2022-11-01 20:42 ` John Helmert III
2022-11-07 12:58 ` kuzetsa CatSwarm [this message]
2022-11-07 11:19 ` Joonas Niilola
2022-11-12 23:26 ` David Seifert
2022-11-13 3:03 ` Alec Warner
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=90a4c069-fecd-92f6-6e99-51132c2159d1@searh.us \
--to=kuzetsa@searh.us \
--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