From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: stable-bot is down. Temporary? Forever? Can we have a contacts page for it?
Date: Tue, 8 Oct 2019 22:57:29 +1100 [thread overview]
Message-ID: <4e4819ce-84e5-8730-da43-177e1219b45e@gentoo.org> (raw)
In-Reply-To: <4170258.EnrzZEfU2y@porto>
On 10/8/19 7:21 AM, Andreas K. Huettel wrote:
> In any case, since many people *do* rely on it, maybe we should declare it
> official? [+]
>
> And, if that's OK with both of you, move it onto infra hardware?
>
> Happy to sponsor both for the next council meeting agenda.
>
>
> [+] At some point the one remaining whiner doesnt count anymore.
>
In the past, infra has been understandably hesitant to take on new
services due to staffing issues.
Additionally, I understand that the current infra design does not easily
allow granular access control, preventing non-infra members from easily
performing maintenance on individual services.
Has this situation changed? I doubt infra want to take responsibility
for the bot, and I don't fancy the hassle of trying to find people to
poke things on my behalf.
next prev parent reply other threads:[~2019-10-08 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 7:28 [gentoo-dev] stable-bot is down. Temporary? Forever? Can we have a contacts page for it? Sergei Trofimovich
2019-10-02 15:43 ` Matt Turner
2019-10-03 19:32 ` Robin H. Johnson
2019-10-04 3:09 ` bman
2019-10-04 11:30 ` Mike Gilbert
2019-10-07 11:29 ` [gentoo-dev] " Michael Palimaka
2019-10-07 19:11 ` Robin H. Johnson
2019-10-07 20:21 ` Andreas K. Huettel
2019-10-08 11:57 ` Michael Palimaka [this message]
2019-10-08 12:22 ` Rich Freeman
2019-10-08 15:46 ` Alec Warner
2019-10-07 11:27 ` Michael Palimaka
2019-12-24 12:19 ` Sergei Trofimovich
2019-12-06 16:15 ` [gentoo-dev] " Matt Turner
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=4e4819ce-84e5-8730-da43-177e1219b45e@gentoo.org \
--to=kensington@gentoo.org \
--cc=gentoo-dev@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