Now I'm trying to package things to rack up some contributions to
Debian (and Ubuntu in that vein) by packaging more things.
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.
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.
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 08:59:27 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,475 |