3. Add the option to subscribe to a package on BTS
This would at least allow people who don't/wouldn't use PTS to receive new bug reports for packages they care about. PTS is a separate service that happens to forward BTS bug reports, in a way.
There is another downside to the BTS sending mails to uploaders. - There
is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs related to it.
On Tue, Mar 04, 2025 at 07:13:50PM +0800, Blair Noctis wrote:
There is another downside to the BTS sending mails to uploaders. - There >>>is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs related to it.
Packages accumulate Uploaders, because people who lose interest in a
package or in Debian as a whole rarely remove themselves.
On 03/03/2025 01:40, Marc Haber wrote:
Maintainer: Debian Adduser Developers <[email protected]>
Maintainer: Debian Sudo Maintainers <[email protected]>
Honestly I never understood how exactly @p.d.o addresses work.
Devref says it's "a simple email alias" that "provides a way to email the maintainer",
"whatever their individual email address (or addresses) may be",
but doesn't tell which kind of email addresses it forwards to.
Nor can I find info at other places, like wiki.d.o.
I always thought [email protected] would forward to the Maintainer of foo,
but setting [email protected] as the Maintainer of foo means forwarding to itself.
I'd also appreciate some (clearer) documentation of the @p.d.o addresses, >other than the vague mention in devref.
Policy doesn't seem to describe it,
nor did I succeed searching in wiki.d.o.
Consider somebody being an active momeber of a larger team and leaving
it. He would continue to receive the mails sent uploaders. And the only
way to "unsubsribe" would be to make a (possibly huge) number of
sourceful uploads.
On 04/03/2025 01:29, Andreas Metzler wrote:[...]
There is another downside to the BTS sending mails to uploaders. - There
is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs related to it.
Or if one really wants to,
they could set up a filter in their email client and/or server,
to filter out such emails.
This requires extra work,
just like your suggestion above.
On 2025-03-04 Blair Noctis <[email protected]> wrote:
On 04/03/2025 01:29, Andreas Metzler wrote:[...]
There is another downside to the BTS sending mails to uploaders. - There >> > is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs related to it.
Or if one really wants to,
they could set up a filter in their email client and/or server,
to filter out such emails.
This requires extra work,
just like your suggestion above.
Consider somebody being an active momeber of a larger team and leaving
it. He would continue to receive the mails sent uploaders. And the only
way to "unsubsribe" would be to make a (possibly huge) number of
sourceful uploads.
On 2025-03-04 Blair Noctis <[email protected]> wrote:
On 04/03/2025 01:29, Andreas Metzler wrote:[...]
There is another downside to the BTS sending mails to uploaders. - There is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs related to it.
Or if one really wants to,
they could set up a filter in their email client and/or server,
to filter out such emails.
This requires extra work,
just like your suggestion above.
Consider somebody being an active momeber of a larger team and leaving
it. He would continue to receive the mails sent uploaders. And the only
way to "unsubsribe" would be to make a (possibly huge) number of
sourceful uploads.
On 04/03/2025 21:43, Marc Haber wrote:[...]
On Tue, 4 Mar 2025 19:15:16 +0800, Blair Noctis <[email protected]>
wrote:
[...]
Honestly I never understood how exactly @p.d.o addresses work.
Devref says it's "a simple email alias" that "provides a way to
email the maintainer",
"whatever their individual email address (or addresses) may be",
but doesn't tell which kind of email addresses it forwards to.
though it seems further clarification can only come from p.d.o staff.
So if the "staff" agrees,
we can make @p.d.o addresses forward also to Uploaders,
thus with @p.d.o address as Maintainer,
also forwarding bug reports to Uploaders,
achieving the goal.
From your initial list, my preferred outcome is to modify tracker.debian.org so that all Uploaders are automatically subscribed, that's what has been requested for a long time in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756954
That would be nice.
Thanks for considering it.
New/removed subscriptions should be notified by emails to the affected persons.
Agreed.
If we are to make the tracker "smart",
these should of course be considered.
Need some hands?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 165:09:06 |
| Calls: | 12,096 |
| Calls today: | 4 |
| Files: | 15,001 |
| Messages: | 6,517,803 |