public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>, council@gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Council Meeting 2023-05-14: Agenda
Date: Sat, 13 May 2023 23:02:11 +0100	[thread overview]
Message-ID: <87cz3351qi.fsf@gentoo.org> (raw)
In-Reply-To: <9da77897-6997-93f9-02ee-c007723de0d7@gentoo.org>

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


Florian Schmaus <flow@gentoo.org> writes:

> On 12.05.23 17:55, Michał Górny wrote:
>> On Fri, 2023-05-12 at 17:40 +0200, Florian Schmaus wrote:
>>> Hi Michał,
>>>
>>> On 12.05.23 14:27, Michał Górny wrote:
>>>> The next Council meeting will be on Sunday 2023-05-14, 19:00 UTC in the
>>>> #gentoo-council channel on Libera Chat.
>>>>
>>>> Agenda:
>>>>
>>>> 1. Roll call
>>>> 2. Mark GLEP 78 as final [1,2]
>>>> 3. Open bugs with Council participation [3]
>>>> 4. Open floor
>>>
>>> Is there a reason why the request to council to vote on whether EGO_SUM
>>> should be reinstated ("un-deprecated") or not, did not make it on the
>>> agenda?
>>>
>> I don't see it in replies to the call for agenda items:
>
> I am sorry. I was unaware that one could only propose agenda items
> between the call for agenda items and the council meeting.
>
> The mail with the request to council@ was sent on 2023-04-24, after
> the last council meeting. I assumed this was enough to get it on the
> agenda, especially since I received no feedback otherwise.
>
> Or maybe did the request fall through the cracks? Such things happen.
>
> In any case, please consider the request to be added to the council's
> agenda. Thanks. :)

I gave feedback: https://marc.info/?l=gentoo-dev&m=168305630404739&w=2

(The pkgcheck thing still hasn't been addressed either.)


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

  reply	other threads:[~2023-05-13 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 12:27 [gentoo-project] Council Meeting 2023-05-14: Agenda Michał Górny
2023-05-12 15:40 ` [gentoo-project] Re: [gentoo-dev-announce] " Florian Schmaus
2023-05-12 15:55   ` Michał Górny
2023-05-13  8:24     ` Florian Schmaus
2023-05-13 22:02       ` Sam James [this message]
2023-05-14  3:03       ` Michał Górny
2023-05-14  3:01 ` [gentoo-project] Council Meeting 2023-05-14: Agenda -r1 Michał Górny

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=87cz3351qi.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@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