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

Felix, On Fri, Mar 07 2025, Ricardo Wurmus wrote: I'd rather work on Guix. Then why is there a backlog of bugs? This is such an odd thing to ask, I cannot convince myself that it's a serious question asked in good faith. Surely you are not suggesting that my desire to work on Guix rath

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

Hi, I agree with most of Maxim’s message. I add two points. On Tue, 04 Mar 2025 at 20:22, Maxim Cournoyer wrote: > I see the argument that there's an HTTP API for Forgejo; that's great, > but it requires that everyone relearn another way of doing something > that already works well enough for

Re: Scaling issues with forges Was: Trying out Codeberg

On Fri, Mar 07, 2025 at 04:39:34PM +0100, Denis 'GNUtoo' Carikli wrote: > If we look at big projects like Linux, they have faced a similar issue > in the past and as I understand they solved it by using more adapted > tools and processes and they even ended up making their own software > tools (git

Re: Guix booth at JDLL in Lyon, France?

Hi Julien, On Tue Mar 4, 2025 at 11:38 AM CET, Julien Lepiller wrote: > There is a regular event in Lyon, called JDLL (journées du logiciel libre): > . It will happen end of may this year. I’ve never been there! 😱 > We have until march 16 to submit a proposal for a talk or a

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

Divya Ranjan writes: We have a *humongous* backlog of patches, [...] [...] we host a backend service that regularly checks the Codeberg repository for any new issues or PRs and then communicates to us through the Codeberg’s Forgejo API [0] the content of said issues and PRs. The data recei

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

On Fri, 07 Mar 2025 01:24:28 +0800, Efraim Flashner wrote: > > > 4. Check module diff, content of sources marked as TODO and output of > > 'check-for-pregenerated-files phase. > > After the backdoor in xz being hidden in a test tarball I'm not going to > suggest we drop scanning the test directorie

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

Hi Ricardo, On Fri, Mar 07 2025, Ricardo Wurmus wrote: > I'd rather work on Guix. Then why is there a backlog of bugs? I only see a group of software developers unable to close more bugs than are being opened. It's not because of technical limitations, but because the committers are overwhelme

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

Hello, Am Fri, Mar 07, 2025 at 09:40:28AM -0500 schrieb Suhail Singh: > Based on Andreas's observations in [1]: > It seems if we are basing our experimentations on only "trivial patches" > that are sent to , we may not be > observing the instances where a forge-s

Re: Trying out Codeberg

On Thu, 06 Mar 2025 10:10:03 +0900 Maxim Cournoyer wrote: > > Is Docker the only current solution for runners in the CI? This is my understanding from my discussion with neox. > > Having a less generic solution might be better though, like using > > 'guix' or 'debootstrap' to build containers wi

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

Andreas Enge writes: > my observation was rather the inverse: our current debbugs approch > struggles for patch series. Ah, my bad. I mistook "issues" to mean issues on a forge as opposed to a debbugs issue. Thank you for correcting. > Which says nothing about the experience on a forge, logic

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

Ludovic Courtès writes: > As for experimenting, I agree and I reiterate my invitation to send > trivial patches to (or to > Guix-Science, Guix-Past, etc.). I think this GCD’s discussion period is > the right time to give it a try as it can better inform discus

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

Hello, I also agree that we should either not switch, or switch with a short period of overlap. It does not make sense to spread our limited time to work on two systems at the same time. And it definitely does not make sense to spend additional development work (by whom?) to create a bridge betwee

Re: Guix booth at JDLL in Lyon, France?

On 7/03/25 8:53, Tanguy Le Carrour wrote: On Thu Mar 6, 2025 at 1:52 PM CET, Luis Felipe wrote: And it goes with the kakemono. 🤔 The kakemono doesn’t have the lambda sun logo. Do you mean it’s the same yellow? Yes, the color. OpenPGP_0x0AB0D067012F08C3.asc Description: OpenPGP public key

New committer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 We have a C++ team! Has the survey shown that project contributors are happier when members of a team and those patches reviewed more promptly? I find Guix to be a powerful tool with unbounded potential. Thank you to all who have contributed. My par

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

Hi Ricardo, On Fri, Mar 07 2025, Ricardo Wurmus wrote: > Surely you are not suggesting that my desire to work on Guix [...] > would be sufficient in reducing the backlog of bugs? The remainder of my message made that clear but you were offended and hit reply too fast. My observation was about t

Re: Guix booth at JDLL in Lyon, France?

On 6/03/25 7:56, Tanguy Le Carrour wrote: 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) when gathering. I have the kakemono ready, though! 😎 Just chiming in to su

Re: Guix booth at JDLL in Lyon, France?

Hi Luis Felipe, On Thu Mar 6, 2025 at 1:52 PM CET, Luis Felipe wrote: > On 6/03/25 7:56, Tanguy Le Carrour wrote: >> 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

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

Hello Ricardo, >> We have a *humongous* backlog of patches, [...] > >> [...] we host a backend service that regularly checks the Codeberg >> repository for any new issues or PRs and then communicates to us >> through the Codeberg’s Forgejo API [0] the content of said issues >> and >> PRs. The da

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

Hello Suhail, > "Thompson, David" writes: > >> The email-based workflow worked well enough in the early days, but >> Guix outgrew it 5+ years ago. > > Do you also believe that the Linux kernel has outgrown the "email-based > workflow"? If not, what makes things different for Guix, in your > opin

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

Suhail Singh writes: Ludovic Courtès writes: As for experimenting, I agree and I reiterate my invitation to send trivial patches to (or to Guix-Science, Guix-Past, etc.). I think this GCD’s discussion period is the right time to give it a try as it can

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

"Thompson, David" writes: > The email-based workflow worked well enough in the early days, but > Guix outgrew it 5+ years ago. Do you also believe that the Linux kernel has outgrown the "email-based workflow"? If not, what makes things different for Guix, in your opinion? Since a number of cri

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

Divya Ranjan writes: > I had to realize that Linux gets a *lot* more in funding and > infrastructure than Guix. While I agree in general, I don't understand the specific point you were making. Was it that Linux with its greater funding has someone to manage something like Bugzilla, where Guix m

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

Hello, On Sun, Feb 23, 2025 at 10:21 AM Ludovic Courtès wrote: > > Hello Guix! > > This is the formal submission of “Migrating repositories, issues, and > patches to Codeberg” (GCD 002), a preliminary draft of which I posted > before the Guix Days⁰. I support this proposal! It's about time! The

Re: New committer

On 2025-03-07 17:55, Greg Hogan wrote: We have a C++ team! Has the survey shown that project contributors are happier when members of a team and those patches reviewed more promptly? I find Guix to be a powerful tool with unbounded potential. Thank you to all who have contributed. My particular

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

"Thompson, David" writes: >> Do you also believe that the Linux kernel has outgrown the "email-based >> workflow"? If not, what makes things different for Guix, in your >> opinion? > > I don't contribute to Linux so I have nothing to add here. I don't believe that that's a necessary pre-requisi

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

On Fri, Mar 07, 2025 at 01:49:46PM -0500, Suhail Singh wrote: > While I agree in general, I don't understand the specific point you were > making. Was it that Linux with its greater funding has someone to > manage something like Bugzilla, where Guix may not? Linux contributors and maintainers are

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

On Fri, Mar 7, 2025 at 12:40 PM Suhail Singh wrote: > > "Thompson, David" writes: > > > The email-based workflow worked well enough in the early days, but > > Guix outgrew it 5+ years ago. > > Do you also believe that the Linux kernel has outgrown the "email-based > workflow"? If not, what makes