Re: Request to join the Debian Python Team

[Louis-Philippe Véronneau]

On 2024-10-27 12 h 19 p.m., 陈 晟祺 wrote:

Hi all,

I would like to join the Debian Python Team on salsa. My username is @harry.

I am currently a DM and have been maintaining several packages[1].
I would like to maintain some new packages along with the team, like virtualbmc 
(#1086153).
I have read have read the Debian Python Team Policy [2] and accept it.


[1]: https://qa.debian.org/developer.php?login=harry-c...@outlook.com
[2]: 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks,
Shengqi Chen



Welcome to the team.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: Upload request: psrecord (NEW)

[Alexandru Mihail]

First, thank you all for the insightful replies ! 
> - psrecord as source package name
> - python3-psrecord as binary package name (shipping executable and module)
> 
> 
> Is choosing psrecord as source package name still advisable in the above 
> cases? Or is python-psrecord as source package name better for the 
> executable+module case?
> 
My question towards myself, exactly. Looking forward to more opinions. Perhaps, 
after we decided, we (I) could update DPT docs with a nifty little table who 
could help others finding themselves in this niché or similar.
> Best regards
> 
> Peter
> 
Have a great one,
Alex

Re: Upload request: psrecord (NEW)

[Scott Kitterman]

On October 27, 2024 9:04:41 PM UTC, Peter Wienemann  wrote:
>Hi Scott,
>
>On 2024-10-27 20:12:28, Peter Wienemann wrote:
>> On 2024-10-26 17:00:18, Scott Kitterman wrote:
>>> From reading this thread, it seems like psrecord is an application written 
>>> in Python.  Upstream could, if they felt like it, re-implement the whole 
>>> thing in
>>> Rust and it would still be psrecord.  Assuming that's at least generally
>>> correct, I think psrecord is definitely the correct package name.
>> 
>> yes, I think this applies to psrecord.
>> 
>>> The only exception is that applications which provide a publically available
>>> module/ extension that other programs can use should provide a binary which
>>> uses the python3-foo naming convention (see spf-engine as an example).  It 
>>> is
>>> a matter of taste and judgement for small applications that provide a public
>>> module/extension should ship the application in a separate binary package or
>>> not.  Generally, tiny packages are bad because they require more overhead,
>>> including making the packages file bigger for every single user.
>> 
>> In addition psrecord provides a public module (as per [0]) but I am inclined 
>> to consider this one of the "small application" cases which do not warrant a 
>> separate binary package.
>
>re-reading your message, I think I got it wrong in my above reply. Sorry for 
>the confusion. I am trying to summarize to clarify the situation:
>
>Since psrecord ships both an executable and a public module (and it is small), 
>the suggested package names are:
>
>- psrecord as source package name
>- python3-psrecord as binary package name (shipping executable and module)
>
>Alternative (but not recommended due to the smallness):
>
>- psrecord as source package name
>- python3-psrecord as binary package name (shipping the module)
>- psrecord as additional binary package name (shipping the executable).
>
>Is choosing psrecord as source package name still advisable in the above 
>cases? Or is python-psrecord as source package name better for the 
>executable+module case?

I think this is fine:

- psrecord as source package name
- python3-psrecord as binary package name 

You can also have

Provides: psrecord

Then apt install psrecord will work.

Scott K

Re: Upload request: psrecord (NEW)

[Peter Wienemann]

Hi Scott,

On 2024-10-27 20:12:28, Peter Wienemann wrote:

On 2024-10-26 17:00:18, Scott Kitterman wrote:
From reading this thread, it seems like psrecord is an application 
written in Python.  Upstream could, if they felt like it, re-implement 
the whole thing in

Rust and it would still be psrecord.  Assuming that's at least generally
correct, I think psrecord is definitely the correct package name.


yes, I think this applies to psrecord.

The only exception is that applications which provide a publically 
available
module/ extension that other programs can use should provide a binary 
which
uses the python3-foo naming convention (see spf-engine as an 
example).  It is
a matter of taste and judgement for small applications that provide a 
public
module/extension should ship the application in a separate binary 
package or
not.  Generally, tiny packages are bad because they require more 
overhead,

including making the packages file bigger for every single user.


In addition psrecord provides a public module (as per [0]) but I am 
inclined to consider this one of the "small application" cases which do 
not warrant a separate binary package.


re-reading your message, I think I got it wrong in my above reply. Sorry 
for the confusion. I am trying to summarize to clarify the situation:


Since psrecord ships both an executable and a public module (and it is 
small), the suggested package names are:


- psrecord as source package name
- python3-psrecord as binary package name (shipping executable and module)

Alternative (but not recommended due to the smallness):

- psrecord as source package name
- python3-psrecord as binary package name (shipping the module)
- psrecord as additional binary package name (shipping the executable).

Is choosing psrecord as source package name still advisable in the above 
cases? Or is python-psrecord as source package name better for the 
executable+module case?


Best regards

Peter

Re: Upload request: psrecord (NEW)

[Peter Wienemann]

Hi Alexandru,

On 2024-10-24 21:30:48, Peter Wienemann wrote:

d/control
-
a) The present code fails to build in a clean build environment because 
the following build dependencies are missing:

- python3-psutil
- help2man

b) The "Provides" field should be removed (cf. [3]).


I forgot one more item in the above list:

c) To be able to use the --plot option, python3-matplotlib is needed. 
Therefore you should add a corresponding Recommends or Suggests field 
(cf. [0]) to the binary package.


Best regards

Peter

[0] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends

Re: Upload request: psrecord (NEW)

[Peter Wienemann]

Hi Scott,

On 2024-10-26 17:00:18, Scott Kitterman wrote:
From reading this thread, it seems like psrecord is an application written in 
Python.  Upstream could, if they felt like it, re-implement the whole thing in

Rust and it would still be psrecord.  Assuming that's at least generally
correct, I think psrecord is definitely the correct package name.


yes, I think this applies to psrecord.


The only exception is that applications which provide a publically available
module/ extension that other programs can use should provide a binary which
uses the python3-foo naming convention (see spf-engine as an example).  It is
a matter of taste and judgement for small applications that provide a public
module/extension should ship the application in a separate binary package or
not.  Generally, tiny packages are bad because they require more overhead,
including making the packages file bigger for every single user.


In addition psrecord provides a public module (as per [0]) but I am 
inclined to consider this one of the "small application" cases which do 
not warrant a separate binary package.


Best regards,

Peter

[0] https://peps.python.org/pep-0008/#public-and-internal-interfaces

Request to join the Debian Python Team

[陈 晟祺]

Hi all,

I would like to join the Debian Python Team on salsa. My username is @harry.

