Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Kent Fredric
On Wed, 16 Sep 2020 16:05:49 -0600 Tim Harder wrote: > Speaking for myself, I avoid hosting most of my Gentoo-related work > (outside of gentoo repo ebuild mangling) on gentoo.org since I prefer > the services offered elsewhere in terms of usability, visibility, and > project maintenance. Take

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Kent Fredric
On Wed, 16 Sep 2020 19:47:35 -0400 Rich Freeman wrote: > Seems like a way to improve this would be better documentation and a > DIY infra testing platform. > > First, document how to prepare a service for infra hosting. Maybe > provide an example service. > > Second, publish a tarball of a

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Kent Fredric
On Wed, 16 Sep 2020 07:11:12 -0400 Rich Freeman wrote: > I realize this is a bit more tangential. I just think that infra is > already a huge failure point, so having more stuff on infra actually > makes that failure point more critical. A Gentoo where little is > hosted on stuff we own is

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Rich Freeman
On Wed, Sep 16, 2020 at 11:44 AM Alec Warner wrote: > > - repomirror-ci and all the CI stuff is on infra because mgorny is also on > infra! It's not like we set his stuff up for him; instead we gave him access > to all the infra repos and he had to write his own puppet configs and > whatnot.

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Tim Harder
On 2020-09-16 Wed 09:36, Jonas Stein wrote: > The heart of a distribution is basically its infrastructure and the > tools to test, maintain and distribute packages. > > If a distribution relies on external sources, which are not maintained > by the distribution, but a single person, it has been

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Alec Warner
On Wed, Sep 16, 2020 at 1:17 AM Kent Fredric wrote: > On Mon, 14 Sep 2020 10:15:31 -0400 > Rich Freeman wrote: > > > It might be easier to take smaller steps, such as having a policy that > > "any call for devs to use/test a new tool/service, or any service that > > automatically performs

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Jonas Stein
Hi, > However, we are still facing the same problem: Only one person is > involved in development and knows how to run it. In case something will > break again and Michał will be unavailable, we can’t just push a fix and > watch a CI pipeline picking up and deploying new nattka. Instead someone >

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Rich Freeman
On Wed, Sep 16, 2020 at 4:17 AM Kent Fredric wrote: > > On Mon, 14 Sep 2020 10:15:31 -0400 > Rich Freeman wrote: > > > It might be easier to take smaller steps, such as having a policy that > > "any call for devs to use/test a new tool/service, or any service that > > automatically performs

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-16 Thread Kent Fredric
On Mon, 14 Sep 2020 10:15:31 -0400 Rich Freeman wrote: > It might be easier to take smaller steps, such as having a policy that > "any call for devs to use/test a new tool/service, or any service that > automatically performs transactions on bugzilla, must be FOSS, and the > link to the source

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-14 Thread Rich Freeman
On Sun, Sep 13, 2020 at 11:52 PM Kent Fredric wrote: > > But when you file a bug, you rely on bugzilla being maintained by > Gentoo Infra, not some 3rd party. > I think the Council will need to consider where it wants to draw the lines on something like this. Here is my sense of how these sorts

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-13 Thread Kent Fredric
On Sun, 13 Sep 2020 12:04:39 -0700 Alec Warner wrote: > Is openrc critical to Gentoo? it doesn't live on our infra. > Is pkgcore critical to Gentoo? it doesn't live on our infra. Both those things are "things employed by users for their systems". Neither of those things are integral to any

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-13 Thread Michał Górny
On Sun, 2020-09-13 at 20:31 +0200, Thomas Deutschmann wrote: > You maybe all remember what happened to stable-bot: Years ago, > kensington created stable-bot on his own as PoC which revolutionized the > way how we do package stabilization in bugzilla. The service run on his > own infrastructure.

Re: [gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-13 Thread Alec Warner
On Sun, Sep 13, 2020 at 11:31 AM Thomas Deutschmann wrote: > Hi, > > TL;DR: jstein asked council [Bug 729062] for a motion that any service > and software which is critical for Gentoo should be developed/run in > Gentoo namespace. Because any request to council must be discussed I > volunteered

[gentoo-dev] [RFC] Services and software which is critical for Gentoo should be developed/run in Gentoo namespace

2020-09-13 Thread Thomas Deutschmann
Hi, TL;DR: jstein asked council [Bug 729062] for a motion that any service and software which is critical for Gentoo should be developed/run in Gentoo namespace. Because any request to council must be discussed I volunteered to bring this topic to the mailing list (sorry for the huge delay!).