Hi,
I have been looking at the thread, and here is what I think
I saw as the emerging consensus:
1) allow submiters subscribe to a bug at submit@ time
(perhaps the default being to subscribe, and unsubscription an
option)
2) nnn-submitter@ makes "certain" that the submitter gets one copy
message as well as the bug report. (Currently nnn-submitter@ is an
alias for the submitter only.)
3) allow direct subscription of people to bugs by the BTS, report
subscribers to bugs back to the BTS
So, is this an accurate summary of the rough consensus:
1) mail to n...@b.d.o reaches the submitter if they are subsribed,
otherwise not,
2) mail to nnn-submitter /always/ reaches the submitter (to be used to
get additional information) -- and also is sent to the subscribers
and maintainer (and debian-bugs-dist)
3) maintonly and quiet work as they do now.
|------------------+-----+---------------+---------------+-----------|
| | nnn | nnn-submitter | nnn-maintonly | nnn-quiet |
|------------------+-----+---------------+---------------+-----------|
| Submitter | ? | X | | |
| debian-bugs-dist | X | X | | |
| Subscribers | X | X | | |
| maintainer | X | X | X | |
| Bug log | X | X | X | X |
|------------------+-----+---------------+---------------+-----------|
There is a convention on the SELinux devel list, and LKML, where
anyone who responds to a thread is added to the CC list. I have grown
fond of that feature; and I wonder whether #351856 ought to be
extended to anyone who weighs in on a bug report.
manoj
--
A winner isn't nearly as afraid of losing as a loser is secretly afraid
of winning.
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
