Open jwoolston opened 9 years ago
We don't, afaik, have a policy on licensing. Anyone have a complaint with using AGPL?
The problem now is not that it's unprotected, but over-protected. What we make should be open-source. Everything is under full copyright protection until we poke holes in it by giving others permission to use it, with conditions at our option.
I asked him to open the ticket as I thought I had put it under Apache. Anyways, in the spirit of letting anyone have this code with the least amount of problems, the WTFPL is a good choice in my opinion which is effectively just saying it is public domain I believe.
If we want something less.. vulgar.. then possibly the MIT license? It is compatible with the Apache licenses in the libraries we use.
This is probably part of a larger discussion since we'll adapt whatever license we choose for all of our other Code for Orlando projects. Code for Miami uses a specific Code for America license, but I'm sure we can use something else if necessary.
Currently there is no license specified in either the
master
ordevelopment
roots, leaving the code unprotected. A license file should be added to the project root and, ideally, all files updated to include a header specifying the license as well.