Gentoo Archives: gentoo-dev

From: Thomas Deutschmann <whissi@g.o>
To: gentoo development <gentoo-dev@l.g.o>
Subject: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace
Date: Sun, 13 Sep 2020 18:31:29
1 Hi,
3 TL;DR: jstein asked council [Bug 729062] for a motion that any service
4 and software which is critical for Gentoo should be developed/run in
5 Gentoo namespace. Because any request to council must be discussed I
6 volunteered to bring this topic to the mailing list (sorry for the huge
7 delay!).
10 Problem
11 =======
12 You maybe all remember what happened to stable-bot: Years ago,
13 kensington created stable-bot on his own as PoC which revolutionized the
14 way how we do package stabilization in bugzilla. The service run on his
15 own infrastructure. Because of the benefit of the service the bot
16 provided, arch team’s workflow became dependent on stable-bot. We were
17 lucky that stable-bot just worked most of the time until the service was
18 down for a while. Nobody was able to help here: Kensigton himself was
19 unavailable, nobody had the sources… the end of the story: mgorny
20 created nattka which replaced stable-bot.
22 However, we are still facing the same problem: Only one person is
23 involved in development and knows how to run it. In case something will
24 break again and Michał will be unavailable, we can’t just push a fix and
25 watch a CI pipeline picking up and deploying new nattka. Instead someone
26 will have to fork repository from Michał’s private repository at GitHub,
27 make the changes and hope that anyone within infrastructure team can
28 help to deploy fixed nattka.
30 This is what the motion is about: This is not about that Gentoo depends
31 on single persons or things like that. It’s about the idea to
32 *formalize* the requirement that any service and software which is
33 critical for Gentoo (think about pkgcore) should live within Gentoo
34 namespace (, i.e. be accessible for *any*
35 Gentoo developer and deployments should be based on these repositories.
36 Or in other words: Make sure that we adhere to social contract even for
37 critical software and services Gentoo depends on. So that we will never
38 ever face the situation that something we depend on doesn’t work
39 anymore. Taking care of working pipelines before something is broken
40 should also help us in case something stops working so we don’t have to
41 figure out how to fix and re-deploy when house is already burning (like
42 portage: In case Zac can't do a release for some reason, in theory,
43 every Gentoo developer would be able to roll a new release).
46 See also:
47 =========
48 Bug 729062:
51 --
52 Regards,
53 Thomas Deutschmann / Gentoo Linux Developer
54 C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5


File name MIME type
signature.asc application/pgp-signature