Add a license before pushing code

[scottveirs]

Most Orcasound projects have defaulted to a permissive MIT license, with copyright to the Orcasound open source community (not a legal entity). Here is an example from the code developed by the all-volunteer Microsoft hackathon teams over the past few years.

Happy to discuss our experience to date with open source licenses, as well as Creative Commons licenses for data, and -- most recently -- emerging licenses for models that address ethical use of AI.

[jonom]

@scottveirs sounds good - MIT license would be my choice as well. @ben-hendricks do you have an opinion on the copyright aspect? The way I see it copyright is kind of redundant when paired with an MIT license so I don't have any preference about who is named as the copyright owner.

[ben-hendricks]

I am fine with an MIT license. I feel any copyright statement should reflect that this is a joint project between NCCS, OrcaSound, SWAG, and SoundSpace Analytics and some of the organizations may have an interest in not just using the code for their interest but be acknowledged as their creator and financial contributor. Any copyright message should reflect this, otherwise I prefer to not specify a copyright at all. Thoughts?

[scottveirs]

Hey @jonom and @ben-hendricks, I added an MIT license here with this copyright notice:

Copyright (c) 2023 Orcasound, North Coast Cetacean Society, SoundSpace Analytics (v.1)