mne-tools
Clarify license of testing data
@drammock I suspect you know more about licensing than I do -- any thoughts here?
Creative commons licenses are appropriate for data(bases).
https://creativecommons.org/faq/#can-databases-be-released-under-cc-licenses
CC licenses are indeed appropriate for data.
Are you the copyright holders of the whole the testing dataset?
Lots of different people/groups have contributed data to the repo, and we never asked them to do so under any specific license.
I am not an expert at all on these issues, so not really sure how to proceed. I suspect what we probably need to do is decide on a license (CC0?), and then contact all people who acquired data and contributed it here to accept licensing the data that way. I think it will be a lot of work ☹️ There have been over a hundred PRs...
I am not an expert at all on these issues, so not really sure how to proceed. I suspect what we probably need to do is decide on a license (CC0?), and then contact all people who acquired data and contributed it here to accept licensing the data that way.
And it is not unlikely that some contributors will not be able to (re)license the data 🤔
What would speak against having individual licenses for each "dataset"? Or to license under CC0 what we can, and to branch out the rest into another repository and/or replacing it as well as we can with new, CC0 data.
What would speak against having individual licenses for each "dataset"?
nothing is in principle wrong with that. But we'd still need to track down the contributors to find out what license they think the data has / should have.
Or to license under CC0 what we can, and to branch out the rest into another repository and/or replacing it as well as we can with new, CC0 data.
-1 on splitting the repo. +1 on eventually replacing anything that we can't establish as CC0 with an alternative file(s) that we can license as CC0. But first let's just try asking people. I'll try to get a start on this toward the end of this week.