Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.project > #14154
| From | Soren Stoutner <soren@debian.org> |
|---|---|
| Newsgroups | linux.debian.project |
| Subject | Re: is copyleft packaging bad for Debian? |
| Date | 2026-02-04 18:30 +0100 |
| Message-ID | <MkORr-fIvr-7@gated-at.bofh.it> (permalink) |
| References | <MiXYR-etP8-3@gated-at.bofh.it> <Mk3Sx-fdfc-5@gated-at.bofh.it> <MkHGh-fDCO-11@gated-at.bofh.it> |
| Organization | Debian |
[Multipart message — attachments visible in raw view] - view raw
On Wednesday, February 4, 2026 2:38:13 AM Mountain Standard Time Guillem Jover wrote: > It feels like problems with for example weak/team maintainership always > get obviated in this kind of commentary. Such as, it shifting > disagreement from maintainer vs user to internal team strife *and* > team vs user, it substantially increasing communication and consensus > overhead, both of which can very easily either cause "edit wars" or > "paralysis by lack of consensus", or feelings of rudeness or unease > when one internal faction plows ahead regardless of consensus. It > might make maintainers have to work closer than desired with people > they'd rather keep at a distance with, besides the minimum required, > say via bug reports or whatever else. It makes having a coherent vision > of how the package is being maintained harder to understand from outside, > both from upstream and within the project. It makes it harder to invest > in deep understanding of how the upstream code works. It makes it harder > to have a reliable and clear contact point of interest from outside and > within the project. It makes it harder to have a long-standing > relationship with upstream and knowing/understanding each other's quirks, > requirements, preferences or disagreements. It makes unmaintained packages > more difficult to track, it makes inactive teams more difficult to deal > with and detect. It makes trying and experimenting with different packaging > styles or techniques harder, because one has to justify diverting from > any team practices, for something that might well be a dead end. People > feel way less responsible for packages, as supposedly "someone else in > the team can take care of it". Etc. > > . . . > > A weak ownership team is not inherently a better way to maintain > packages, and I'd not like to see this reductionist maintainership view > keep being pushed across the project. I agree with the above. There are pros and cons to both strong and weak maintainership models. Neither one guarantees that a packages will be well maintained, but there are good examples of packages being well maintained under both models. I prefer a strong maintainership model as long as the maintainer is doing a good job. Personally, I prefer to have at least one co-maintainer where we communicate well, are both on the same page as to how to handle the package, and both have a relationship with upstream. All of the complaints against a strong maintainership model have to do with the maintainer not doing a good job. Usually that is through inactivity, but occasionally it is through active participation in negative ways. -- Soren Stoutner soren@debian.org
Back to linux.debian.project | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
is copyleft packaging bad for Debian? Jonas Smedegaard <dr@jones.dk> - 2026-01-30 15:50 +0100
Re: is copyleft packaging bad for Debian? Matthias Geiger <werdahias@riseup.net> - 2026-01-30 17:40 +0100
Re: is copyleft packaging bad for Debian? Martin <debacle@debian.org> - 2026-01-31 12:30 +0100
Re: is copyleft packaging bad for Debian? Soren Stoutner <soren@debian.org> - 2026-01-30 17:40 +0100
Re: is copyleft packaging bad for Debian? Andrey Rakhmatullin <wrar@debian.org> - 2026-01-30 17:40 +0100
Re: is copyleft packaging bad for Debian? Arto Jantunen <viiru@debian.org> - 2026-01-31 10:40 +0100
Re: is copyleft packaging bad for Debian? Jonas Smedegaard <dr@jones.dk> - 2026-01-31 12:30 +0100
Re: is copyleft packaging bad for Debian? Andrey Rakhmatullin <wrar@debian.org> - 2026-01-31 12:50 +0100
Re: is copyleft packaging bad for Debian? Matthias Geiger <werdahias@riseup.net> - 2026-01-31 17:30 +0100
Re: is copyleft packaging bad for Debian? Mechtilde Stehmann <mechtilde@debian.org> - 2026-01-31 18:00 +0100
Re: is copyleft packaging bad for Debian? Tollef Fog Heen <tfheen@err.no> - 2026-01-31 20:50 +0100
Re: is copyleft packaging bad for Debian? Simon Josefsson <simon@josefsson.org> - 2026-02-02 16:20 +0100
Re: is copyleft packaging bad for Debian? "Andrea Pappacoda" <andrea@pappacoda.it> - 2026-02-03 15:10 +0100
Re: is copyleft packaging bad for Debian? Guillem Jover <guillem@debian.org> - 2026-02-04 10:50 +0100
Re: is copyleft packaging bad for Debian? Soren Stoutner <soren@debian.org> - 2026-02-04 18:30 +0100
Re: is copyleft packaging bad for Debian? "Andrea Pappacoda" <tachi@debian.org> - 2026-01-31 17:10 +0100
Is Packaging Copyrightable (was: is copyleft packaging bad for Debian?) Soren Stoutner <soren@debian.org> - 2026-02-02 20:10 +0100
Re: Is Packaging Copyrightable Martin <debacle@debian.org> - 2026-02-02 21:50 +0100
as any other metadata + code expression Question: Is Packaging Copyrightable Yaroslav Halchenko <yoh@debian.org> - 2026-02-03 00:30 +0100
Re: Is Packaging Copyrightable Tollef Fog Heen <tfheen@err.no> - 2026-02-02 23:00 +0100
Re: Is Packaging Copyrightable Soren Stoutner <soren@debian.org> - 2026-02-02 23:40 +0100
Re: is copyleft packaging bad for Debian? Antoine Le Gonidec <vv221@debian.org> - 2026-01-31 17:40 +0100
Re: is copyleft packaging bad for Debian? Russ Allbery <rra@debian.org> - 2026-01-31 20:00 +0100
csiph-web