Don Armstrong wrote:
On Thu, 10 Sep 2009, Sandro Tosi wrote:
I was thinking about this a couple of hours ago, but in the
different direction: why not mailing the submitter by default?
Ideally, I'd imaging nnn...@b.d.o to reach
- submitter
n...@bdo should reach submitters who are interested in being reached by
default, but submitters who just want their problem fixed shouldn't be
deluged with mail. Always cc'ing submitters doesn't allow for
submitters to decide not to get those mail messages.
On what % of bugs will the submitter be unnecessarily "deluged with
mail"? This seems like an abstract hypothetical with no basis in reality
at least according to any of the packages I've ever worked on.
The submitter almost always needs to be in on the discussion for testing
fixes and clarifying the report. For non-team maintained packages, there
shouldn't be a whole lot of discussion in the bug report anyway that
doesn't concern the submitter. As for XSF bugs (as an example of
team-maintained packages) I can't recall an example when we didn't
consider it critical to have the submitter in the loop for all
communication.
The only counter-example I can think of is when maintainers decide to be
jerks and play bug ping-pong, in which case we have an entirely
different problem.
I, for one, would much prefer to have the submitter always CC'ed by default.
- David Nusinow
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
