4 ms·
Apache License 2 is among the most 'liberal' in allowing reuse, inside other open source or proprietary products. As long as you're the copyright holder, you c
by gojomo 16y ago
Apache License 2 is among the most 'liberal' in allowing reuse, inside other open source or proprietary products.
As long as you're the copyright holder, you can always relicense the work however you'd like, and in multiple ways simultaneously. Practically, you can't revoke a previously-offered license for a prior version – people who retain and distribute that version under the previous license can continue to do so. But you can offer your own proprietary products based on your same codebase, or let others do so with your permission.
If you start accepting outside contributions – which is usually something you want to do, and a sign of a healthy project – your ability to relicense could become more complicated, because then you're mixing others' copyrighted work in, and they were probably assuming it'd stay under the license in effect when they contributed. (If the governing license is Apache2, then they were already giving very broad permission to reuse in other works, so even if you can't 'relicense' it should be OK to keep integrating their Apache-licensed contributions into all sorts of other things.)
A competitor could also use your Apache2-licensed code in their own proprietary offerings. Their extensions/improvements would be under whatever license they prefer.
If that's a major fear, you want to look into 'Copyleft' licenses, of which the GPL is the major example. They make use conditional on derivatives staying free-licensed. That reassures some contributors, but can also prevent some adoption you'd like to see.
- metonymie 16y agoThank you for the reply, it has cleared a lot of doubts. I was really concerned about being able to reuse the code in a proprietary release, since my possible clients are limited and you sometimes you have to accept their conditions. I will look at the GPL right now. The question I still have is whether a possible competitor might (even under the GPL) do a release, open source it to their clients but not make it publicly accessible, meaning I wouldn't have access to their changes. If that is still possible, then I would stick to Apache 2, cause I want the technology to be used. Again thank you for your reply.
- gojomo 16y agoThe GPL's terms do not allow someone to make a derivative and then 'distribute' it to some (such as paying clients), unless they also make the source available to others under the GPL. But, if an unethical or confused competitor did convert your GPL'd code into a proprietary release, you'd still need to find out, raise a public objection, and possibly threaten/file a lawsuit to truly 'enforce' the terms.
- metonymie 16y agoI understand but "make the source available to others under the GPL" may mean give their clients source code under the GPL, not necessarily publishing said source code on the internet. (Though of course, the client may publish it on their own). Or I'm missing something and they do have an obligation to make it accessible? Anyhow I have chosen the Apache License. Thank you for clearing my doubts and for your reply.
- gojomo 16y agoYou should ask the FSF (the foundation around the GPL) for the finer details of their preferred interpretation. By my reading, essentially, anyone who gets a copy of the modified work must also be given the right to give it to others, and to get the source code. I suppose your competitor could try to conspire with some small, cohesive group of customers to hide from you any evidence/copies of their derivative product. But, the competitor can't make this secrecy a license condition of using what they built from your code, without also violating the GPL's terms. So you could then go after them for violating your copyright, if you know they've added license terms. (If they have violated your copyright/license, the remedy isn't automatically that you or anyone else gets their source code under the GPL; it could be some other correction/settlement/damages.)
- metonymie 16y agoI have contacted the FSF on one occasion ( regarding a patent problem ) and they weren't very responsive. I have already decided on the Apache license 2 for this version of the project. But it's just a quick and dirty release that is intended to showcase the technology. I might in the future have to port it to a another language ( the project is too dependent on a library that's not actively being maintained and I might have to write my own version ). If I do this I will definitely look at the GPL license. Again, Thank you for the reply.