Re: Shoutout to the organizers!

On Mon, Feb 03, 2025 at 11:26:01PM +0100, Ludovic Courtès wrote: > Hello Guix, > > Huge thanks to the organizers of the Guix Days and the declarative & > minimalistic computing track at FOSDEM, in particular Pjotr as the > overseer máximo (I think I heard him say he’s looking for a successor, >

Re: bug#75851: Don't add propagated-inputs for all outputs

Hi, 宋文武 writes: > Hello, we have a TODO for "extend `propagated-inputs` with support for > multiple outputs". I try to do it for a while, but unable to find a > clear way, since add a new syntax for specify output in > propagated-inputs require changes in too many places.. > > Think about the i

Re: [GCD] Set search paths without program wrappers

Hi Simon, Simon Tournier writes: > Hi, > > On Sun, 02 Feb 2025 at 12:57, 宋文武 via "Development of GNU Guix and > the GNU System distribution." wrote: > >> Hello, when trying to fix some issues caused by program wrappers in >> , it was suggested that I should >>

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

Thank you for taking the time to respond. Ludovic Courtès writes: > even though I’m currently mixing ‘fj.el’ and the dreaded web > interface. Out of curiosity, could you please briefly mention what you're using each for as of now? With the understanding that it's not meant as a recommendation,

Shoutout to the organizers!

Hello Guix, Huge thanks to the organizers of the Guix Days and the declarative & minimalistic computing track at FOSDEM, in particular Pjotr as the overseer máximo (I think I heard him say he’s looking for a successor, just sayin’!), Tanguy as the fearless Guix Foundation treasurer, Jonathan who f

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

Hey Carlo, Carlo Zancanaro skribis: > Moving to using Codeberg for issues and pull requests may mean that the > most "natural" ways of people interacting with the project are more > isolated. For contributors, this has advantages (e.g. less chance of > being overwhelmed by emails), and disadvant

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

Hi, Suhail Singh skribis: > The move to codeberg has the potential to alleviate the rate limiting > step (the throughput of committing patches). This has been discussed. > However, said move also has the potential to reduce the throughput of > reviews. It's not clear that the number of Guix co

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

Hi, Christopher Baines skribis: >> ## Workflow >> >> Once continuous integration (CI) is fully operational, pull requests may >> be merged if and only if they successfully built. “World-rebuild” pull >> requests would still follow the [existing branching >> process](https://guix.gnu.org/manual/

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

Hi Simon, Simon Tournier skribis: > First, since we bounded the various periods, could you be clear about > them? Because, you already found two “sponsors” and the GCD has not > been sent to info-guix, if I read correctly. Like I wrote, I’m anticipating on the GCD process being accepted at all

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

Hi, Liliana Marie Prikler skribis: > Am Dienstag, dem 28.01.2025 um 15:33 +0100 schrieb Ludovic Courtès: >> To keep track of bug reports and patches, Guix historically chose >> tools that were *simple* in their design: >> >>   - bug reports and patches can be sent by plain email, without >>

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

Hi Noé, Noé Lopez skribis: >> SPDX-License-Identifier: CC-BY-SA-4.0 OR GFDL-1.3-no-invariants-only > > GCD#0001 says GFDL 1.3 or later, but has « only » in the license > identifier. So this should be GFDL-1.3-no-invariants-or-later. Or maybe > not, I don’t know the legal implications of saying t

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

Hello, Cayetano Santos skribis: > Given the current work in progress status of tooling at Codeberg side, > would it be feasible to consider a period of time during which the two > strategies overlap ? Kind of a testing cohabitation period. This is more or less what some proposed at the Guix Da

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

Tomas Volf <~@wolfsden.cz> skribis: >> The software behind the forge has to be free software that is >> *plausibly* self-hosted on Guix System—this probably rules out GitLab >> Community Edition > > I am curious about this. GitLab Community Edition is under MIT (so > ticks the free software check

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

Hi Christopher, Codeberg.org / Forgejo does have an API, and there are Emacs interfaces. They are mentioned in the GCD. -- Ricardo

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

Hi Tomas, Tomas Volf <~@wolfsden.cz> skribis: > From more ideological point of view, I think it is a strict downgrade > regarding the entry barrier. The very first thing new contributor needs > to do before contributing to GNU Guix is to read Terms of Service > document of a third party and agre

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

Hi, > Interesting! So, there would be like a 'guix-history' channel that one > could use with time-machine? either that or just keep the current repo at the current location and start fresh at a new location. Lars

Re: bug#75552: Non-committers can't keep authenticated forks updated

On 2025-02-03 16:43, Simon Tournier wrote: > Hi, > > On Fri, 17 Jan 2025 at 22:44, Nicolas Graves wrote: > >> I recently started a guix extension to help manage complexities of >> maintaining guix soft-forks. > > [...] > > >> https://git.sr.ht/~ngraves/guix-stack > > Oh cool! This appears to me

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

There are so many replies on this thread, I don't have time to work through them all. So I just wanted to throw out my concerns: I do host some little projects on Codeberg (none worth listing), but neverthess: - I prefer not to have to use a Web browser interface at all to checks news or issues

Re: bug#75552: Non-committers can't keep authenticated forks updated

Hi, On Fri, 17 Jan 2025 at 22:44, Nicolas Graves wrote: > I recently started a guix extension to help manage complexities of > maintaining guix soft-forks. [...] > https://git.sr.ht/~ngraves/guix-stack Oh cool! This appears to me the right direction. Instead of yet another subcommand, I th

Re: [GCD] Set search paths without program wrappers

Hi, On Sun, 02 Feb 2025 at 12:57, 宋文武 via "Development of GNU Guix and the GNU System distribution." wrote: > Hello, when trying to fix some issues caused by program wrappers in > , it was suggested that I should > discussed the idea and implementation more br

Re: bug#75552: Non-committers can't keep authenticated forks updated

Hi, On Thu, 16 Jan 2025 at 15:34, Liliana Marie Prikler wrote: > lfam: that's interesting that there is really a merge > commit, for example if I remember right, the core updates merge few > months ago happened by directly appending the commits instead of a > merge commit > Yes, there

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

Just for the record, and as for Sourcehut maintainers, "sr.ht is mostly hosted in the Netherlands, with a backup site in the US" -- Cayetano Santos GnuPG Key: https://meta.sr.ht/~csantosb.pgp FingerPrint: CCB8 1842 F9D7 058E CD67 377A BF5C DF4D F6BF 6682 signature.asc Description: PGP signatu