On Tuesday 21 March 2006 20:43, Thomas Bushnell BSG wrote:
> Nathanael Nerode <neroden@twcny.rr.com> writes:
> So a mere non-reply does not, it seems to me, connote anything bad; it
> may simply mean that the bug report is complete in itself, and well
> get attention when I decide I have the attention to give it. If more
> than this is required, more needs to be asked.
The problem with that is that there is no way for the submitter to know
that, there's several possible reasons for not getting any reaction:
- maintainer currently busy with other stuff
- maintainer MIA
- maintainer doesn't care
- maintainer thinks bugrepport is complete and doesn't need any more info,
will be included/fixed in next upload
- ...
By not answering there's no way for the submitter to know which of the above
applies, it's an issue of not leaving users in uncertainty about what is
going on.
A simple 1 line reply is enough to remove that uncertainty:
- this takes maybe half a minute
- this makes Debian look a _lot_ more responsive then 2 months of silence
wile notting happens (because the maintainer is working on more pressing
problems/other packages or whatever).
--
Cheers, cobaco (aka Bart Cornelis)
1. Encrypted mail preferred (GPG KeyID: 0x86624ABB)
2. Plain-text mail recommended since I move html and double
format mails to a low priority folder (they're mainly spam)
Attachment:
pgpWJNBlm0YTJ.pgp
Description: PGP signature