From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A079D15806E for ; Sun, 14 May 2023 03:03:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 897CFE07EF; Sun, 14 May 2023 03:03:22 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 72510E07EF for ; Sun, 14 May 2023 03:03:22 +0000 (UTC) Message-ID: Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Council Meeting 2023-05-14: Agenda From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-project@lists.gentoo.org Cc: council@gentoo.org Date: Sun, 14 May 2023 05:03:18 +0200 In-Reply-To: <9da77897-6997-93f9-02ee-c007723de0d7@gentoo.org> References: <905f8802eb6da5a3463022275d5e694dbc4adefd.camel@gentoo.org> <9f55ab30003917669079a03853dff4ff76b24080.camel@gentoo.org> <9da77897-6997-93f9-02ee-c007723de0d7@gentoo.org> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 59c08a51-c4dd-47d4-a320-beaabbfa0b7b X-Archives-Hash: a744eab62bef866ca4a68610e5641c25 On Sat, 2023-05-13 at 10:24 +0200, Florian Schmaus wrote: > I am sorry. I was unaware that one could only propose agenda items=20 > between the call for agenda items and the council meeting. >=20 > The mail with the request to council@ was sent on 2023-04-24, after the= =20 > last council meeting. I assumed this was enough to get it on the agenda,= =20 > especially since I received no feedback otherwise. >=20 > Or maybe did the request fall through the cracks? Such things happen. Indeed it did. You can't really expect us to go through month's backlog over all mailing lists to see if one of the mails in middle of a ml thread didn't have an explicit request for the Council. > In any case, please consider the request to be added to the council's=20 > agenda. Thanks. :) I've sent the updated agenda a minute ago. --=20 Best regards, Micha=C5=82 G=C3=B3rny