Update: I have also packaged a fork of python-patch that is better maintained to close #845482, which is visible at https://salsa.debian.org/ItzSwirlz-guest/python-patch-ng. I've decided to set the team as Maintainer and me as Uploader this time, as I figured I would still technically be a maintainer if I was part of the team. As soon as pyupgrade gets its initial release I will do the same.
-Josh ________________________________ From: Joshua Peisach Sent: Friday, August 27, 2021 4:44 PM To: debian-python@lists.debian.org <debian-python@lists.debian.org> Subject: pyupgrade has been packaged + request to join the team Hello everyone, Quick introduction about myself: I maintain the Ubuntu Cinnamon Remix and highly respect Debian (it's what everything is built off of). Norbert Preining recently stepped down as Cinnamon maintainer for KDE, and now we are sort of in a limbo state with me and Fabio Fantoni. However, neither of us are able to pass the NM process, primarily due to GPG keys/lack of contributions/work to Debian. Although I had a higher chance, and was able to maintain it longer, we are behind on the latest version, and I pretty much seemed to have no interest in the BTS. My previous RFS's was a handful of Nemo extensions, which happened to be at the time Bullseye freeze depression struck, and they were all expired. Now I'm trying to package things to rack up some contributions to Debian (and Ubuntu in that vein) by packaging more things. Anyways, personal story aside, so everyone knows where I'm coming from (because you won't find me on contributors.debian.org), the point of this is to announce I've packaged pyupgrade, a "tool to automatically upgrade syntax for newer versions". I was told at the DebConf BoF on etherpad to request to join the team, and then I can RFS, so here are my questions. 1. Can I be the maintainer for pyupgrade and have the team as an uploader? I'm asking this because the wiki mentions rule of thumb is the team maintaining to find a 'knowledgeable person'. 2. Can I join the team and later move pyupgrade to the python-team repos? This way I can still upload my package(s, and more as I heard some help is needed for pip at the BoF), and get contributions in for my NM. 3. When I join, for the initial release: can the git repo still be my personal salsa repo and use pypi? This way I can just get it pushed, and then later it can be adjusted to pull from a GitHub tag and moved to the team. Even after I get my maintainership for Cinnamon, I still want to stay a part of the python-team because I use a lot of it and would love to help the team. So, with that being said, can I join the team, how should I carry the initial release out? Let me know when you are ready for me to open an RFS. This closes Debbug #988658<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988658>. Repo is https://salsa.debian.org/ItzSwirlz-guest/pyupgrade [https://salsa.debian.org/assets/gitlab_logo-7ae504fe4f68fdebb3c2034e36621930cd36ea87924c11ff65dbcb8ed50dca58.png]<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> Joshua Peisach / pyupgrade<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language. salsa.debian.org -Josh
