On Wed, Apr 03, 2024 at 04:48:44PM +0200, Paul Boddie wrote: > On Wednesday, 3 April 2024 16:25:10 CEST Andrey Rakhmatullin wrote: > > On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote: > > > > > > Many thanks for giving me access! Would it make sense to move the existing > > > project into the Python Team's packages collection on Salsa, or is that > > > only permitted for packages that are actually adopted by the team? > > > > If you are going to maintain this package in the team then it can and > > should be in the team namespace, or are you asking about something else? > > My aim is to maintain it in the team, yes. Then putting the repo in the team namespace makes sense.
> However, I did not presume that I could just set the Maintainer field in > debian/control before applying to join the team, nor did I set any particular > headers or metadata in the ITP for shedskin to reference the team, since I > thought that this might be impolite. I imagine that I would change the > Maintainer as noted in the team policy if the package were to be adopted > within the team. There is no "adopted within the team" process for packages, so you just put the repo there and put the team into d/control. -- WBR, wRAR
signature.asc
Description: PGP signature
