1 |
> On 8 Nov 2022, at 00:23, Rich Freeman <rich0@g.o> wrote: |
2 |
> |
3 |
> On Mon, Nov 7, 2022 at 6:16 PM Sam James <sam@g.o> wrote: |
4 |
>> |
5 |
>>> On 7 Nov 2022, at 06:07, Oskari Pirhonen <xxc3ncoredxx@×××××.com> wrote: |
6 |
>>> |
7 |
>>> On Sun, Nov 06, 2022 at 11:37:24 +0100, Piotr Karbowski wrote: |
8 |
>>>> I would be in favour of stepping up the social contract and actually |
9 |
>>>> prohibiting this kind of things, we had that before too, the nattka you |
10 |
>>>> mgorny wrote is replacement for old bugzilla bot that was ... |
11 |
>>>> closedsource and perished, though nattka now have way more features than |
12 |
>>>> the old thing ever had. |
13 |
>>> |
14 |
>>> As a user, I think it would be really cool if there was a requirement |
15 |
>>> that all infra and infra-adjacent stuff was free software. |
16 |
>>> |
17 |
>>> I feel like I've read that Debian already has something like this. While |
18 |
>>> doing some quick searches I didn't find a full-on requirement, but all |
19 |
>>> their infra bits I did find were powered by free software. The most |
20 |
>>> relevant ones being buildd [1] and debci [2]. Additionally, the debci |
21 |
>>> docs has inctructions on reproducing tests yourself [3] which is a nice |
22 |
>>> extra IMO. |
23 |
>> |
24 |
>> Gentoo has https://www.gentoo.org/get-started/philosophy/social-contract.html. |
25 |
> |
26 |
> I feel like something like a dev-run tinderbox is a bit out of the |
27 |
> scope of that. |
28 |
|
29 |
I intentionally didn't comment on the scope for now, but I'm glad you did. |
30 |
|
31 |
> |
32 |
> Suppose I file a bug against a package, pointing out some issue in it. |
33 |
> How do you know I didn't use some proprietary static code analysis |
34 |
> tool to discover that error? Does it even really matter? The bug |
35 |
> speaks for itself. It is like worrying about whether somebody who |
36 |
> filed a bug was running Windows or another proprietary OS or browser |
37 |
> on their desktop. |
38 |
> |
39 |
|
40 |
It matters if someone can't then reproduce the bug which happens |
41 |
somewhat often here. |