Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Maxim Cournoyer
Hi, Simon Tournier writes: > Hi, > > On Wed, 13 Sep 2023 at 21:14, Liliana Marie Prikler > wrote: > >> I do wonder how the ChangeId would work in practice. Since it's not >> really assigned by the committer, it would have to be generated "on the >> fly" and attached to the mail in between,

Swineherd: Guix System container manager

2023-09-13 Thread Ricardo Wurmus
Hi there, you know the Shepherd: it is an elegant service manager looking after a herd of daemons. Since it can be extended with Guile, I decided to do just that to add an extra skill to the Shepherd, turning it into the Swineherd. The Swineherd is a manager of Guix System containers. It is

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Giovanni Biscuolo
Hi Liliana and Maxim, Liliana Marie Prikler writes: [...] > The thing is, we're discussing the same basic workflow No, we are discussing two (complementary) workflows: 1. the one I suggested to add a "footer-metadata-field" named Fix/Fixes/Close/Closes/whatever that will allow people pushing

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

2023-09-13 Thread Simon Tournier
Hi Katherine, On Tue, 12 Sep 2023 at 10:05, Katherine Cox-Buday wrote: > And these are subjective statements, which are bad to rest decisions on. > I have the opinion that this style of commit message is difficult and > doesn't have a lot of value; others think it's easy and find a lot of >

Re: Mumi CLI client (was: How can we decrease the cognitive overhead for contributors?)

2023-09-13 Thread Ricardo Wurmus
Giovanni Biscuolo writes: > AFAIU mumi does not (still?) have ad authentication/authorization, > right? > > If so how do you plan to deal with users posting SPAM or similar > unappropriate content? It only sends email on behalf of commenters, so we’re using the same email mechanism to deal

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

2023-09-13 Thread Fannys
Ekaitz Zarraga writes: >> > This is what I mean when I say many times emacs is kind of mandatory, >> > and >> > this thread is kind of a demonstration of what I meant because the main >> > discussion evolved to: you can use this or that in emacs to ease the >> > dev >> > experience. >> >> >>

Commenting bug reports via mumi web interface (was: How can we decrease the cognitive overhead for contributors?)

2023-09-13 Thread Giovanni Biscuolo
Hi Ricardo, Ricardo Wurmus writes: > Giovanni Biscuolo writes: > >> AFAIU mumi does not (still?) have ad authentication/authorization, >> right? >> >> If so how do you plan to deal with users posting SPAM or similar >> unappropriate content? > > It only sends email on behalf of commenters, so

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

2023-09-13 Thread Simon Tournier
Re, On Wed, 13 Sep 2023 at 09:57, Simon Tournier wrote: > Somehow, the line is drawn using a two-axis plot of “easy vs boring” > when instead we should draw a two-axis plot of “complexity vs capture > the values”. I meant, the thread is considering a one-axis plot using a subjective parameter

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

2023-09-13 Thread MSavoritias
Ekaitz Zarraga writes: >> > This is what I mean when I say many times emacs is kind of mandatory, >> > and >> > this thread is kind of a demonstration of what I meant because the main >> > discussion evolved to: you can use this or that in emacs to ease the >> > dev >> > experience. >> >> >>

Re: performance issue with TeX Live

2023-09-13 Thread Emmanuel Beffara
De Olivier Dion le 12/09/2023 à 19:11: > On Tue, 12 Sep 2023, Emmanuel Beffara wrote: > > Hello Guix devel, > > > > I am facing a severe performance issue with TeX Live: compilation of any > > document is an order of magnitude slower with a Guix installed system as > > compared to a manual

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

2023-09-13 Thread MSavoritias
Simon Tournier writes: > Hi, > > On Tue, 29 Aug 2023 at 12:53, MSavoritias wrote: > >> Do you know if there are any plans to write a scheme bug/patching >> system? Because looking a bit into it, it doesn't seem like its that >> actively developed so maybe we would be better served by one in

Re: performance issue with TeX Live

2023-09-13 Thread Nicolas Goaziou
Hello, Emmanuel Beffara writes: > I am facing a severe performance issue with TeX Live: compilation of any > document is an order of magnitude slower with a Guix installed system as > compared to a manual installation. Is anyone confronted to this phenomenon, or > is there a way to fix this ?

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Maxim Cournoyer
Hi Giovanni, Giovanni Biscuolo writes: [...] Liliana Marie Prikler writes: > > WDYT about the following >   Applies: [patch] >   Closes: [patch] >   Resolves: [patch] >   Done: [patch] [...] > Anyway, I agree with Liliana that having more keyworks will help

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

2023-09-13 Thread MSavoritias
I dont think we need to compare things here. Of course we should be able to make lives easier for reviewers and contributors. There is no need here to compare them. Remember that making lives easier for contributors will make lives easier for reviewers too after all :) Because more correct

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

2023-09-13 Thread MSavoritias
Simon Tournier writes: > Hi Katherine, > > Thank you for your extensive analysis. I concur. > > On Wed, 30 Aug 2023 at 10:11, Katherine Cox-Buday > wrote: > >> 3. We should reify a way for Guix, the project, to measure, and track >> progress, >>    against long-term goals. Particularly

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

2023-09-13 Thread Maxim Cournoyer
Hi Fannys, Fannys writes: > Ekaitz Zarraga writes: > >>> > This is what I mean when I say many times emacs is kind of mandatory, >>> > and >>> > this thread is kind of a demonstration of what I meant because the main >>> > discussion evolved to: you can use this or that in emacs to ease the

Re: Swineherd: Guix System container manager

