Re: Move to salsa? Team structure preview ready
Hi, 2018-02-12 12:38 GMT+01:00 Ondrej Novy : > I also noticed that this package: >> https://salsa.debian.org/python-team/modules/twodict is not accessible >> on salsa >> (and neither is accessible on alioth anymore). Is this expected? >> > > not expected, fixed. > there was 82 more like this. Fixed all of them. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Move to salsa? Team structure preview ready
Hi, 2018-02-12 12:14 GMT+01:00 Félix Sipma : > Do you plan changing the Vcs-fields for all packages automatically? > yes. > I also noticed that this package: > https://salsa.debian.org/python-team/modules/twodict is not accessible on > salsa > (and neither is accessible on alioth anymore). Is this expected? > not expected, fixed. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Move to salsa? Team structure preview ready
Hi, Do you plan changing the Vcs-fields for all packages automatically? I also noticed that this package: https://salsa.debian.org/python-team/modules/twodict is not accessible on salsa (and neither is accessible on alioth anymore). Is this expected? Thanks! signature.asc Description: PGP signature
Re: Move to salsa? Team structure preview ready
Hi, On 08.02.2018 15:16, Ondrej Novy wrote: > I disabled "request to join" feature. To join DPMT/PAPT you need to send > email to debian-python and agree with policy. We already ignored alioth > join requests. As someone who was just joined to PAPT via an Alioth request two days ago (thanks, Piotr), I beg to differ ;-) It probably makes a lot sense to update the PAPT policy[0] section "Joining the team" if the migration to salsa means applicants should definitely write an email. Cheers, Thomas [0] http://python-apps.alioth.debian.org/policy.html signature.asc Description: OpenPGP digital signature
Re: Move to salsa? Team structure preview ready
thanks for taking the lead. On 2018-02-08 15:16, Ondrej Novy wrote: > > But I don't think all DD are masters in our team. This is true only > for 'Debian' team. Even if you are DD, you need to join team or > subteam to have commit access to it. i think this is true. at least i had to request membership explicitely for all teams but "debian" (fka "collab-maint"), > > I disabled "request to join" feature. To join DPMT/PAPT you need to send > email to debian-python and agree with policy. We already ignored alioth > join requests. [...] > > maybe we can cleanup member list and don't do migration at all. So > require explicit request to join. I don't have to process it. i'm confused. how do i become member of the salsa group? automatically, by taking the alioth group? manually, by re-requesting access (to cleanup the team of those who no longer have interest in the team)? will DDs and guest accounts be handled differently? do i have to send a formal email to request membership *again*? fgamsdr IOhannes PS: there's numerous scripts out their to help the migration. here's the one i was using to migrate the Pd-packages into the multimedia-team/pd/ subgroup (and is based on the script that migrated the remaining ~400 packages for the multimedia-team without subgroups). it automatically registers email-notifications (via tracker.d.o) and pending-uploads tags, and (by default) irker notifications. it has a number of options. https://salsa.debian.org/umlaeute/multimedia-cli
Re: Move to salsa? Team structure preview ready
Hi, 2018-02-08 14:35 GMT+01:00 Raphael Hertzog : > This is not really needed. In fact I would suggest to de-activate the > "request to join" feature. It mails all "masters" (and all DD are masters > since they need to be able to create new repositories) and it doesn't > offer a way to explain why you need to join the team. > I disabled "request to join" feature. To join DPMT/PAPT you need to send email to debian-python and agree with policy. We already ignored alioth join requests. But I don't think all DD are masters in our team. This is true only for 'Debian' team. Even if you are DD, you need to join team or subteam to have commit access to it. Instead one should go through alioth project members and add them directly > to salsa. And -guest users should create their account and ask here to be > added (explaining that they were member before already). > maybe we can cleanup member list and don't do migration at all. So require explicit request to join. I don't have to process it. > But IMO alioth project members should be added to the "modules" sub-group > and not to the top-level group. Otherwise the "interpreter" subgroup will > have way too many members compared to what is desired. > agree. DPMT members should be members of "modules" group, PAPT members should be members of "applications". -- S pozdravem/Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Move to salsa? Team structure preview ready
On Thu, 08 Feb 2018, W. Martin Borgert wrote: > No need to merge the subgroups ever. > With this structure, it is one team already. > > If there nobody objects, we have to: > - migrate the git archives (you volunteered, thanks!) - setup the webhook to close bugs - configure email on pushes to send commit mails to the package tracker - configure IRC notifications (irker?) > - ask for membership in the team (everybody) This is not really needed. In fact I would suggest to de-activate the "request to join" feature. It mails all "masters" (and all DD are masters since they need to be able to create new repositories) and it doesn't offer a way to explain why you need to join the team. Instead one should go through alioth project members and add them directly to salsa. And -guest users should create their accound and ask here to be added (explaining that they were member before already). But IMO alioth project members should be added to the "modules" sub-group and not to the top-level group. Otherwise the "interpreter" subgroup will have way too many members compared to what is desired. > - change Python team documentation (who?) - document how to setup new repositories (with the webhook, tracker integration, etc.) > - make an MR for https://salsa.debian.org/salsa/AliothRewriter (who?) > - ? > Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Re: Move to salsa? Team structure preview ready
Quoting Ondrej Novy : 2018-02-08 10:14 GMT+01:00 Ondrej Novy : I created team "python-team" in salsa with 3 subgroups: interpreter modules applications OK. I can do DPMT GIT migration, but I need agreement on new structure. OK! :~) We can merge two subgroups later. No need to merge the subgroups ever. With this structure, it is one team already. If there nobody objects, we have to: - migrate the git archives (you volunteered, thanks!) - ask for membership in the team (everybody) - change Python team documentation (who?) - make an MR for https://salsa.debian.org/salsa/AliothRewriter (who?) - ?
Re: Move to salsa? Team structure preview ready
Hi, 2018-02-08 10:39 GMT+01:00 Piotr Ożarowski : > could you describe these groups? What goes into modules and what into > packages? > it was typo, already fixed in next mail. Group description is in Salsa too. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Move to salsa? Team structure preview ready
Hi, Thanks for pushing it forward [Ondrej Novy, 2018-02-08] > I created team "python-team" in salsa with 3 subgroups: > interpreter > modules > packages could you describe these groups? What goes into modules and what into packages? -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: Move to salsa? Team structure preview ready
2018-02-08 10:14 GMT+01:00 Ondrej Novy : > I created team "python-team" in salsa with 3 subgroups: > interpreter > modules > packages > interpreter modules applications sry :). -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Move to salsa? Team structure preview ready
Hi, I created team "python-team" in salsa with 3 subgroups: interpreter modules packages See: https://salsa.debian.org/python-team Any thoughts? I can do DPMT GIT migration, but I need agreement on new structure. I think talk about PAPT+DPMT merging is big discussion, so let's put it aside. We can merge two subgroups later. We need to focus on ->salsa migration now. Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
