Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg

Hello Carlo, > I don't think this is a fair summary of the goal. The first sentence of > the GCD[1] is: > > The contribution workflow in Guix has been facing several challenges: > difficult onboarding, lack of legibility, complex, unreliable, and > labor-intensive infrastructure, and lack of

Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Divya, On Fri, Mar 07 2025, Divya Ranjan via Guix-patches via wrote: > To achieve our goal of helping newcomers, [...] I don't think this is a fair summary of the goal. The first sentence of the GCD[1] is: The contribution workflow in Guix has been facing several challenges: difficult onb

Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg

Hello Guix devs, I concur with Ekaitz’s observation: > We would be pushing that complexity only to committers, not to > ocasional contributors, which may help attracting people. But, on the > other hand, we would force people who is already very busy (and very > efficient with their current workf

Re: Packaging golang applications - multi-stage build?

Hi Hilton, On Thu, Mar 06 2025, Hilton Chain wrote: > I understand that feeling. I agree current packaging model doesn't suits Go > ecosystem well. I also have a ‘go mod vendor’-based fetcher implementation > kept > in my notes. > > But as a distribution, knowing little about dependencies is no

Re: How to move forward about Rust? antioxidant, cargo2guix, etc.

On Fri, 07 Mar 2025 04:54:43 +0800, Murilo wrote: > > On Thu Mar 6, 2025 at 2:24 PM -03, Efraim Flashner wrote: > > On Wed, Mar 05, 2025 at 09:20:50PM +0800, Hilton Chain wrote: > >> 1. Unpack package source then update lockfile: > >> --8<---cut here---start->8--

Re: How to move forward about Rust? antioxidant, cargo2guix, etc.

On Thu Mar 6, 2025 at 2:24 PM -03, Efraim Flashner wrote: > On Wed, Mar 05, 2025 at 09:20:50PM +0800, Hilton Chain wrote: >> 1. Unpack package source then update lockfile: >> --8<---cut here---start->8--- >> cargo generate-lockfile >> --8<---cut here-

Amending GCD (was Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg)

Hi, On Sun, 02 Mar 2025 at 22:54, Ludovic Courtès wrote: >> This contradicts GCD 001 no? The 001 requires the GCD to be sent as >> patch to guix-patc...@gnu.org. How will this be handled? > > I think we would amend GCD 001 to change references to the email > workflow with references to the Cod

Meeting regarding qa.guix.gnu.org and related things

Hey, Thanks to Felix's initiative, 4 of us met up today and discussed QA and related things, I think the discussion went well. I said I'd suggest a time for meeting up next, how about the same time (0900h Pacific, 1200h Eastern, 1700h London and 1800h Central European) on Tuesday the 18th of Marc

Re: ngspice GUI?

On 2025-03-06 18:55, Christopher Howard wrote: Hi, is ngspice supposed to have a GUI? Is our package a minimalistic version without one? The tutorials I'm following seem to show a gui of some sort, or the ability to display simulation results in a gui graph, so I'm wondering about that. Insid

ngspice GUI?

Hi, is ngspice supposed to have a GUI? Is our package a minimalistic version without one? The tutorials I'm following seem to show a gui of some sort, or the ability to display simulation results in a gui graph, so I'm wondering about that. Inside ngspice command line interpreter, if I try to s

Re: Golang packaging, following up Rust conversation on packaging

On Wed, 26 Feb 2025 05:35:29 +0800, Sharlatan Hellseher wrote: > > [1 ] > > Hi Guix, > > After reading the thread: > How to move forward about Rust? antioxidant, cargo2guix, etc. > > > I've faced with the fact that Golang had a

Re: Guix booth at JDLL in Lyon, France?

> >> Note that the event is mostly French-speaking. >> >> Thoughts? Volunteers? >> >> I'll bring stickers ;) > > You got me at "French-speaking", but stickers are nice too! 😉 > What about t-shirts? People asked me about that at Guix Days. Some feel that > we > lack a "visual identity" (my words) w

Re: mumi CLI now supports tagging

Arun Isaac writes: > Hi Noé, > >> Seeing closed issues is very important depending on what I’m looking >> for. How about having a colored « open » indicator next to the tags (or >> as a tag)? > > Yes, we could have an "open/closed" indicator badge similar to the tag > badges. I'll implement that

Re: Large rebuilds, nss, and QA

Hello Chris, all, Am Thu, Feb 27, 2025 at 09:18:32PM + schrieb Christopher Baines: > Following on from Andreas's points on difficulty understanding what the > build coordinator is doing, I do want to make some improvements to the > interface to address those issues, and maybe a infra handbook