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
Some concerns that have come up during discussion (input from license/legal experts welcome):
Namespace squatting (where somebody else says, "no, I'm the Citation File Format"). Is this covered by copyright? Does CC BY do anything for us for this case?
What happens if someone forks the project as opposed to just the repo?
Software vs documentation vs data vs other stuff
Currently, this is being ignored by using a single CC BY 4.0 license
Mixed licensing (Apache-2.0) and representation on GitHub and Zenodo
The text was updated successfully, but these errors were encountered:
Related: I'm using REUSE by the Free Software Foundation Europe to apply different licenses to different files in some of my projects.
Doing this for the schema & website repos would help solve these two sub-issues:
* Software vs documentation vs data vs other stuff
* Currently, this is being ignored by using a single CC BY 4.0 license
* Mixed licensing (Apache-2.0) and representation on GitHub and Zenodo
Some concerns that have come up during discussion (input from license/legal experts welcome):
The text was updated successfully, but these errors were encountered: