Re: salsa join request

[Lee Garrett]

On 23.04.24 15:29, Stefano Rivera wrote:

Hi Lee (2024.04.17_16:35:33_+)

I've been part of the DPMT team in the past [0]. I'd like to put ansible and
ansible-core under the Debian Python Team umbrella. My salsa login is
"lgarrett". I have read 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and I accept it.


Welcome back. Added you.

Stefano


Cheers!

Re: salsa join request

[Stefano Rivera]

Hi Lee (2024.04.17_16:35:33_+)
> I've been part of the DPMT team in the past [0]. I'd like to put ansible and
> ansible-core under the Debian Python Team umbrella. My salsa login is
> "lgarrett". I have read 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and I accept it.

Welcome back. Added you.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

salsa join request

[Lee Garrett]

Hi,

I've been part of the DPMT team in the past [0]. I'd like to put ansible and 
ansible-core under the Debian Python Team umbrella. My salsa login is 
"lgarrett". I have read 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst 
and I accept it.


Greets,
Lee


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: request for removal of my packages from the DPT namespace

[Andreas Tille]

Hi,

Am Tue, Apr 16, 2024 at 11:21:51AM +0200 schrieb Jeroen Ploemen:
> Jeroen Ploemen  wrote:
> > please delete the following packages from the DPT namespace on
> > salsa:
> > 
> > cheetah
> > jaraco.classes
> > jaraco.collections
> > jaraco.context
> > jaraco.text
> > nfoview
> > ply
> > puremagic
> > python-autocommand
> > python-jaraco.functools
> > python-portend
> > python-rarfile
> > python-tempora
> > python-yenc
> > sabctools
> > sabnzbdplus
> > 
> > All of these have already been mirrored into my personal namespace
> > to keep a public VCS available, while gaining at least some
> > protection against ongoing policy violations.

Not that I would have permissions to remove any repositories in DPT but
I've just checked

$ apt showsrc cheetah 2>/dev/null | grep Vcs-Git
Vcs-Git: https://salsa.debian.org/python-team/packages/cheetah.git

I would not remove anything that is referenced from package metadata.
I realised 

$ apt showsrc sabnzbdplus 2>/dev/null | grep Vcs-Git
Vcs-Git: https://salsa.debian.org/jcfp/sabnzbdplus.git

so here the DPT repository is probably misleading.

Kind regards
Andreas.

-- 
https://fam-tille.de

Re: request for removal of my packages from the DPT namespace

[Jeroen Ploemen]

*ping*


On Tue, 19 Mar 2024 13:41:04 +0100
Jeroen Ploemen  wrote:

> Dear team admins,
> 
> please delete the following packages from the DPT namespace on
> salsa:
> 
> cheetah
> jaraco.classes
> jaraco.collections
> jaraco.context
> jaraco.text
> nfoview
> ply
> puremagic
> python-autocommand
> python-jaraco.functools
> python-portend
> python-rarfile
> python-tempora
> python-yenc
> sabctools
> sabnzbdplus
> 
> 
> All of these have already been mirrored into my personal namespace
> to keep a public VCS available, while gaining at least some
> protection against ongoing policy violations.


pgppk_g_DEJl0.pgp
Description: OpenPGP digital signature

Re: Request to join the team

[Ricardo B. Marliere]

On  3 Apr 15:48, Pierre-Elliott Bécue wrote:
> Hi Ricardo,
> 
> "Ricardo B. Marliere"  wrote on 29/01/2024 at 
> 23:07:59+0200:
> 
> > Hi,
> >
> > My name is Ricardo and I've been trying to get involved with Debian to
> > give back to the community. I'm "rbmarliere" in Salsa [1] and I have
> > made a few contributions to the Go team. However, I have more experience
> > with Python and would like to help in fixing bugs for the team and
> > other general QA work. I have read and accept the Debian Python Team
> > Policy [2].
> 
> Considering your past contributions, I've granted you a Developer access.

Thank you Pierre! I'll go look for things to help with :)

> 
> Feel free to reach out when you need new repos created.
> 
> On the long-term if you contribute, I'll be happy to extend your ACLs.
> 
> Thanks, and sorry for the delay.
> -- 
> PEB

Re: Request to join the Debian Python Team

[Paul Boddie]

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

Re: Request to join the Debian Python Team

[Pierre-Elliott Bécue]

Paul Boddie  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  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


signature.asc
Description: PGP signature

Re: Request to join the Debian Python Team

[Paul Boddie]

On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote:
> Paul Boddie  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

Re: Membership request

[Pierre-Elliott Bécue]

Hi Nicolas,

Nicolas Couture  wrote on 04/04/2024 at 10:32:05+0200:

> Hello Pierre-Elliott,
>
> Thank you for your response.
>
> I believe that a contribution track is a way to contribute to the Python team 
> without being a full member. I am interested in learning
> more about the contribution track and how I can get involved.
>
> Please let me know if there is any additional information or resources that 
> you can provide.
>
> Thank you for your time and consideration.
>
> Best regards,

What I was meaning is that before granting full access, it would be good
to build trust.

To do so, I was offering to create the specific repositories you want to
work on in the group and grant you access on these very repositories.

After some time we could consider expanding your access to the whole
group packages.

Would that be fine?
-- 
PEB


signature.asc
Description: PGP signature

Re: Membership request

[Nicolas Couture]

Hello Pierre-Elliott,

Thank you for your response.

I believe that a contribution track is a way to contribute to the Python
team without being a full member. I am interested in learning more about
the contribution track and how I can get involved.

Please let me know if there is any additional information or resources that
you can provide.

Thank you for your time and consideration.

Best regards,
Nicolas Couture
Open Source Enthusiast


On Wed, Apr 3, 2024 at 9:45 AM Pierre-Elliott Bécue  wrote:

> Nicolas Couture  wrote on 27/02/2024 at
> 21:00:58+0200:
>
> > Good day,
> >
> > As I met "pollo" this morning on OFTC after inquiring about helping out
> with the adoption of virtualenvwrapper or researching more into
> > the state of packaging pyenv in Debian, he suggested a good starting
> point would be to read  https://deb.li/PyPolicy which I had not until
> > now and then join the team to help out on any team-maintained packages.
> >
> > I understand the gist of it but I'm starting to think that "pollo" might
> actually be a chicken, because he's excellent at laying out
> > eggs-amples of policy, but when it comes to packaging, he believes in
> free-range.
> >
> > On with the serious phase of this request:
> >
> > Why you want to join the team:
> >
> >  * Help maintain specific packages though my interest might be broader
> than that and I'm willing to help out on team-maintained
> >  packages to become familiar with the workflows
> >  * Salsa login: ncouture
> >  * I have read and accept
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> >
> > Best regards,
>
> Hello Nicolas,
>
> Sorry for not replying to your request earlier.
>
> And nice of you roasting pollo. :-)
>
> I'd be glad to give you access to specific repositories (and create
> those which you need to have created), but before granting you a full
> access to the group, I guess I'd like to see a bit of your contributions
> track.
>
> Would that be a fine compromise for you?
>
> --
> PEB
>

Re: Request to join the Debian Python Team

[Pierre-Elliott Bécue]

Paul Boddie  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

Re: Request to join the Debian Python Team

[Andrey Rakhmatullin]

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


signature.asc
Description: PGP signature

Re: Request to join the Debian Python Team

[Paul Boddie]

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

Re: Request to join the Debian Python Team

[Andrey Rakhmatullin]

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

Re: Request to join the Debian Python Team

[Paul Boddie]

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

Re: Request to Join Debian Python Team as a Package Maintainer

[Stefano Rivera]

Hi Pulak (2024.02.20_19:12:33_+)
> I am interested in joining the Python Team to actively contribute to the 
> maintenance of Python-related packages within Debian. I am currently 
> maintaining a set of packages (python-pylatex, python-duet, 
> python-sphinx-contributors, and python-sphinx-autodoc2) and would like to 
> collaborate with the team to bring in more packages to Debian. 

Added, welcome.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join Debian Python Team

[Stefano Rivera]

Hi Francesco (2024.01.30_12:05:04_+)
> With this email, I am asking you to let me join your team with my
> salsa username francesco.ballarin, associated with this email address.

Added to the team, welcome!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join the Debian Python Team

[Andrey Rakhmatullin]

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


signature.asc
Description: PGP signature

Re: Request to join the Debian Python Team

[Paul Boddie]

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

Re: Request to join the Debian Python Team

[Pierre-Elliott Bécue]

Hi Paul,

Paul Boddie  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


signature.asc
Description: PGP signature

Re: Request to join debian-python team

[Pierre-Elliott Bécue]

Hi,

eevelweezel  wrote on 21/01/2024 at 22:53:06+0200:

> Hello,
>
> I am working on packaging pdm, and I would like to join Debian Python Team. 
> My username on salsa is eevelweezel. 
>
> I have read and accept the Debian Python Team policy. 
>
> Best,
> ./wzl

I'd be happy to create a repository or give you a specific access on a
repository you'd like to maintain.

On the other hand giving you full group access while you seem to have no
contributions to Debian so far seems a bit far-fetched at this time.

In the meantime, you can submit Merge Requests to the projects you want
to contribute to, this would help us creating this track record I
mentioned above.

I hope you'll understand our position.

Bests,
-- 
PEB


signature.asc
Description: PGP signature