2023-09-13 Thread Katherine Cox-Buday
On 9/13/23 3:06 AM, Ricardo Wurmus wrote: Hi there, you know the Shepherd: it is an elegant service manager looking after a herd of daemons. Since it can be extended with Guile, I decided to do just that to add an extra skill to the Shepherd, turning it into the Swineherd. The Swineherd is a

Re: Swineherd: Guix System container manager

2023-09-13 Thread Thompson, David
Hey, nice job Ricardo! This looks awesome! On Wed, Sep 13, 2023 at 11:29 AM Katherine Cox-Buday wrote: > > On 9/13/23 3:06 AM, Ricardo Wurmus wrote: > > Hi there, > > > > you know the Shepherd: it is an elegant service manager looking after a > > herd of daemons. Since it can be extended with

Implementing the guix-dameon in Guile

2023-09-13 Thread Christopher Baines
Hey! I think this has been talked about for a while [1], but I want to make it happen. Currently the guix-daemon is still similar to the nix-daemon that it was forked from, and is implemented in C++. I think that a Guile implementation of the guix-daemon will simplify Guix and better support

Re: Implementing the guix-dameon in Guile

2023-09-13 Thread Development of GNU Guix and the GNU System distribution.
Hi Chris, On Wed, Sep 13, 2023 at 9:29 AM Christopher Baines wrote: > > Rewrites are risky because you only get the value right at the end, > therefore the priority is to get a minimal but viable implementation in > Guile that can be switched to Sounds exciting! I would like to help with

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Maxim Cournoyer
Hi Liliana, Liliana Marie Prikler writes: > Hi Maxim, > > Am Montag, dem 11.09.2023 um 16:41 -0400 schrieb Maxim Cournoyer: >> [...] >> Perhaps both approach[es] could be combined.  I still see value in a >> general scheme to automate closing applied series that linger on in >> Debbugs. >> >>

to PR or not to PR, is /that/ the question?

2023-09-13 Thread Giovanni Biscuolo
Hi Simon, please forgive me if I continue drifting in this beautiful sea... This message is /very/ long but it's just because I'm trying to do my best to provide a deep analisys of the **big** problems with eventually adopting a «web based PR model» (please see below for a definition) for

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Maxim Cournoyer
Hi, Vagrant Cascadian writes: > On 2023-09-09, Maxim Cournoyer wrote: >> Vagrant Cascadian writes: Did you see my message about integrating a commit-hook similar to what Gerrit uses? It produces unique ID such as: --8<---cut

Re: Implementing the guix-dameon in Guile

2023-09-13 Thread Maxim Cournoyer
Hi! Felix Lechner via "Development of GNU Guix and the GNU System distribution." writes: > Hi Chris, > > On Wed, Sep 13, 2023 at 9:29 AM Christopher Baines wrote: >> >> Rewrites are risky because you only get the value right at the end, >> therefore the priority is to get a minimal but viable

Re: Swineherd: Guix System container manager

2023-09-13 Thread Ricardo Wurmus
> Can you share any ways you're currently using this? We had been using this at work as part of a much bigger training platform to launch customizable (but still reproducible) interactive environments for workshops and courses. An example is pre-configured RStudio installations with shared

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Liliana Marie Prikler
Am Mittwoch, dem 13.09.2023 um 11:27 -0400 schrieb Maxim Cournoyer: > For just closing cross-referenced bugs, I agree.  For closing > forgotten, already merged issues on guix-patches we'd need the > Change-Id and a tool able to map Change-Ids -> issue number (mumi is > in the best place to do so).

Re: Swineherd: Guix System container manager

2023-09-13 Thread Simon Tournier
Hi Ricardo, On Wed, 13 Sep 2023 at 11:06, Ricardo Wurmus wrote: [...] > > The Swineherd was designed to be used with Shepherd on foreign distros, > so it does not assume to be running on top of Guix System (for better or > worse). Oh! It is very promising. Really cool! > Of course the

Re: Implementing the guix-dameon in Guile

2023-09-13 Thread Vagrant Cascadian
On 2023-09-13, Christopher Baines wrote: > I think this has been talked about for a while [1], but I want to make it > happen. Currently the guix-daemon is still similar to the nix-daemon > that it was forked from, and is implemented in C++. I think that a Guile > implementation of the guix-daemon

Re: [workflow] Automatically close bug report when a patch is committed

2023-09-13 Thread Simon Tournier
Hi, On Wed, 13 Sep 2023 at 21:14, Liliana Marie Prikler wrote: > I do wonder how the ChangeId would work in practice. Since it's not > really assigned by the committer, it would have to be generated "on the > fly" and attached to the mail in between, which could result in all > kinds of nasty

Re: to PR or not to PR, is /that/ the question?

2023-09-13 Thread Simon Tournier
Hi Giovanni, Thank you for your detailed message. Sorry, I have not read all the details because I have been lost. What do you want to explain? Well, let me explain my understanding using my own words. :-) When one reduces to the core of the workflows, the main difference between “email

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

2023-09-13 Thread Ekaitz Zarraga
Hi, On Wednesday, September 13th, 2023 at 3:42 PM, Maxim Cournoyer wrote: > > There's no lock-in. You can use any tool you want. Most people hacking > on Guix do so with Emacs and Geiser because these are currently the best > tools (that I know of) to do the job; these are the tools many of

Cuirass actors

2023-09-13 Thread Ludovic Courtès
Hello Guix! My (useful? misguided? questionable?) quest around Cuirass has led me closer to some of the goals mentioned in my previous message¹ and in the ‘TODO’ file². The ‘wip-actors’ branch³, which I plan to merge soon, splits activities of the ‘cuirass register’ process among several actors.