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 2022-07-10 - call for agenda items
Date: Wed, 06 Jul 2022 07:59:35 +0200	[thread overview]
Message-ID: <utu7ukchk@gentoo.org> (raw)

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

The first council meeting of this election term will be on
Sunday 2022-07-10, 19:00 UTC in the #gentoo-council channel
on Libera Chat.

Preliminary agenda:

1. Roll call
2. Constitute the new council
   - Decide on time of meetings. The previous council had its meetings
     on the 2nd Sunday of every month at 19:00 UTC
   - Vote for continuing last council's workflow considering sending
     a call for agenda items (two weeks in advance), sending the
     agenda (one week in advance) and have the meeting focussed, i.e.
     have major discussions on the gentoo-project mailing list prior
     to the meeting
   - Appoint chairmen for this term's meetings
4. Open bugs with council involvement [1]
5. Open floor

The agenda is still open for additional items that the council should
discuss or vote on. For agenda items, please respond to this message
on the gentoo-project mailing list.

The final agenda for the meeting will be sent on Saturday 2022-07-09.

Ulrich

[2] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

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

             reply	other threads:[~2022-07-06  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  5:59 Ulrich Mueller [this message]
2022-07-09  9:02 ` [gentoo-dev-announce] Council meeting 2022-07-10 - agenda 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=utu7ukchk@gentoo.org \
    --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