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
signature.asc
Description: PGP signature
