Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #15415 > unrolled thread

Request to join the Debian Python Team

Back to article view | Back to linux.debian.maint.python

Contents

  Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-01-16 01:30 +0100
    Re: Request to join the Debian Python Team Pierre-Elliott Bécue <peb@debian.org> - 2024-04-06 09:50 +0200
      Re: Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-04-06 09:51 +0200
        Re: Request to join the Debian Python Team Pierre-Elliott Bécue <peb@debian.org> - 2024-04-06 09:52 +0200
    Re: Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-04-06 09:50 +0200
      Re: Request to join the Debian Python Team Andrey Rakhmatullin <wrar@debian.org> - 2024-04-06 09:51 +0200
    Re: Request to join the Debian Python Team Andrey Rakhmatullin <wrar@debian.org> - 2024-04-06 09:51 +0200
      Re: Request to join the Debian Python Team Andrey Rakhmatullin <wrar@debian.org> - 2024-04-06 09:52 +0200
      Re: Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-04-06 09:52 +0200
    Re: Request to join the Debian Python Team Pierre-Elliott Bécue <peb@debian.org> - 2024-04-06 09:51 +0200
      Re: Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-04-06 09:52 +0200
    Re: Request to join the Debian Python Team Paul Boddie <paul@boddie.org.uk> - 2024-04-06 09:51 +0200

#15415 — Request to join the Debian Python Team

Hello,

I would like to request membership of the Debian Python Team. For a while, I 
have been working on a package for Shed Skin (shedskin) which is a compiler 
for a dialect of Python.

I previously maintained a package for this software in the Python 2 era, and 
since it has been made compatible with Python 3, I feel that it would be 
beneficial to Debian users to have convenient access to it once again. To this 
end, I filed an "intent to package" report a while back:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051352

The principal developer of Shed Skin is very encouraging of packaging efforts 
and has been responsive to feedback about issues that might otherwise incur 
distribution-level patches. Personally, I think that the software deserves 
more exposure, especially when considering some of the transformative effects 
it has on some kinds of Python code:

http://shed-skin.blogspot.com/2024/01/fast-doom-wad-renderer-in-999-lines-of.html

I have sought to follow advice provided in the team policy, making a Salsa 
project available here:

https://salsa.debian.org/pboddie/shedskin

Building on experience with a previous repository (noted in the ITP report), I 
have hopefully managed to follow the branching and pristine-tar guidelines, 
also introducing test running using Salsa CI.

I have read and accept the policy published here:

https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst

My Salsa login is pboddie.

Thanks in advance for any guidance that might be offered!

Paul

[toc] | [next] | [standalone]

#15707

Paul Boddie <paul@boddie.org.uk> wrote on 03/04/2024 at 16:21:05+0200:

> On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:
>> 
>> I've granted you developer access to the package subgroup. You can
>> create a shedskin project here if you want.
>
> 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?

On the contrary, please do!

>> If you lack some access, don't hesitate to reach out for help (we are on
>> #debian-python on OFTC IRC network).
>> 
>> Don't hesitate after some time and contributions to ask for maintainer
>> access if you need to create new repos.
>
> One step at a time, I think!
>
> Thanks once again,

You're welcome.
-- 
PEB

[toc] | [prev] | [next] | [standalone]

#15723

On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote:
> Paul Boddie <paul@boddie.org.uk> wrote on 03/04/2024 at 16:21:05+0200:
> > 
> > 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?
> 
> On the contrary, please do!

It seems that the "transfer project" function would be the most appropriate 
way of moving the project, but I don't think I am allowed to perform the 
transfer. In the settings for my project, the pull-down menu only offers 
transfer to the "moin" group where I have some other projects.

I reviewed the documentation...

https://salsa.debian.org/help/user/project/settings/migrate_projects#transfer-a-project-to-another-namespace

...and I think that the only obstacle is that I am a developer as opposed to a 
maintainer. I suppose that I could re-create the project in the group instead, 
if that is more appropriate.

Thanks in advance for any assistance that can be offered, and sorry to bring 
up such tedious administrative issues!

Paul

[toc] | [prev] | [next] | [standalone]

#15738

[Multipart message — attachments visible in raw view] — view raw

Paul Boddie <paul@boddie.org.uk> wrote on 04/04/2024 at 17:22:35+0200:

> On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote:
>> Paul Boddie <paul@boddie.org.uk> wrote on 03/04/2024 at 16:21:05+0200:
>> > 
>> > 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?
>> 
>> On the contrary, please do!
>
> It seems that the "transfer project" function would be the most appropriate 
> way of moving the project, but I don't think I am allowed to perform the 
> transfer. In the settings for my project, the pull-down menu only offers 
> transfer to the "moin" group where I have some other projects.
>
> I reviewed the documentation...
>
> https://salsa.debian.org/help/user/project/settings/migrate_projects#transfer-a-project-to-another-namespace
>
> ...and I think that the only obstacle is that I am a developer as opposed to a 
> maintainer. I suppose that I could re-create the project in the group instead, 
> if that is more appropriate.
>
> Thanks in advance for any assistance that can be offered, and sorry to bring 
> up such tedious administrative issues!

I've bumped your access to maintainer, let's try, and I'll downgrade
when you're done.

-- 
PEB

[toc] | [prev] | [next] | [standalone]

#15709

