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

2023-08-28 Thread Maxim Cournoyer
Hi, Saku Laesvuori writes: [...] > I agree on the ChangeLogs being a weird thing to require in commit > messages. I think of commit messages as the place where you record the > reasons behind the change in the commit. The ChangeLog seems to just > record the changes which the diff of the commit

Opportunity For Guix: RFI Areas of long-term focus and Prioritization

2023-08-28 Thread jgart
Hi Guixers, Just reposting this chat message from Ryan Prior over #guix for anyone interested: > The US Federal government has an RFI open on "Areas of long-term focus and > Prioritization". They're looking for 10 page briefing memos on supporting > memory-safe languages, strengthening softwar

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

2023-08-28 Thread paul
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 import manag

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

2023-08-28 Thread paul
Hi Katherine , thank you for bringing this up. I too am somewhat of a contributor since about 2019 and I completely agree with your points. From reading this discussion it appears sourcehut supporting both the web and email workflow and being free software is really the best solution. It appea

Re: documentation in TeX Live collections

2023-08-28 Thread Andreas Enge
Hello, Am Mon, Aug 28, 2023 at 06:54:35PM +0200 schrieb Nicolas Goaziou: > Emmanuel Beffara writes: > > I don't understand how "out" and "doc" are different in this respect. The > > "out" output of a collection meta-package has no content of its own and it > > only serves to gather the "out" outp

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Nicolas Goaziou writes: > Emmanuel Beffara writes: >>> In any case, I suggest to write a proper bug report for this. Hopefully, >>> someone with better understanding about the implications of GUIX_TEXMF >>> will be able to solve this. >> >> I can do that for the texdoc behaviour. By the way, I

Re: (computed-origin-method) and (origin)'s file-name field

2023-08-28 Thread Simon Tournier
Hi, On Sun, 27 Aug 2023 at 20:25, Adam Faiz wrote: > Must the 'computed-origin-method' workaround be solved by adding the > renaming capability to snippets? > > Why couldn't the file-name field of the source origin be used to > rename it? > > If it's because the upstream source might be confused

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

2023-08-28 Thread Simon Tournier
Hi, On Fri, 25 Aug 2023 at 09:31, Attila Lendvai wrote: > 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. First, please note that thanks to tireless Chris work about QA, testing is not hard! C

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

2023-08-28 Thread Simon Tournier
Hi, On Fri, 25 Aug 2023 at 18:39, Katherine Cox-Buday wrote: > 2. Remember the email address (it might seem silly unless you have forms > of dyslexia. is it guix-patches? or patches-guix? Wait, what was I doing?) > 3. And then the whole deal with what to do with follow ups. For what it is wor

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

2023-08-28 Thread Simon Tournier
Hi, On Sat, 26 Aug 2023 at 19:42, kias...@disroot.org wrote: > I would like to hear from committers if non-committer reviews are > helpful, because I don't really know how or what I can comment on for > incoming patches on packages I'm not really familiar with. Well, I do not have enough commi

Re: collection of “guix pull“ bug reports

2023-08-28 Thread Simon Tournier
Hi Maxim, On Sat, 26 Aug 2023 at 22:34, Maxim Cournoyer wrote: >> https://issues.guix.gnu.org/issue/62830 >> https://issues.guix.gnu.org/issue/63451 >> https://issues.guix.gnu.org/issue/63830 >> https://issues.guix.gnu.org/issue/64489 >> https://issues.guix.gnu.org/issue/64659 >> https://issues.

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

2023-08-28 Thread Simon Tournier
Hi, On Thu, 24 Aug 2023 at 02:18, Csepp wrote: > By the way, that's another issue. Using a TeX based document format for > the docs is, uuuh, maybe not the best idea. Info is a pretty okayish > documentation reader, but it's a relatively big barrier to entry > compared to what you need to know

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

2023-08-28 Thread Simon Tournier
Hi Katherine, On Fri, 25 Aug 2023 at 19:02, Katherine Cox-Buday wrote: > I think there's utility in distinguishing between familiarity and > eliminating toil. I think it was incorrect of me to suggest forming > habits in my original message. I think it's better to focus on > eliminating toil

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

2023-08-28 Thread Liliana Marie Prikler
Am Montag, dem 28.08.2023 um 10:15 +0200 schrieb Giovanni Biscuolo: > Liliana Marie Prikler writes: > > > 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 looke

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Emmanuel Beffara writes: > I don't understand how "out" and "doc" are different in this respect. The > "out" output of a collection meta-package has no content of its own and it > only serves to gather the "out" outputs of its inputs. Similarly, the "doc" > output would have no content of its own

Re: Updates for Go

2023-08-28 Thread Katherine Cox-Buday
On 8/27/23 9:41 AM, wolf wrote: Sure, golang compiles faster than C++ for example, but anecdotal data point: at $DAYJOB we had to start persisting the compiler cache to make CI fast enough. I've seen similar things done at companies. This is perhaps an interesting avenue to pursue later: if Go

Re: Updates for Go

2023-08-28 Thread Katherine Cox-Buday
On 8/25/23 6:29 PM, John Kehayias wrote: I've not been following in detail this discussion, but where do we currently stand? Is the proposed Go 1.21 patch basically ready? As far as I know, yes. I've been using it locally since I submitted the patch, and things seem to be working as expected.

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

2023-08-28 Thread Giovanni Biscuolo
Hi, interesting thread: thank you very much to all for the comments and tips! For email based patch workflow one and two things are indispensable: a mailbox and a MUA capable of piping a message to a command (git am); this is the one and only obstacle for contrubutors who are accustomed to less t

Re: GDB-multiarch

2023-08-28 Thread Ekaitz Zarraga
ElenQ Technology Ethical Innovation --- Original Message --- On Monday, August 28th, 2023 at 11:04 AM, 宋文武 wrote: > Ekaitz Zarraga eka...@elenq.tech writes: > > > Hi all, > > > > As you might know I'm talking part on the RISC-V bootstrapping efforts in > > Guix. > > This makes

Re: GDB-multiarch

2023-08-28 Thread 宋文武
Ekaitz Zarraga writes: > Hi all, > > As you might know I'm talking part on the RISC-V bootstrapping efforts in > Guix. > This makes me need a multi-architecture GDB. So I made this simple package: > > ``` scheme > (define-module (gdb) > #:use-module (gnu packages) > #:use-module (gnu package

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Hello, Emmanuel Beffara writes: > Yet, as far as I know, most packages in Guix (apart from texlive-* ones) come > with their documentation, so it feels somewhat inconsistent. Every texlive-* package comes with its documentation, in a separate output. "doc" output are not uncommon at all in Guix

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

2023-08-28 Thread Giovanni Biscuolo
Liliana Marie Prikler writes: > 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