New answers tagged

2

We have a question here called So the GPL doesn't restrict the creator of the software in any way? which addresses the first part of this issue. Essentially, as long as you are the sole rightsholder in this library (ie, it's not GPL because it's based on somebody else's GPL code) then it is fine for you to convey the library to the client on terms other ...


2

I'm going to answer your question from the perspective: what is the risk to open sourcing the technology that your friend's business has developed. I try to tackle your more specific question at the end. TL,DR If your friend's company is built around the technology the company would open source, it's a real risk that their company would not be financially ...


3

Plausible, an open source alternative to Google analytics, released a blog post detailing their move from MIT licensing to the AGPL (Affero GNU Public License). In it, they have the following claim: Here are a couple of events that made us aware of the risks with a permissive open source license: There’s been at least one case where a corporation has taken ...


2

Depending on jurisdiction, there could be copyright exceptions available that allow reverse-engineering for the purpose of interoperability. Sniffing is particularly unproblematic because you're observing behaviour instead of reading copyright-protected material, but decompilation could be an issue because it's not clear that your software is your own ...


Top 50 recent answers are included