On Sat, Mar 09, 2024 at 06:46:52PM +0100, Anton Gladky wrote: > Same for me. Thanks for proposal. +1 > Anton > Am Sa., 9. März 2024 um 17:51 Uhr schrieb Nilesh Patra <nil...@debian.org>: > > I am late to the party but I agree with the policy change.
Following on from some earlier discussions, I've been thinking about the relationship between the DPT (presumably a group of developers who work together) and salsa (could there be packages in the python-team/packages area which are not team maintained?). I reread much of the policy at https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and discovered something quite strange. The introduction begins: --- Introduction: The Debian Python Team (DPT) aims to improve the Python packages situation in Debian, by packaging available modules and applications that may be useful and providing a central location for packages maintained by a team, hence improving responsiveness, integration, and standardization. The DPT is hosted at salsa.debian.org, the Debian GitLab installation. We currently have a Git repository and a mailing list whose email address can be used in the Maintainer or Uploaders fields on co-maintained packages. --- If the DPT is a team (a group of maintainers/developers/helpful others), what does "The DPT is hosted at salsa" mean - how can a "team" be hosted? (And in the first paragraph, "maintained by a team" seems a little strange too.) Perhaps something like the following would be better (shifting the focus from the tools to the people), and would also separate concerns more clearly: --- Introduction: The Debian Python Team (DPT) is a group of maintainers who are jointly responsible for a large number of Python packages in Debian. They package and support available Python modules and applications that may be useful. By using a central location on salsa.debian.org, the Debian GitLab instance, for these team-maintained packages, the DPT are able to improve responsiveness, integration, and standardization. --- Then the details of how to mark a package as being team-maintained can be left to the Maintainership section. We could then include a statement along the lines of the following (though I'm not sure where would be best): --- Python module packages which are not team-maintained by the DPT can also be stored in the python-team/packages namespace on salsa in order to benefit from the integration and standardization tools such as Janitor. Manual changes to these packages by someone other than the package's maintainer should be proposed via salsa merge requests or comments in the BTS (or using NMUs if appropriate) as for any other individually-maintained package. --- It would be good to say something about Uploaders in the Maintainership section. Perhaps something like this: --- A package maintained within the team must have the name of the team in the Maintainer field: Maintainer: Debian Python Team <team+pyt...@tracker.debian.org> This enables the team to have an overview of its packages on the DDPO_website. If a particular developer wishes to take primary responsibility for a package, they should put their name in the Uploaders field. [*** What does this mean though? Maybe something like: In this case, any DPT member is still welcome to make changes to the package, though it is polite to contact the developer(s) named in the Uploaders field first. ***] If there are complications in the packaging of the module, for example, if certain modules are interdependent and need to be updated together, this should be documented in debian/README.source [*** or somewhere else ***] --- Best wishes, Julian