I am currently a DM and have been maintaining several packages[1].
I would like to maintain some new packages along with the team, like virtualbmc 
(#1086153).
I have read have read the Debian Python Team Policy [2] and accept it.


[1]: https://qa.debian.org/developer.php?login=harry-c...@outlook.com
[2]: 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks,
Shengqi Chen

Re: Upload request: psrecord (NEW)

[Scott Kitterman]

On Saturday, October 26, 2024 7:26:48 AM EDT Alexandru Mihail wrote:
> > Package name
> > 
> > I saw that you started with psrecord as source package name and
> > tijuca
> > suggested to use python-psrecord in [0]. After looking into the
> > package,
> > my personal preference is to switch back to psrecord as source
> > package
> > name since in my view the main task of the package is to provide a
> > psrecord executable and I consider the fact that it is written in
> > Python
> > an implementation detail. This is basically the situation mentioned
> > by
> > stefanor in [1]. Therefore my proposal is to use psrecord for both
> > the
> > source and the binary package name.
> > 
> > I understand that this is an unfortunate situation for you since one
> > person suggests to do A and another person suggests to do B.
> > Therefore I
> > propose to wait a bit and see what other people think about this.
> > More
> > opinions are much appreciated - in particular in view of recent
> > discussions about namespacing Python packages.
> 
> Yes, indeed after first reading DPT conventions, I also concluded the
> best source/binary pkg name combo would be plain psrecord. I'll wait a
> bit more, suggestions are very much welcome. If nothing relevant
> happens in the meantime (both in this thread or more general
> discussions) I will move the whole repo again to salsa/dpt/psrecord.
> This little tool is quite useful and I'd hate for it to be stuck in
> limbo for too long.

Some additional background on this:

In the before times, what is now the Debian Python Team was two teams:

Debian Python Modules Team (DPMT)
Python Applications Packaging Team (PAPT).

DPMT packaged Python modules and extensions and the binary package naming 
rules (that are at least informally extended to source package names now) 
applied.

PAPT packaged applications written in Python and these naming rules did not 
apply.

Part of the reason why they were separate is that there are some things about 
packaging applications that are different.  This is one of them.  It is an 
unfortunate side effect of the team's merger that this distinction has been 
somewhat lost.  

>From reading this thread, it seems like psrecord is an application written in 
Python.  Upstream could, if they felt like it, re-implement the whole thing in 
Rust and it would still be psrecord.  Assuming that's at least generally 
correct, I think psrecord is definitely the correct package name.  

The only exception is that applications which provide a publically available 
module/ extension that other programs can use should provide a binary which 
uses the python3-foo naming convention (see spf-engine as an example).  It is 
a matter of taste and judgement for small applications that provide a public 
module/extension should ship the application in a separate binary package or 
not.  Generally, tiny packages are bad because they require more overhead, 
including making the packages file bigger for every single user.

It would be good if you would review the existing DPT documentation 
(particularly the policy) with this in mind and see if you have suggestions to 
make it clearer.

Scott K

signature.asc
Description: This is a digitally signed message part.

Re: Upload request: psrecord (NEW)

[Alexandru Mihail]

Hi Peter,

Thanks for your time reviewing my work.


> 
> Package name
> 
> I saw that you started with psrecord as source package name and
> tijuca 
> suggested to use python-psrecord in [0]. After looking into the
> package, 
> my personal preference is to switch back to psrecord as source
> package 
> name since in my view the main task of the package is to provide a 
> psrecord executable and I consider the fact that it is written in
> Python 
> an implementation detail. This is basically the situation mentioned
> by 
> stefanor in [1]. Therefore my proposal is to use psrecord for both
> the 
> source and the binary package name.
> 
> I understand that this is an unfortunate situation for you since one 
> person suggests to do A and another person suggests to do B.
> Therefore I 
> propose to wait a bit and see what other people think about this.
> More 
> opinions are much appreciated - in particular in view of recent 
> discussions about namespacing Python packages.

Yes, indeed after first reading DPT conventions, I also concluded the
best source/binary pkg name combo would be plain psrecord. I'll wait a
bit more, suggestions are very much welcome. If nothing relevant
happens in the meantime (both in this thread or more general
discussions) I will move the whole repo again to salsa/dpt/psrecord.
This little tool is quite useful and I'd hate for it to be stuck in
limbo for too long.
> 
> Packaging details
> =
> 
> branch layout
> -
> The team policy specifies branch name conventions [2]. According to
> this 
> policy the branch containing the upstream source should be called 
> "upstream". Actually used is "upstream/latest" (also note that the 
> presently used upstream branch does not match the branch specified in
> d/gbp.conf).
> 
As per recent DEP14 discussions here, we might move DPT default policy
to upstream/latest anyway(DEP14 is not yet out, though). I didn't put
the branch like that randomly, it was on suggestion of Carsten
Schoenert in an older thread regarding repository naming conventions,
again :) (Re: Moving default branch after project creation)

>> I suggest to use `upstream/latest` as upstream branch.
>> It spares you separating upstream/latest, upstream/master,
>> upstream/whatever later.

Now I agree with both of you, I quite like the way upstream/latest
works but I am willing to change it of course since this is unreleased
anyway.

> d/control
> -
> 
Thank you for all the other observations, I will begin fixing the
problems. You have a keen eye ! :D
> > Also, to anyone with admin powers, please nuke
> > https://salsa.debian.org/python-team/packages/psrecord as this was
> > migrated to the new location following discussions about naming
> > conventions. it's empty.
> 
> I cannot help with this part. But in view of the open discussion
> about 
> the package name, it might be prudent to wait until this issue has
> been 
> settled.
Yes, sure.
> 
> If you have questions concerning anything mentioned above, do not 
> hesitate to ask.
> 

> Best regards,
> 
> Peter
Have a great day and thanks for the help,

Alexandru Mihail



signature.asc
Description: This is a digitally signed message part

Re: Upload request: psrecord (NEW)

[Peter Wienemann]

Hi Alexandru,

On 2024-10-15 18:02:10, Alexandru Mihail wrote:

I'd like to request an upload of the psrecord NEW package
( https://salsa.debian.org/python-team/packages/python-psrecord ) as I
don't have uploading rights. This closes #1075810. It's lintian OK and
the latest upstream version.


thanks for working on this new package. I reviewed your work and have 
the following remarks:


Package name

I saw that you started with psrecord as source package name and tijuca 
suggested to use python-psrecord in [0]. After looking into the package, 
my personal preference is to switch back to psrecord as source package 
name since in my view the main task of the package is to provide a 
psrecord executable and I consider the fact that it is written in Python 
an implementation detail. This is basically the situation mentioned by 
stefanor in [1]. Therefore my proposal is to use psrecord for both the 
source and the binary package name.


I understand that this is an unfortunate situation for you since one 
person suggests to do A and another person suggests to do B. Therefore I 
propose to wait a bit and see what other people think about this. More 
opinions are much appreciated - in particular in view of recent 
discussions about namespacing Python packages.


Packaging details
=

branch layout
-
The team policy specifies branch name conventions [2]. According to this 
policy the branch containing the upstream source should be called 
"upstream". Actually used is "upstream/latest" (also note that the 
presently used upstream branch does not match the branch specified in 
d/gbp.conf).


d/control
-
a) The present code fails to build in a clean build environment because 
the following build dependencies are missing:

- python3-psutil
- help2man

b) The "Provides" field should be removed (cf. [3]).

d/rules
---
a) The override_dh_auto_build target is unnecessary and can be removed.

b) The "ifeq ($(filter nodoc,$(DEB_BUILD_PROFILES)),)" block is empty 
and can thus be removed.


c) When using the package clean-up validation as described on [4], I get 
the following diff


1c1
< /<> directory 300
---
> /<> directory 320
31a32
> /<>/psrecord.egg-info directory 40

Fixing this requires replacing

rm -rf psrecord.egg-info/SOURCES.txt

by

rm -rf psrecord.egg-info

in the override_dh_auto_clean target.

d) execute_before_dh_installman target:
This assumes that the package being built is installed in the build 
environment (uses /usr/bin/psrecord). What would work is using 
"$(CURDIR)/debian/psrecord/usr/bin/psrecord" instead. But this requires 
PYTHONPATH to be set properly, e. g. by adding


export PYTHONPATH=$(shell pybuild --print build_dir -i python3)

It is also nicer and less error-prone to avoid a hardcoded version in 
the help2man call. You can set it at runtime, e. g. by adding


VERSION=$(shell dpkg-parsechangelog -S version)

and use the VERSION variable in the help2man version string.

e) If you generate the manpage during the build, it is better to remove 
the static version from d/psrecord.1. Otherwise potential future changes 
between the provided and the generated version will again result in 
package clean-up validation issues.


d/copyright
---
a) According to [5], the Upstream-Contact "[m]ay be free-form text, but 
by convention will usually be written as a list of RFC5322 addresses or 
URIs." Following this convention means using


Upstream-Contact: Thomas Robitaille 

(note the angle brackets).

b) I see slight deviations from the upstream license file for the 
"Files: *" stanza. It should be:


Copyright: 2013, Thomas P. Robitaille

In the "License: BSD-2-clause" stanza, the "All rights reserved." line 
is missing.


c) There is no "Files: debian/*" stanza.

[0] https://lists.debian.org/debian-python/2024/08/msg00049.html
[1] https://lists.debian.org/debian-python/2024/10/msg00093.html
[2] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#branch-names
[3] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#virtual-packages-provides

[4] https://wiki.debian.org/sbuild#Validate_package_cleanup
[5] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0


