Re: Request to join the Debian Python Team

2022-03-26 Thread Stefano Rivera
Hi Martin (2022.03.11_15:32:10_+)
> I would like to join the Debian Python Team. My salsa handle is "mguenther"

Added, welcome!

SR

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



Re: Request to join the python team

2022-03-26 Thread Stefano Rivera
Hi Timon (2022.03.12_21:06:00_+)
> I have now also read the Debian Python Team Policy and accept it.

Added, welcome.

> (I also suggest to update https://wiki.debian.org/Teams/PythonTeam/HowToJoin 
> with the
> current text from policy.rst as it is much more clearly structured.)

It probably doesn't makes sense to duplicate the same thing in both
places. If there is duplication, I'd suggest trimming the duplication
from the wiki.

If you have suggestions for improving the policy structure, please file
an MR against it and post on the team list, here.

SR

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



Re: I want to join the DPT

2022-03-26 Thread Stefano Rivera
Hi vimer (2022.03.17_14:34:11_+)
> I have read the policy [1] and accept it.
> In fact, in my native language, the follow is the same as accept.
> Whataway, I accept the policy now.

Added, welcome.

SR

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



Re: DebConf22 -- Python Team BoF + Sprint?

2022-03-26 Thread Stefano Rivera
Hi Louis-Philippe (2022.03.20_21:51:45_+)
> The DebConf22 content team has issued a call for papers [1]. As I'm
> planning to be there this year, I'd be happy to send a proposal for our
> annual BoF :)

Yes, please (and I can see that you've submitted it, thanks!)

> I think it would also be neat to have a team sprint during DebCamp. Here
> are a few ideas of things we could work on:
> 
> * pybuild improvements (getting the autopkgtest MR in would be great)
> * general team QA (maybe based on [2]?)
> * lintian tags used for the team

+1 to a sprint, as usual.

I think upstream cpython would also appreciate it if we did a pass
through all of our cpython patches and ensured they were forwarded. Ping
bugs, etc. Same goes for any core libraries / big packages.
I've attempted to document them all, this year, which is a start. But
only a start. In many cases forwarding the patch would require clearly
defining the bug, writing reproducer scripts, etc.

I'd happily mentor people in working on this.

SR

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