From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Call for agenda items - Council meeting 2018-02-11
Date: Sun, 28 Jan 2018 14:05:29 +0100 [thread overview]
Message-ID: <23149.51865.998621.918722@a1i15.kph.uni-mainz.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
In two weeks from now, the council will meet again. This is the time
to raise and prepare items that the council should put on the agenda
to discuss or vote on.
Please respond to this message with agenda items. Do not hesitate to
repeat your agenda item here with a pointer if you previously
suggested one (since the last meeting).
The agenda for the meeting will be sent out on Sunday 2018-02-04.
Please reply to the gentoo-project list.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2018-01-28 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 13:05 Ulrich Mueller [this message]
2018-01-29 17:32 ` [gentoo-project] Call for agenda items - Council meeting 2018-02-11 Michał Górny
2018-01-30 10:02 ` [gentoo-project] " Michael Palimaka
2018-04-11 13:46 ` Raymond Jennings
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=23149.51865.998621.918722@a1i15.kph.uni-mainz.de \
--to=ulm@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