Also, to anyone with admin powers, please nuke
https://salsa.debian.org/python-team/packages/psrecord as this was
migrated to the new location following discussions about naming
conventions. it's empty.


I cannot help with this part. But in view of the open discussion about 
the package name, it might be prudent to wait until this issue has been 
settled.


If you have questions concerning anything mentioned above, do not 
hesitate to ask.


Best regards,

Peter

Re: Request to join Debian Python Team

[Louis-Philippe Véronneau]

On 2024-10-19 11:23, Rebecca N. Palmer wrote:
I (rnpalmer-guest) have already contributed to at least ~10 team 
packages [0] (often to unblock pandas[1] transitions/uploads), and this 
would be a simpler process if I was in the team.


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


[0] https://salsa.debian.org/users/rnpalmer-guest/projects
[1] pandas itself is science-team, but many related packages are python- 
team.




You're also a DM :P https://nm.debian.org/person/rnpalmer/

Welcome (officially!) to the team.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: Request to join the Python Debian team

[Pierre-Elliott Bécue]

Hey,

souravbhattacha...@tutamail.com wrote on 19/10/2024 at 11:49:20+0200:

> Greetings Pollo,
>
>
> Here's my salsa account: https://salsa.debian.org/sxctic-54l (which
> can also be found in my application). I have thoroughly read the team
> policy and hereby accept all terms outlined therein.

Invitation sent.
-- 
PEB


signature.asc
Description: PGP signature

Request to join Debian Python Team

[Rebecca N. Palmer]

I (rnpalmer-guest) have already contributed to at least ~10 team 
packages [0] (often to unblock pandas[1] transitions/uploads), and this 
would be a simpler process if I was in the team.


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


[0] https://salsa.debian.org/users/rnpalmer-guest/projects
[1] pandas itself is science-team, but many related packages are 
python-team.

Re: Request to join the Python Debian team

[souravbhattacharya]

Greetings Pollo,


Here's my salsa account: https://salsa.debian.org/sxctic-54l (which can also be 
found in my application). I have thoroughly read the team policy and hereby 
accept all terms outlined therein.




Not sure if this email will show up as a reply to your last response, as I was 
not subscribed previously and hence didn't receive it in my inbox. For 
reference, the original threads can be found here:
https://lists.debian.org/debian-python/2024/10/msg00046.html [My application]
https://lists.debian.org/debian-python/2024/10/msg00052.html [Thread I'm 
replying to]

Thank you for your time.




Regards,
Sourav

Re: Request to join python-debian team and ITP

[Louis-Philippe Véronneau]

On 2024-10-18 09:10, Olivier Aubert wrote:

Hi

I would like to join the Debian Python Team. I have read the policy.rst
and accept it.

I plan to contribute on existing packages such as python-vlc (for which
I am the upstream author), python-gstreamer and python-gtk, and also
would like to reintroduce the Advene package.

Advene[1] is a video annotation software (GPL), developed with python,
Gtk and Gstreamer. It was present in older Debian releases [2], but got
removed some years ago due to major migrations (python2->python3,
Gtk2->Gtk3,  Gstreamer0.10->Gstreamer1.0).

Since then, the application has been updated and is now in good
shape to be reintroduced into Debian. The updated Debian package[3],
migrated from cdbs to dh_python, has been used/tested for at least 3
years (distributed through a private repository[4]). As per [5]/[6]
a ITP bug has been filed: #1014535

It was previously maintained under the Multimedia Team umbrella, but
I think the python team may be a better umbrella. I am looking for
help/sponsorship from the Python Team to help getting the package back
in Debian. I can do most of the work but would welcome guidance wrt the
current practices of python packages.

Happy hacking! Best,
Olivier Aubert

[1] https://www.advene.org/
[2] https://tracker.debian.org/pkg/advene
[3] https://salsa.debian.org/multimedia-team/advene
[4] http://advene.org/download.html#linux
[5]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs
[6]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#newpackage



Welcome to the team!

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: Request to join the Python Debian team

[Louis-Philippe Véronneau]

On 2024-10-18 10:52, Michael Prokop wrote:

Hi,

I'm a DD since 2009 and want to join the Python team to assist in
maintaining the packages, e.g. like RC bug
https://salsa.debian.org/python-team/packages/flake8-quotes/-/merge_requests/1

My Salsa login is "mika" and I read + accept
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks for consideration && regards from Debian's BSP in Salzburg
-mika-


Welcome to the team!

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Request to join the Python Debian team

[Michael Prokop]

Hi,

I'm a DD since 2009 and want to join the Python team to assist in
maintaining the packages, e.g. like RC bug
https://salsa.debian.org/python-team/packages/flake8-quotes/-/merge_requests/1

My Salsa login is "mika" and I read + accept
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks for consideration && regards from Debian's BSP in Salzburg
-mika-


signature.asc
Description: PGP signature

Request to join python-debian team and ITP

[Olivier Aubert]

Hi

I would like to join the Debian Python Team. I have read the policy.rst
and accept it.

I plan to contribute on existing packages such as python-vlc (for which
I am the upstream author), python-gstreamer and python-gtk, and also
would like to reintroduce the Advene package.

Advene[1] is a video annotation software (GPL), developed with python,
Gtk and Gstreamer. It was present in older Debian releases [2], but got
removed some years ago due to major migrations (python2->python3, 
Gtk2->Gtk3,  Gstreamer0.10->Gstreamer1.0).

Since then, the application has been updated and is now in good
shape to be reintroduced into Debian. The updated Debian package[3],
migrated from cdbs to dh_python, has been used/tested for at least 3
years (distributed through a private repository[4]). As per [5]/[6]
a ITP bug has been filed: #1014535

It was previously maintained under the Multimedia Team umbrella, but
I think the python team may be a better umbrella. I am looking for
help/sponsorship from the Python Team to help getting the package back
in Debian. I can do most of the work but would welcome guidance wrt the
current practices of python packages.

Happy hacking! Best,
Olivier Aubert

[1] https://www.advene.org/
[2] https://tracker.debian.org/pkg/advene
[3] https://salsa.debian.org/multimedia-team/advene
[4] http://advene.org/download.html#linux
[5]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs
[6]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#newpackage

Re: Request to join the Debian Python Team

[Louis-Philippe Véronneau]

On 2024-10-16 07:24, kathara sasikumar wrote:

Hey all,

I would like to join the Debian Python Team on salsa. I recently became 
a Debian Maintainer and have been maintaining few packages[1]. I would 
like to maintain my current packages within the Debian Python team :)


My Salsa login is @kathara[3].

I have read have read the Debian Python Team - Policy[2] and accept it.


[1] https://qa.debian.org/developer.php? 
login=katharasasikumar007%40gmail.com
[2] https://salsa.debian.org/python-team/tools/python-modules/blob/ 
master/policy.rst

[3] https://salsa.debian.org/kathara



Welcome to the team!

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Request to join the Debian Python Team

[kathara sasikumar]

Hey all,

I would like to join the Debian Python Team on salsa. I recently became 
a Debian Maintainer and have been maintaining few packages[1]. I would 
like to maintain my current packages within the Debian Python team :)


My Salsa login is @kathara[3].

I have read have read the Debian Python Team - Policy[2] and accept it.


[1] 
https://qa.debian.org/developer.php?login=katharasasikumar007%40gmail.com
[2] 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

[3] https://salsa.debian.org/kathara

--
kathara

Upload request: psrecord (NEW)

[Alexandru Mihail]

Hello,

