public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting 2019-10-13 19:00 UTC
Date: Mon, 07 Oct 2019 12:42:04 +0200	[thread overview]
Message-ID: <w6g36g4j0qr.fsf@kph.uni-mainz.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

The next council meeting will be on Sunday 2019-10-13, 19:00 UTC
in the #gentoo-council channel on Freenode.

Agenda:

1. Roll call
2. Allow pkgcheck as repoman replacement [1]
3. Valid forms of activity for recruitment/retirement [2]
4. Open bugs with council participation [3]
5. Open floor

Ulrich

[1] https://archives.gentoo.org/gentoo-project/message/915d843e638656fc037dc21aa0e7243f
[2] https://archives.gentoo.org/gentoo-project/message/6bfdb844b9a9abfaf8ae20c386308ba2
[3] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

                 reply	other threads:[~2019-10-07 16:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=w6g36g4j0qr.fsf@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