> If I want my source code under Apache-2.0, why should I have to change it to GPL just for you. You don't have to. Don't use the GPL'd code. The author of t

> If I want my source code under Apache-2.0, why should I have to change it to GPL just for you. You don't have to. Don't use the GPL'd code. The author of the GPL'd work has chosen unwaivering freedom for the user over all else. You are free to write your own implementation. Why should that developer have to allow you to use her code in proprietary software? Speaking personally: I'm a free software activist. I write my code in the hope that it will be useful to others, but under the condition that it always remain free/libre. I would rather my software never be used at all than be incorporated into a proprietary program. In certain cases, depending on the community (e.g. Web), I recognize that my choice might certainly mean that nobody will use the software. If I choose the LGPL for something to permit its use in proprietary software, then it's a strategic choice.[0] I currently have no LGPL'd projects. [0]: https://www.gnu.org/licenses/why-not-lgpl.html https://www.gnu.org/licenses/why-not-lgpl.html