Decide on licensing

[abettermap]

Summary

Project needs a license, for both the code and data (two separate things).

Intentions and requirements

(distilled from email convo)

• Flexibility
• Wide usage
• Ideally, require attribution
• Some reservations about commercial reuse (so MIT license seems inapplicable)

Resources

Code

• Creative Commons discourages their license to be used for software
• Chose open source license (simple chooser tool made by GitHub): https://choosealicense.com/
• https://help.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository

Data

• https://opendatacommons.org/licenses/by/summary/index.html
• https://opendatacommons.org/licenses/index.html
• ...and ODbL looks ideal.
• ...has a human readable summary here

Related

License stuff needs to happen before:

• Sign up for Sentry (error tracking) #15
• Jason creates the .github "community" repo. Can elaborate in an issue once there is one. So far GitHub: init templates for GH issues and PR's #3 is closest thing as all the GH "community" stuff will likely all happen at once.

[rperlin-ela]

ODbL for the data sounds good to me.

I'm out of my depth in terms of selecting a license for the code, but it seems like some different practices may apply (e.g. commerical reuse seems common). If MIT is a standard that's easiest for everyone, that should be fine, I guess the chances of serious abuse are very low. Want to get thoughts from @markturin @fiddleHeads

[markturin]

I am afraid that I am also out of my depth in this. And I am packing and preparing to leave for camping so am afraid that I don’t have the headspace for this right now How can we work towards a decision? Kindly Mark From: rperlin-ela <notifications@github.com> Reply-To: Language-Mapping/language-map <reply@reply.github.com> Date: Tuesday, June 23, 2020 at 15:47 To: Language-Mapping/language-map <language-map@noreply.github.com> Cc: "Turin, Mark" <mark.turin@ubc.ca>, Mention <mention@noreply.github.com> Subject: Re: [Language-Mapping/language-map] Decide on licensing (#19) ODbL<https://opendatacommons.org/licenses/odbl/index.html> for the data sounds good to me. I'm out of my depth in terms of selecting a license for the code, but it seems like some different practices may apply (e.g. commerical reuse seems common). If MIT is a standard that's easiest for everyone, that should be fine, I guess the chances of serious abuse are very low. Want to get thoughts from @markturin<https://github.com/markturin> @fiddleHeads<https://github.com/fiddleHeads> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKCODWFANAI7KGKETNHC4SDRYEWJRANCNFSM4OGBJ3KA>.

[abettermap]

@markturin let's discuss when you get back. I don't think it's holding anything up since the repo is private for now.

Have fun camping!

[markturin]

Thanks all From: Jason Lampel <notifications@github.com> Reply-To: Language-Mapping/language-map <reply@reply.github.com> Date: Tuesday, June 23, 2020 at 18:46 To: Language-Mapping/language-map <language-map@noreply.github.com> Cc: "Turin, Mark" <mark.turin@ubc.ca>, Mention <mention@noreply.github.com> Subject: Re: [Language-Mapping/language-map] Decide on licensing (#19) @markturin<https://github.com/markturin> let's discuss when you get back. I don't think it's holding anything up since the repo is private for now. Have fun camping! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKCODWGLCWBSU37AD52USELRYFLGBANCNFSM4OGBJ3KA>.

[rperlin-ela]

Ok, we're ready to move forward with MIT (for the code) and ODbL (for the data). For ODbL with the data, I think it's sufficient just to include some text in the About page and in any eventually downloadable data. And it seemed like we were potentially all set with applying the MIT license.

[abettermap]

Sounds good. I don’t think anything is needed on my end then (except to fetch the About content obviously, but that will happen later).

I’ll close this issue since #11 should cover it.