Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13400 > unrolled thread
| Started by | Fabrice Bauzac-Stehly <noon@mykolab.com> |
|---|---|
| First post | 2021-05-22 22:40 +0200 |
| Last post | 2021-05-24 18:10 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
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
| From | Fabrice Bauzac-Stehly <noon@mykolab.com> |
|---|---|
| Date | 2021-05-22 22:40 +0200 |
| Subject | How to contribute |
| Message-ID | <ChGzD-3pX-5@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Andrey Rahmatullin <wrar@debian.org> |
|---|---|
| Date | 2021-05-24 18:10 +0200 |
| Message-ID | <Ciljr-2XY-1@gated-at.bofh.it> |
| In reply to | #13400 |
[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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web