Re: Interesting learnings about Guix contributor dynamics that apply to Debian?

> I would significantly reduce my enjoyment of Debian if we were to move > away from mailing lists and the BTS. Surely the BTS could be a bit > more friendly in its advanced features, but new contibutors can simply > ignore those, and a motivated person mght build a nice web interface > for those.

Re: Private code: to forge, or not to forge?

On 5/21/25 22:18, Thomas Hochstein wrote: Probably Otto thought you would be going to provide as an alternative to salsa. oh, I see. no - I absolutely don't want to do anything like that at all. I do want to provide forgejo packages in Debian so it's available and

Re: Private code: to forge, or not to forge?

Daniel Baumann wrote: > On 5/21/25 03:23, Otto Kekäläinen wrote: >> costs from fragmentation. > > I'm not sure I understand what you mean with "fragmentation" in this > context. Would you mind explaining? Probably Otto thought you woould be going to provide as an a

Re: Interesting learnings about Guix contributor dynamics that apply to Debian?

On 21/05/2025 20:23, Marc Haber wrote: On Wed, 21 May 2025 08:48:00 -0700, Otto Kekäläinen wrote: Debian has certainly done many things right in the past 30 years, but treatment of new contributors is currently pretty harsh, considering how many cracks and false turns they need to overcome on t

Re: Interesting learnings about Guix contributor dynamics that apply to Debian?

On May 21, Marc Haber wrote: I would like to keep the BTS with its opportunity to pull up a complicated bug report in my mail client WITH FULL THREADING. Amen. -- ciao, Marco signature.asc Description: PGP signature

Re: Interesting learnings about Guix contributor dynamics that apply to Debian?

On Wed, 21 May 2025 08:48:00 -0700, Otto Kekäläinen wrote: >Debian has certainly done many things right in the past 30 years, but >treatment of new contributors is currently pretty harsh, considering >how many cracks and false turns they need to overcome on to become >regular contributors. I woul

Interesting learnings about Guix contributor dynamics that apply to Debian?

Hi! I came across this post https://issues.guix.gnu.org/76503 in Guix where they discuss how to improve the contributor experience, and in particular what technical changes they are doing. Guix is interesting as they use a clone of Debbugs as their bug tracker at https://debbugs.gnu.org/cgi/pkgre

Re: #1011572: toilet: Salsa

Am 21.05.25 um 12:56 schrieb Kirill Rekhov: Hi, Could I please get developer/maintainer rights for the toilet package on salsa? https://salsa.debian.org/debian/toilet I have time to pay attention to this package. My Debian Packages: https://qa.debian.

Re: debian/upstream/metadata (Re: git branches vs debian specific git tools (Re: RFC for changes regarding NMU in developers reference)

Hello, On Sun 18 May 2025 at 10:46pm +02, Julien Plissonneau Duquène wrote: > Also concerning the Source field in d/copyright, personally I see it as the > place from where the source was obtained when it was initially packaged (and > in some cases that might be "the place where the source used t

#1011572: toilet: Salsa

Hi, Could I please get developer/maintainer rights for the toilet package on salsa? https://salsa.debian.org/debian/toilet I have time to pay attention to this package. My Debian Packages: https://qa.debian.org/developer.php?login=krekhov@gmail.com My Debian Salsa: https://salsa.debian.org/k

Re: Bug#1106057: ITP: gwh -- git-buildpackage workflow helper

On Wednesday, May 21, 2025 12:37:11 AM Mountain Standard Time Jonathan Dowland wrote: > On Wed May 21, 2025 at 12:45 AM BST, Soren Stoutner wrote: > > As someone who is one of the most vocal supporters of standardizing > > how we package things, I would like to say that I always worry when > > som

Re: Bug#1106057: ITP: gwh -- git-buildpackage workflow helper

On Wed May 21, 2025 at 12:45 AM BST, Soren Stoutner wrote: As someone who is one of the most vocal supporters of standardizing how we package things, I would like to say that I always worry when someone says, “Don’t package this new thing. The things we have are already good enough.” I worry

Re: Private code: to forge, or not to forge?

Hi Otto, On 5/21/25 03:23, Otto Kekäläinen wrote: It would be nice to read a writeup of what you plan is, and how the Go team or other DDs in general are expected to relate to this. I'm packaging forgejo (currently ~21 golang packages are waiting in NEW, another ~10 soon to be finished) to be