Path: csiph.com!news.neodome.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Andrey Rahmatullin Newsgroups: linux.debian.maint.python Subject: Re: How to contribute Date: Mon, 24 May 2021 18:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon May 24 16:04:04 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.88 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, MURPHY_SCAM1=0.1, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .durkon.wrar. - helo-domain: .wrar.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CZOS1R+ecGkk2T/2" Content-Disposition: inline X-Mailing-List: archive/latest/19191 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/YKvOYomMxBPRxnJw@belkar.wrar.name Approved: robomod@news.nic.it Lines: 63 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 24 May 2021 21:03:46 +0500 X-Original-Message-ID: X-Original-References: <87cztiec5x.fsf@mykolab.com> Xref: csiph.com linux.debian.maint.python:13403 --CZOS1R+ecGkk2T/2 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > https://salsa.debian.org/python-team/packages/beaker/-/merge_requests/1 >=20 > It's been there for 3 months without comment. =20 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?=20 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. --=20 WBR, wRAR --CZOS1R+ecGkk2T/2 Content-Type: application/pgp-signature; name="signature.asc" -----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----- --CZOS1R+ecGkk2T/2--