[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How can we decrease the cognitive overhead for contributors?
From: |
Maxim Cournoyer |
Subject: |
Re: How can we decrease the cognitive overhead for contributors? |
Date: |
Sat, 26 Aug 2023 23:27:58 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Hello,
Attila Lendvai <attila@lendvai.name> writes:
>> Now you might say that this leads to less diversity in the team of
>> committers and maintainers as you need a certain level of privilege to
>> seriously entertain the idea of dedicating that much time and effort to
>> a project and I agree, but I also think this is a bigger reality of
>> volunteer work in general.
>
>
> the ultimate goal is not just diversity, but high efficiency of the
> people who cooperate around Guix, which then translates into a better
> Guix.
>
> if the "rituals" around Guix contribution were merely a steep initial
> learning curve, then one could argue that it's a kind of filter that
> helps with the signal to noise ratio. but i think it's also a constant
> hindrance, not just an initial learning curve.
>
>
>> Just because it's brought up a lot of times doesn't mean it's a good
>> idea. There is a lot of good things that can be done for our web-based
>> front ends; improving the search results on issues.guix.gnu.org would
>> be one of them. However, I have little hopes for a web based means to
>> submit contributions. I think email should be a format that's
>> understood by folks who know how to operate a web browser.
>
>
> again, i would press the argument that it's not about being able to,
> but about how much effort/attention is wasted on administration
> (i.e. not on hacking). i often have the impression that it took
> comparable effort to submit a smaller to mid size patch than making
> it.
In the simplest case, it can be as simple as:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix refresh -u some-package
[build it, try it, fix if needed]
$ ./etc/committer.scm
$ git send-email
--8<---------------cut here---------------end--------------->8---
Since it's a single patch, there's no jumping through hoops to create
the original issue, and the auto-configured git will CC teams people
subscribed to the scope of your change (if there are any).
--
Thanks,
Maxim
Re: How can we decrease the cognitive overhead for contributors?, Katherine Cox-Buday, 2023/08/25
Re: How can we decrease the cognitive overhead for contributors?, Liliana Marie Prikler, 2023/08/23
Re: How can we decrease the cognitive overhead for contributors?, Ricardo Wurmus, 2023/08/23
Re: How can we decrease the cognitive overhead for contributors?, Ahmed Khanzada, 2023/08/23
Re: How can we decrease the cognitive overhead for contributors?, (, 2023/08/24
Re: How can we decrease the cognitive overhead for contributors?, (, 2023/08/28