On Wednesday, 3 April 2024 16:51:33 CEST Andrey Rakhmatullin wrote:
> 
> Then putting the repo in the team namespace makes sense.

OK. I will aim to do that.

> On Wed, Apr 03, 2024 at 04:48:44PM +0200, Paul Boddie wrote:
> > 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.

Right. I will do that.

I was just looking at the Wiki documentation for this and I think there might 
need to be some updates and clarifications. For example, on this page:

https://wiki.debian.org/Teams/PythonTeam/HowToJoin

Here, it mentions the Maintainers and Uploaders fields and a more 
comprehensive policy than in the Salsa-hosted policy document. I assume that 
this policy is still applicable, but I wonder how it interacts with people 
like me who do not have Debian Developer status and presumably cannot be an 
uploader.

The above page also has references to Alioth mailing lists, which seem to be 
active even though the archives contain a lot of spam. It also says this:

"If the team is in Maintainer field, remember to subscribe appropriate mailing 
list or at least bts and contact keywords on this [Advanced subscription form 
for the Package Tracking System] page."

I assume that this would involve me subscribing to the applications list or to 
notifications from the PTS, but the grammar in the above sentence is ambiguous 
and I don't have the background knowledge to successfully disambiguate it. It 
could also mean subscribing the team to the PTS for the package.

Sorry if this is asking questions with obvious answers!

Paul

[toc] | [prev] | [next] | [standalone]

#15720

[Multipart message — attachments visible in raw view] — view raw

On Wed, Apr 03, 2024 at 05:21:15PM +0200, Paul Boddie wrote:
> I was just looking at the Wiki documentation for this and I think there might 
> need to be some updates and clarifications. For example, on this page:
> 
> https://wiki.debian.org/Teams/PythonTeam/HowToJoin
> 
> Here, it mentions the Maintainers and Uploaders fields and a more 
> comprehensive policy than in the Salsa-hosted policy document. I assume that 
> this policy is still applicable, but I wonder how it interacts with people 
> like me who do not have Debian Developer status and presumably cannot be an 
> uploader.
The Maintainer/Uploaders fields list maintainers, not people who literally
upload this package. See
https://www.debian.org/doc/debian-policy/ch-controlfields.html#maintainer

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#15712

[Multipart message — attachments visible in raw view] — view raw

On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote:
> On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:
> > 
> > I've granted you developer access to the package subgroup. You can
> > create a shedskin project here if you want.
> 
> 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?

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#15728

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#15734

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. Previously, I maintained the 
package in Debian, although I never became an actual Debian developer and 
relied on a mentor to perform uploads. This time round, I envisaged that it 
would be more sustainable if I joined the Debian Python Team, maintained the 
package, but would be able to rely on uploaders in the team to perform the 
uploads.

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.

Paul

[toc] | [prev] | [next] | [standalone]

#15714

[Multipart message — attachments visible in raw view] — view raw

Hi Paul,

Paul Boddie <paul@boddie.org.uk> wrote on 16/01/2024 at 02:10:14+0200:

> Hello,
>
> I would like to request membership of the Debian Python Team. For a while, I 
> have been working on a package for Shed Skin (shedskin) which is a compiler 
> for a dialect of Python.
>
> I previously maintained a package for this software in the Python 2 era, and 
> since it has been made compatible with Python 3, I feel that it would be 
> beneficial to Debian users to have convenient access to it once again. To this 
> end, I filed an "intent to package" report a while back:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051352
>
> The principal developer of Shed Skin is very encouraging of packaging efforts 
> and has been responsive to feedback about issues that might otherwise incur 
> distribution-level patches. Personally, I think that the software deserves 
> more exposure, especially when considering some of the transformative effects 
> it has on some kinds of Python code:
>
> http://shed-skin.blogspot.com/2024/01/fast-doom-wad-renderer-in-999-lines-of.html
>
> I have sought to follow advice provided in the team policy, making a Salsa 
> project available here:
>
> https://salsa.debian.org/pboddie/shedskin
>
> Building on experience with a previous repository (noted in the ITP report), I 
> have hopefully managed to follow the branching and pristine-tar guidelines, 
> also introducing test running using Salsa CI.
>
> I have read and accept the policy published here:
>
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/
> policy.rst
>
> My Salsa login is pboddie.
>
> Thanks in advance for any guidance that might be offered!

I've granted you developer access to the package subgroup. You can
create a shedskin project here if you want.

If you lack some access, don't hesitate to reach out for help (we are on
#debian-python on OFTC IRC network).

Don't hesitate after some time and contributions to ask for maintainer
access if you need to create new repos.

-- 
PEB

[toc] | [prev] | [next] | [standalone]

#15727

On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:
> 
> I've granted you developer access to the package subgroup. You can
> create a shedskin project here if you want.

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 lack some access, don't hesitate to reach out for help (we are on
> #debian-python on OFTC IRC network).
> 
> Don't hesitate after some time and contributions to ask for maintainer
> access if you need to create new repos.

One step at a time, I think!

Thanks once again,

Paul

[toc] | [prev] | [next] | [standalone]

#15717

On Thursday, 4 April 2024 18:02:42 CEST Pierre-Elliott Bécue wrote:
> 
> I've bumped your access to maintainer, let's try, and I'll downgrade
> when you're done.

The project has been transferred and now resides here:

https://salsa.debian.org/python-team/packages/shedskin

Many thanks once again!

Paul

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web