Request for Python Team assistance in Debian Mentors

Discussion:

(too old to reply)

Phil Wyett

2024-06-13 06:30:01 UTC

Dear Python Team Members,

At present we have a number of Python related packages[1] within Debian
Mentors[2]. Would it be possible for team members/DD's to offer their expert
assistance to these submitters and their packages with a goal of upload to
Debian where appropriate.

Your time and assistance would be greatly appreciated.

[1] Package list, not exhaustive...

https://mentors.debian.net/package/python-keep/
https://mentors.debian.net/package/python-autodocsumm/
https://mentors.debian.net/package/python-radexreader/
https://mentors.debian.net/package/anytree/
https://mentors.debian.net/package/browser-cookie3/

[2] https://mentors.debian.net/packages/

Regards

Phil

--
Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Pierre-Elliott Bécue

2024-06-13 10:40:01 UTC

Permalink

Hey,

Post by Phil Wyett
Dear Python Team Members,
At present we have a number of Python related packages[1] within Debian
Mentors[2]. Would it be possible for team members/DD's to offer their expert
assistance to these submitters and their packages with a goal of upload to
Debian where appropriate.
Your time and assistance would be greatly appreciated.
[1] Package list, not exhaustive...
https://mentors.debian.net/package/python-keep/
https://mentors.debian.net/package/python-autodocsumm/
https://mentors.debian.net/package/python-radexreader/
https://mentors.debian.net/package/anytree/
https://mentors.debian.net/package/browser-cookie3/
[2] https://mentors.debian.net/packages/

Thanks for poking us.

I can't promise that it will be fast but I'll try to give it some time.

Bests,

--
PEB

Phil Wyett

2024-06-13 11:10:01 UTC

Permalink

Post by Pierre-Elliott BÃ©cue
Hey,

Thanks for poking us.
I can't promise that it will be fast but I'll try to give it some time.
Bests,

Thanks. All assistance is appreciated.

Regards

Phil

--
Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Andrey Rakhmatullin

2024-06-13 10:50:01 UTC

Permalink

I'm always hesitant to look at Python module RFSes because on one hand I
would like all of them to be in the team but on the other hand I'm not
sure if it makes sense to write "please move this to DPT" or "please
consider moving this to DPT", especially for people who are first time
packages without a team membership.
Perhaps we should discuss this and find a single recommended practice for
such packages.

--
WBR, wRAR

Phil Wyett

2024-06-13 11:10:01 UTC

Permalink

Post by Andrey Rakhmatullin

Hi,

This sounds very reasonable. I think we would value the opinion of Python Team
members on how they would like to handle new packages/members coming via mentors
that would integrate well into their team/workflow.

Regards

Phil

--
Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Pierre-Elliott Bécue

2024-06-13 11:20:01 UTC

Permalink

Post by Andrey Rakhmatullin

I really think we should encourage newcomers to apply joining the team
and put their packages there.

What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)

--
PEB

weepingclown

2024-06-13 17:00:01 UTC

Permalink

Hi,

The ruby team has a similar ruby-team/mentors namespace for newcomers. That works quite nicely.

Best,
Ananthu

Post by Pierre-Elliott BÃ©cue

Post by Andrey Rakhmatullin

I really think we should encourage newcomers to apply joining the team
and put their packages there.
What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)
--
PEB

Emmanuel Arias

2024-06-13 19:00:01 UTC

Permalink

Hi,

That's a good idea. IIRC Rust Team has a similar idea for newcomers.

Post by weepingclown
Hi,
The ruby team has a similar ruby-team/mentors namespace for newcomers. That works quite nicely.
Best,
Ananthu

Post by Pierre-Elliott BÃ©cue

Post by Andrey Rakhmatullin

I really think we should encourage newcomers to apply joining the team
and put their packages there.
What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)
--
PEB

--
cheers,
Emmanuel Arias

â¢â£Žâ Ÿâ »â¢¶â£Šâ
â£Ÿâ â¢ â â â£¿â¡ ***@debian.org
â¢¿â¡â â ·â â â OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
â â ³â£

Phil Wyett

2024-06-13 21:40:01 UTC

Permalink

Post by weepingclown
Hi,
The ruby team has a similar ruby-team/mentors namespace for newcomers. That works quite nicely.
Best,
Ananthu

Post by Andrey Rakhmatullin

I really think we should encourage newcomers to apply joining the team
and put their packages there.
What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)

Hi all,

Many thanks for the pointer to the Ruby Team. Their approach looks interesting.
If the Python Team were be able to consider a similar approach that of course
fits the teams particular needs it could prove very productive overall for the
team and newcomers.

Regards

Phil

--
Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Peter Wienemann

2024-06-16 17:20:01 UTC

Permalink

Hi,

Post by Andrey Rakhmatullin
I'm always hesitant to look at Python module RFSes because on one hand I
would like all of them to be in the team but on the other hand I'm not
sure if it makes sense to write "please move this to DPT" or "please
consider moving this to DPT", especially for people who are first time
packages without a team membership.
Perhaps we should discuss this and find a single recommended practice for
such packages.

I really think we should encourage newcomers to apply joining the team
and put their packages there.
What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)

I agree with both of you that it would be good to encourage new
contributors to put their Python packages in the Python team namespace.

If one does not want to grant push rights to all team repositories to
newcomers, an alternative to a separate namespace would be that a
sponsor (who is a member of the Python group on salsa) creates a
repository in the Python team namespace (after approval by the sponsored
person), moves the repository contents to the created repository and
grants the right to push to this repository to the sponsored person.
During that phase, new contributors can only submit changes to other
repositories in the team namespace by other means, e. g. by submitting
merge requests (although MRs are not ideal for all cases, e. g. updating
packages to new upstream versions). After a couple of good contributions
access to all team repositories could be granted if there is interest in
broader team contributions (rather than focusing on one's own packages).

This sketched procedure is e. g. followed by the security tools
packaging team (see e. g. Samuel Henrique's explanation on [0]). It does
not involve an additional migration step but adopting this by the Python
team probably requires rethinking the team policy acceptance workflow.

Best regards,

Peter

[0] https://lists.debian.org/debian-security-tools/2021/10/msg00003.html

Andreas Tille

2024-06-18 06:10:01 UTC

Permalink

Post by Pierre-Elliott BÃ©cue
What we could do if the idea of giving broad commit rights to newcomers
poses issues is to create a specific namespace in python-team for
newcomers. (then we'd need to have some migration plan and then oh dear)

I agree with both of you that it would be good to encourage new contributors
to put their Python packages in the Python team namespace.

ACK. My personal policy is to sponsor only packages from some team
space in Salsa for various reasons, mainly because:
1. The sponsee should feel connected to some team to make me as
sponsor "replaceable" by other team members.
2. Its way easier if I commit some slight changes to Git myself and
write extensive commit messages than asking the sponsee to do
change XY and move it to mentors again.

I'm fine with using some sub-namespace (never worked with this in other
teams but it might be appropriate here).

Kind regards
Andreas.

--
https://fam-tille.de