Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread Maxim Cournoyer
Hi, Csepp writes: [...] > but as soon as something breaks, you are thrown into the deep end, > having to dissect logs, bisect commit ranges, learn strace, gdb (which > still doesn't work well on Guix) Hm? Why GDB on Guix may be sometimes more challenging than say, on Fedora, I only know of

Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread Attila Lendvai
> > > straight out forgotten/ignored submissions (khm). especially if > > > it's about some hw or some sw that none of the committers care > > > about, or could test locally (e.g. Trezor support: > > > https://issues.guix.gnu.org/65037 that > > > doesn't even build in master). > > Do you mean

Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread Liliana Marie Prikler
Hi kiasoc5, hi Attila Am Samstag, dem 26.08.2023 um 19:42 +0200 schrieb kias...@disroot.org: > On 2023-08-25 11:31, Attila Lendvai wrote: > > > I feel like the advantages of a email-based workflow nowadays is > > > more on the maintainer side of things (as managing large projects > > > is easier

Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread kiasoc5
On 2023-08-25 11:31, Attila Lendvai wrote: I feel like the advantages of a email-based workflow nowadays is more on the maintainer side of things (as managing large projects is easier another thing worth pointing out here is that the harder it is to test a submitted patchset locally, the

Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread kiasoc5
On 2023-08-24 08:33, ( wrote: Katherine Cox-Buday writes:     I can't ever seem to get the GNU style commit messages correct. I use the     templates provided, but those don't cover all cases, and I've even gotten     feedback in a review to change a message it created. You do get used to

Re: How can we decrease the cognitive overhead for contributors?

2023-08-26 Thread Liliana Marie Prikler
Am Freitag, dem 25.08.2023 um 08:07 + schrieb Attila Lendvai: > i couldn't even find out which tools are used by those who are > comfortable with the email based workflow. i looked around once, even > in the manual, but maybe i should look again. Users who have tried curlbash also looked at

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/24/23 12:53 PM, Simon Tournier wrote: Hi, At some point, I sympathize. On Wed, 23 Aug 2023 at 10:25, Katherine Cox-Buday wrote: I don't use the email-based patch workflow day-to-day, so this is another area where I spend a lot of time trying to make sure I'm doing things correctly.

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/24/23 12:33 AM, ( wrote: * We could support a managed web-based workflow The problem with this is that it would not be possible without changing the git hosting entirely to something like Gitea. I'm personally a fan of the email-based workflow; what, specifically, is it that bothers you

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/23/23 9:33 PM, Ahmed Khanzada via Development of GNU Guix and the GNU System distribution. wrote: My wife and I are currently trying, so I hope to be a busy parent soon too! Good luck to you! The debate comes down to: the people contributing the most code already have a very familiar

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/24/23 6:10 PM, Ekaitz Zarraga wrote: Lots of important use cases that Guix could serve are ignored because the people who need them are not represented in our community and/or they can't contribute and no one is able/willing to write code for them.

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/23/23 6:18 PM, Csepp wrote: * Contributing to Guix is not for you     I would be really sad if someone ever said this, but I guess it's a     possibility. Maybe someone like me just can't be a contributor to Guix until     I have the bandwidth to manage all the details. I would

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/25/23 3:57 AM, Attila Lendvai wrote: Otherwise I do not get your point: I keep untreated messages with the latest patch version in my Guix inbox, and file away the others in a separate mbox. So things are not flat, but have two levels: "to be treated" or "done". my point is that in a PR

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/23/23 12:03 PM, Andreas Enge wrote: Hello, Am Wed, Aug 23, 2023 at 10:27:31AM -0700 schrieb Felix Lechner via Development of GNU Guix and the GNU System distribution.: I can't ever seem to get the GNU style commit messages correct. Neither can I. The style apparently helps with

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Katherine Cox-Buday
On 8/23/23 11:27 AM, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote: * Encourage upstream communities like "Guix 'R Us" Every contributor should have their own channels for packages [1] and for Guix. [2] Testing patches before they are submitted would vastly

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Wilko Meyer
Hi Attila, Attila Lendvai writes: > i couldn't even find out which tools are used by those who are > comfortable with the email based workflow. i looked around once, even > in the manual, but maybe i should look again. I can only speak for myself here, but I tend to use magit[0] from inside

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Attila Lendvai
> For this, I either go to issues.guix.gnu.org to download the newest patches, > in case the message is not in my inbox. some patchsets evolve a lot, and there are countless messages where obsolete patche versions are intermingled with non-obsolete discussion... > Otherwise I do not get your

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Attila Lendvai
> I feel like the advantages of a email-based workflow nowadays is more on > the maintainer side of things (as managing large projects is easier another thing worth pointing out here is that the harder it is to test a submitted patchset locally, the fewer non-committer reviews will happen. and

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Andreas Enge
Hello, just a quick reply with what I do personally as one irrelevant data point :) Am Fri, Aug 25, 2023 at 08:07:53AM + schrieb Attila Lendvai: > i couldn't even find out which tools are used by those who are comfortable > with the email based workflow. i looked around once, even in the

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Attila Lendvai
> 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

Re: How can we decrease the cognitive overhead for contributors?

2023-08-25 Thread Attila Lendvai
another +1 for the general sentiment of Katherine's message. > I am all for it if it supplements the email based workflow (every > time I need to do a modern style pull request type action, I am > completely out of my depths and lost in the web interfaces...). in my experience learning the

Re: How can we decrease the cognitive overhead for contributors?

2023-08-24 Thread Ekaitz Zarraga
Hi, > This definitely falls into the IDE tooling issue that I complained about > a bunch of times. There seems to be a reality distortion field around > Lisp that makes some users believe that s-expressions automatically lead > to a good IDE experience. And yet, Java IDEs have had automatic

Re: How can we decrease the cognitive overhead for contributors?

2023-08-24 Thread Csepp
Katherine Cox-Buday writes: > Summary: for people who don't contribute to Guix a lot, each > contribution has > very high cognitive overhead. Can we work to reduce that? > > Hey all, > > Contributing to Guix is currently pretty difficult for me. I'm a Mom with a > full-time job, and anything

Re: How can we decrease the cognitive overhead for contributors?

2023-08-24 Thread Simon Tournier
Hi, At some point, I sympathize. On Wed, 23 Aug 2023 at 10:25, Katherine Cox-Buday wrote: > I don't use the email-based patch workflow day-to-day, so this is > another area where I spend a lot of time trying to make sure I'm doing > things correctly. I agree that Debbugs is not handy at

Re: How can we decrease the cognitive overhead for contributors?

2023-08-24 Thread Wilko Meyer
Hi Katherine, Katherine Cox-Buday writes: > That last part is what I wanted to discuss, because > that's the part > that prevents me from contributing more than I do, and I think there are > probably others whom are impacted by this. Yes, I'd actually love contributing more to Guix; but even

Re: How can we decrease the cognitive overhead for contributors?

2023-08-24 Thread (
Katherine Cox-Buday writes: >     I signed up on Savannah with the intention of applying to be a committer. >     Savannah closed my account one or two days later due to inactivity. That happened to me, too :| >     I can't ever seem to get the GNU style commit messages correct. I use the >    

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Development of GNU Guix and the GNU System distribution.
My wife and I are currently trying, so I hope to be a busy parent soon too! What you have mentioned is a big problem with contributing to anything GNU. It's hard for people that are familiar with the frictionless approach of GitHub pull requests to adapt to the decentralized mailing list approach

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Jack Hill
Katherine, Thanks for starting this thread! I'd like to offer my perspective on mistake making (of course it's OK, but definitely less fun to repeatedly make the same mistakes over again rather than new, interesting ones): My personal experience is the initial steps to submitting a

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Ricardo Wurmus
Katherine Cox-Buday writes: > * We could support a managed web-based workflow I started packaging some requirements of sourcehut. I’d be happy to retire mumi + debbugs and use whatever sourcehut offers if we can host it. I haven’t ever used sourcehut things, but I hear they are good for

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Liliana Marie Prikler
Hi Katherine, Am Mittwoch, dem 23.08.2023 um 10:25 -0600 schrieb Katherine Cox-Buday: > Summary: for people who don't contribute to Guix a lot, each > contribution has very high cognitive overhead. Can we work to reduce > that? > > Hey all, > > Contributing to Guix is currently pretty

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Andreas Enge
Hello, Am Wed, Aug 23, 2023 at 10:27:31AM -0700 schrieb Felix Lechner via Development of GNU Guix and the GNU System distribution.: > > I can't ever seem to get the GNU style commit messages correct. > Neither can I. The style apparently helps with automated maintenance > of the changelog,

Re: How can we decrease the cognitive overhead for contributors?

2023-08-23 Thread Development of GNU Guix and the GNU System distribution.
Hi Katherine, On Wed, Aug 23, 2023 at 9:27 AM Katherine Cox-Buday wrote: > > I'm a Mom Congratulations, and thanks for dedicating your life to someone else! > Savannah closed my account one or two days later due to inactivity. That happened to me too, although it took a couple of weeks.

<    1   2   3