[KolmogorovComp]

Seem to me some people have forgotten about FOSS projects

> 15. Disclaimer of Warranty.

> THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

[f33d5173]

Here's the OSS users disclaimer:

I RESERVE THE RIGHT TO COMPLAIN, WHINGE, CRITIQUE, GET MAD AT, OR OTHERWISE COMMENT ON ANY AND DECISIONS, COMMITS, PATCHES, MARKETING, OR OTHER DECISIONS MADE BY THE PROJECT. THESE COMMENTS COME WTH NO WARRANTY FOR FITNESS FOR ANY PURPOSE, INCLUDING THE IMPLIED WARRANTY OF BEING CORRECT, USEFUL, OR KIND. SHOULD MY COMMENTS PROVE UNWANTED, YOU RESERVE THE RIGHT TO STICK IT WHERE THE SUN DON'T SHINE.

Feel free to print out this disclaimer so you have a copy to reference whenever you come across unwanted criticism of a foss project.

I really don't get how people don't realize that this "they can do whatever they want" stance cuts both ways. Users can do whatever they want as well. If they don't like something, they can express it...

[senordevnyc]

lol, no one is trying to silence you. Yeah, of course you can whine and complain, no one is stopping you. Just don't expect anyone to give a fuck.

[latexr]

“No warranty” isn’t the same as “no complaints”. Otherwise there wouldn’t be an issue tracker and a discussions section.

The issue in question has already gone to crap and your point has been made there as well. It could definitely have been handled better, by all parties involved, but blindly quoting legalese isn’t going to resolve anything or make it better.

[KolmogorovComp]

An Issue tracker is to track issues regarding the behaviour of the program, not the behaviour of the maintainer.

[fg137]

Disagree. Issue trackers are used for all sorts of things in all kinds of projects. Go look around, plenty of examples out there. Unless the maintainers have explicitly specified how issue trackers are supposed to be used, (reasonable) discussions are usually allowed on issue trackers, especially GitHub Issues.

[latexr]

And focusing on that after the fact does nothing to resolve the situation or advance the discussion, which should be the goal now.

During an emergency situation where an issue is running out of control, the priority is to evaluate and contain the problem then address it, it is not the time to assign blame and quote regulations which weren’t followed. That’s for later, when everything is stable, together with understanding why the rules weren’t followed and if you can improve that process for the future.

[layer8]

If issues with the program are caused by behavior of the maintainer, it doesn’t seem inappropriate.

[tardedmeme]

Oh he's legally allowed to do this, it's just that he's a dick for doing it.

One of the issue comments says:

> Just because you are giving free soup to the homeless, doesn't mean you can piss in it.

[indrora]

Diogenes would disagree.

But I also think Diogenes would look at this whole situation and start flinging his own shit at people only to say "What, I'm participating in the same way you are" when called on it.

[account42]

Seems reactonaries have forgotten that writing something in a license doesn't mean you can just it as a get out of jail free card in every situation.