You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just pasted both licenses into one license file, but looking at how https://github.com/rust-lang/rust handles multiple licenses as well as https://nmfs-opensci.github.io/GitHub-Guide/#sec-license, it looks like maybe it's better to host separate license files and then describe their relevance/use+copyright disclaimer in the README file. I'm not sure if we want to do that now or if @eeholmes we're going to get new guidance soon about our licenses?
The text was updated successfully, but these errors were encountered:
New guidance is Apache 2.0 for code as that is fully permissible license which GPL2 is copy-left which is restrictive. Still no clear guidance on multiple licenses. Something like the Rust approach was discussed https://github.com/rust-lang/rust?tab=readme-ov-file. I need to get clarity on the COPYRIGHT file. Q is do we need to have data/doc under CC0 or is it ok to have everything under Apache 2.0?
I just pasted both licenses into one license file, but looking at how https://github.com/rust-lang/rust handles multiple licenses as well as https://nmfs-opensci.github.io/GitHub-Guide/#sec-license, it looks like maybe it's better to host separate license files and then describe their relevance/use+copyright disclaimer in the README file. I'm not sure if we want to do that now or if @eeholmes we're going to get new guidance soon about our licenses?
The text was updated successfully, but these errors were encountered: