4 ms·
If your organization uses any of: Linux, Android, emacs, gcc or any GNU utility, OpenJDK, or MongoDB, then GPL is clearly not a no-go. GPL only poses issues whe
by pron 9y ago
If your organization uses any of: Linux, Android, emacs, gcc or any GNU utility, OpenJDK, or MongoDB, then GPL is clearly not a no-go. GPL only poses issues when the product is a library. For standalone products or ones with linking/access exceptions like OpenJDK, GPL poses no issues, and organizations aren't afraid to use it, especially when they don't intend to modify it.
GPL is a great license that ensures that improvements to the product are shared back with the community. In fact, for a database like Riak, Affero GPL, like the MongoDB license may even be better, as organizations that make improvements to Riak but don't redistribute it but run it internally on their servers would also be required to contribute back their modifications.
- romwell 9y ago> GPL only poses issues when the product is a library What about the client libraries? Do you consider them to be a part of the product? It might make sense to release the client code (library) and the server code under different licenses (Apache2/GPL, respectively) if GPL is to be used.
- pron 9y ago> It might make sense to release the client code (library) and the server code under different licenses (Apache2/GPL, respectively) if GPL is to be used. Yep.
- mirashii 9y ago> If your organization uses any of: Linux, Android, emacs, gcc or any GNU utility, Two things wrong with this right off the bat. First, not all of these are GPLv3, which is the version with the problematic patent clauses that scare companies away. Second, it is not just in libraries that the GPLv3 is generally accepted to pose potential issues. You need look no further than Apple and the great investment they went through to avoid ever shipping GPLv3 software. The GPL kicks in as soon as you distribute the software.
- pron 9y ago> First, not all of these are GPLv3, which is the version with the problematic patent clauses that scare companies away. So, if Linux were GPLv3 you're saying that most companies wouldn't use it? > You need look no further than Apple and the great investment they went through to avoid ever shipping GPLv3 software. Most companies aren't like Apple. > The GPL kicks in as soon as you distribute the software. That's right, and that's a good thing. If you distribute GPL software that you modify, you need to make your modifications public. But as Riak is not a library, it does not infect any other component. If you distribute software with (say, Android) Linux but don't modify Linux then the GPL doesn't infect the other components of your software, as they're not actually linked (or Linux has some explicit exceptions).
- atonse 9y agoThat's a valid point, GPL is especially scary for libraries, less so with server software. Maybe I was a bit hyperbolic. :)