I'd like to request an upload of the psrecord NEW package
( https://salsa.debian.org/python-team/packages/python-psrecord ) as I
don't have uploading rights. This closes #1075810. It's lintian OK and
the latest upstream version.
Also, to anyone with admin powers, please nuke
https://salsa.debian.org/python-team/packages/psrecord as this was
migrated to the new location following discussions about naming
conventions. it's empty.


Have a great one,

Alexandru Mihail


signature.asc
Description: This is a digitally signed message part

Re: Request to join the Debian Python team

[Jeff]

On 09/10/2024 16:16, Louis-Philippe Véronneau wrote:

Welcome to the team.


Thanks!


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Request to join the Python Debian team

[Louis-Philippe Véronneau]

On 2024-10-08 22:46, souravbhattacha...@tutamail.com wrote:

Hello Soren,
Thank you for your message. I’ve read through the team policy and apologize for 
not indicating this earlier. I accept the terms and look forward to moving 
forward with the team.

Regards,
Sourav Bhattacharya


Hi,

You have not given us your salsa account name, so I can't add you.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: Request to join the Debian Python team

[Louis-Philippe Véronneau]

On 2024-10-08 15:44, Jeff wrote:

Hi,

I am a DD (jjr) and would like to join the Debian Python team.

I've been in the Perl team for many years, but am in the process of 
transcribing the packages for which I am upstream due to better gtk-4 
support in Python.


Regards

Jeff


Welcome to the team.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: Request to join the Python Debian team

[souravbhattacharya]

Hello Soren,
Thank you for your message. I’ve read through the team policy and apologize for 
not indicating this earlier. I accept the terms and look forward to moving 
forward with the team.

Regards,
Sourav Bhattacharya 

9 Oct 2024, 07:29 by so...@debian.org:

> Sourav,
>
> Pleased to make your acquaintance.
>
> Please read over the team policy and indicate that you accept it;
>
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/
> policy.rst
>
> On Tuesday, October 8, 2024 11:02:50 AM MST souravbhattacha...@tutamail.com 
> wrote:
>
>> Hello Debian Python Team,
>>
>>
>> I hope this message finds you well. My name is Sourav Bhattacharya, and I’m
>> eager to contribute to Debian by becoming a part of the Debian Python Team.
>> As an aspiring data science and machine learning professional, I’ve been
>> focusing on improving my Python skills and am enthusiastic about deepening
>>
> my
>
>> involvement in the open-source community.
>>
>>
>> While I’m not yet an expert in Python, I have a strong desire to learn and
>> grow. I'm ready to take on challenges related to Python packages in Debian
>> and will dedicate myself to making meaningful contributions.
>>
>>
>> Thank you for your time and consideration. I look forward to your response
>>
> and
>
>> any further instructions.
>>
>>
>>
>>
>> Best regards,
>> Sourav Bhattacharya
>> https://salsa.debian.org/sxctic-54l
>>
>
>
> -- 
> Soren Stoutner
> so...@debian.org
>

Re: Request to join the Python Debian team

[Soren Stoutner]

Sourav,

Pleased to make your acquaintance.

Please read over the team policy and indicate that you accept it;

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

On Tuesday, October 8, 2024 11:02:50 AM MST souravbhattacha...@tutamail.com 
wrote:
> Hello Debian Python Team,
> 
> 
> I hope this message finds you well. My name is Sourav Bhattacharya, and I’m
> eager to contribute to Debian by becoming a part of the Debian Python Team.
> As an aspiring data science and machine learning professional, I’ve been
> focusing on improving my Python skills and am enthusiastic about deepening 
my
> involvement in the open-source community.
> 
> 
> While I’m not yet an expert in Python, I have a strong desire to learn and
> grow. I'm ready to take on challenges related to Python packages in Debian
> and will dedicate myself to making meaningful contributions.
> 
> 
> Thank you for your time and consideration. I look forward to your response 
and
> any further instructions.
> 
> 
> 
> 
> Best regards,
> Sourav Bhattacharya
> https://salsa.debian.org/sxctic-54l


-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

Request to join the Debian Python team

[Jeff]

Hi,

I am a DD (jjr) and would like to join the Debian Python team.

I've been in the Perl team for many years, but am in the process of 
transcribing the packages for which I am upstream due to better gtk-4 
support in Python.


Regards

Jeff


OpenPGP_signature.asc
Description: OpenPGP digital signature

Request to join the Python Debian team

[souravbhattacharya]

Hello Debian Python Team,


I hope this message finds you well. My name is Sourav Bhattacharya, and I’m 
eager to contribute to Debian by becoming a part of the Debian Python Team. As 
an aspiring data science and machine learning professional, I’ve been focusing 
on improving my Python skills and am enthusiastic about deepening my 
involvement in the open-source community.


While I’m not yet an expert in Python, I have a strong desire to learn and 
grow. I'm ready to take on challenges related to Python packages in Debian and 
will dedicate myself to making meaningful contributions.


Thank you for your time and consideration. I look forward to your response and 
any further instructions.




Best regards,
Sourav Bhattacharya
https://salsa.debian.org/sxctic-54l

Re: Upload request: meson-python

[James Addison]

On Fri, 4 Oct 2024 at 12:58, Simon McVittie  wrote:
>
> On Thu, 03 Oct 2024 at 15:54:16 +, James Addison wrote:
> > I'd like to request an upload of the src:meson-python package, in
> > particular to close bug #1076806, a reproducibility bug related to
> > documentation copyright notices
>
> Done, but I'm curious why making this particular package reproducible
> was a high enough priority for you that it needed to be called out
> specifically? I don't normally prioritize uploading low-impact fixes like
> this one, on the basis that each upload needs testing to make sure it
> isn't going to regress other packages, and minor fixes can be included
> next time there is a more important update to be done.

Thank you for the upload - in this case, I'd been iterating through the list of
Debian 'package sets'[1] displayed on the Reproducible Builds test result
website, searching for any packages that could be encouraged along the path to
building reproducibly.

Core/popular package sets seem like good places to look for opportunities to
improve Debian reproducibility for many users, although sometimes with
associated risk because of the number of systems potentially affected.

Although it doesn't appear there any more, I believe meson-python was listed in
the 'build-essential-depends' set.  After noticing that it was pending upload,
and had been for a reasonable duration of time, I asked around in the RB IRC
channel about a potential NMU (that I understand are generally considered not
ideal, but sometimes acceptable), and then after some feedback there, decided
that it might make more sense to ask directly on the bugreport and mailing
list.

If I'd felt that this was one of a category of similar possible uploads, I
would have attempted to describe/list the relevant packages - in this case the
package was a one-off.

[1] - 
https://tests.reproducible-builds.org/debian/unstable/amd64/index_pkg_sets.html

Re: Upload request: meson-python

[Simon McVittie]

On Thu, 03 Oct 2024 at 15:54:16 +, James Addison wrote:
> I'd like to request an upload of the src:meson-python package, in
> particular to close bug #1076806, a reproducibility bug related to
> documentation copyright notices

Done, but I'm curious why making this particular package reproducible
was a high enough priority for you that it needed to be called out
specifically? I don't normally prioritize uploading low-impact fixes like
this one, on the basis that each upload needs testing to make sure it
isn't going to regress other packages, and minor fixes can be included
next time there is a more important update to be done.

(Of course other team members are welcome to take responsibility for
uploading whatever is pending in the packaging git repo at any time,
if their priorities differ from mine.)

smcv

Upload request: meson-python

[James Addison]

Hello,

I'd like to request an upload of the src:meson-python package, in
particular to close bug #1076806, a reproducibility bug related to
documentation copyright notices -- the patch there has been
committed[1] in Salsa, and also subsequently merged[2] into the
upstream codebase.

There haven't been any newer releases by upstream since the current
version in Debian testing (0.16.0-1), and the only other pending
change as far as I can tell is a Standards-Version increment.

Also note, to reduce possible ambiguity: this package isn't the meson
build system itself, but is a Python PEP517 plugin -- a plugin that
allows Python packages to use meson during their own build/setup
processes.

Thanks!
James

[1] - 
https://salsa.debian.org/python-team/packages/meson-python/-/commit/b17dbeae9a9489c1a2e5dcdb4fab4d9c9e5aad1f

[2] - https://github.com/mesonbuild/meson-python/pull/652

Re: Merge Request for python-ciso8601

[Alexandre Detiste]

Uploaded.

Thank you very much

Le jeu. 3 oct. 2024 à 07:52, Antonio Valentino
 a écrit :
>
> Dear Malihe, dear all,
> python-ciso8601 has an RC bug (#1080128) and it is marked for
> autoremoval on the 30th of October.
>
> I have provided in salsa [1] a simple patch that should solve the issue.
> I kindly ask to review/apply the patch and upload the new version.
>
> If you prefer I can prepare the package myself and update the git repo
> directly, but I would need in any case a DD to sponsor the upload.
>
>
> [1]
> https://salsa.debian.org/python-team/packages/python-ciso8601/-/merge_requests/1
>
>
> kind regards
> --
> Antonio Valentino
>

Merge Request for python-ciso8601

[Antonio Valentino]

Dear Malihe, dear all,
python-ciso8601 has an RC bug (#1080128) and it is marked for 
autoremoval on the 30th of October.


I have provided in salsa [1] a simple patch that should solve the issue.
I kindly ask to review/apply the patch and upload the new version.

If you prefer I can prepare the package myself and update the git repo 
directly, but I would need in any case a DD to sponsor the upload.



[1] 
https://salsa.debian.org/python-team/packages/python-ciso8601/-/merge_requests/1



kind regards
--
Antonio Valentino

Request for review before first upload of python-construct-classes

[Soren Stoutner]

I have prepared python-construct-classes.

https://salsa.debian.org/python-team/packages/python-construct-classes

I would appreciate any feedback before I do the initial upload.  I have 
updated Python packages in the past, but this is the first time I have prepared 
one from scratch.

Thanks.

-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

Re: Request to join the Debian Python Team

[Louis-Philippe Véronneau]

On 2024-09-12 19:51, Soren Stoutner wrote:

I would like to join the Debian Python Team to help maintain the python-trezor
package.  I am the maintainer of the electrum package, which depends on
python-trezor, but the version in Debian is so out-of-date that it is
currently non-functional.

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

I have communicated with Richard Ulrich, the current uploader, who indicated
he would appreciate help maintaining the package.

My Salsa login is soren.

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



Welcome to the team!

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Request to join the Debian Python Team

[Soren Stoutner]

I would like to join the Debian Python Team to help maintain the python-trezor 
package.  I am the maintainer of the electrum package, which depends on 
python-trezor, but the version in Debian is so out-of-date that it is 
currently non-functional.

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

I have communicated with Richard Ulrich, the current uploader, who indicated 
he would appreciate help maintaining the package.

My Salsa login is soren.

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

-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

Re: Debian Python Team Join Request: Jason Blackwell

[Nicholas D Steeves]

Hi Jason,

Louis-Philippe Véronneau  writes:

> On 2024-09-09 16:16, Jason Blackwell wrote:
>> Hi all,
>> 
>> I would like to join the Debian Python Team to help maintain the 
>> pmbootstrap package to start. I have interest in working on other 
>> packages as well once I get the process down.
>> 
>> I would like to tackle this bug first: https://bugs.debian.org/cgi-bin/ 
>> bugreport.cgi?bug=1079785
>> 
>> Followed by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069772
>> 
>> If approved, I will work to consolidate these merge requests and make 
>> changes directly to the branches for the 2.3.1 pmbootstrap update as 
>> recommended on #debian-python.
>> 
>> https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
>> merge_requests/1
>> https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
>> merge_requests/2
>> https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
>> merge_requests/3
>> 
>> Salsa login: @blackwell https://salsa.debian.org/blackwell
>> 
>> I have read https://salsa.debian.org/python-team/tools/python-modules/ 
>> blob/master/policy.rst and I accept the terms.
>> 
>> Please let me know if there is any other information I can provide, or 
>> if you have ideas on other packages/things that I can assist with.
>> 
>> Regards,
>> 
>> Jason Blackwell
>> 
>> 
>> 
>> Background:
>> 
>> https://www.linkedin.com/in/blackwelljason/
>> 
>> https://github.com/blackwellops/
>> 
>> Commits for Fedora pmbootstrap 2.3.1 update: https:// 
>> src.fedoraproject.org/rpms/pmbootstrap/ 
>> c/613271ac8c52aa5d3ba03ba472b53e26ebe2451b?branch=rawhide
>> 
>> Current Maintainer for pmbootstrap on Gentoo GURU: https://github.com/ 
>> gentoo/guru/blob/master/dev-util/pmbootstrap/metadata.xml
>> 
>
> Welcome to the team :)

P.S. Wow, impressive introduction and statement of intent! :)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Re: Debian Python Team Join Request: Jason Blackwell

[Louis-Philippe Véronneau]

On 2024-09-09 16:16, Jason Blackwell wrote:

Hi all,

I would like to join the Debian Python Team to help maintain the 
pmbootstrap package to start. I have interest in working on other 
packages as well once I get the process down.


I would like to tackle this bug first: https://bugs.debian.org/cgi-bin/ 
bugreport.cgi?bug=1079785


Followed by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069772

If approved, I will work to consolidate these merge requests and make 
changes directly to the branches for the 2.3.1 pmbootstrap update as 
recommended on #debian-python.


https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
merge_requests/1
https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
merge_requests/2
https://salsa.debian.org/python-team/packages/pmbootstrap/-/ 
merge_requests/3


Salsa login: @blackwell https://salsa.debian.org/blackwell

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


Please let me know if there is any other information I can provide, or 
if you have ideas on other packages/things that I can assist with.


Regards,

Jason Blackwell



Background:

https://www.linkedin.com/in/blackwelljason/

https://github.com/blackwellops/

Commits for Fedora pmbootstrap 2.3.1 update: https:// 
src.fedoraproject.org/rpms/pmbootstrap/ 
c/613271ac8c52aa5d3ba03ba472b53e26ebe2451b?branch=rawhide


Current Maintainer for pmbootstrap on Gentoo GURU: https://github.com/ 
gentoo/guru/blob/master/dev-util/pmbootstrap/metadata.xml




Welcome to the team :)

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Debian Python Team Join Request: Jason Blackwell

