Re: Merging the PAPT and the DMPT

2020-11-05 Thread Nicholas D Steeves
Ondrej Novy writes: > Hi, > > po 21. 9. 2020 v 13:04 odesílatel Ondrej Novy napsal: > >> Todo: >> >>- send debian-devel-announce (i will) >>- mass-commit vcs+maintainer change >> >> > done. > > Thanks to all who helped me with these. > Yes, thank you! And I'm sure maintainers with

Re: Merging the PAPT and the DMPT

2020-09-24 Thread Ondrej Novy
Hi, po 21. 9. 2020 v 13:04 odesílatel Ondrej Novy napsal: > Todo: > >- send debian-devel-announce (i will) >- mass-commit vcs+maintainer change > > done. Thanks to all who helped me with these. -- Best regards Ondřej Nový

Re: Merging the PAPT and the DMPT

2020-09-21 Thread Christian Kastner
On 2020-09-21 10:45, Ondrej Novy wrote: > út 15. 9. 2020 v 0:12 odesílatel Christian Kastner Has getting rid of the subgroups entirely been considered, IOW: moving > the packages directory to python-team/? > > reason is ACL. We need different access for "tools" and for "packages".  

Re: Merging the PAPT and the DMPT

2020-09-21 Thread Nick Morrott
On Mon, 21 Sep 2020 at 12:21, Ondrej Novy wrote: > > Example of mass-commit: > https://salsa.debian.org/python-team/packages/alembic/-/commit/0519af5c5f82cced88431b6c0ec364f2979e0c42 > https://salsa.debian.org/python-team/packages/alembic/-/commit/51dbd7b278551fbd33abac72c7a240e6baea6a16 > >

Re: Merging the PAPT and the DMPT

2020-09-21 Thread Ondrej Novy
Hi, po 14. 9. 2020 v 9:59 odesílatel Ondrej Novy napsal: > I prepared scripts for: > >- cloning ACLs from modules+applications subgroups to newly created >packages subgroup >- transferring all project from modules+applications to packages >subgroup >- tested on one project:

Re: Merging the PAPT and the DMPT

2020-09-21 Thread Ondrej Novy
Hi, út 15. 9. 2020 v 0:12 odesílatel Christian Kastner napsal: > Has getting rid of the subgroups entirely been considered, IOW: moving > the packages directory to python-team/? > > The only remaining subgroup seems to be "tooling", and that could live > on as a subgroup unless I'm

Re: Merging the PAPT and the DMPT

2020-09-20 Thread Dmitry Shachnev
On Sat, Sep 19, 2020 at 06:24:06PM -0600, Nicholas D Steeves wrote: > Are there plans to do this team-wide (for team email in Maintainer) in > one fell swoop, or will this be a per-maintainer task? I know Ondrej has the tooling to do mass updates, so I hope he will do it :) Of course this is

Re: Merging the PAPT and the DMPT

2020-09-19 Thread Nicholas D Steeves
Hi, Dmitry Shachnev writes: > Hi Ondrej! > > On Mon, Sep 14, 2020 at 09:59:00AM +0200, Ondrej Novy wrote: >> Hi, >> >> I prepared scripts for: >> >>- cloning ACLs from modules+applications subgroups to newly created >>packages subgroup >>- transferring all project from

Re: Merging the PAPT and the DMPT

2020-09-18 Thread Louis-Philippe Véronneau
On 2020-09-14 17 h 54, Christian Kastner wrote: > On 2020-09-14 09:59, Ondrej Novy wrote: >> * transferring all project from modules+applications to packages subgroup > > Has getting rid of the subgroups entirely been considered, IOW: moving > the packages directory to python-team/? > > The

Re: Merging the PAPT and the DMPT

2020-09-14 Thread Christian Kastner
On 2020-09-14 09:59, Ondrej Novy wrote: > * transferring all project from modules+applications to packages subgroup Has getting rid of the subgroups entirely been considered, IOW: moving the packages directory to python-team/? The only remaining subgroup seems to be "tooling", and that could

Re: Merging the PAPT and the DMPT

2020-09-14 Thread Ondrej Novy
Hi, po 14. 9. 2020 v 14:39 odesílatel Dmitry Shachnev napsal: > I think it's better to update Vcs fields in all packages to point to the > new location, not one that redirects. > > Probably also update Maintainer/Uploader fields with the new team > name/email. > yep. But updating these is a

