merge the DPMT and the PAPT policies into a common one

As we discussed on the mailing list, we should merge the DPMT and the PAPT!

1. I'm not sure what the different alioth lists (python-modules-team@lists.alioth.debian.org, python-apps-team@lists.alioth.debian.org) are for. I replaced that with debian-python@lists.debian.org.

2. I don't know what to do with URLs yet. If we merge the two teams, what hierarchy should we go with? Do we:

• want to keep having a separation between applications and modules in Salsa (tools, python-applications, python-modules)?
• want to have a new namespace, (tools, packages)?

1. The Debian Lists admins don't like using the @l.d.o lists in Maintainer fields for that many packages, so we should probably get a new list (or a tracker.d.o team, currently there are the two dpmt/papt teams there)
2. I'd vote for /packages/ - the repositories can be moved within gitlab obtaining redirects, therefore, the move would be transparent for people using the old names.

1. I vote for team+python@tracker.debian.org (but I'm open to reason why it's not good idea :)
2. I agree with @mattia: /packages is fine for me. Or maybe /pkgs or /pkg?

added 1 commit

• c25c3a18 - merge the DPMT and the PAPT policies into a common one

Compare with previous version

I've created a new team on tracker.d.o (https://tracker.debian.org/teams/python/) and updated the MR accordingly.

I also agree a common /packages/ makes a lot a sense.

What is the next step to get this rolling?

@morph @kitterman @piotr I'd be happy to work on this migration during the Holidays, but at the moment I'm blocked :)

I'm not an admin, so i defer to them for any decision.

approved this merge request

2020?

changed this line in version 3 of the diff

added 1 commit

• b8017d2c - merge the DPMT and the PAPT policies into a common one

Compare with previous version

merged

mentioned in commit c3f6be6a