• pyupgrade has been packaged + request to join the team

    From Stefano Rivera@21:1/5 to All on Thu Sep 16 21:20:02 2021
    Hi Joshua (2021.09.05_23:13:14_+0000)
    Now I'm trying to package things to rack up some contributions to
    Debian (and Ubuntu in that vein) by packaging more things.

    Welcome. We're glad to have you rack up contributions in our
    neighbourhood.

    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.

    Sometimes the most effective way to get things sponsored in the python
    team is via the IRC sponsorship request list. But sometimes they pile up because nobody is sponsoring...

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

    Yes, you can. Or the other way around if you want people in the team to
    feel free to work on your package (this tends to be rare, though).

    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.

    If the team is an uploader or maintainer of the package, it should live
    in the team repos.

    You can move existing package repos into the python-team/packages group.

    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.

    Yes, you can delay adding the team as a Maintainer, until the package is
    moved into the team salsa group.

    So, with that being said, can I join the team

    Please read the team policy: https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
    And send an email saying that you agree to it.

    how should I carry the initial release out? Let me know when you are
    ready for me to open an RFS.

    Once you've got membership, you can move your repo into the team and
    request sponsorship.

    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.

    In Debian we generally consider the Maintainer and Uploaders of a
    package to all be the maintainers of the package. The Maintainer field
    only permits a single entity while Uploaders permits more.

    In the Debian Python Team, we have some extra nuance about whether the
    team is in the Maintainer or Uploaders field. Team as maintainer means
    anybody can work on the package, team as uploader means feel free to
    commit changes to git but ask for permission before uploading. This is
    unusual, I don't know of any other teams that do that.

    SR

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)