[Jason Blackwell]

Hi all,

I would like to join the Debian Python Team to help maintain the 
pmbootstrap package to start. I have interest in working on other 
packages as well once I get the process down.


I would like to tackle this bug first: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079785


Followed by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069772

If approved, I will work to consolidate these merge requests and make 
changes directly to the branches for the 2.3.1 pmbootstrap update as 
recommended on #debian-python.


https://salsa.debian.org/python-team/packages/pmbootstrap/-/merge_requests/1
https://salsa.debian.org/python-team/packages/pmbootstrap/-/merge_requests/2
https://salsa.debian.org/python-team/packages/pmbootstrap/-/merge_requests/3

Salsa login: @blackwell https://salsa.debian.org/blackwell

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


Please let me know if there is any other information I can provide, or 
if you have ideas on other packages/things that I can assist with.


Regards,

Jason Blackwell



Background:

https://www.linkedin.com/in/blackwelljason/

https://github.com/blackwellops/

Commits for Fedora pmbootstrap 2.3.1 update: 
https://src.fedoraproject.org/rpms/pmbootstrap/c/613271ac8c52aa5d3ba03ba472b53e26ebe2451b?branch=rawhide


Current Maintainer for pmbootstrap on Gentoo GURU: 
https://github.com/gentoo/guru/blob/master/dev-util/pmbootstrap/metadata.xml




OpenPGP_0x4A9003E0A864B491.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Package review request: cocotb -- library for writing VHDL and Verilog testbenches in Python

[Agathe Porte]

مرحبًا أحمد

I was not able to fix the hardening-no-bindnow errors by adding the
usual hardening=+bindnow to the DEB_BUILD_MAINT_OPTIONS in d/rules.

However I saw some other things that I think should be fixed before you
upload. I have created a PR here:

https://salsa.debian.org/electronics-team/cocotb/-/merge_requests/1

 debian/copyright| 10 --
 debian/lintian-overrides|  2 ++
 debian/source/lintian-overrides |  3 +++
 3 files changed, 9 insertions(+), 6 deletions(-)

Otherwise I think the package is good to upload. Maybe the other
warnings can be fixed later.

Best regards,

Agathe.

