7 ms·
> As a maintainer, it is his choice which patches to accept. If you're not happy with his decisions, choose another project, fork it, or pay someone to do it f
by izacus 7y ago
> As a maintainer, it is his choice which patches to accept. If you're not happy with his decisions, choose another project, fork it, or pay someone to do it for you.
Sure, but that DOES NOT mean you're immune to criticism, especially when it comes to security.
Your type of argument could otherwise be used for pretty much everything - even large corporations. It's not useful.
- deng 7y ago> Your type of argument could otherwise be used for pretty much everything - even large corporations. It's not useful. No, if you pay for things, you have a contract and things are immediately different.
- makomk 7y agoSo basically, if you use open source code in your code, you should expect there to be security vulnerabilities which people know about and are keeping quiet about because it'd be unfair to the unpaid creator to criticise them? Tbat sure makes it sound like it's morally irresponsible to use open-source rather than purchased commercial code in something like a web-facing service in 2020, especially given what we know now about the damage compromises can do and the resulting legal climate.
- komali2 7y agoYou can report on security vulnerabilities in a library without being vitriolic. Find vulnerability. Already, awesome of you to have done. Issue patch request. That's 10x even better, you're a boon to the community. You submit it, it gets rejected, you find out why and it's the maintainer is just not feeling it or some other irrational reason. Fork, put in the readme why you forked, write a blog post without being a dick about it, done. The article we're talking about is referring to the bloodbath of a Reddit pile-on. That's totally unacceptable behavior from an adult.
- deng 7y agoPlease don't twist my words. I never said you have to keep quiet or that you're not allowed to criticize. If you see that a project has serious issues, feel free to write a blog post about it. Maybe offer to help, but don't demand your help being accepted.
- asjw 7y ago> if you use open source code in your code, you should expect there to be security vulnerabilities You should be able.to fix them yourself That's the premise of OSS if you don't want to pay for a cab or a driver, you should be able to drive
- badloginagain 7y agoYou can fix them yourself, by duplicating the car and fixing it yourself. You can't force someone else to fix the locks on their car
- aurosul 7y agoThe only guarantee OSS gives is - full access to the source code - full rights to modify it and use it as it was your own There's no other guarantee. So if someone writes some code that becomes highly popular, they have no obligation whatsoever to maintain it the way people want. They don't even have to maintain it at all, if they don't want to! It's out in the public, it's free, that's the end of the agreement on the creato's side. If a writer gave away their writings for free, could people pretend that they write what people want them to write, the way they want? Is it fair to judge the writer because the answer was "WONTFIX"? But the reality is worse than that. A lot of companies are literally making billions using OSS, but they are not paying for it, a lot of programmers are making a lot of money by assembling OSS for their clients, but they are not paying for it, hell most of them are not even contributing in _any_ way, what does entitle them to pretend the attention of the OSS maintainer or that the maintainer should act in a way or another, according to the "community" desires?
- UncleMeat 7y agoYes. I would expect there to be vulns and inconsistent patching for all OSS that I depend on and where I don't have a professional contract with its maintainers.
- hvis 7y agoNo, I am allowed to criticize a corporation which is obviously acting against public good. Even if I'm not paying them anything.
- creyes 7y agoThe problem here was not that there was criticism, it's the TYPE of criticism (anger, hate etc). And you know what's a good form of criticism? An issue with an attached PR
- throwlaplace 7y agono your argument isn't useful. the question is never about rights because we all know what the maintainer's rights are (so it's always a discussion of obligation). if you accept that the open source projects are voluntary as an axiom then you in fact cannot criticize choices made by the volunteer. here's an analogy: a homeless person asks for money. you don't give him money but buy him food. can the homeless person rightfully criticize you?
- wgerard 7y agoHere's another analogy: A homeless person asks for money. You don't give him money but give him some advice. Can the homeless person rightfully criticize you? You can absolutely criticize choices made by volunteers. I don't think you need to think too deeply about this to imagine situations where few would object to criticizing a volunteer's behavior. An obvious one would be if an open source maintainer willfully included malware/etc. into their project - which, to many people, ignoring glaring security issues is vaguely equivalent. I obviously don't think vitriol is warranted ever, but criticism obviously is from time-to-time.
- throwlaplace 7y agowhat is the relationship of your analogy to this situation? is the maintainer the homeless person in your analogy? you can criticize all you want as an exercise of your critical thinking faculties but the volunteer is not in anyway obligated to heed the criticism. "it's my money/time and I'll spend it how I want, which includes burning it" is the fundamental axiom. Given that that is the foundation what sense would it make to criticize that person for burning the money - it's right there in the premise that they're allowed to!
- wgerard 7y ago> what is the relationship of your analogy to this situation? is the maintainer the homeless person in your analogy? It's your analogy, you tell me. > you can criticize all you want as an exercise of your critical thinking faculties but the volunteer is not in anyway obligated to heed the criticism. Nobody said they were. Nobody's trying to punish the maintainer legally. That doesn't mean criticism won't be offered or warranted. Here's another analogy: You have a right to be a jerk in real life. Nobody's going to physically or legally stop you, barring extreme circumstances. People will still criticize you for being a jerk, as is THEIR right.
- SkyBelow 7y ago>Sure, but that DOES NOT mean you're immune to criticism, especially when it comes to security. But our society does not just openly accept giving criticism. There are rules. Unwritten and extremely vague ones, no doubt, but still social rules. This is especially so when criticizing something a person is providing for free. In this incident, did the criticism cross the boundary and violate those rules? It seems so. Many people likely gave respectful criticism that followed the rules but they appear to have been drowned out by those who did not.
- HorstG 7y agoSecurity isn't a special license for being nasty. Criticism is fine, even with some urgency due to security being important. But software done for free by volunteers carries no obligation of a legal or even a moral kind, whatsoever. This is completely different from selling software or doing work for hire or donations. There a moral and often even legal obligation exists.
- UncleMeat 7y agoCriticism is one thing. Dog piling and vitriol for the sake of feeling superior and joining a circlejerk is another thing.
- endorphone 7y agoThis has been the argument throughout the various discussions -- that somehow if there isn't a payment structure between party A and party B, there is full immunity from criticism, questioning, expectations, etc. It is absolutely insipid and is a logical non-starter that doesn't pass the most basic of considerations. Yet it keeps recurring. It's bizarre.
- pgeorgi 7y ago> Sure, but that DOES NOT mean you're immune to criticism The problem wasn't the criticism, but the expectation that said criticism invokes a certain behavior of the maintainer. You can criticize open source maintenance by creating a fork in which you outline your vision (e.g. "much less use of 'unsafe' in the web package") - and deal with the burden of being a maintainer. Everything else is just trying to force people to do stuff for you, and that's rude.
- weberc2 7y agoFWIW, I don't have a dog in this fight. On the one hand, there is the maintainer who is within his rights to accept or reject patches as he wishes (although it's not great that he's allegedly falsely advertising his project as secure) and you have critics who are within their right to criticize (although it's not great that much criticism is vitriolic, etc). As TFA says, it's a sad affair all around. > The problem wasn't the criticism, but the expectation that said criticism invokes a certain behavior of the maintainer. Of course it implies that the maintainer should change. All criticism implies an expectation of change, at least when the opportunity to change is still available. > Everything else is just trying to force people to do stuff for you, and that's rude. Criticism isn't "force" or "attempted force". This is just criticism. If you think criticism is rude, that's fine. Hypocritical, but fine. You can't rationally say the maintainer is within his rights for rejecting security patches and then argue that critics are wrong for criticizing these practices.
- pgeorgi 7y ago> Criticism isn't "force" or "attempted force". If you think criticism is rude, that's fine. Hypocritical, but fine. No, the attempt to make somebody do what you want by brigading is what's attempting to exert force and what's rude. Hiding that behind "I'm just criticizing" (you didn't, but it's a popular refrain in such "debates") is more than only rude, it's also cowardice. > You can't rationally say the maintainer is within his rights for rejecting security patches and then argue that critics are wrong for criticizing these practices. The author of the package didn't force their code onto the users. The authors of the criticism forced their criticism on him by throwing it his way in the form of bug reports etc. even when it was clear that there's no interest in it.