License (again)

[jkmarz]

I see that a long time ago, someone opened an issue because there was no license information. Now there is a license (yay!) but it is not an OSI-approved license (boo!). Would you ever consider licensing under a permissive, OSI-approved license instead of WTFPL for jquery.event.swipe and jquery.event.move? If you really don't care what people do with your code, CC0 (Creative Commons public domain declaration) is a totally acceptable way to go. More and more development teams are being required to ONLY use OSS under OSI-approved licenses...

Thanks for your consideration!

[stephband]

Want to enlighten me as to what OSI means?

––––––––––––
http://sound.io
http://cruncher.ch
http://stephen.band

On 28 March 2016 at 23:25, jkmarz [email protected] wrote:

I see that a long time ago, someone opened an issue because there was no
license information. Now there is a license (yay!) but it is not an
OSI-approved license (boo!). Would you ever consider licensing under a
permissive, OSI-approved license instead of WTFPL for jquery.event.swipe
and jquery.event.move? If you really don't care what people do with your
code, CC0 (Creative Commons public domain declaration) is a totally
acceptable way to go. More and more development teams are being required to
ONLY use OSS under OSI-approved licenses...

Thanks for your consideration!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#36

[jkmarz]

Oh, hi, sure! OSI is the Open Source Initiative. They are the 'stewards' of the Open Source Definition and as such, a lot of people look to them and the Free Software Foundation for guidance on open source policy issues. The OSI-approved licenses are well-understood by both legal and software development communities and are thus palatable to folks who approve the usage of open source software within their organizations...