On Thu, 1 Aug 2024 at 10:36, Johannes Schauer Marin Rodrigues <jo...@debian.org> wrote: > > Hi Otto, > > Quoting Otto Kekäläinen (2024-07-28 00:38:40) > > I have drafted a new DEP at > > https://salsa.debian.org/dep-team/deps/-/merge_requests/8 titled "DEP-18: > > Enable true open collaboration on all Debian packages". > > > > Direct link to raw text: > > https://salsa.debian.org/dep-team/deps/-/raw/798bfa5a1e1609afd4e48ee20aff80a82bcd4a2f/web/deps/dep18.mdwn > > > > This would have been a great topic to discuss in person at DebConf, but > > unfortunately I can't attend this year, so I'll just kick this off on the > > mailing list. > > thank you for working on this. > > > This is continuation to the 'single maintainership' discussions earlier this > > year. I also think that more unified and open collaboration processes could > > help decrease maintainer burnout, lower barrier for existing and new > > maintainers to help with multiple packages, and overall perhaps also improve > > quality of uploads by having more attention on the source code prior to > > upload. > > A slightly related topic: what is everybody's opinion on maybe starting with > some of the basic items of DEP-18, lets say items 1-3, and prescribe them to > only a very small set of packages in Debian. And which set of packages in > Debian should *especially* have easy open collaboration enabled if not the set > of source packages producing our Essential:yes packages? So why not start with > the source packages in the Essential:yes set, have them adhere to better > collaboration standards like packaging in git on salsa and with salsa CI > enabled?
This is a great idea, as it would provide a real testing ground while having a clearly delineated and well defined scope, and with the greatest potential return of investment.
