3 ms·
> 'screw you'? Not classy. Then, fine, tone police, I'm not classy. I am, however, a FOSS developer who understands the value of non-technical contributions t
by BugsJustFindMe 9y ago
> 'screw you'? Not classy.
Then, fine, tone police, I'm not classy.
I am, however, a FOSS developer who understands the value of non-technical contributions to a project.
Know which kinds of bugs don't get fixed? The ones your users never tell you about because you decided to make it hard to report them.
- scrollaway 9y agoA thousand times this. Issues are generally a favour your user is doing you and your project. Yes, sometimes they're a waste of time; it's fine to close them if they are, it takes exactly one click to do so. Most of the time however, they're valuable even if you don't fix them: Other devs might see them and fix them for you. In almost all cases, turning issues off is incredibly counter-productive.
- robotresearcher 9y agoI agree with your argument completely. Just be nice, and your accurate advice is more likely to be useful. That's all.
- BugsJustFindMe 9y ago> Just be nice, and your accurate advice is more likely to be useful. That's all. https://en.wikipedia.org/wiki/Tone_policing https://en.wikipedia.org/wiki/Tone_policing My advice is already useful. If someone chooses not to take it because they'd rather tell non-technical users to pound sand, then I hope their project suffers for it.
- robotresearcher 9y agoThere is an obvious meta comment to make here that I leave as an exercise for the reader.
- BugsJustFindMe 9y agoNah, you're probably mistaken.
- Touche 9y agoI'd wager that 75% or more of GitHub projects are things like libraries, not end-user applications. So most people using GitHub are technical users.
- guelo 9y ago> the person maintaining the code actually knows what it does and how it works But apparently they're not allowed to decide what works best for their project as far as bug reports.