reconsider license

[grst]

The software is currently GPL-licensed. This could lead other companies avoid the package.
We could consider relicensing it under a more permissive license. Otherwise we should at least make sure that the templates have a more permissive license. Like that it should be the case that our license doesn't have any impact on DSO projects, only on the command line interface.

[grst]

By now I learned about open source licenses:

• Just using a GPL license doesn't force us to license DSO as GPL. But it means anyone using the combination of our code + the GPL dependency needs to abide to GPL terms. However code snippets from our code-based could still be reused under our license terms.
• There are weaker copy-left licenses like LGPL or Mozilla public license that could be interesting for us.

[grst]

I think I lean towards:

• LGPL for the package
• CC-0 for the templates

This should ensure that there are no strings attached for anyone using the template code, and provides some copyleft on dso itself (if someone modifies the code and distribute it, they need to share it, which is fair) while not having the "viral" property of GPL for anything building on top of it.