-
Notifications
You must be signed in to change notification settings - Fork 1
License for governance documents #1
Comments
For licenses like CC-BY, the Creative Commons license wiki page says that attribution must be given to "the best of [one's] ability using the information available", and gives a list of what a user would need to do to respect the license. Almost all of those I think we can do ourselves for convenience. The GNU Free Documentation License seems to have quite a few conditions. Some aren't a big deal, but others can get very specific or restrictive about what a user must do (like having to use the same license), and might become a burden later on. In contrast, CC0 has no requirements. Neither party would have to do anything about anything, so it would create the least friction in adoption. There are also other CC license requirements we can include based on what we want. For example:
In my opinion, if these documents catch on, having at least an attribution requirement will really help in raising awareness of the project. I also think commercial use and derivative works should be allowed, so that similar projects can maintain themselves monetarily and change the documents to fit their use cases. I don't have any opinions about the last question, so I'd love to see what someone else thinks. |
I agree that keeping things non-restrictive for governance documents is a good idea.
A simple non-commercial clause usually hurts more than it helps, for example one wouldn't be allowed to print licensed documents and then charge money to make up for the costs. I agree with the assessment that CC-0 or CC-BY are the best options here. I'd favour CC-BY for the reason given by @1011X. Allowing more restrictive licensing for something like governance documents is totally fine as far as I'm concerned. |
We need to decide upon a license for our documents, so people can reuse and remix them without having to ask for permission.
GNU documentation licenses, Creative Commons Attribution, and Creative Commons Zero (public domain) are the main options, but there might be something else too.
The text was updated successfully, but these errors were encountered: