Comments (6)
That is a great question and there is another resource I would like to share regarding this here.
from transform-to-open-science.
The "standard" recommendations for broad usage and re-usage, if you don't have concerns about IP, sensitive data, copyleft, etc. are
Data: CC0 (public domain release)
Code: MIT License
creative works (writing, images, etc.): CC-BY
from transform-to-open-science.
@nasacrawford I know CCO for data is expected, but is there a guideline per SMD for preferred open source software license?
from transform-to-open-science.
Thank you @hmjbarbosa for opening this issue and @admercs and @ha0ye's responses so far. I'd like to make a few additions and clarifications.
I am also aware of the discourse that the "standard" (who are "setting" these "standards"?) for those who "don't want to think about it" is to go with the licenses that @ha0ye suggested, e.g. CC0, MIT, CC BY, etc. However, I contend that "don't want to think about it" is not good practice for open science. For example, CC0, MIT, and CC BY fall under the category of non-reciprocal (also commonly known as "permissive") licenses, which means other people can take works under these licenses and create derivative works that are closed source. There are many cases where this is highly undesirable and harmful and can come back to bite you. Unfortunately, many scientists (and non-scientists!) go for these licenses as the default because they didn't want to think about it, and come to regret it later. They are often completely unaware that there are licenses which can preserve the freedoms that come with open data and other open source outputs.
I recognise that the legal details of open source licensing can be exhausting to fully understand, and will not go into them here. That said, I think it is critical to at least point out that there are two families of open source licenses rather than just the MIT-likes. I propose the following:
Non-reciprocal ("If you are happy with others taking what you made and creating closed-source derivatives"):
- Data: CC0, CDLA Permissive 2.0, CC BY 4.0 (note: CC0 doesn't even require others to give you attribution)
- Software code: MIT (or Apache 2.0, BSD licenses, etc.)
- Hardware designs: CERN OHL-P 2.0
- Other works (writing, images, audio, video, etc.): CC BY 4.0
Reciprocal ("If you want others to respect the freedoms of open source by also releasing their derivatives of your work as open source"):
- Data: CDLA Sharing 1.0, CC BY-SA 4.0
- Software code: GNU GPLv3 or GNU AGPLv3
- Hardware designs: CERN OHL-S 2.0 or CERN OHL-W 2.0
- Other works (writing, images, audio, video, etc.): CC BY-SA 4.0
As you can see, I've included open source hardware licenses because there are hardware-specific legal implications that non-hardware licenses don't address.
And back to @hmjbarbosa's original question:
Has the OpenScience community as defined a standard license that we should use?
No.
Unlike open source software/free software (where "free" means freedom, not free-of-charge) or open source hardware, I don't think there is a standards setting body that prescribes exactly which licenses must be used to qualify a work as open science.
Similarly, I take issue with colloquially referring to the default or "standard" licenses for open source software as MIT, CC BY, etc., because (to my knowledge) there was never a conscious effort to establish such standards, and it obfuscates the need to think about open source licensing more deeply. Again, I refer to my paragraph above on the consequences of not thinking about this.
from transform-to-open-science.
I would like to add to that advise on "Dual Licensing" models for OSS, e.g. , https://en.wikipedia.org/wiki/Multi-licensing. More on that in this twitter thread
from transform-to-open-science.
Thanks @hmjbarbosa for the question. NASA's current Information Policy for the Science Mission Directorate (SMD):
- for data "SMD-funded data shall be reusable with a clear, open, and accessible data, license" with a footnote "Government works are by default in the U.S. public domain and should be used if no other license applies". eg CC0.
- for software: "SMD-funded software should be released under a permissive license that has broad acceptance in the community:
This is a nice article about permissive versus copyleft licenses. Common permissive licenses are MIT, Apache2, BSD3, BSL.
Policy people will probably pick up on two key words there, but as a scientist I didn't really catch the difference until @nasacrawford pointed it out. The data policy states 'Shall' - this is a requirement. The software policy states 'Should' this is a recommendation.
The proposed update to the SMD Information Policy was released for comment 11/2021 and changes the language for software, "SMD-funded software shall be released under a permissive license that has broad acceptance in the community"
The comments are being addressed and it is expected that a new SMD information policy will be released this Summer.
from transform-to-open-science.
Related Issues (20)
- Create Open Science Success Story Solicitation Feature and Database HOT 5
- Create 'request TOPS presentation' HOT 2
- Multi-language Assistance for NASA resource development, DAACs, and Users HOT 5
- Create a NASA jupyterhub/Colab instance to do data analysis in a cloud framework HOT 4
- 🔒 - Create a SECURITY.md file and reference the NASA VDP HOT 4
- Add hacktoberfest label to repository to participate in hacktoberfest! HOT 1
- Add link to the deployed GitHub site on the repo HOT 2
- Cross post open job opportunities to the NumFOCUS job board
- Clarify request for information and PRs from TOPS panelists HOT 2
- Add contribution section to highlight people who contribute to this REPO HOT 1
- Update page titles for better readability in the JupyterBook HOT 2
- Restructure the "Get started" chapter of the JupyterBook HOT 2
- book-requirements.txt should contain dependencies version HOT 2
- Collaboration section for research and publications HOT 1
- updating links on Year of Open Science website HOT 2
- 404 link
- Digital Badging of Experts HOT 1
- Clarification of organizational structure for Year of Open Science training dataset documentation HOT 4
- Add presentation slides summarizing SPD-41a for scientists funded by SMD HOT 1
- TOPS HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from transform-to-open-science.