From: Mikle Kolyada <zlogene@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-09-09
Date: Mon, 27 Aug 2018 09:25:00 +0300 [thread overview]
Message-ID: <53cd1661-f909-9a07-371a-b252665fdf44@gentoo.org> (raw)
In-Reply-To: <20180826201131.6320b8b7@sf>
[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]
On 26.08.2018 22:11, Sergei Trofimovich wrote:
> Hello all!
>
> 9 September (in 2 weeks from now)
> at 19:00 UTC Council will meet again.
>
> Please provide agenda items you would like council@ to
> look at (and act) as a reply to this email.
>
> To get the idea what usually happens at those meetings
> you can have a glance at past meeting notes summary at:
> https://wiki.gentoo.org/wiki/Project:Council/Meeting_logs
>
> Thank you!
>
It will go to the bugs with the council involvement, but I want to
emphasize anyway [1]
It blocks bringing the proctors project up.
[1] - https://bugs.gentoo.org/663466
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-27 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 19:11 [gentoo-project] Call for agenda items - Council meeting 2018-09-09 Sergei Trofimovich
2018-08-27 6:25 ` Mikle Kolyada [this message]
2018-09-03 7:39 ` Ulrich Mueller
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=53cd1661-f909-9a07-371a-b252665fdf44@gentoo.org \
--to=zlogene@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