search

freifunk-ansible / ansible-freifunk

root repository
0 stars 1 forks source link

LICENSE #3

Open 0x4A6F opened 8 years ago

0x4A6F commented 8 years ago

I don't want to start a license war, but...

For code there is no objection against GPL, but for configuration management I'd like to use a more permissive license or no license at all [0]. It should be possible for roles to be included into every project. So to my knowledge at least a GPL with linking exception [1] is required. Preferable BSD/MIT or UNLICENSE/CC0. Any lawyers here?

For the root repository (ansible-freifunk), where the configuration is stored I'd like to use BSD/MIT or UNLICENSE/CC0.

Any objections against this approach?

[0] http://unlicense.org [1] https://en.wikipedia.org/wiki/GPL_linking_exception / https://de.wikipedia.org/wiki/GPL_linking_exception

genofire commented 8 years ago

Freifunk ist und seine Software, ist mir echt egal. Ich wäre dafür :)

/*
* ----------------------------------------------------------------------------
* "THE BEER-WARE LICENSE":
* <geno+dev@fireorbit.de> wrote this file. As long as you retain this notice you
* can do whatever you want with this stuff. If we meet some day, and you think
* this stuff is worth it, you can buy me a beer in return Geno
* ----------------------------------------------------------------------------
*/
``