2024-07-28 07:23 CEST, أحمد المحمودي:
> Hello,
> 
> I need someone from the Python packaging team to review the packaging of 
> cocotb
> 
> The package can be found on Git: 
> https://salsa.debian.org/electronics-team/cocotb
> 
> I am particularly puzzled by the files layout of cocotb, for example 
> compiled libs are under: /usr/lib/python3/dist-packages/cocotb/libs/
> and data files (makefiles mostly) are under:
> /usr/lib/python3/dist-packages/cocotb/share/
> 
> The package has the following lintian issues:
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotb.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbfli_modelsim.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbutils.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_aldec.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_ius.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_modelsim.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_nvc.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_aldec.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_ghdl.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_icarus.vpl]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_ius.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_modelsim.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_vcs.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_verilator.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libembed.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libgpi.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libgpilog.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/libs/libpygpilog.so]
> I: python3-cocotb: hardening-no-bindnow 
> [usr/lib/python3/dist-packages/cocotb/simulator.cpython-312-x86_64-linux-gnu.so]
> I: python3-cocotb: hardening-no-fortify-functions 
> [usr/lib/python3/dist-packages/cocotb/libs/libcocotb.so]
> I: cocotb source: uses-python-distutils [cocotb_build_libs.py:12]
> I: cocotb source: uses-python-distutils [cocotb_build_libs.py:13]
> I: cocotb source: uses-python-distutils [cocotb_build_libs.py:5]
> P: python3-cocotb: repeated-path-segment lib 
> [usr/lib/python3/dist-packages/cocotb/share/lib/]

Re: Request To Join Python Team

[Stefano Rivera]

Hi Shriram (2024.08.07_13:14:11_+)
> I intend to join the python team in order to maintain python-keep
>  and howdoi
> 

Added, welcome.

Stefano

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

Re: Request to join python team

[Stefano Rivera]

Hi Kartik (2024.07.23_09:07:06_+)

>  In addition to that, I have read the
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and I accept it.

Added, welcome.

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

Request To Join Python Team

[Shriram Ravindranathan]

Dear Python Team,

I intend to join the python team in order to maintain python-keep 
 and howdoi 



I would like to bring these packages under the python-team umbrella as 
suggested by the mentors.


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


Best Regards,

Shriram Ravindranathan



OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Request To Join Python Team

[Shriram Ravindranathan]

I forgot to mention my salsa username,

it is s20n 

Sorry for the spam

On 07/08/24 18:44, Shriram Ravindranathan wrote:


Dear Python Team,

I intend to join the python team in order to maintain python-keep 
 and  howdoi 



I would like to bring these packages under the python-team umbrella as 
suggested by the mentors.


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


Best Regards,

Shriram Ravindranathan



OpenPGP_signature.asc
Description: OpenPGP digital signature

Package review request: cocotb -- library for writing VHDL and Verilog testbenches in Python

[أحمد المحمودي]

Hello,

I need someone from the Python packaging team to review the packaging of 
cocotb

The package can be found on Git: 
https://salsa.debian.org/electronics-team/cocotb

I am particularly puzzled by the files layout of cocotb, for example 
compiled libs are under: /usr/lib/python3/dist-packages/cocotb/libs/
and data files (makefiles mostly) are under:
/usr/lib/python3/dist-packages/cocotb/share/

The package has the following lintian issues:
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotb.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbfli_modelsim.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbutils.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_aldec.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_ius.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_modelsim.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvhpi_nvc.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_aldec.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_ghdl.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_icarus.vpl]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_ius.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_modelsim.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_vcs.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotbvpi_verilator.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libembed.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libgpi.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libgpilog.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/libs/libpygpilog.so]
I: python3-cocotb: hardening-no-bindnow 
[usr/lib/python3/dist-packages/cocotb/simulator.cpython-312-x86_64-linux-gnu.so]
I: python3-cocotb: hardening-no-fortify-functions 
[usr/lib/python3/dist-packages/cocotb/libs/libcocotb.so]
I: cocotb source: uses-python-distutils [cocotb_build_libs.py:12]
I: cocotb source: uses-python-distutils [cocotb_build_libs.py:13]
I: cocotb source: uses-python-distutils [cocotb_build_libs.py:5]
P: python3-cocotb: repeated-path-segment lib 
[usr/lib/python3/dist-packages/cocotb/share/lib/]

Regards,

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Re: Request to join python team

[Kartik Kulkarni]

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

On Tue, Jul 23, 2024 at 4:12 PM Kartik Kulkarni 
wrote:

> Hi,
>
> I would like to be added to the salsa python team. I'm interested in using
> the python team group repositories for maintaining python packages.
> My salsa login is : kartik-karz
>
> Regards,
> Kartik
>

Request to join python team

[Kartik Kulkarni]

Hi,

I would like to be added to the salsa python team. I'm interested in using
the python team group repositories for maintaining python packages.
My salsa login is : kartik-karz

Regards,
Kartik

Re: Request to join

[Pierre-Elliott Bécue]

Hi,

Henri  wrote on 16/07/2024 at 16:34:50+0200:

> Hi DPT,
>
> I'm requesting to join the Debian Python Team in order to maintain some
> new packages under the team, such as "wgconfig" [1].
>
> My Salsa username is "towalink".
>
> I have read
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and accept it.
>
> Thanks,

Developer access granted.

Please poke us if you need a hand to setup something.

Bests,
-- 
PEB


signature.asc
Description: PGP signature

Request to join

[Henri]

Hi DPT,

I'm requesting to join the Debian Python Team in order to maintain some
new packages under the team, such as "wgconfig" [1].

My Salsa username is "towalink".

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

Thanks,
Henri

[1]: https://bugs.debian.org/1071868

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

[Louis-Philippe Véronneau]

On 2024-06-20 1 h 03 p.m., Jeroen Ploemen wrote:

*ping* *ping* *ping*


On Thu, 23 May 2024 08:27:42 +0200
Jeroen Ploemen  wrote:


*ping* *ping*


On Tue, 16 Apr 2024 11:21:51 +0200
Jeroen Ploemen  wrote:


*ping*


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


Seeing you haven't got an answer back (the DPT's admin are known to be 
busy...), I'd highly suggest you open a ticket on the Salsa Team's issue 
tracker [1].


In the past, asking them to remove repositories by opening such a ticket 
worked for me.


Cheers,

[1]: https://salsa.debian.org/salsa/support

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

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

[Jeroen Ploemen]

*ping* *ping* *ping*


On Thu, 23 May 2024 08:27:42 +0200
Jeroen Ploemen  wrote:

> *ping* *ping*
> 
> 
> On Tue, 16 Apr 2024 11:21:51 +0200
> Jeroen Ploemen  wrote:
> 
> > *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.


pgp_L3kwoMssb.pgp
Description: OpenPGP digital signature

Re: Handling sponsorship requests by new contributors (was: Request for Python Team assistance in Debian Mentors)

[Andreas Tille]

Am Sun, Jun 16, 2024 at 06:56:51PM +0200 schrieb Peter Wienemann:
> > What we could do if the idea of giving broad commit rights to newcomers
> > poses issues is to create a specific namespace in python-team for
> > newcomers. (then we'd need to have some migration plan and then oh dear)
> 
> I agree with both of you that it would be good to encourage new contributors
> to put their Python packages in the Python team namespace.

ACK.  My personal policy is to sponsor only packages from some team
space in Salsa for various reasons, mainly because:
  1. The sponsee should feel connected to some team to make me as
 sponsor "replaceable" by other team members.
  2. Its way easier if I commit some slight changes to Git myself and
 write extensive commit messages than asking the sponsee to do
 change XY and move it to mentors again.
 
I'm fine with using some sub-namespace (never worked with this in other
teams but it might be appropriate here).

Kind regards
Andreas.

-- 
https://fam-tille.de

Handling sponsorship requests by new contributors (was: Request for Python Team assistance in Debian Mentors)

[Peter Wienemann]

Hi,

On 2024-06-13 13:13:33, Pierre-Elliott Bécue wrote:

Andrey Rakhmatullin  wrote on 13/06/2024 at 12:48:36+0200:

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


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

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


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


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


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


Best regards,

Peter

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

Re: Request for Python Team assistance in Debian Mentors

[Phil Wyett]

