public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Disturbing state of arch testing in Gentoo
Date: Mon, 7 Nov 2022 00:07:16 -0600	[thread overview]
Message-ID: <Y2iglBk6oBw4urQ3@dj3ntoo> (raw)
In-Reply-To: <97f832e7-a14d-9bb9-b0c3-59008f445677@gentoo.org>

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

On Sun, Nov 06, 2022 at 11:37:24 +0100, Piotr Karbowski wrote:
> I would be in favour of stepping up the social contract and actually 
> prohibiting this kind of things, we had that before too, the nattka you 
> mgorny wrote is replacement for old bugzilla bot that was ... 
> closedsource and perished, though nattka now have way more features than 
> the old thing ever had.

As a user, I think it would be really cool if there was a requirement
that all infra and infra-adjacent stuff was free software.

I feel like I've read that Debian already has something like this. While
doing some quick searches I didn't find a full-on requirement, but all
their infra bits I did find were powered by free software. The most
relevant ones being buildd [1] and debci [2]. Additionally, the debci
docs has inctructions on reproducing tests yourself [3] which is a nice
extra IMO.

[1] https://buildd.debian.org
[2] https://ci.debian.net
[3] https://ci.debian.net/doc/file.MAINTAINERS.html

- Oskari

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

  reply	other threads:[~2022-11-07  6:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  8:15 [gentoo-dev] Disturbing state of arch testing in Gentoo Michał Górny
2022-11-06  8:34 ` Sam James
2022-11-08  4:58   ` Arthur Zamarin
2022-11-06 10:37 ` Piotr Karbowski
2022-11-07  6:07   ` Oskari Pirhonen [this message]
2022-11-07  6:26     ` Joonas Niilola
2022-11-07 15:13       ` John Helmert III
2022-11-08  7:40       ` Oskari Pirhonen
2022-11-07 23:16     ` Sam James
2022-11-08  0:23       ` Rich Freeman
2022-11-08  0:30         ` Sam James
2022-11-08  0:34         ` John Helmert III
2022-11-08  0:54           ` Rich Freeman
2022-11-08  6:06         ` Joonas Niilola
2022-11-08 13:26         ` Michał Górny
2022-11-08 13:55           ` Agostino Sarubbo
2022-11-06 13:27 ` John Helmert III
2022-11-06 19:03   ` Agostino Sarubbo
2022-11-06 19:15     ` John Helmert III
2022-11-06 18:50 ` Agostino Sarubbo
2022-11-08  8:43 ` Agostino Sarubbo
2022-11-08 15:18   ` John Helmert III

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=Y2iglBk6oBw4urQ3@dj3ntoo \
    --to=xxc3ncoredxx@gmail.com \
    --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