1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • How to contribute

    From Fabrice Bauzac-Stehly@21:1/5 to All on Sat May 22 22:40:01 2021
    Hello,

    I have followed the procedure to be able to contribute within the Debian
    Python team some time ago, and I now have permissions related to the
    Debian Python team.

    I'd like to know what would be the best course of action and avoid
    seeming bold or rude. Let's take my merge request below as example:

    https://salsa.debian.org/python-team/packages/beaker/-/merge_requests/1

    It's been there for 3 months without comment. Should I expect that
    there are people watching new merge requests, through e.g. some e-mail
    sent to them whenever a new merge request is created? If yes, should I
    assume these people are too busy at the moment and wait some more?

    Or should I advertise this merge request first on this mailing-list, so
    that it gets some attention?

    Or should I assume that I am trusted to be a careful person, merging
    myself changes that I believe are "safe", but starting a thread for
    changes I have doubts about?

    Thanks!

    Best regards

    --
    Fabrice Bauzac-Stehly
    PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
    old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rahmatullin@21:1/5 to Fabrice Bauzac-Stehly on Mon May 24 18:10:01 2021
    On Sat, May 22, 2021 at 10:39:06PM +0200, Fabrice Bauzac-Stehly wrote:
    I have followed the procedure to be able to contribute within the Debian Python team some time ago, and I now have permissions related to the
    Debian Python team.
    Then you can contribute directly, at least to the packages where the team
    is Maintainer.

    I'd like to know what would be the best course of action and avoid
    seeming bold or rude. Let's take my merge request below as example:

    https://salsa.debian.org/python-team/packages/beaker/-/merge_requests/1

    It's been there for 3 months without comment.
    We are frozen, but Salsa MRs are also not always reacted upon immediately
    (or ever).

    Should I expect that
    there are people watching new merge requests, through e.g. some e-mail
    sent to them whenever a new merge request is created?
    No, because it's opt-in, even though https://lists.debian.org/debian-devel-announce/2020/04/msg00009.html asks people to opt in or disable MRs.

    Or should I advertise this merge request first on this mailing-list, so
    that it gets some attention?
    Normal practice is "advertising" it on a bug report.

    Or should I assume that I am trusted to be a careful person, merging
    myself changes that I believe are "safe", but starting a thread for
    changes I have doubts about?
    Well, you don't need to join the team to just send patches and MRs.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmCrzl4tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh BccP/0dIp3fLCUM4DTyuzgIk7b/Hy147xyEI8cVF/BzdSRMmp7kIOdzwWQm1wfAB 02/RwZVSCClwRGRqZ8lrowTROjKU5aEwxZQyhhwY579U3aSW/Du3vAlR4yanMCSg AhCdEzZPNiR/yyDszuROHJ889JxFocAQjszLYjcK3xJlBbqarkt0dC0ABQyC4cYc k8GtqpqMZTyE3dGR3xQMQ2IdMhxP7dY3WesNSAccoQxTO0hsrWuAtjJIs72UE6Jj v9s0zofTwqRrSG67qNaDs+AjsgkWDyksZD0EgzXhJeoW3KU2vRGppglSA+XhY8g4 0eG56+k0jZrM1blP2eAaTrEgKQpNtkN3WXRQ7NfPe9j5WvUhsDxQvU3+umV0BMPV /s5//pmx2RWKGdpqKHCaroukvzHRx/eSISTweeaPQRTRJPbZ47OEJaDjdtxWRBOj qDxYP1b+7CAO+dSYxpV8lmZBiChPin88W2WYILrs/Zcoo2R2jgmkSgy+mWfKyRTJ 8krl9/bGZUlCtP0Bb4BJ+uCUpqgnGoSELpxMkHm71tM4lIxr6d0GAT6FjVEc3wLb bn5ZXCZkZ7BjoGXTY1b9btkRCNW7W90DDJZIez2zFYtiM07d4sAYY5MZrXLdJrF4 GnZQ7NkNr+f5CpRmvmb0JGHWbKQcrR/gZfUo5eRXYHIs4Yez
    =M/hX
    -----END PGP SIGNATURE-----

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