Groups > linux.debian.maint.python > #13403

Re: How to contribute

Path	csiph.com!news.neodome.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Andrey Rahmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: How to contribute
Date	Mon, 24 May 2021 18:10:01 +0200
Message-ID	<Ciljr-2XY-1@gated-at.bofh.it> (permalink)
References	<ChGzD-3pX-5@gated-at.bofh.it>
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	<wrar@debian.org>
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	<debian-python@lists.debian.org> archive/latest/19191
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
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	<YKvOYomMxBPRxnJw@belkar.wrar.name>
X-Original-References	<87cztiec5x.fsf@mykolab.com>
Xref	csiph.com linux.debian.maint.python:13403

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

How to contribute Fabrice Bauzac-Stehly <noon@mykolab.com> - 2021-05-22 22:40 +0200
  Re: How to contribute Andrey Rahmatullin <wrar@debian.org> - 2021-05-24 18:10 +0200

csiph-web