From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Subject: Re: [gentoo-project] Meeting agenda - Council meeting 2019-05-12
Date: Mon, 6 May 2019 11:35:16 -0400 [thread overview]
Message-ID: <CAAr7Pr_pV6YZ165JeDQeGA8MoxfBx5d09Y=h4eWKeB6=GP=jGg@mail.gmail.com> (raw)
In-Reply-To: <65cbd41a-4cdc-4d93-ae86-9dfead3bca03@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
On Mon, May 6, 2019 at 11:26 AM Thomas Deutschmann <whissi@gentoo.org>
wrote:
> The next Council meeting will be on Sunday 2019-05-12, 21:00 UTC
> in the #gentoo-council channel on Freenode.
>
> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190512T21
>
> Meeting agenda:
>
> 1. Roll call
>
> 2. GLEP 63 change request
> =========================
> A motion was proposed by Rich Freeman (rich0) to change GLEP 63 to remove
> key requirement that signing subkey must be different from the primary key
> and does not have any other capabilities enabled.
>
> https://archives.gentoo.org/gentoo-dev/message/d05070a200e4f5858642d308d9b3e39f
>
> 3. GLEP 48 approval requested
> =============================
> Michał Górny (mgorny) requested council to approve current GLEP 48 draft
> (v3 as of today) which would clarify QA project's privileges to issue
> disciplinary actions.
>
> https://archives.gentoo.org/gentoo-project/message/a9d6dc3cf28345a2e96c2cfd164226f2
>
> 4. Registration request for EFI system partition subdirectory namespace
> =======================================================================
> Matthias Maier (tamiko) asked council to register EFI system partition
> subdirectory namespace for Gentoo.
>
> https://archives.gentoo.org/gentoo-project/message/a26ea340c564606c07b9082364bf3367
I already registered the EFI system directory namespace for Gentoo.
-A
>
>
> 5. 17.1 profile stabilization
> =============================
> Michał Górny (mgorny) requested council to mark 17.1 profile stable.
>
> https://archives.gentoo.org/gentoo-project/message/d0358901301850b6e41f0ae9d26cef36
>
> 6. Open bugs with council involvement
> =====================================
>
> https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation
>
> 7. Open floor
>
>
> --
> Regards,
> Thomas Deutschmann / Gentoo Linux Developer
> C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
>
>
[-- Attachment #2: Type: text/html, Size: 3345 bytes --]
next prev parent reply other threads:[~2019-05-06 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 15:26 [gentoo-project] Meeting agenda - Council meeting 2019-05-12 Thomas Deutschmann
2019-05-06 15:35 ` Alec Warner [this message]
2019-05-20 22:51 ` [gentoo-project] " Thomas Deutschmann
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='CAAr7Pr_pV6YZ165JeDQeGA8MoxfBx5d09Y=h4eWKeB6=GP=jGg@mail.gmail.com' \
--to=antarus@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