Re: [DRAFT] DPMT and PAPT is DPT now
Hi, thanks a lot for this. Second version: --- cut --- PAPT and DPMT become DPT Historically, the Debian Python ecosystem was maintained by two separate teams: the Debian Python Applications Packaging Team (PAPT) for applications, and the Debian Python Modules Team (DPMT) for modules used by applications. As there was substantial overlap between the members of these teams, their work, and their tooling, these teams have been merged into one: the Debian Python Team (DPT). Changes --- This merge mainly affects package maintainers. End users should not see a change beyond the Maintainer field of packages. For maintainers, the following has changed: * The respective PAPT and DPMT policies are superseded by the new, more compact DPT policy [1]. Please take a few minutes to familiarize yourself with this new policy. * All Salsa repositories are in "packages" subgroup [2] now. Please set Vcs-* fields of new packages accordingly. * The Maintainer field of new packages should now be set to "Debian Python Team ". Migration - On Salsa, redirects have been implemented from the old "applications" and "modules" subgroups to the new "packages" subgroup. Vcs-* URLs should continue working for now. But it's still a good idea to update your local git remotes to point to new "packages" subgroup. Maintainer and Vcs-* fields were mass-changed in git repositories so there is nothing you need to do as maintainer of DPMT/PAPT packages. All members of DPMT or PAPT are members of DPT now and have access to "packages" subgroup. As always, new contributors are welcomed :) [1] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst [2] https://salsa.debian.org/python-team/packages --- cut --- -- Best regards Ondřej Nový
Re: [DRAFT] DPMT and PAPT is DPT now
On 2020-09-14 17 h 42, Christian Kastner wrote: > Hi Ondřej, > > On 2020-09-14 10:39, Ondrej Novy wrote: >> for simplification we merged two subteams - Debian Python Modules Team >> and Python Applications Packaging Team into just one: Debian Python >> Team, DPT. >> >> All Salsa repositories are in "packages" subgroup [1] now. >> >> We have only one team policy [2] now. >> >> And as always, new contributors are welcomed :) >> >> [1] https://salsa.debian.org/python-team/packages >> [2] >> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst > > I'm prone to be much too verbose, but seeing as -devel-announce has an > audience that might lack context and details that are well-known to > -python, I'd like to suggest the following amended version just in case: > > > PAPT and DPMT become DPT > > > Historically, the Debian Python ecosystem was maintained by two separate > teams: the Debian Python Applications Packaging Team (PAPT) for > applications, and the Debian Python Modules Team (DPMT) for modules used > by applications. > > As there was substantial overlap between the members of these teams, their > work, and their tooling, these teams have been merged into one: the > Debian Python Team (DPT). > > [Or whatever the actual history and motivations were; as I said in an > earlier mail, it was never quite clear to me why two teams were needed > in the first place] > > > Changes > --- > > This merge mainly affects package maintainers. End users should not see > a change beyond the Maintainer field of packages. > > For maintainers, the following has changed: > * The respective PAPT and DPMT policies are superseded by the new, > more compact DPT policy [1]. Please take a few minutes to familiarize > yourself with this new policy. > * All Salsa repositories are in "packages" subgroup [2] now. Please > set Vcs-* fields of new packages accordingly. > * The Maintainer field of new packages should now be set to > "Debian Python Team ". > > > Migration > - > > On Salsa, redirects have been implemented from the old "applications" > and "modules" subgroups to the new "packages" subgroup. Vcs-* URLs > should continue working for now. > > [... and the other migration steps are still being planned, right?] > > > [1] > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst > [2] https://salsa.debian.org/python-team/packages > I like those changes! Sounds good to send as is to me. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Re: [DRAFT] DPMT and PAPT is DPT now
Hello, Le 2020-09-14 à 17 h 42, Christian Kastner a écrit : > PAPT and DPMT become DPT > > > Historically, the Debian Python ecosystem was maintained by two separate > teams: the Debian Python Applications Packaging Team (PAPT) for > applications, and the Debian Python Modules Team (DPMT) for modules used > by applications. There’s also the CPython interpreter itself, maintained by a solo developer for a long time, more recently a third team. Regards
Re: [DRAFT] DPMT and PAPT is DPT now
Hi Ondřej, On 2020-09-14 10:39, Ondrej Novy wrote: > for simplification we merged two subteams - Debian Python Modules Team > and Python Applications Packaging Team into just one: Debian Python > Team, DPT. > > All Salsa repositories are in "packages" subgroup [1] now. > > We have only one team policy [2] now. > > And as always, new contributors are welcomed :) > > [1] https://salsa.debian.org/python-team/packages > [2] > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst I'm prone to be much too verbose, but seeing as -devel-announce has an audience that might lack context and details that are well-known to -python, I'd like to suggest the following amended version just in case: PAPT and DPMT become DPT Historically, the Debian Python ecosystem was maintained by two separate teams: the Debian Python Applications Packaging Team (PAPT) for applications, and the Debian Python Modules Team (DPMT) for modules used by applications. As there was substantial overlap between the members of these teams, their work, and their tooling, these teams have been merged into one: the Debian Python Team (DPT). [Or whatever the actual history and motivations were; as I said in an earlier mail, it was never quite clear to me why two teams were needed in the first place] Changes --- This merge mainly affects package maintainers. End users should not see a change beyond the Maintainer field of packages. For maintainers, the following has changed: * The respective PAPT and DPMT policies are superseded by the new, more compact DPT policy [1]. Please take a few minutes to familiarize yourself with this new policy. * All Salsa repositories are in "packages" subgroup [2] now. Please set Vcs-* fields of new packages accordingly. * The Maintainer field of new packages should now be set to "Debian Python Team ". Migration - On Salsa, redirects have been implemented from the old "applications" and "modules" subgroups to the new "packages" subgroup. Vcs-* URLs should continue working for now. [... and the other migration steps are still being planned, right?] [1] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst [2] https://salsa.debian.org/python-team/packages
[DRAFT] DPMT and PAPT is DPT now
Hi, I would like to send information to debian-devel-announce after the team merge as suggested by Christian Kastner. Draft follows. Suggestions welcome. --- Hi, for simplification we merged two subteams - Debian Python Modules Team and Python Applications Packaging Team into just one: Debian Python Team, DPT. All Salsa repositories are in "packages" subgroup [1] now. We have only one team policy [2] now. And as always, new contributors are welcomed :) [1] https://salsa.debian.org/python-team/packages [2] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst -- Best regards Ondřej Nový