On Thu, 2024-06-13 at 16:54 +, weepingclown wrote:
> Hi,
> 
> The ruby team has a similar ruby-team/mentors namespace for newcomers. That  
> works quite nicely.
> 
> Best,
> Ananthu
> 
> 
> On 13 June 2024 11:13:33 am UTC, "Pierre-Elliott Bécue"  
> wrote:
> > Andrey Rakhmatullin  wrote on 13/06/2024 at 12:48:36+0200:
> > 
> > > On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
> > > > Dear Python Team Members,
> > > > 
> > > > At present we have a number of Python related packages[1] within Debian
> > > > Mentors[2]. Would it be possible for team members/DD's to offer their 
> > > > expert
> > > > assistance to these submitters and their packages with a goal of upload 
> > > > to
> > > > Debian where appropriate.
> > > > 
> > > > Your time and assistance would be greatly appreciated.
> > > > 
> > > > [1] Package list, not exhaustive...
> > > > 
> > > > https://mentors.debian.net/package/python-keep/
> > > > https://mentors.debian.net/package/python-autodocsumm/
> > > > https://mentors.debian.net/package/python-radexreader/
> > > > https://mentors.debian.net/package/anytree/
> > > > https://mentors.debian.net/package/browser-cookie3/
> > > > 
> > > 
> > > I'm always hesitant to look at Python module RFSes because on one hand I
> > > would like all of them to be in the team but on the other hand I'm not
> > > sure if it makes sense to write "please move this to DPT" or "please
> > > consider moving this to DPT", especially for people who are first time
> > > packages without a team membership.
> > > Perhaps we should discuss this and find a single recommended practice for
> > > such packages.
> > > 
> > 
> > I really think we should encourage newcomers to apply joining the team
> > and put their packages there.
> > 
> > What we could do if the idea of giving broad commit rights to newcomers
> > poses issues is to create a specific namespace in python-team for
> > newcomers. (then we'd need to have some migration plan and then oh dear)
> > 

Hi all,

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

Regards

Phil

-- 

Website: https://kathenas.org

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

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


signature.asc
Description: This is a digitally signed message part

Re: Request for Python Team assistance in Debian Mentors

[Emmanuel Arias]

Hi,

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


On Thu, Jun 13, 2024 at 04:54:27PM +, weepingclown wrote:
> Hi,
> 
> The ruby team has a similar ruby-team/mentors namespace for newcomers. That  
> works quite nicely.
> 
> Best,
> Ananthu
> 
> On 13 June 2024 11:13:33 am UTC, "Pierre-Elliott Bécue"  
> wrote:
> >Andrey Rakhmatullin  wrote on 13/06/2024 at 12:48:36+0200:
> >
> >> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
> >>> Dear Python Team Members,
> >>> 
> >>> At present we have a number of Python related packages[1] within Debian
> >>> Mentors[2]. Would it be possible for team members/DD's to offer their 
> >>> expert
> >>> assistance to these submitters and their packages with a goal of upload to
> >>> Debian where appropriate.
> >>> 
> >>> Your time and assistance would be greatly appreciated.
> >>> 
> >>> [1] Package list, not exhaustive...
> >>> 
> >>> https://mentors.debian.net/package/python-keep/
> >>> https://mentors.debian.net/package/python-autodocsumm/
> >>> https://mentors.debian.net/package/python-radexreader/
> >>> https://mentors.debian.net/package/anytree/
> >>> https://mentors.debian.net/package/browser-cookie3/
> >> I'm always hesitant to look at Python module RFSes because on one hand I
> >> would like all of them to be in the team but on the other hand I'm not
> >> sure if it makes sense to write "please move this to DPT" or "please
> >> consider moving this to DPT", especially for people who are first time
> >> packages without a team membership.
> >> Perhaps we should discuss this and find a single recommended practice for
> >> such packages.
> >
> >I really think we should encourage newcomers to apply joining the team
> >and put their packages there.
> >
> >What we could do if the idea of giving broad commit rights to newcomers
> >poses issues is to create a specific namespace in python-team for
> >newcomers. (then we'd need to have some migration plan and then oh dear)
> >
> >-- 
> >PEB
> >

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Re: Request for Python Team assistance in Debian Mentors

[weepingclown]

Hi,

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

Best,
Ananthu

On 13 June 2024 11:13:33 am UTC, "Pierre-Elliott Bécue"  wrote:
>Andrey Rakhmatullin  wrote on 13/06/2024 at 12:48:36+0200:
>
>> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
>>> Dear Python Team Members,
>>> 
>>> At present we have a number of Python related packages[1] within Debian
>>> Mentors[2]. Would it be possible for team members/DD's to offer their expert
>>> assistance to these submitters and their packages with a goal of upload to
>>> Debian where appropriate.
>>> 
>>> Your time and assistance would be greatly appreciated.
>>> 
>>> [1] Package list, not exhaustive...
>>> 
>>> https://mentors.debian.net/package/python-keep/
>>> https://mentors.debian.net/package/python-autodocsumm/
>>> https://mentors.debian.net/package/python-radexreader/
>>> https://mentors.debian.net/package/anytree/
>>> https://mentors.debian.net/package/browser-cookie3/
>> I'm always hesitant to look at Python module RFSes because on one hand I
>> would like all of them to be in the team but on the other hand I'm not
>> sure if it makes sense to write "please move this to DPT" or "please
>> consider moving this to DPT", especially for people who are first time
>> packages without a team membership.
>> Perhaps we should discuss this and find a single recommended practice for
>> such packages.
>
>I really think we should encourage newcomers to apply joining the team
>and put their packages there.
>
>What we could do if the idea of giving broad commit rights to newcomers
>poses issues is to create a specific namespace in python-team for
>newcomers. (then we'd need to have some migration plan and then oh dear)
>
>-- 
>PEB
>

Re: Request for Python Team assistance in Debian Mentors

[Pierre-Elliott Bécue]

Andrey Rakhmatullin  wrote on 13/06/2024 at 12:48:36+0200:

> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
>> Dear Python Team Members,
>> 
>> At present we have a number of Python related packages[1] within Debian
>> Mentors[2]. Would it be possible for team members/DD's to offer their expert
>> assistance to these submitters and their packages with a goal of upload to
>> Debian where appropriate.
>> 
>> Your time and assistance would be greatly appreciated.
>> 
>> [1] Package list, not exhaustive...
>> 
>> https://mentors.debian.net/package/python-keep/
>> https://mentors.debian.net/package/python-autodocsumm/
>> https://mentors.debian.net/package/python-radexreader/
>> https://mentors.debian.net/package/anytree/
>> https://mentors.debian.net/package/browser-cookie3/
> I'm always hesitant to look at Python module RFSes because on one hand I
> would like all of them to be in the team but on the other hand I'm not
> sure if it makes sense to write "please move this to DPT" or "please
> consider moving this to DPT", especially for people who are first time
> packages without a team membership.
> Perhaps we should discuss this and find a single recommended practice for
> such packages.

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

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

-- 
PEB

Re: Request for Python Team assistance in Debian Mentors

[Phil Wyett]

On Thu, 2024-06-13 at 15:48 +0500, Andrey Rakhmatullin wrote:
> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
> > Dear Python Team Members,
> > 
> > At present we have a number of Python related packages[1] within Debian
> > Mentors[2]. Would it be possible for team members/DD's to offer their expert
> > assistance to these submitters and their packages with a goal of upload to
> > Debian where appropriate.
> > 
> > Your time and assistance would be greatly appreciated.
> > 
> > [1] Package list, not exhaustive...
> > 
> > https://mentors.debian.net/package/python-keep/
> > https://mentors.debian.net/package/python-autodocsumm/
> > https://mentors.debian.net/package/python-radexreader/
> > https://mentors.debian.net/package/anytree/
> > https://mentors.debian.net/package/browser-cookie3/
> I'm always hesitant to look at Python module RFSes because on one hand I
> would like all of them to be in the team but on the other hand I'm not
> sure if it makes sense to write "please move this to DPT" or "please
> consider moving this to DPT", especially for people who are first time
> packages without a team membership.
> Perhaps we should discuss this and find a single recommended practice for
> such packages.
> 

Hi,

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

Regards

Phil

-- 

Website: https://kathenas.org

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

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


signature.asc
Description: This is a digitally signed message part

Re: Request for Python Team assistance in Debian Mentors

[Phil Wyett]

On Thu, 2024-06-13 at 12:36 +0200, Pierre-Elliott Bécue wrote:
> Hey,
> 
> Phil Wyett  wrote on 13/06/2024 at 08:28:32+0200:
> 
> > Dear Python Team Members,
> > 
> > At present we have a number of Python related packages[1] within Debian
> > Mentors[2]. Would it be possible for team members/DD's to offer their expert
> > assistance to these submitters and their packages with a goal of upload to
> > Debian where appropriate.
> > 
> > Your time and assistance would be greatly appreciated.
> > 
> > [1] Package list, not exhaustive...
> > 
> > https://mentors.debian.net/package/python-keep/
> > https://mentors.debian.net/package/python-autodocsumm/
> > https://mentors.debian.net/package/python-radexreader/
> > https://mentors.debian.net/package/anytree/
> > https://mentors.debian.net/package/browser-cookie3/
> > 
> > [2] https://mentors.debian.net/packages/
> 
> Thanks for poking us.
> 
> I can't promise that it will be fast but I'll try to give it some time.
> 
> Bests,
> 

Thanks. All assistance is appreciated.

Regards

Phil

-- 

Website: https://kathenas.org

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

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


signature.asc
Description: This is a digitally signed message part

Re: Request for Python Team assistance in Debian Mentors

[Andrey Rakhmatullin]

On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote:
> Dear Python Team Members,
> 
> At present we have a number of Python related packages[1] within Debian
> Mentors[2]. Would it be possible for team members/DD's to offer their expert
> assistance to these submitters and their packages with a goal of upload to
> Debian where appropriate.
> 
> Your time and assistance would be greatly appreciated.
> 
> [1] Package list, not exhaustive...
> 
> https://mentors.debian.net/package/python-keep/
> https://mentors.debian.net/package/python-autodocsumm/
> https://mentors.debian.net/package/python-radexreader/
> https://mentors.debian.net/package/anytree/
> https://mentors.debian.net/package/browser-cookie3/
I'm always hesitant to look at Python module RFSes because on one hand I
would like all of them to be in the team but on the other hand I'm not
sure if it makes sense to write "please move this to DPT" or "please
consider moving this to DPT", especially for people who are first time
packages without a team membership.
Perhaps we should discuss this and find a single recommended practice for
such packages.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Request for Python Team assistance in Debian Mentors

[Pierre-Elliott Bécue]

Hey,

Phil Wyett  wrote on 13/06/2024 at 08:28:32+0200:

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

Thanks for poking us.

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

Bests,

-- 
PEB


signature.asc
Description: PGP signature

Request for Python Team assistance in Debian Mentors

[Phil Wyett]

Dear Python Team Members,

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

Your time and assistance would be greatly appreciated.

[1] Package list, not exhaustive...

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

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

Regards

Phil

-- 

Website: https://kathenas.org

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

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


signature.asc
Description: This is a digitally signed message part

Re: Request to join the Python packaging team

[Stefano Rivera]

Hi Federico (2024.06.03_16:11:27_+)
> I was in the DPMT back when it was on Alioth and I would like to join
> it again. My Salsa login is "federico".

Added, welcome back

Stefano

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

Re: Request to join the Debian Python Team

[Stefano Rivera]

Hi Mwadime (2024.06.04_21:28:52_+)

> Hello I am Calvin Mwadime Makokha, with @CalvoM as the salsa login.
> I would like to join DPT so that I would help maintain python3-inotify
> that is up for adoption.

Added, welcome!

Stefano

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

Request to join the Debian Python Team

[Mwadime Makokha]

Hello I am Calvin Mwadime Makokha, with @CalvoM as the salsa login.
I would like to join DPT so that I would help maintain python3-inotify
that is up for adoption.
I have read
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and accepted it.


-- 
*Mwadime Makokha*

Request to join the Python packaging team

[Federico Ceratto]

Hello,

I was in the DPMT back when it was on Alioth and I would like to join
it again. My Salsa login is "federico".

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

Thank you!
--
Federico

Re: Request to join

[Scott Kitterman]

On Sunday, June 2, 2024 12:20:46 PM EDT Tiago Bortoletto Vaz wrote:
> Hello,
> 
> I'm participating in a Debian event today and willing to put some time
> into a package under debian-python team:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072061
> 
> I'm also willing to move a few packages I maintain in debian-multimedia
> to debian-python.
> 
> I've read and accepted the policy at
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy
> .rst
> 
> My salsa username is tiago.

Welcome to the team.

Scott K

signature.asc
Description: This is a digitally signed message part.

Request to join

[Tiago Bortoletto Vaz]

Hello,

I'm participating in a Debian event today and willing to put some time
into a package under debian-python team:

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

I'm also willing to move a few packages I maintain in debian-multimedia
to debian-python.

I've read and accepted the policy at
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

My salsa username is tiago.

Bests & thanks,

-- 
Tiago Vaz
https://tvaz.cc

Re: Request to join the DPT

[Pierre-Elliott Bécue]

Hey,

Simon Chopin  wrote on 30/05/2024 at 16:56:39+0200:

> On jeu. 30 mai 2024 13:57:58, Simon Chopin wrote:
>> Hi folks,
>>
>> Could I please join the DPT Salsa team? My Salsa login is `schopin`.
>>
>> My rationale for joining isn't because of specific packages, but rather
>> that as part of my work in Ubuntu I tend to touch a lot of Python
>> packages, and being a member of the DPT would reduce the friction in
>> submitting those changes back to Debian (my eventual goal being becoming
>> a DD so that friction gets reduced even further).
>
> Forgot to add:
>
> I have read the policy at
> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> and I accept it.

Maintainr access granted. :)
-- 
PEB


signature.asc
Description: PGP signature

RE: Request to join the DPT

[Simon Chopin]

On jeu. 30 mai 2024 13:57:58, Simon Chopin wrote:
> Hi folks,
>
> Could I please join the DPT Salsa team? My Salsa login is `schopin`.
>
> My rationale for joining isn't because of specific packages, but rather
> that as part of my work in Ubuntu I tend to touch a lot of Python
> packages, and being a member of the DPT would reduce the friction in
> submitting those changes back to Debian (my eventual goal being becoming
> a DD so that friction gets reduced even further).

Forgot to add:

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

>
> Cheers,
>
> Simon

Request to join the DPT

[Simon Chopin]

Hi folks,

Could I please join the DPT Salsa team? My Salsa login is `schopin`.

My rationale for joining isn't because of specific packages, but rather
that as part of my work in Ubuntu I tend to touch a lot of Python
packages, and being a member of the DPT would reduce the friction in
submitting those changes back to Debian (my eventual goal being becoming
a DD so that friction gets reduced even further).

Cheers,

Simon

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

[Jeroen Ploemen]

*ping* *ping*


On Tue, 16 Apr 2024 11:21:51 +0200
Jeroen Ploemen  wrote:

> *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.  


pgpfK4zsErNoZ.pgp
Description: OpenPGP digital signature

Re: Request to join Debian Python Team

[Pierre-Elliott Bécue]

Hi,

Maytham Alsudany  wrote on 15/05/2024 at 11:37:19+0200:

> Hi DPT,
>
> I'm requesting to join the Debian Python Team in order to maintain some
> new packages under the team, such "nwg-clipman"[1], as well as moving
> "nwg-hello"[2] to team maintenance. (I also may look into packaging
> "plots"[3] in the long term.)
>
> My Salsa username is "Maytha8".
>
> I have read
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and I accept it.
>
> Thanks,

Developer access granted to the group.

Welcome!
-- 
PEB


signature.asc
Description: PGP signature

Request to join Debian Python Team

[Maytham Alsudany]

Hi DPT,

I'm requesting to join the Debian Python Team in order to maintain some
new packages under the team, such "nwg-clipman"[1], as well as moving
"nwg-hello"[2] to team maintenance. (I also may look into packaging
"plots"[3] in the long term.)

My Salsa username is "Maytha8".

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

Thanks,
Maytham

[1]: https://bugs.debian.org/1071154
[2]: https://tracker.debian.org/pkg/nwg-hello
[3]: https://bugs.debian.org/1060245


signature.asc
Description: This is a digitally signed message part

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