Closed jpotts18 closed 9 years ago
Well, I chose AGPL because I would like the community to get back any improvements done on the DAG package itself. I guess that this shouldn't apply to the whole software that embeds DAG, but I'm not a lawyer, feel free to suggest a proper licence that forces the users to give back their improvements.
I'd be happy to give back any improvements. Personally I am a fan of the Apache 2.0 license.
http://opensource.org/licenses/Apache-2.0 http://opensource.org/licenses/category
There should be a license that just says "Leave it better than you found it"
Apache Licence is too liberal for me.
After a quick search on the net, it seems like that a "lesser" AGPL for libraries does not exists. Personally I would not consider a simple use of DAG library as a "derivative work". If this statement is not enough for you and you are using DAG in a commercial application you have probably a budget higher enough to buy a cheap WTFPL ( http://en.wikipedia.org/wiki/WTFPL ) licence from me.
I think I will just have to write my own, its only like 1k lines of code.
I would like to use this software in a commercial application but I can not because "Thus the GNU Affero GPL v3 stipulates that any adaptation of software that it covers must prominently offer its source code for download to users who interact with it over a network."
http://oss-watch.ac.uk/resources/agpl
Can you change the license to something less restrictive?