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 theThen you can contribute directly, at least to the packages where the team
Debian Python team.
I'd like to know what would be the best course of action and avoidWe are frozen, but Salsa MRs are also not always reacted upon immediately
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 thatNo, 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.
there are people watching new merge requests, through e.g. some e-mail
sent to them whenever a new merge request is created?
Or should I advertise this merge request first on this mailing-list, soNormal practice is "advertising" it on a bug report.
that it gets some attention?
Or should I assume that I am trusted to be a careful person, mergingWell, you don't need to join the team to just send patches and MRs.
myself changes that I believe are "safe", but starting a thread for
changes I have doubts about?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 349 |
Nodes: | 16 (2 / 14) |
Uptime: | 116:09:55 |
Calls: | 7,612 |
Files: | 12,786 |
Messages: | 5,683,798 |