From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] call for agenda items -- council meeting 2021-05-09
Date: Mon, 03 May 2021 10:59:28 +0200 [thread overview]
Message-ID: <00d9f2b305889294210bb01748d2045a0cd603f0.camel@gentoo.org> (raw)
In-Reply-To: <YI9sYoh9KLTCm0XM@linux1.home>
On Sun, 2021-05-02 at 22:22 -0500, William Hubbs wrote:
> On Sun, May 02, 2021 at 09:07:11PM +0200, Thomas Deutschmann wrote:
> > Hi,
> >
> > On 2021-05-01 17:14, Andreas K. Huettel wrote:
> > > There's rumors going around that Agostino's tinderbox basically
> > > already burned through our entire 2021 AWS Open Source credit budget
> > > and has overdrawn it significantly.
> > >
> > > Independent of whether this rumor is true or not, I would like to
> > > discuss
> > > * how we can avoid such a situation in the future,
> > > * and how we can fairly handle the distribution of limited infra
> > > resources that may end up costing us money
> >
> > Is this really a topic for council?
> >
> > Isn't foundation an independent body and if someone requests funding
> > from foundation and will get it approved...
> >
> > Or in other words: Can council veto against funding requests the
> > foundation received and wants to approve?
>
> The way I see it is, if the council wants funding for something they
> can request it from the foundation, but I don't think they can direct
> the foundation not to fund something someone else requests.
>
> Also, given Antarus' response in the thread, I'm not sure there is
> anything for council to discuss.
>
Does 'being not sure' authorize you to arbitrarily decide to skip agenda
items from the community?
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2021-05-03 8:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 19:01 [gentoo-project] call for agenda items -- council meeting 2021-05-09 William Hubbs
2021-04-25 19:12 ` Michał Górny
2021-04-27 18:56 ` Andreas K. Huettel
2021-04-28 0:56 ` Sam James
2021-05-09 15:22 ` David Seifert
2021-04-28 4:10 ` Joonas Niilola
2021-05-01 15:14 ` Andreas K. Huettel
2021-05-02 10:33 ` Marek Szuba
2021-05-02 19:07 ` Thomas Deutschmann
2021-05-02 20:22 ` Michał Górny
2021-05-03 15:03 ` Thomas Deutschmann
2021-05-03 20:25 ` Michał Górny
2021-05-03 3:22 ` William Hubbs
2021-05-03 8:59 ` Michał Górny [this message]
2021-05-03 9:15 ` Ulrich Mueller
2021-05-03 10:39 ` Michał Górny
2021-05-03 14:31 ` William Hubbs
2021-05-03 20:26 ` Michał Górny
2021-05-03 15:02 ` Andreas K. Huettel
2021-05-03 13:55 ` Andreas K. Huettel
2021-05-03 14:25 ` Thomas Deutschmann
2021-05-03 15:04 ` Andreas K. Huettel
2021-05-03 15:31 ` Thomas Deutschmann
2021-05-03 15:48 ` Andreas K. Huettel
2021-05-03 16:40 ` Alec Warner
2021-05-03 16:42 ` Rich Freeman
2021-05-03 18:12 ` Sam James
2021-05-03 19:19 ` Thomas Deutschmann
2021-05-03 20:00 ` Sam James
2021-05-04 22:24 ` Alec Warner
2021-05-02 19:18 ` Alec Warner
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=00d9f2b305889294210bb01748d2045a0cd603f0.camel@gentoo.org \
--to=mgorny@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