Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you tell people to submit bugs to a mailing list, that means that devs will manually confirm bugs before putting them onto the bug tracker: this gives an incentive to get them taken care of faster, because right as it's added, someone who knows the codebase has a general idea of what's wrong.

Mail is standard, so it's not really a barrier. It kind of lessens the Caps-Lock Warriors of Bugzilla-like systems, though.



Then they have to subscribe to the mailing list, which is another set of extra steps. Some people only know the web exists and don't even know mailing lists are a thing.


url: projectpage.tld/bugs

Hi! If you're here, you must have found a bug. Send an email to XXX@projectpage.tld describing the bug, and we'll see to fixing it as fast as we can, and we'll alert you when we've started working on it!

You don't have to have them subscribe, necessarily.


As soon as someone thinks about reporting a bug, they’re already doing you a massive favour. Making them go away and write an email (which many people don’t often do any more) you’re already going to be testing their patience. You should be bending over backward to accept the report.



Which is basically what I said in https://news.ycombinator.com/item?id=21490182 Never put up barriers to accepting bug reports. Now does Trac help in any of this? No.


Trac is better than the GitHub/Bugzilla model, in any case, in my opinion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: