Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1198150 > unrolled thread
| Started by | Timo Röhling <roehling@debian.org> |
|---|---|
| First post | 2024-05-21 11:50 +0200 |
| Last post | 2024-05-21 14:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#1071561: python-gnupg: DPT as package maintainer? Timo Röhling <roehling@debian.org> - 2024-05-21 11:50 +0200
Bug#1071561: python-gnupg: DPT as package maintainer? Elena ``of Valhalla'' <valhalla@debian.org> - 2024-05-21 14:40 +0200
| From | Timo Röhling <roehling@debian.org> |
|---|---|
| Date | 2024-05-21 11:50 +0200 |
| Subject | Bug#1071561: python-gnupg: DPT as package maintainer? |
| Message-ID | <IGui5-eOZZ-3@gated-at.bofh.it> |
Source: python-gnupg Version: 0.5.2-1 Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear maintainer, I noticed that your package uses the so-called "weak team maintainer" model, where the Debian Python Team is listed as uploader instead of as maintainer. According to Team Policy, that means that other team members must not upload your package at all without asking you first, even for trivial changes. Is this a deliberate decision or merely an artifact of some packaging helper tool such as py2dsc, which generated the initial d/control that way? If it is the latter, would you be willing to switch Maintainer and Uploader and thereby further open up your package for (reasonable) team uploads? Thank you for considering this. Feel free to close the bug and/or tag it wontfix if you do not wish to apply this change. Cheers Timo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmZMa8kACgkQzIxr3RQD 9MoQGxAAyR5fW+Z43OtucHXoZH255Hz0UkQ+4GzyjtyejBLQdsbPwJKA/2Oq+Evd LtcDuE8Lgv2cNnHozJiYkgJDiMLc3alit7wEoqwhgmOwb2e99CO7Fb5jHnGY6Td8 8/Zhla0ioSTims93tv8t+J3yRNh+rzXu2R61k0dSiy2WjM1xOoN+hcKGmFkz0mkF 61Jad4tPmcKRSRWy9tqEVlFAgWakqnH82A0bfT2UO47VkvsXNmQdVi15YBAHUwR6 t1GaIsTWtkFgfeokHSmWabPFRqPei8xNAo4GenEKJ/3cVq+0fmyGjHImOLwGNqWn Di3qnu1Au0PWkQ+g0H+zzKni8QVqItuMqMiqybGpJ3VBGaHFvjH2ndDBYXcKew3p yJT1cAPm17wOHXIt6P/AwKnyb74iNUbByX7muGpS4MnGX8IE8+klYnGTD7G1/DC5 Y73bO4FgvVSRWJ6LWeC+4PRLcHhLHcw05QVOWzXtAQ9gcnnl7hZBCo5npXLuRp7L k++mxXdwoVzN/jGXfAJ28tPabQz3PeoABXau85mCVVcCz/wOITr8GFOUE7Dk7GGl vSiv7lT7EsS6TU7Q8tZQZzEOrwHvpQfuOBZdhGoTpfj7TODOC7LLHgVGXvmY7Rai 8X5cfyblNM2wTZ5UZm+jP8V/YlV89uiMEzew3Q3dMYL/4c8dvfk= =W3vP -----END PGP SIGNATURE-----
[toc] | [next] | [standalone]
| From | Elena ``of Valhalla'' <valhalla@debian.org> |
|---|---|
| Date | 2024-05-21 14:40 +0200 |
| Message-ID | <IGwWB-eQDv-3@gated-at.bofh.it> |
| In reply to | #1198150 |
[Multipart message — attachments visible in raw view] — view raw
On 2024-05-21 at 11:39:25 +0200, Timo Röhling wrote: > I noticed that your package uses the so-called "weak team maintainer" model, > [...] > Is this a deliberate decision or merely an artifact of some packaging helper > tool [...] Thanks for looking into this. It is a deliberate decision: this package is somewhat quirky and in the past I've had to say no to suggestions that would have fixed some issue, but caused problems elsewhere, so I'd prefer to keep the weak team maintainer model (as long as it is in a wide-scope team). Of course the typical team-wide changes are much welcome, but those usually don't trigger a new upload. This should be the only package I maintain that uses the weak team maintainer model, all of the other ones should be already using the team as the Maintainer (if they don't, *that* is an artifact of something, and if I'll notice it I'll fix it) -- Elena ``of Valhalla''
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web