Closed ghost closed 11 years ago
Thanks again! I plan to eventually pull the licenses from license-templates rather than have them duplicated.
Ah okay, sounds good! Should I just add as many licenses as I can over at license-templates? Or should I try to stick to the most popular ones to help reduce license proliferation?
We definitely want to stick with commonly used licenses. Mostly OSI approved for open licenses. Closed licenses are okay too as they are ones that are frequently used. Also, an uncommon one is mostly okay if it's been used by one or two really notable projects. lice does support a command-line arg to specify a license template so it might be a good idea to create another directory/repo where people can throw in ANYTHING. But that's something for later.
Anyway, if you'd like to contribute licenses, license-templates is the best place to do it. Having the licenses in this repo become stale would be a good motivator for me to add the dependency.
Thanks much!
I replaced the existing template-cc0 with the officially-released plaintext version, and added the officially-released CC0 header.