Re: Request to join the team

[Pierre-Elliott Bécue]

Hi Ricardo,

"Ricardo B. Marliere"  wrote on 29/01/2024 at 
23:07:59+0200:

> Hi,
>
> My name is Ricardo and I've been trying to get involved with Debian to
> give back to the community. I'm "rbmarliere" in Salsa [1] and I have
> made a few contributions to the Go team. However, I have more experience
> with Python and would like to help in fixing bugs for the team and
> other general QA work. I have read and accept the Debian Python Team
> Policy [2].

Considering your past contributions, I've granted you a Developer access.

Feel free to reach out when you need new repos created.

On the long-term if you contribute, I'll be happy to extend your ACLs.

Thanks, and sorry for the delay.
-- 
PEB


signature.asc
Description: PGP signature

Re: Membership request

[Pierre-Elliott Bécue]

Nicolas Couture  wrote on 27/02/2024 at 21:00:58+0200:

> Good day,
>
> As I met "pollo" this morning on OFTC after inquiring about helping out with 
> the adoption of virtualenvwrapper or researching more into
> the state of packaging pyenv in Debian, he suggested a good starting point 
> would be to read  https://deb.li/PyPolicy which I had not until
> now and then join the team to help out on any team-maintained packages.
>
> I understand the gist of it but I'm starting to think that "pollo" might 
> actually be a chicken, because he's excellent at laying out
> eggs-amples of policy, but when it comes to packaging, he believes in 
> free-range.
>
> On with the serious phase of this request:
>
> Why you want to join the team:
>
>  * Help maintain specific packages though my interest might be broader than 
> that and I'm willing to help out on team-maintained
>  packages to become familiar with the workflows
>  * Salsa login: ncouture
>  * I have read and accept 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>
> Best regards,

Hello Nicolas,

Sorry for not replying to your request earlier.

And nice of you roasting pollo. :-)

I'd be glad to give you access to specific repositories (and create
those which you need to have created), but before granting you a full
access to the group, I guess I'd like to see a bit of your contributions
track.

Would that be a fine compromise for you?

-- 
PEB


signature.asc
Description: PGP signature

Re: Request to join Debian Python team

[Pierre-Elliott Bécue]

Hi,

Xuanteng Huang  wrote on 05/03/2024 at 
10:25:03+0200:
> Hi all,
>
> I’m a newcomer to Debian community and interested in participating in Debian 
> package maintainances.
> I’m willing to maintain jupyter-cache[1], the execution cache system of 
> Jupyter Notebook under DPT, as other jupyer related package do.
>
> My Salsa login is xuantengh [2] and I’ve read the DPT policy [3] and accept 
> it.
>
> Best,
> Xuanteng Huang
>
> [1] https://github.com/executablebooks/jupyter-cache
> [2] https://salsa.debian.org/xuantengh
> [3] 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

As Christian is sponsoring your application I gave you Developer access
to the package subgroup.

This means some ACLs will be missing, but you can ask Christian to do
privileged operations you can't.

If you contribute on the long-term I'll be glad to increase your access
level.

Thanks!
-- 
PEB


signature.asc
Description: PGP signature

Re: Request to join Debian Python team

[Pierre-Elliott Bécue]

Hi Daniel,

Daniel Echeverri  wrote on 15/03/2024 at 18:20:32+0200:

> Hello Team!
>
> El sáb, 9 mar 2024 a la(s) 11:33 a.m., Daniel Echeverri (epsi...@debian.org) 
> escribió:
>
>  Hi Team,
>
>  I am interested in joining the team, because, actually I am working in 
> adopting some python apps [1][2][3]
>
>  My Salsa login is epsilon[4].
>
>  Thanks!
>
>  Regards
>
>  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065239
>  [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065241
>  [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065237
>  [4]: https://salsa.debian.org/epsilon
>
>  --
>  Daniel Echeverri
>  Debian Developer
>  Linux user: #477840
>  GPG Fingerprint:
>  D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
>
> I forgot to say, that I accept the policy team mentioned in 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>
> Thanks in advance.
>
> Kind Regards.

It'd have been best to sign your request, but giving access to a DD to
the group without such a sig is not really something problematic to me.

Access granted. :)
-- 
PEB


signature.asc
Description: PGP signature

Re: Request to Join Debian Python Team

[Pierre-Elliott Bécue]

Dear Marcos,

Marcos Rodrigues de Carvalho (aka oday)  wrote on 
19/03/2024 at 06:28:23+0200:

> Dear Debian Python Team,
>
> I hope this email finds you well. My name is 
> Marcos Rodrigues de Carvalho (aka oday),
> and I am a Debian contributor interested in joining the Debian Python
> Team.
>
> I am reaching out to express my interest in becoming a member of the team and
> contributing to Python-related package maintenance within the Debian 
> ecosystem.
> I  believe that collaborating with the Debian Python Team will allow me to
> contribute more effectively and efficiently to the Debian project.
>
> My Salsa login is: marcos.rcarvalho.
>
> I have thoroughly reviewed the team's policies outlined in the following
> document:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team.
> I fully understand and accept the responsibilities and guidelines set forth in
> the policy document.
>
> I am eager to join the team to help maintain existing packages, contribute to
> specific packages, and collaborate with other members of the Debian Python
> community.
>
> Thank you for considering my request to join the Debian Python Team. I look
> forward to the opportunity to contribute and collaborate with fellow team
> members.

First, I'd like to apologize for the long delay for you to get a reply.

Second, as you're quite new to Debian in terms of contributions, I'd
like to ask you first to point to specific repositories you'd like to
contribute to, and second, to start doing so by submitting merge
requests (which are open for anyone).

Once you'll have built sufficient trust, we'll consider a wide-range
inclusion in DPT.

I hope that you'll understand our position on this matter.

-- 
PEB


signature.asc
Description: PGP signature

Re: Request to join DPT

[Pierre-Elliott Bécue]

Hi Jakob,

Jakob Haufe  wrote on 27/03/2024 at 11:43:55+0200:
> Hi all,
>
> I recently adopted intelhex[1] and would like to continue maintaining
> it in the repo under the DPT group.
>
> My salsa username is sur5r[2].
>
> I have read the policy[3] and accept it.
>
> Cheers,
> sur5r
>
> [1] https://bugs.debian.org/976074
> [2] https://salsa.debian.org/sur5r
> [3] 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Sorry for the delay, invitation sent!

-- 
PEB


signature.asc
Description: PGP signature

Re: Team join request

[Pierre-Elliott Bécue]

Hi Vivek,

Vivek K J  wrote on 31/03/2024 at 10:38:20+0200:

> [[PGP Signed Part:Good signature from A5FF4BB3EA53C5DF Vivek K J 
>  (trust undefined) created at 2024-03-31T10:38:20+0200 
> using RSA]]
> Hey,
>
> I would like to join debian-python team for helping in maintaining some
> python packages. I've got experience in maintaining packages in ruby and
> JS teams. For now, I would like to update pmbootstrap package for fixing
> #1065637.
>
> My salsa login: vivekkj
>
> I've read python-team policy, and I'm ready to follow all the guidelines.

Invitation sent.
--
PEB


signature.asc
Description: PGP signature

Team join request

[Vivek K J]

Hey,

I would like to join debian-python team for helping in maintaining some
python packages. I've got experience in maintaining packages in ruby and
JS teams. For now, I would like to update pmbootstrap package for fixing
#1065637.

My salsa login: vivekkj

I've read python-team policy, and I'm ready to follow all the guidelines.

-- 
Regards,

Vivek K J
Debian Maintainer
---
 .''`.
Personal Website:  https://vivekkj.in   : :'  :
GPG Key: D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF `. `'`
  `-

OpenPGP_0xA5FF4BB3EA53C5DF.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: request for removal of my packages from the DPT namespace

[Thomas Goirand]

On 3/27/24 14:31, Jeroen Ploemen wrote:

On Wed, 27 Mar 2024 00:33:15 +0100
Thomas Goirand  wrote:


On 3/19/24 13:41, Jeroen Ploemen wrote:

Dear team admins,

please delete the following packages from the DPT namespace on
salsa:

cheetah
jaraco.classes
jaraco.collections
jaraco.context
jaraco.text
nfoview
ply
puremagic
python-autocommand
python-jaraco.functools
python-portend
python-rarfile
python-tempora
python-yenc
sabctools
sabnzbdplus


All of these have already been mirrored into my personal
namespace to keep a public VCS available, while gaining at least
some protection against ongoing policy violations.

Hi,

Usually, you'd ask for one of the Salsa admins to actually *move*
the packages from one namespace to another, so that there's
redirections, rather than copying somewhere else and deleting. This
can be done by a simple ticket at:

https://salsa.debian.org/salsa/support

Or is it too late, and you already cloned, and don't want to bother?


Thomas, thanks for getting back to me on this.

I would have preferred to have redirects in place, but simply
overlooked the possibility of the salsa overlords doing the moves
after figuring out gitlab wouldn't let me move things out and the
team admins in turn wouldn't be able to move anything into my
namespace.

I'll try to keep that in mind for next time; for now, please proceed
with the deletion from the team namespace as I outright lack the time
for another round of reorganising git repos for weeks to come.


Sure, no worries. Unless they authorize me to do it, I'll let the DPT 
admins do it then (as I don't want to step on their feet with my 
"overlord" power as you said... :P).


Thanks for clarifying the situation with your packages (which is what 
the change of policy is about...), and sorry for the added 
administrative work that was pushed on you because of it.


Cheers,

Thomas Goirand (zigo)

Re: request for removal of my packages from the DPT namespace

[Jeroen Ploemen]

On Wed, 27 Mar 2024 00:33:15 +0100
Thomas Goirand  wrote:

> On 3/19/24 13:41, Jeroen Ploemen wrote:
> > Dear team admins,
> > 
> > please delete the following packages from the DPT namespace on
> > salsa:
> > 
> > cheetah
> > jaraco.classes
> > jaraco.collections
> > jaraco.context
> > jaraco.text
> > nfoview
> > ply
> > puremagic
> > python-autocommand
> > python-jaraco.functools
> > python-portend
> > python-rarfile
> > python-tempora
> > python-yenc
> > sabctools
> > sabnzbdplus
> > 
> > 
> > All of these have already been mirrored into my personal
> > namespace to keep a public VCS available, while gaining at least
> > some protection against ongoing policy violations.  
> Hi,
> 
> Usually, you'd ask for one of the Salsa admins to actually *move*
> the packages from one namespace to another, so that there's
> redirections, rather than copying somewhere else and deleting. This
> can be done by a simple ticket at:
> 
> https://salsa.debian.org/salsa/support
> 
> Or is it too late, and you already cloned, and don't want to bother?

Thomas, thanks for getting back to me on this.

I would have preferred to have redirects in place, but simply
overlooked the possibility of the salsa overlords doing the moves
after figuring out gitlab wouldn't let me move things out and the
team admins in turn wouldn't be able to move anything into my
namespace.

I'll try to keep that in mind for next time; for now, please proceed
with the deletion from the team namespace as I outright lack the time
for another round of reorganising git repos for weeks to come.


pgpyC069KPAIP.pgp
Description: OpenPGP digital signature

Request to join DPT

[Jakob Haufe]

Hi all,

I recently adopted intelhex[1] and would like to continue maintaining
it in the repo under the DPT group.

My salsa username is sur5r[2].

I have read the policy[3] and accept it.

Cheers,
sur5r

[1] https://bugs.debian.org/976074
[2] https://salsa.debian.org/sur5r
[3] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

-- 
ceterum censeo microsoftem esse delendam.


pgpNQaVE73H1Z.pgp
Description: OpenPGP digital signature

Re: request for removal of my packages from the DPT namespace

[Thomas Goirand]

On 3/19/24 13:41, Jeroen Ploemen wrote:

Dear team admins,

please delete the following packages from the DPT namespace on salsa:

cheetah
jaraco.classes
jaraco.collections
jaraco.context
jaraco.text
nfoview
ply
puremagic
python-autocommand
python-jaraco.functools
python-portend
python-rarfile
python-tempora
python-yenc
sabctools
sabnzbdplus


All of these have already been mirrored into my personal namespace to
keep a public VCS available, while gaining at least some protection
against ongoing policy violations.

Hi,

Usually, you'd ask for one of the Salsa admins to actually *move* the 
packages from one namespace to another, so that there's redirections, 
rather than copying somewhere else and deleting. This can be done by a 
simple ticket at:


https://salsa.debian.org/salsa/support

Or is it too late, and you already cloned, and don't want to bother?

Cheers,

Thomas Goirand (zigo)

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[Andreas Tille]

Am Wed, Mar 20, 2024 at 11:04:41AM + schrieb c.bu...@posteo.jp:
> Sorry, guys but I don't understand nearly nothing of what you explain here
> because I don't know the tool chain nor the process. But I hope you all do.
> 
> I modified the section:
> https://wiki.debian.org/Python/GitPackaging#Policies
> 
> Feel free to improve my modification.

IMHO the best fit is:

- * '''Patch management regime''': The Debian Python team has chosen `gbp pq`. 
But it is also possible to use `quilt`.
+ * '''Patch management regime''': The Debian Python team recommends `gbp pq` 
as interface to `quilt` patches.

Kind regards
   Andreas.

-- 
https://fam-tille.de

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[c . buhtz]

Sorry, guys but I don't understand nearly nothing of what you explain 
here because I don't know the tool chain nor the process. But I hope you 
all do.


I modified the section:
https://wiki.debian.org/Python/GitPackaging#Policies

Feel free to improve my modification.
But please keep the target audience of this wiki page in mind. Keep it 
short and simple. Background infos and reationals should go into another 
document (e.g. a policy or DPT guide).


Kind
Christian Buhtz

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[Andreas Tille]

Hi Brian,

Am Wed, Mar 20, 2024 at 10:59:34AM +1100 schrieb Brian May:
> Andreas Tille  writes:
> 
> > As someone who touched a lot of packages (>2000) I've always used quilt
> > successfully and have seen quilt patches used by the majority of all
> > those packages.  This is not only true for DPT than generally in Debian.
> > Considering quilt as not recommended is definitely not matching the
> > reality and should not be written in Wiki.
> 
> gbp pq is just another way of quilt patches. The debian/patches written
> by gbp pq are compatable with quilt. The patches written to by quilt can
> be read using gbp pq import.
> 
> While gbp pq has a patch queue stored in git, you probably don't want to
> push this to a shared repo.
> 
> But: If you create patches with quilt, and then import and export them
> using gbp pq you might find that gbp pq wants to make minor/trivial
> changes to the unchanged patch files. Which can be irritating when
> making security patches, etc. Maybe this is why the practise is not
> recommended?

Thanks a lot for the explanation.  So the Wiki should be changed in this
direction it should include this explanation.  In any case creating the
impression quilt should not be used does not reflect reality.

Kind regards
   Andreas.

-- 
https://fam-tille.de

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[Brian May]

Andreas Tille  writes:

> As someone who touched a lot of packages (>2000) I've always used quilt
> successfully and have seen quilt patches used by the majority of all
> those packages.  This is not only true for DPT than generally in Debian.
> Considering quilt as not recommended is definitely not matching the
> reality and should not be written in Wiki.

gbp pq is just another way of quilt patches. The debian/patches written
by gbp pq are compatable with quilt. The patches written to by quilt can
be read using gbp pq import.

While gbp pq has a patch queue stored in git, you probably don't want to
push this to a shared repo.

But: If you create patches with quilt, and then import and export them
using gbp pq you might find that gbp pq wants to make minor/trivial
changes to the unchanged patch files. Which can be irritating when
making security patches, etc. Maybe this is why the practise is not
recommended?
-- 
Brian May @ Debian

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[Andreas Tille]

Hi,

Am Tue, Mar 19, 2024 at 11:48:47AM + schrieb weepingclown:
> Improving docs is a very important thing, I appreciate your effort.

+1
 
> I quickly went through thr diff off your changes and it seems that you've 
> changed the wiki to mention that using quilt is not recommended. While gbp pq 
> is what the python team prefers indeed, the python team policy does not 
> prevent quilt usage and instead mentions explicitly that optionally quilt can 
> be used. As such, I do not find mentioning "using quilt is not recommended" 
> appropriate as it has the connotation "you should not use quilt". As someone 
> who takes advantage of the policy leniency and find quilt easier than gbp pq, 
> I thought this has to be mentioned.

As someone who touched a lot of packages (>2000) I've always used quilt
successfully and have seen quilt patches used by the majority of all
those packages.  This is not only true for DPT than generally in Debian.
Considering quilt as not recommended is definitely not matching the
reality and should not be written in Wiki.

> Once again, improving the wiki is a great thing to do. Please keep up the 
> good work :)

+1

Kind regards
   Andreas.

> Best,
> Ananthu
> 
> On 19 March 2024 10:47:07 am UTC, c.bu...@posteo.jp wrote:
> >Hello together,
> >
> >I still struggle with the docs but also improving them.
> >
> >First of all please review my modifications to make sure there are no 
> >misleading errors in the content. I restructured the "Policy" section [1]. I 
> >shortened and rephrased the text. I also added a sub section "Setup and 
> >configure the system" with missing details.
> >
> >I think in the long run I will add setup information to 
> >https://wiki.debian.org/Salsa and link to it from Python/GitPackaging wiki 
> >page.
> >Please see my Salsa related questions in the other thread.
> >
> >As a side note: There is an open discussion at MoinWiki to improve the 
> >handling of headings and page titles [2]. The later should not be part of 
> >the TOC.
> >
> >Best Regards,
> >Christian Buhtz
> >
> >[1] -- 
> >[2] -- 
> >

-- 
http://fam-tille.de

request for removal of my packages from the DPT namespace

[Jeroen Ploemen]

Dear team admins,

please delete the following packages from the DPT namespace on salsa:

cheetah
jaraco.classes
jaraco.collections
jaraco.context
jaraco.text
nfoview
ply
puremagic
python-autocommand
python-jaraco.functools
python-portend
python-rarfile
python-tempora
python-yenc
sabctools
sabnzbdplus


All of these have already been mirrored into my personal namespace to
keep a public VCS available, while gaining at least some protection
against ongoing policy violations.


pgpe_6_ro4Wy1.pgp
Description: OpenPGP digital signature

Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[weepingclown]

Hi Christian,

Improving docs is a very important thing, I appreciate your effort.

I quickly went through thr diff off your changes and it seems that you've 
changed the wiki to mention that using quilt is not recommended. While gbp pq 
is what the python team prefers indeed, the python team policy does not prevent 
quilt usage and instead mentions explicitly that optionally quilt can be used. 
As such, I do not find mentioning "using quilt is not recommended" appropriate 
as it has the connotation "you should not use quilt". As someone who takes 
advantage of the policy leniency and find quilt easier than gbp pq, I thought 
this has to be mentioned.

Once again, improving the wiki is a great thing to do. Please keep up the good 
work :)

Best,
Ananthu

On 19 March 2024 10:47:07 am UTC, c.bu...@posteo.jp wrote:
>Hello together,
>
>I still struggle with the docs but also improving them.
>
>First of all please review my modifications to make sure there are no 
>misleading errors in the content. I restructured the "Policy" section [1]. I 
>shortened and rephrased the text. I also added a sub section "Setup and 
>configure the system" with missing details.
>
>I think in the long run I will add setup information to 
>https://wiki.debian.org/Salsa and link to it from Python/GitPackaging wiki 
>page.
>Please see my Salsa related questions in the other thread.
>
>As a side note: There is an open discussion at MoinWiki to improve the 
>handling of headings and page titles [2]. The later should not be part of the 
>TOC.
>
>Best Regards,
>Christian Buhtz
>
>[1] -- 
>[2] -- 
>

Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

[c . buhtz]

Hello together,

I still struggle with the docs but also improving them.

First of all please review my modifications to make sure there are no 
misleading errors in the content. I restructured the "Policy" section 
[1]. I shortened and rephrased the text. I also added a sub section 
"Setup and configure the system" with missing details.


I think in the long run I will add setup information to 
https://wiki.debian.org/Salsa and link to it from Python/GitPackaging 
wiki page.

Please see my Salsa related questions in the other thread.

As a side note: There is an open discussion at MoinWiki to improve the 
handling of headings and page titles [2]. The later should not be part 
of the TOC.


Best Regards,
Christian Buhtz

[1] -- 
[2] -- 

Request to Join Debian Python Team

[aka oday]

Dear Debian Python Team,

I hope this email finds you well. My name is 
Marcos Rodrigues de Carvalho (aka oday),
and I am a Debian contributor interested in joining the Debian Python
Team.

I am reaching out to express my interest in becoming a member of the team and
contributing to Python-related package maintenance within the Debian ecosystem.
I  believe that collaborating with the Debian Python Team will allow me to
contribute more effectively and efficiently to the Debian project.

My Salsa login is: marcos.rcarvalho.

I have thoroughly reviewed the team's policies outlined in the following
document:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team.
I fully understand and accept the responsibilities and guidelines set forth in
the policy document.

I am eager to join the team to help maintain existing packages, contribute to
specific packages, and collaborate with other members of the Debian Python
community.

Thank you for considering my request to join the Debian Python Team. I look
forward to the opportunity to contribute and collaborate with fellow team
members.

Best regards,


-- 
Marcos Rodrigues de Carvalho (aka oday) 

Re: Request to join Debian Python team

[Daniel Echeverri]

Hello Team!

El sáb, 9 mar 2024 a la(s) 11:33 a.m., Daniel Echeverri (epsi...@debian.org)
escribió:

> Hi Team,
>
> I am interested in joining the team, because, actually I am working in
> adopting some python apps [1][2][3]
>
> My Salsa login is epsilon[4].
>
> Thanks!
>
> Regards
>
> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065239
> [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065241
> [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065237
> [4]: https://salsa.debian.org/epsilon
>
> --
> Daniel Echeverri
> Debian Developer
> Linux user: #477840
> GPG Fingerprint:
> D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
>

I forgot to say, that I accept the policy team mentioned in
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks in advance.

Kind Regards.


-- 
Daniel Echeverri
Debian Developer
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Re: Feature Request (docu): Define "dsc-file"

[Andreas Tille]

Hi again,

Am Fri, Mar 15, 2024 at 11:06:13AM + schrieb c.bu...@posteo.jp:
> Thanks for all your answers.
> 
> Am 15.03.2024 11:07 schrieb Andreas Tille:
> > Please try a web search for instance with the terms
> > [...]
> > which brought several helpful links.  Alternatively you can ask ChatGPT,
> > Gemini or the LLM of your choice
> 
> I am a bit shocked about that advise. For what was Hypertext invented?

Sorry if I might have been a bit blunt. I admit you Wiki changes are OK.

> My mail was not a support question but a Feature Request. Of course I am
> able to search this myself. But this won't help future readers and also
> won't improve the quality of the docs. The latter is my intention.

I'm fine if someone wants to improve the docs.

> Basic knowledge is needed to understand? Of course this is always the case
> in every section of live and the world.
> But why not point to that knowledge? That is what Hypertext is invented for.
> 
> > I do not think that things which are easy to find
> 
> No it is not "easy" when I have to run search engine for it. It is also not
> sustainable.

Well, I'm usually a fan of letting newcomers enhance the docs since
experts might fail to see beginners hurdles.  I admit I was afraid that
the request would end up explaining very basic packaging stuff at places
where the topic is specific about using Git for the Python team.

> > and is pretty clear
> > for the average reader of the text you want to extend should be written
> > down here.
> 
> I don't understand that section.
 
I mean that the topic of that page is "Using git for team packages" and
we should not blur that topic with information which is very basic for
the intended user audience.  Adding a hyperlink as you did is OK.
Explaining .dsc format is over the top IMHO.

To make sure you will not misunderstand me:  I did not wanted to scare
away a newcomer by redirecting to other resources of information.  I
hope that my hints where helpful enough for you to know now what .dsc
is.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Re: Feature Request (docu): Define "dsc-file"

[c . buhtz]

Close via 
https://wiki.debian.org/Python/GitPackaging?action=diff=97=98

Re: Feature Request (docu): Define "dsc-file"

[c . buhtz]

Thanks for all your answers.

Am 15.03.2024 11:07 schrieb Andreas Tille:

Please try a web search for instance with the terms
[...]
which brought several helpful links.  Alternatively you can ask 
ChatGPT,

Gemini or the LLM of your choice


I am a bit shocked about that advise. For what was Hypertext invented?

My mail was not a support question but a Feature Request. Of course I am 
able to search this myself. But this won't help future readers and also 
won't improve the quality of the docs. The latter is my intention.


Basic knowledge is needed to understand? Of course this is always the 
case in every section of live and the world.
But why not point to that knowledge? That is what Hypertext is invented 
for.



I do not think that things which are easy to find


No it is not "easy" when I have to run search engine for it. It is also 
not sustainable.



and is pretty clear
for the average reader of the text you want to extend should be written
down here.


I don't understand that section.

Re: Feature Request (docu): Define "dsc-file"

[Andrey Rakhmatullin]

On Fri, Mar 15, 2024 at 07:39:39AM +, c.bu...@posteo.jp wrote:
> Hi,
> 
> this is a feature request to someone who has access and the knowledge to
> improve.
> 
> Description of the problem:
> 
> The second paragraph in
> <https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package> tell me
> about importing a "dsc-file" without explaining what a dsc-file is or why I
> have to import it. The knowledge background is missing.
Most of the Debian packaging docs assume at least basic knowledge about
Debian source and binary packages.

> Suggested solution:
> Create or locate the dsc-file definition in the wiki. 
I'm not sure if it makes sense to cross-link basic stuff on all wiki
pages, to be honest. But that's
https://wiki.debian.org/Packaging/SourcePackage


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Feature Request (docu): Define "dsc-file"

[Andreas Tille]

Hi

Am Fri, Mar 15, 2024 at 07:39:39AM + schrieb c.bu...@posteo.jp:
> Hi,
> 
> this is a feature request to someone who has access and the knowledge to
> improve.
> 
> Description of the problem:
> 
> The second paragraph in
> <https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package> tell me
> about importing a "dsc-file" without explaining what a dsc-file is or why I
> have to import it. The knowledge background is missing.

Please try a web search for instance with the terms

debian source format dsc file

which brought several helpful links.  Alternatively you can ask ChatGPT,
Gemini or the LLM of your choice

Can you explain what "import an existing .dsc file" means?

which produced a very verbose and good understandable text for me.

I do not think that things which are easy to find and is pretty clear
for the average reader of the text you want to extend should be written
down here.

Thank you for your suggestion anyway
Andreas.

 
> There is a hyper link behind the text "import an existing .dsc file"
> pointing to <https://wiki.debian.org/PackagingWithGit/GitDpm/ImportDsc>.
> Regarding that URL I assume this wiki entry is not maintained by DPT. But it
> also do not explain about dsc-file.
> 
> Suggested solution:
> Create or locate the dsc-file definition in the wiki. It should be an extra
> page. Then just use a hyperlink in your own docu to point to that
> definition.
> 
> "import an existing .dsc file"
>  ^^ ^
>  I  L <https://wiki.debian.org/DSC-DEFINITION>
>  L <https://wiki.debian.org/PackagingWithGit/GitDpm/ImportDsc>
> 
> Please let me know if there is another "channel" where I should open such
> requests.
> 
> Thanks in advance
> Christian Buhtz
> 
> 

-- 
http://fam-tille.de

Feature Request (docu): Define "dsc-file"

[c . buhtz]

Hi,

this is a feature request to someone who has access and the knowledge to 
improve.


Description of the problem:

The second paragraph in 
<https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package> 
tell me about importing a "dsc-file" without explaining what a dsc-file 
is or why I have to import it. The knowledge background is missing.


There is a hyper link behind the text "import an existing .dsc file" 
pointing to <https://wiki.debian.org/PackagingWithGit/GitDpm/ImportDsc>. 
Regarding that URL I assume this wiki entry is not maintained by DPT. 
But it also do not explain about dsc-file.


Suggested solution:
Create or locate the dsc-file definition in the wiki. It should be an 
extra page. Then just use a hyperlink in your own docu to point to that 
definition.


"import an existing .dsc file"
 ^^ ^
 I  L <https://wiki.debian.org/DSC-DEFINITION>
 L <https://wiki.debian.org/PackagingWithGit/GitDpm/ImportDsc>

Please let me know if there is another "channel" where I should open 
such requests.


Thanks in advance
Christian Buhtz

Re: Request to join Debian Python team

[Christian Kastner]

Hi admins,

On 2024-03-09 16:49, Xuanteng Huang wrote:
> Sorry for bothering. I’m writing this to kindly remind this request.
> And please let me know if there is anything to fix.

I fully support this request, if it's any help. Xuanteng is working with
the Debian ROCm Team but I asked him to publish the general Python stuff
under the DPT.

Best,
Christian

Request to join Debian Python team

[Daniel Echeverri]

Hi Team,

I am interested in joining the team, because, actually I am working in
adopting some python apps [1][2][3]

My Salsa login is epsilon[4].

Thanks!

Regards

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065239
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065241
[3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065237
[4]: https://salsa.debian.org/epsilon

--
Daniel Echeverri
Debian Developer
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Re: Request to join Debian Python team

[Xuanteng Huang]

Hi DPT,

Sorry for bothering. I’m writing this to kindly remind this request.
And please let me know if there is anything to fix.

Regards,
Xuanteng


> On Mar 5, 2024, at 16:25, Xuanteng Huang  wrote:
> 
> Hi all,
> 
> I’m a newcomer to Debian community and interested in participating in Debian 
> package maintainances.
> I’m willing to maintain jupyter-cache[1], the execution cache system of 
> Jupyter Notebook under DPT, as other jupyer related package do.
> 
> My Salsa login is xuantengh [2] and I’ve read the DPT policy [3] and accept 
> it.
> 
> Best,
> Xuanteng Huang
> 
> [1] https://github.com/executablebooks/jupyter-cache
> [2] https://salsa.debian.org/xuantengh
> [3] 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> 

Request to join Debian Python team

[Xuanteng Huang]

Hi all,

I’m a newcomer to Debian community and interested in participating in Debian 
package maintainances.
I’m willing to maintain jupyter-cache[1], the execution cache system of Jupyter 
Notebook under DPT, as other jupyer related package do.

My Salsa login is xuantengh [2] and I’ve read the DPT policy [3] and accept it.

Best,
Xuanteng Huang

[1] https://github.com/executablebooks/jupyter-cache
[2] https://salsa.debian.org/xuantengh
[3] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst



signature.asc
Description: Message signed with OpenPGP

Re: Request to Join Debian Python Team as a Package Maintainer

[Pulak Bhushan]

Hi Debian Python Team, 


I am following up on my previous request. Could someone please assist
with adding me to th group?

Salsa ID: pulakb

Thank you. 

Regards, 
Pulak Bhushan


On Wed, Feb 21, 2024 at 12:42:33AM +0530, Pulak Bhushan wrote:

Dear Debian Python Team,

I am writing to express my interest in joining the Debian Python Team as a 
package maintainer.

I am interested in joining the Python Team to actively contribute to the 
maintenance of Python-related packages within Debian. I am currently 
maintaining a set of packages (python-pylatex, python-duet, 
python-sphinx-contributors, and python-sphinx-autodoc2) and would like to 
collaborate with the team to bring in more packages to Debian.


My Salsa login is: pulakb

I have thoroughly read the Python Team's policy document, and I accept its 
terms. I am committed to adhering to the guidelines and standards outlined in 
the policy to ensure the smooth functioning of the team and the Debian project 
as a whole.

Thank you for considering my application. I look forward to the opportunity to 
contribute to the Debian Python Team and help enhance the Python ecosystem 
within Debian.

Regards
Pulak Bhushan
pulakbhus...@gmail.com <mailto:pulakbhus...@gmail.com>






signature.asc
Description: PGP signature

Membership request

[Nicolas Couture]

Good day,

As I met "pollo" this morning on OFTC after inquiring about helping out
with the adoption of virtualenvwrapper or researching more into the state
of packaging pyenv in Debian, he suggested a good starting point would be
to read  https://deb.li/PyPolicy which I had not until now and then join
the team to help out on any team-maintained packages.

I understand the gist of it but I'm starting to think that "pollo" might
actually be a chicken, because he's excellent at laying out eggs-amples of
policy, but when it comes to packaging, he believes in free-range.

On with the serious phase of this request:

*Why you want to join the team:*


   - Help maintain specific packages though my interest might be broader
   than that and I'm willing to help out on team-maintained packages to become
   familiar with the workflows
   - Salsa login: ncouture
   - I have read and accept
   
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst


Best regards,

Nicolas Couture
Open Source Enthusiast

Request to Join Debian Python Team as a Package Maintainer

[Pulak Bhushan]

Dear Debian Python Team,

I am writing to express my interest in joining the Debian Python Team as a 
package maintainer.

I am interested in joining the Python Team to actively contribute to the 
maintenance of Python-related packages within Debian. I am currently 
maintaining a set of packages (python-pylatex, python-duet, 
python-sphinx-contributors, and python-sphinx-autodoc2) and would like to 
collaborate with the team to bring in more packages to Debian. 


My Salsa login is: pulakb

I have thoroughly read the Python Team's policy document, and I accept its 
terms. I am committed to adhering to the guidelines and standards outlined in 
the policy to ensure the smooth functioning of the team and the Debian project 
as a whole.

Thank you for considering my application. I look forward to the opportunity to 
contribute to the Debian Python Team and help enhance the Python ecosystem 
within Debian.

Regards
Pulak Bhushan 
pulakbhus...@gmail.com 



smime.p7s
Description: S/MIME cryptographic signature

Request to Join Debian Python Team

[marcosrcarvalho42]

Dear Debian Python Team,

I hope this email finds you well. I am writing to express my strong interest in
joining the Debian Python Team. Working with Debian has been a dream of mine,
and I am eager to contribute to the Python ecosystem within the Debian project.

My Salsa login is: marcos.rcarvalho

I am passionate about Python and its role in the open-source community. I have
been actively involved in maintaining Python packages and contributing to
various Python projects. Joining the Debian Python Team would not only allow me
to continue maintaining my current packages within the team but also provide me
with an opportunity to collaborate with other team members and contribute to
maintaining specific packages.

I believe that being part of the Debian Python Team would not only enhance my 
skills but also enable me to make meaningful contributions to the Debian project
as a whole.

Thank you for considering my request. I look forward to the possibility of 
working together with you all.

Best regards,
  
  Marcos Rodrigues de Carvalho (aka oday) 

Request to join Debian Python Team

[Francesco Ballarin]

Dear Debian Python Team managers,
my name is Francesco Ballarin, and I am currently training to become a
Debian Maintainer under the sponsorship of Drew Parsons.

With this email, I am asking you to let me join your team with my
salsa username francesco.ballarin, associated with this email address.
The rationale for this request is the following:
* I helped getting
https://salsa.debian.org/python-team/packages/python-scooby started.
python-scooby will be maintained within the Debian Python Team.
* I filed a RFS for
https://salsa.debian.org/python-team/packages/pusimp . If accepted,
pusimp would be maintained within the Debian Python Team.
* I am working on https://salsa.debian.org/science-team/python-pyvista
within the science team. python-pyvista depends on several packages
maintained by the Debian Python Team, hence it would be beneficial if
I were part of both teams.

I confirm I have read
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and accept the policies there.

Best regards,
Francesco Ballarin
[http://static.unicatt.it/ext-portale/5xmille_firma_mail_2023.jpg] 
<https://www.unicatt.it/uc/5xmille>

Request to join the team

[Ricardo B. Marliere]

Hi,

My name is Ricardo and I've been trying to get involved with Debian to
give back to the community. I'm "rbmarliere" in Salsa [1] and I have
made a few contributions to the Go team. However, I have more experience
with Python and would like to help in fixing bugs for the team and
other general QA work. I have read and accept the Debian Python Team
Policy [2].


Thank you,
-   Ricardo.

---
[1] https://salsa.debian.org/rbmarliere
[2] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Request to join debian-python team

[eevelweezel]

Hello,

I am working on packaging pdm, and I would like to join Debian Python Team.
My username on salsa is eevelweezel.

I have read and accept the Debian Python Team policy.

Best,
./wzl

Request to join the Debian Python Team

[Paul Boddie]

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

Re: Request to join the team

[Eduardo M KALINOWSKI]

On 31/12/2023 15:02, Stefano Rivera wrote:

Hi Eduardo (2023.11.19_12:52:22_+)

I'd like to join the Python team. I intend to package the browser_cookie3
module (https://github.com/borisbabic/browser_cookie3), ITP #1056159.


What's the use-case for this package in Debian? It's a bit of a weird
library (digging around in the user's browser profile isn't something
expected).


The general use case is mostly for scraping utilities that require a 
session cookie, one logs in to the site, then this library can help 
getting the cookie so that the requests including the cookie can be made.


The specific use case is that a next version of instaloader 
(https://tracker.debian.org/pkg/instaloader), a Instagram scraper, will 
probably require this library (the current RC version includes the 
feature that uses this library).



Please prepare some packaging on salsa and get some review of it. I
don't really like to add members to the team when the only work I can
see of theirs is an email requesting membership...


As a matter of fact, I have already done so: 
https://lists.debian.org/debian-python/2023/12/msg00042.html . The 
package is in my personal salsa area: 
https://salsa.debian.org/ekalin/browser-cookie3


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: Request to join the team

[Stefano Rivera]

Hi Alexandre (2023.12.10_02:39:08_+)
> I'm interested:
> - fixing the bug I submitted
> - checking if old python2 compatibility layers are actually still used:
>- unittest2
>- future
>- six
>- dose1
>- 
>( I also check upstreams & send PR if upstream is still active)
> 
> - add typing annotations to native packages
> (alike python3-debian, python3-debconf, apt-listchanges ...)
> 
> - helping with Py3.12 support & random RC bugs

Added, welcome to the team. We always need more people do this kind of
work.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join the team

[Stefano Rivera]

Hi Fabio (2023.12.12_21:08:57_+)
> Hi, I would like to join the Debian Python team for help to maintain
> bleachbit, that I already helped, and possible occasional help to other
> packages with low or zero activity.

Added, welcome to the team!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to Join the Debian Python Team

[Stefano Rivera]

Hi Dale (2023.12.21_22:23:20_+)
> My Salsa ID is: doge-tech [1]

Added, welcome to the team!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join the team

[Stefano Rivera]

Hi Matthias (2023.12.09_20:50:29_+)

> My username on Salsa is mak as well, and I have read the policy
> document at 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and I accept it.

Added, welcome to the team!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join the team

[Stefano Rivera]

Hi Eduardo (2023.11.19_12:52:22_+)
> I'd like to join the Python team. I intend to package the browser_cookie3
> module (https://github.com/borisbabic/browser_cookie3), ITP #1056159.

What's the use-case for this package in Debian? It's a bit of a weird
library (digging around in the user's browser profile isn't something
expected).

Please prepare some packaging on salsa and get some review of it. I
don't really like to add members to the team when the only work I can
see of theirs is an email requesting membership...

I just want to see something that shows that you're likely to follow
through with this package maintenance.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Request to Join the Debian Python Team

[Dale Richards]

Dear all,

First off, as a long time lover of both Debian and Python I'd like to thank you 
for all the
work you've done in building and maintaining the Debian Python ecosystem. Now 
it's my turn
to give back. ;)

I'd like to join the team so I can help maintain Python-related packages 
currently in
Debian, as well as contribute new packages where I believe there is a benefit 
to the Debian
community. In particular, I'm eager to help squash the outstanding Python 3.12 
bugs in
current packages, as well helping with other outstanding bugs and out-of-date 
packages.

My Salsa ID is: doge-tech [1]

My contributions so far include updates/fixes for aioquic[2] and 
haproxy-log-analysis[3],
as well as the new package python-dbutils[4]. 

Outside of Debian, I work as an information security manager, so as well as 
using Python on
a regular basis I also have a keen eye for security issues and fixes.

I have read, understood and accepted the Debian Python Team Policy[5].

Thank you for your consideration!

Best regards,
Dale Richards


[1] https://salsa.debian.org/doge-tech
[2] https://salsa.debian.org/python-team/packages/aioquic/-/merge_requests/1
[3] 
https://salsa.debian.org/python-team/packages/haproxy-log-analysis/-/merge_requests/2
[4] https://mentors.debian.net/package/python-dbutils/
[5] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Re: Request for getting added to the team

[Stefano Rivera]

Hi Gregor (2023.08.17_09:45:22_+)
> herewith I request getting added to the Debian Python Team.
> 
> The reason for this is that I'd like to package Darker [0] and possibly more
> libraries and applications in the future.
> 
> My Salsa login is "gdstr" [1].

Added, sorry I missed this before.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Request to join the team

[Fabio Fantoni]

Hi, I would like to join the Debian Python team for help to maintain 
bleachbit, that I already helped, and possible occasional help to other 
packages with low or zero activity.


My salsa login is fantu and I'm a DM.

I have read 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst, 
and I accept it.




OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Request to join the team

[Alexandre Detiste]

Hi,

I would like to join the Debian Python team too,
my Salsa login is detiste-guest.


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

I'm interested:
- fixing the bug I submitted
- checking if old python2 compatibility layers are actually still used:
   - unittest2
   - future
   - six
   - dose1
   - 
   ( I also check upstreams & send PR if upstream is still active)

- add typing annotations to native packages
(alike python3-debian, python3-debconf, apt-listchanges ...)

- helping with Py3.12 support & random RC bugs

Greetings

Request to join the team

[Matthias Klumpp]

Hi everyone!

I would like to join the Debian Python team, primarily to
maintain/update python-firehose (I got permission from paultag for
that), and potentially to add more Python packages, as I am about to
package a larger Python project for Debian (the only thing that seems
to be missing in our repos is mautrix-python though).

My username on Salsa is mak as well, and I have read the policy
document at 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and I accept it.

Thanks to everyone for maintaining Python and its packages, it's a
great resource and I am looking forward to helping out with the
firehose package.
Best,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Request to join the team

[Eduardo M KALINOWSKI]

I'd like to join the Python team. I intend to package the 
browser_cookie3 module (https://github.com/borisbabic/browser_cookie3), 
ITP #1056159.


My salsa login is ekalin.

I've read and accept the Python Python policy.


Thanks,

--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: Request for DPT salsa access

[Stefano Rivera]

Hi weepingclown (2023.11.12_11:44:44_+)
> I would like to request for DPT salsa access so that I can work on packages
> with the Python Team. I have a few packages that I would like to work on and
> am currently packaging yte and its dependency dpath-python.

Added. Welcome to the team!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join Python Team -Packaging disptrans and gradientmodel

[Stefano Rivera]

Hi Yogeswaran (2023.11.08_16:51:47_+)
> I'm packaging two Python packages that comprise analysis software and
> models, making them accessible to the scientific community. I would like
> to be part of the Python Team and maintain those two packages within the
> team.

Added, welcome to the team.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Request for DPT salsa access

[weepingclown]

Hello Debian Python Team,

I would like to request for DPT salsa access so that I can work on 
packages with the Python Team. I have a few packages that I would like 
to work on and am currently packaging yte and its dependency dpath-python.


My salsa username is weepingclown. I have read the Debian Python Team 
Policy 
(https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst) 
and agree to its conditions.


Thanks

--

PGP: BC55 8A19 E57C 716D D12F 2FA2 EEED 479E 6CEC F707

Request to join Python Team -Packaging disptrans and gradientmodel

[Yogeswaran Umasankar]

Hi,
I'm packaging two Python packages that comprise analysis software and
models, making them accessible to the scientific community. I would like
to be part of the Python Team and maintain those two packages within the
team.

Salsa login: yogu

I read the Policy
(https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst)
and I accept it.

Best regards,
Yogeswaran Umasankar.

Re: Request to join Python Team, maintaining B2 packages

[Stefano Rivera]

Hi Jiri (2023.11.06_10:03:03_+)
> I'd like to join Python team to maintain B2 packages, specifically:

Added, welcome.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Request to join Python Team, maintaining B2 packages

[Jiri Suchan]

Hi,
I'd like to join Python team to maintain B2 packages, specifically:

- https://salsa.debian.org/python-team/packages/python-b2sdk/
- https://salsa.debian.org/python-team/packages/backblaze-b2/

Hereby I confirm I read the Debian Team Policy (
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst)
and I accept it.

My salsa login is `yedpodtrzitko`

Kind regards,
Jiri Suchan

Re: Request to join python team

[Stefano Rivera]

Hi Santiago (2023.10.25_14:43:34_+)
> I'd like to work on QA issues. Mainly FTBFS bugs, and mainly ensuring that
> they are backported to stable if needed (with similar aim I joined debian-med
> and go team).
> 
> I've read Python Policy and accept it.

Added, welcome! We could always use more people willing to work across
the team, and not just trying to add their own packages with the minimum
effort :)

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request access to salsa for python package for gitlab-emulator

[Stefano Rivera]

Hi Ian (2023.10.23_12:09:59_+)
> Hi, I'm the owner/maintainer of the gitlab-emulator project
> https://gitlab.com/cunity/gitlab-emulator  I'd like to request access
> to Salsa to introduce a debian package for gitlab-emulator.

Sorry, I'm afraid the Python Team doesn't gate salsa access. You need to
get an account before joining the team. If your account hasn't been
approved, go and chase the salsa team on #salsa on IRC.

This does sound like a useful package that would be nice to have in
Debian. I suggest filing an ITP bug and starting to work on it.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join the Python Team

[Stefano Rivera]

Hi Guilherme (2023.10.21_23:28:42_+)
> I would like to join the Python Team on Salsa. I'm currently working on
> packaging pytest-flake8-path and flake8-spellcheck.

Added, welcome to the team.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join Python Team

[Stefano Rivera]

Hi Alexander (2023.10.19_14:36:35_+)
> I would like to join the Python Team on Salsa

Added, welcome to the team

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join Python Team - Packaging Thumbor smart imaging service

[Stefano Rivera]

Hi Raphael (2023.10.18_20:11:57_+)
> I'm packaging a Python tool named Thumbor and I would like to enter the team 
> to upload the package under the Gitlab Salsa team umbrella.
> My salsa login is: raphael.rossi https://salsa.debian.org/raphael.rossi
> 
> I've read and agree with the Debian Python Team - Policy [1].

Added, too. Welcome!

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Request to join Python Team - Packaging Thumbor smart imaging service

[Stefano Rivera]

Hi Pedro (2023.10.18_19:55:38_+)
> I'm packaging a Python tool named Thumbor and I would like to enter the
> team to upload the package under the Gitlab Salsa team umbrella.
> My salsa login is: devppjr 
> 
> I've read and agree with the Debian Python Team - Policy [1].

Added, welcome.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Request to join python team

[Santiago Vila]

Hello.

I'd like to work on QA issues. Mainly FTBFS bugs, and mainly ensuring that
they are backported to stable if needed (with similar aim I joined debian-med
and go team).

I've read Python Policy and accept it.

Thanks.

Re: Python module packaging request to help me maintain apt-listchanges

[Timo Röhling]

Hi Jonathan,

* Jonathan Kamens  [2023-10-23 06:00]:
I'm writing to ask for your assistance in getting pytest-subprocess 
packaged into Debian:


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


As one of the uploaders for pytest, I am happy to sponsor you!

Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Re: Python module packaging request to help me maintain apt-listchanges

[Ian Norton]

Pytest-subprocess looks interesting, I'd probably myself have done the
mocks directly using pytest-mock but it's good to know this exists.

On Mon, 23 Oct 2023, 12:49 Jonathan Kamens,  wrote:

> Hello all,
>
> I'm writing to ask for your assistance in getting pytest-subprocess
> packaged into Debian:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053360
>
> The use case here is that I've taken over maintenance of apt-listchanges
> and added among other things a unit-test suite, and I want to make the
> unit-tests cover as much of the code as possible, and to do that I need to
> be able to mock out subprocess calls which apt-listchanges does quite a lot
> of in its work.
>
> I am happy to do most of the work if someone on this list is willing to
> mentor me, since I've never packages a Python module for Debian before and
> don't want to screw something up / spin my wheels learning lessons the team
> already has institutional knowledge of. I imagine that packaging a simple
> package like this one is probably quick and straightforward for folks who
> have done it before, so perhaps it would be easier for one of y'all to do
> it than to guide me through the process, but I leave that choice to your
> discretion. ;-)
>
> Thank you in advance for any assistance you can provide.
>
> Regards,
>
> Jonathan Kamens
>
>
>

Request access to salsa for python package for gitlab-emulator

[Ian Norton]

Hi, I'm the owner/maintainer of the gitlab-emulator project
https://gitlab.com/cunity/gitlab-emulator  I'd like to request access
to Salsa to introduce a debian package for gitlab-emulator.

I've submitted a registration request for Salsa and have read
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and agree to it's conditions.

Many thanks :)

Ian

Python module packaging request to help me maintain apt-listchanges

[Jonathan Kamens]

Hello all,

I'm writing to ask for your assistance in getting pytest-subprocess 
packaged into Debian:


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

The use case here is that I've taken over maintenance of apt-listchanges 
and added among other things a unit-test suite, and I want to make the 
unit-tests cover as much of the code as possible, and to do that I need 
to be able to mock out subprocess calls which apt-listchanges does quite 
a lot of in its work.


I am happy to do most of the work if someone on this list is willing to 
mentor me, since I've never packages a Python module for Debian before 
and don't want to screw something up / spin my wheels learning lessons 
the team already has institutional knowledge of. I imagine that 
packaging a simple package like this one is probably quick and 
straightforward for folks who have done it before, so perhaps it would 
be easier for one of y'all to do it than to guide me through the 
process, but I leave that choice to your discretion. ;-)


Thank you in advance for any assistance you can provide.

Regards,

Jonathan Kamens

Request to join the Python Team

[Guilherme Puida Moreira]

Hello,

I would like to join the Python Team on Salsa. I'm currently working on
packaging pytest-flake8-path and flake8-spellcheck.

My username on Salsa is 'puida', and I have read and accepted the Debian Python
Team Policy document.

Thanks,
Guilherme Puida

Re: Sponsorship request: python-ping3

[Carles Pina i Estany]

Hi,

On 20 Oct 2023 at 09:03:07, Santiago Ruano Rincón wrote:
> El 18/10/23 a las 00:56, Carles Pina i Estany escribió:

> > I've checked that no ICMP replies even using the standard ping binary
> > from iputils-ping:
> > -
> > Test-Command: set +e ; ping -c 4 8.8.8.8 ; ping -c 4 example.com ; curl -s 
> > -I https://en.wikipedia.org ; curl -s -L https://en.wikipedia.org | head -5
> > Depends: python3-ping3, iputils-ping, curl
> > Restrictions: needs-root, needs-internet
> > Features: test-name=test-real-ping
> > -
> > That's in:
> > https://salsa.debian.org/carlespina/python-ping3/-/blob/autopkgtest-connectivity/debian/tests/control
> > 
> > The output:
> > https://salsa.debian.org/carlespina/python-ping3/-/jobs/4822521#L213
> > 
> > 4 packets transmitted, 0 received, 100% packet loss, time 3059ms
> > 4 packets transmitted, 0 received, 100% packet loss, time 3079ms
> 
> ...
> 
> AFAIU, there are network restrictions on salsa. Reaching HTTPS in the
> outside world should work. But I am not sure about ICMP.
> 
> FWIW, this is probably overengineering, but it is also possible to use
> namespaces to avoid reaching INET, pinging from one namespace to the
> other.
> 
> As example:
> https://salsa.debian.org/debian/isc-dhcp/-/blob/master/debian/tests/client-server

I liked the idea of using namespaces! Thanks very much, I might use it
in the future.

Like you, I think that for python-ping3 unit tests this is
overengineering (but I might play with this for python-ping3 or
somehting else in the future...).

In python-ping3, upstream has some IPs and hostnames hardcoded. The
hostnames are easy to "tweak" via /etc/hosts (even to ping 127.0.0.1).

The IPs: last night, I thought that another approach would be to use
iptables (or nftables) and destination NAT. Redirect 8.8.8.8 to
127.0.0.1. It has the advantage that I could remove needs-internet,
keeping all the unit tests 100% local.

Cheers,

-- 
Carles Pina i Estany
https://carles.pina.cat


signature.asc
Description: PGP signature

Re: Sponsorship request: python-ping3

[Santiago Ruano Rincón]

El 18/10/23 a las 00:56, Carles Pina i Estany escribió:
> 
> Hi,
> 
> On 17 Oct 2023 at 22:42:27, Carles Pina i Estany wrote:
> 
> [...]
> 
> > >  2. Regarding testing, this package is a bit a mess. First you probably
> > > realized that you can't run tests at buildtime because a raw socket
> > > requires root privilege. I see you designed custom autopkgtest to
> > 
> > yep...
> > 
> > [...]
> > 
> > > From there you have two options: the first one is to drop the
> > > Testsuite: field and keep the two tests you designed and call it a
> > > day, or you drop it and write a third test stanza in
> > > debian/tests/control with a shell script you'd also have to write
> > > that moves the tests to the tmp dir autopkgtest creates, puts
> > > localhost in /etc/hosts and then run tests. In that case you need
> > > to add pytest to the dependencies of this test stanza.
> > 
> > Sounds doable no problem, I'll try it this evening and see how it goes.
> 
> From doable to "I'm 99% sure that not possible". I cannot send pings
> from autopkgtest in salsa with any software.
> 
> Side note: I remembered that when using "needs-internet": HTTP GET
> requests (even using hostnames) works. This is my first package for
> Debian, but I've used autopkgtest with needs-internet to run a sphinx
> "linkcheck" and it was working correctly.
> 
> I've checked that no ICMP replies even using the standard ping binary
> from iputils-ping:
> -
> Test-Command: set +e ; ping -c 4 8.8.8.8 ; ping -c 4 example.com ; curl -s -I 
> https://en.wikipedia.org ; curl -s -L https://en.wikipedia.org | head -5
> Depends: python3-ping3, iputils-ping, curl
> Restrictions: needs-root, needs-internet
> Features: test-name=test-real-ping
> -
> That's in:
> https://salsa.debian.org/carlespina/python-ping3/-/blob/autopkgtest-connectivity/debian/tests/control
> 
> The output:
> https://salsa.debian.org/carlespina/python-ping3/-/jobs/4822521#L213
> 
> 4 packets transmitted, 0 received, 100% packet loss, time 3059ms
> 4 packets transmitted, 0 received, 100% packet loss, time 3079ms

...

AFAIU, there are network restrictions on salsa. Reaching HTTPS in the
outside world should work. But I am not sure about ICMP.

FWIW, this is probably overengineering, but it is also possible to use
namespaces to avoid reaching INET, pinging from one namespace to the
other.

As example:
https://salsa.debian.org/debian/isc-dhcp/-/blob/master/debian/tests/client-server

Cheers!

 -- Santiago


signature.asc
Description: PGP signature

Re: Sponsorship request: python-ping3

[Carles Pina i Estany]

Hi,

On 20 Oct 2023 at 01:06:01, Pierre-Elliott Bécue wrote:
> Carles Pina i Estany  wrote on 18/10/2023 at 01:56:46+0200:

> >> Tell me when you're fine with your work and I'll upload.
> >
> > To me, it can be uploaded :-)
> >
> > Let me know if I need or can do anything else.
> 
> Uploaded, remember to put a tag on the latest commit. :)

Excellent!

Tagged via:
$ git tag -s debian/4.0.4-1
   ("Initial release" the commit message)

$ git push upstream debian/4.0.4-1

I've just realised that there is "gbp tag" :-/ I'll use it next time.
Reading the description in man gbp-tag: I was in the right branch and
the verifications would have been ok! (last commit in the debian
branch).

Thanks!

-- 
Carles Pina i Estany
https://carles.pina.cat


signature.asc
Description: PGP signature

Re: Sponsorship request: python-ping3

[Pierre-Elliott Bécue]

Carles Pina i Estany  wrote on 18/10/2023 at 01:56:46+0200:

> [[PGP Signed Part:No public key for A802884F60A55F81 created at 
> 2023-10-18T01:56:46+0200 using RSA]]
>
> Hi,
>
> On 17 Oct 2023 at 22:42:27, Carles Pina i Estany wrote:
>
> [...]
>
>> >  2. Regarding testing, this package is a bit a mess. First you probably
>> > realized that you can't run tests at buildtime because a raw socket
>> > requires root privilege. I see you designed custom autopkgtest to
>> 
>> yep...
>> 
>> [...]
>> 
>> > From there you have two options: the first one is to drop the
>> > Testsuite: field and keep the two tests you designed and call it a
>> > day, or you drop it and write a third test stanza in
>> > debian/tests/control with a shell script you'd also have to write
>> > that moves the tests to the tmp dir autopkgtest creates, puts
>> > localhost in /etc/hosts and then run tests. In that case you need
>> > to add pytest to the dependencies of this test stanza.
>> 
>> Sounds doable no problem, I'll try it this evening and see how it goes.
>
> From doable to "I'm 99% sure that not possible". I cannot send pings
> from autopkgtest in salsa with any software.
>
> Side note: I remembered that when using "needs-internet": HTTP GET
> requests (even using hostnames) works. This is my first package for
> Debian, but I've used autopkgtest with needs-internet to run a sphinx
> "linkcheck" and it was working correctly.
>
> I've checked that no ICMP replies even using the standard ping binary
> from iputils-ping:
> -
> Test-Command: set +e ; ping -c 4 8.8.8.8 ; ping -c 4 example.com ; curl -s -I 
> https://en.wikipedia.org ; curl -s -L https://en.wikipedia.org | head -5
> Depends: python3-ping3, iputils-ping, curl
> Restrictions: needs-root, needs-internet
> Features: test-name=test-real-ping
> -
> That's in:
> https://salsa.debian.org/carlespina/python-ping3/-/blob/autopkgtest-connectivity/debian/tests/control
>
> The output:
> https://salsa.debian.org/carlespina/python-ping3/-/jobs/4822521#L213
>
> 4 packets transmitted, 0 received, 100% packet loss, time 3059ms
> 4 packets transmitted, 0 received, 100% packet loss, time 3079ms
>
> Even more: I think that curl -I (--head) (HTTP HEAD) might not work? but
> curl HTTP GET works. I'm not sure about the curl -I but I don't think it
> is relevant for this discussion. Somewhere, I think, I had read
> something that it implied that autopkgtest needs-internet was using a
> proxy? I cannot find it anyway and ICMP seems that cannot be used.
>
> So, for now, I've:
> -Used wrap-and-soft (excellent!).
> -Removed "set -e" in one of my Test-Commands: it's the default in
>  autopkgtest (I discovered with the "pings..." and then documenation)
> -Fixed a cosmetic line in d/tests/control (s/features/Features)
> -Removed "Testsuite: autopkgtest-pkg-pybuild" from d/control because
>  ICMP is not available anyway
> -Ran dch -r to update the date
> -"dput --force mentors python-ping3_4.0.4-1_amd64.changes"
>
> I've also discovered that there are a few unit tests in upstream that do
> not work. Some have an easy fix, I will do a MR of the fixes that I've
> done for some of them (separately, in GitHub, not tonight).
>
>> Your call.
>> 
>> Tell me when you're fine with your work and I'll upload.
>
> To me, it can be uploaded :-)
>
> Let me know if I need or can do anything else.

Uploaded, remember to put a tag on the latest commit. :)
-- 
PEB


signature.asc
Description: PGP signature

Request to join Python Team

[Alexander Sulfrian]

Hello,

I would like to join the Python Team on Salsa. Currently I am packaging
the python package scramp. I already prepared the package in a personal
repo:

https://salsa.debian.org/animux/python-scramp

and I would like to move it to the team namespace.

After python-scramp is ready I would like to update python-pg8000 to a
more recent version as the current version in Debian is from 2016 and it
currently has a FTBFS bug.

My Salsa login is: Animux


I have read and accept the "Debian Python Team - Policy".


Thanks,
Alexander Sulfrian

Request to join Python Team - Packaging Thumbor smart imaging service

[Raphael Rossi]

Hello Python Team,

I'm packaging a Python tool named Thumbor and I would like to enter the team to 
upload the package under the Gitlab Salsa team umbrella.
My salsa login is: raphael.rossi https://salsa.debian.org/raphael.rossi

I've read and agree with the Debian Python Team - Policy [1].

JpegIPTC (Thumbor dependency) bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053579

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

Thanks,


-


Raphael Rossi

Developer
+55 11 941460992

Request to join Python Team - Packaging Thumbor smart imaging service

[Pedro Paulo]

Hello Python Team,


I'm packaging a Python tool named Thumbor and I would like to enter the
team to upload the package under the Gitlab Salsa team umbrella.
My salsa login is: devppjr 

I've read and agree with the Debian Python Team - Policy [1].

JpegIPTC (Thumbor dependency) bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053579


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


Thanks,
Pedro Paulo

Re: Sponsorship request: python-ping3

[Carles Pina i Estany]

Hi,

On 17 Oct 2023 at 22:42:27, Carles Pina i Estany wrote:

[...]

> >  2. Regarding testing, this package is a bit a mess. First you probably
> > realized that you can't run tests at buildtime because a raw socket
> > requires root privilege. I see you designed custom autopkgtest to
> 
> yep...
> 
> [...]
> 
> > From there you have two options: the first one is to drop the
> > Testsuite: field and keep the two tests you designed and call it a
> > day, or you drop it and write a third test stanza in
> > debian/tests/control with a shell script you'd also have to write
> > that moves the tests to the tmp dir autopkgtest creates, puts
> > localhost in /etc/hosts and then run tests. In that case you need
> > to add pytest to the dependencies of this test stanza.
> 
> Sounds doable no problem, I'll try it this evening and see how it goes.

From doable to "I'm 99% sure that not possible". I cannot send pings
from autopkgtest in salsa with any software.

Side note: I remembered that when using "needs-internet": HTTP GET
requests (even using hostnames) works. This is my first package for
Debian, but I've used autopkgtest with needs-internet to run a sphinx
"linkcheck" and it was working correctly.

I've checked that no ICMP replies even using the standard ping binary
from iputils-ping:
-
Test-Command: set +e ; ping -c 4 8.8.8.8 ; ping -c 4 example.com ; curl -s -I 
https://en.wikipedia.org ; curl -s -L https://en.wikipedia.org | head -5
Depends: python3-ping3, iputils-ping, curl
Restrictions: needs-root, needs-internet
Features: test-name=test-real-ping
-
That's in:
https://salsa.debian.org/carlespina/python-ping3/-/blob/autopkgtest-connectivity/debian/tests/control

The output:
https://salsa.debian.org/carlespina/python-ping3/-/jobs/4822521#L213

4 packets transmitted, 0 received, 100% packet loss, time 3059ms
4 packets transmitted, 0 received, 100% packet loss, time 3079ms

Even more: I think that curl -I (--head) (HTTP HEAD) might not work? but
curl HTTP GET works. I'm not sure about the curl -I but I don't think it
is relevant for this discussion. Somewhere, I think, I had read
something that it implied that autopkgtest needs-internet was using a
proxy? I cannot find it anyway and ICMP seems that cannot be used.

So, for now, I've:
-Used wrap-and-soft (excellent!).
-Removed "set -e" in one of my Test-Commands: it's the default in
 autopkgtest (I discovered with the "pings..." and then documenation)
-Fixed a cosmetic line in d/tests/control (s/features/Features)
-Removed "Testsuite: autopkgtest-pkg-pybuild" from d/control because
 ICMP is not available anyway
-Ran dch -r to update the date
-"dput --force mentors python-ping3_4.0.4-1_amd64.changes"

I've also discovered that there are a few unit tests in upstream that do
not work. Some have an easy fix, I will do a MR of the fixes that I've
done for some of them (separately, in GitHub, not tonight).

> Your call.
> 
> Tell me when you're fine with your work and I'll upload.

To me, it can be uploaded :-)

Let me know if I need or can do anything else.

Thank you!

-- 
Carles Pina i Estany
https://carles.pina.cat


signature.asc
Description: PGP signature