4 ms·
Worth remembering: under many other popular licenses, there would be no possibility whatsoever of legal action that leads to Ubiquiti releasing the full/proper
by notacoward 12y ago
Worth remembering: under many other popular licenses, there would be no possibility whatsoever of legal action that leads to Ubiquiti releasing the full/proper source for what runs on their devices.
- kelnos 12y agoWell, duh... most popular licenses don't require modifiers to release full source. Which is fine if that's the author's choice.
- notacoward 12y ago"Well, duh." Thank you for reinforcing my point (elsewhere) about how the "gratuitous negativity" rule will never be used to do anything but reinforce the HN zeitgeist. I knew I wouldn't have to wait long for an example I could point to.
- zaroth 12y agoI personally consider the new rule an exhortation to down-vote more aggressively whatever gratneg we come across. As I like to say, there's a button for that! To respond to your original point, I don't get it. If you choose to release under a license which doesn't require releasing source of any mods, that's a perfectly reasonable choice. Why should there be a "possibility of legal action" against something which is explicitly allowed by the license?
- notacoward 12y ago"down-vote more aggressively " I can't (as an interlocutor), and I can see that nobody else has either. The prediction seems to have survived at least this one test. "If you choose to release under a license which doesn't require releasing source of any mods" ...and there's nothing wrong with that. I'm not saying non-copyleft licenses are bad. I don't believe that. Even if I did, I don't have time for another round of that debate. I'm just pointing out what the practical difference is. People who care about the security aspect of Ubiquiti's behavior, or about the lost potential to install an alternate OS on their hardware, should be aware that permissive licenses give them zero leverage toward affecting a remedy. Those people might want to consider software licensing as part of their router purchase decision, even if they don't like GPL for their own code.
- kelnos 12y agoPerhaps I could have worded my response in a nicer way, but I stand by the point I was making. You're pretty much stating the obvious here; I don't see what it adds to the discussion. (I generally try to avoid meta-discussion, so this is all I'll say on this topic.)
- tbrownaw 12y agoYup. Only with GPL do sloppy development practices (lack of automated builds, sloppy version tracking, ...) tend to directly result in legal liability. Other licenses just don't make those sorts of demands.
- simoncion 12y agoNot so. Think of a license that limits you to X deployments per unit of time, and forbids any additional deployments. If your automated deployment system performs X+Y deployments (where Y > 0) in a unit of time, then you're in violation of your contract and legally liable for your actions. Is this contrived? A little. But, realistically: 1) The GPL isn't the only license that you can violate with sloppy dev practices. 2) In the overwhelming majority of GPL violation cases, the remedy is for the violator to simply comply with the code's license and ship the code covered by the GPL.
- tbrownaw 12y agoContrived examples are contrived. 1) Sibling post mentioned forgetting to include notices in the documentation. Which is a valid counterpoint, but I would assume requires more of a one-time effort than a permanent change (improvement) in work procedures. 2) Assuming they can even find the right version.
- simoncion 12y ago> I would assume [remembering to put copyright notices in documentation] requires more of a one-time effort than a permanent change (improvement) in work procedures. You assume wrong. There is always another project, or another library.
- belorn 12y agoPeople with sloppy development practices could easily forget to include all the required copyright notices. All popular license require that the copyright notice is included in distribution, and forgetting to do so puts one under legal liability.
- geofft 12y agoI don't think this is correct, but I'm also a little unsure what you're trying to say. For why I don't think is correct: if you violate a license, you are legally liable for copyright infringement, just as if there was no license on it in the first place. Every license other than CC-0, Unlicense, and other PD-equivalents requires something of you. If you use a piece of BSD-licensed software without attribution, you are liable for copyright infringement. (In at least the US, if the use was commercial, this is probably criminal copyright infringement.) The rightsholder can sue, and offer to settle out of court by having you release source instead of paying damages. It would be unusual but possible. For why I'm confused by this comment: isn't it intentional, on the part of almost all other popular licenses, to permit commercial reuse without requiring the release of source? Wouldn't one only use the Apache License, the BSD license, etc. if one wanted Ubiquiti to be able to use it without being compelled to release source? Is your claim that people are bad at understanding what licenses mean, and are unintentionally choosing weak copylefts when they want strong copylefts? I could believe that, but I haven't seen much evidence of that.
- tokenrove 12y agoI suspect the point is that people often say, in discussions about the GPL, that they expect commercial users of their BSD/MIT/etc licensed software to /usually/ contribute their changes back even though they're not obligated. My anecdotal experience with this, having done many contracts providing commercial modifications of OSS, is that the companies that contribute their changes back is a tiny tip on the iceberg of use and modification. That's not to say this is bad, if it's what one intends. But it's frustrating to watch people denigrate the GPL, sometimes, because of their wishful thinking about other licenses.