Re: Merging the PAPT and the DMPT

2020-09-14 Thread Ondrej Novy
Hi, po 14. 9. 2020 v 14:26 odesílatel Emmanuel Arias napsal: > So, we shouldn't be worried about changing the VCS-* path during the > migration process, isn't it? > right, we should update them in d/control, but it will work with old one too, which simplifies that process. -- Best regards

Re: Merging the PAPT and the DMPT

2020-09-14 Thread Dmitry Shachnev
Hi Ondrej! On Mon, Sep 14, 2020 at 09:59:00AM +0200, Ondrej Novy wrote: > Hi, > > I prepared scripts for: > >- cloning ACLs from modules+applications subgroups to newly created >packages subgroup >- transferring all project from modules+applications to packages subgroup >- tested

Re: Merging the PAPT and the DMPT

2020-09-14 Thread Emmanuel Arias
Hi, On Mon, Sep 14, 2020 at 5:15 AM Ondrej Novy wrote: > Hi, > > I prepared scripts for: > >- cloning ACLs from modules+applications subgroups to newly created >packages subgroup >- transferring all project from modules+applications to packages >subgroup >- tested on one

Re: Merging the PAPT and the DMPT

2020-09-07 Thread Christian Kastner
On 2020-09-07 13:38, Ondrej Novy wrote: > ~10 days without reply, merged. I'm really happy about this :-) I've always found the split odd. By the way, this might be something worth sending to debian-devel-announce, possibly including a short summary/description of how this affects contributors

Re: Merging the PAPT and the DMPT

2020-09-07 Thread Ondrej Novy
Hi, pá 28. 8. 2020 v 15:04 odesílatel Ondrej Novy napsal: > But because it's really huge change I want ack from at least one another > admin. > ~10 days without reply, merged. Thanks for working on this! -- Best regards Ondřej Nový

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Louis-Philippe Véronneau
On 2020-08-28 10 h 53, Emmanuel Arias wrote: > oops, I forgot, I think we must update the line > > ``` > Copyright (c) 2005-2019 Debian Python Team. All rights reserved. > ``` > > to 2020, isn't? Fixed. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org /

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Emmanuel Arias
oops, I forgot, I think we must update the line ``` Copyright (c) 2005-2019 Debian Python Team. All rights reserved. ``` to 2020, isn't? On Fri, Aug 28, 2020 at 11:52 AM Emmanuel Arias wrote: > Hi everybody! > > +1 for the merge. > > I think it's easy to change the link to vcs-* in bulk?

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Emmanuel Arias
Hi everybody! +1 for the merge. I think it's easy to change the link to vcs-* in bulk? (Talking from my ignorance) Cheers! Emmanuel On Fri, Aug 28, 2020 at 10:54 AM Ondrej Novy wrote: > Hi, > > pá 28. 8. 2020 v 15:27 odesílatel Louis-Philippe Véronneau < > po...@debian.org> napsal: > >> I

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Ondrej Novy
Hi, pá 28. 8. 2020 v 15:27 odesílatel Louis-Philippe Véronneau napsal: > I think changing the path would be a good idea, as I don't see the point > between the libraries and applications divide. +1. GitLab will take care with redirects. It's a mess now :) -- Best regards Ondřej Nový

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Louis-Philippe Véronneau
On 2020-08-28 05 h 28, Andrey Rahmatullin wrote: > Can you please also describe the current plans for changing/not changing > the Git paths after the merge? > During the BoF, most people were against changing the git paths after the merge and this differs from the discussion we had in the Merge

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Ondrej Novy
Hi, čt 27. 8. 2020 v 22:22 odesílatel Louis-Philippe Véronneau napsal: > In October 2019, following a short discussion on the ML [1], I opened a > merge request on the policy [2] for this. Most if not all issues in that > MR have since been resolved and the only blocker is getting the admins >

Re: Merging the PAPT and the DMPT

2020-08-28 Thread Andrey Rahmatullin
Can you please also describe the current plans for changing/not changing the Git paths after the merge? -- WBR, wRAR signature.asc Description: PGP signature

Merging the PAPT and the DMPT

2020-08-27 Thread Louis-Philippe Véronneau
Hello folks! Yesterday during the Python BoF at DebConf20 I brought up the question of merging the PAPT and the DMPT into a single, coherent Python Team. Most of the people present at the BoF agreed the merge would be a good idea to: * improve documentation * have a consistent workflow between