From b39b157e81ca9014dacaf85bd4750560959b2d22 Mon Sep 17 00:00:00 2001 From: Bryan Harter <41062454+bryan-harter@users.noreply.github.com> Date: Tue, 26 Aug 2025 21:28:38 +0000 Subject: [PATCH 1/2] Adding some more information about data licensing --- docs/source/licensing.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/source/licensing.md b/docs/source/licensing.md index 11a442a..8098270 100644 --- a/docs/source/licensing.md +++ b/docs/source/licensing.md @@ -81,6 +81,22 @@ you’re distributing/producing. 3. Fill out the copyright, noting that it is NOT LASP, but *Regents of CU. Copyright (c) YYYY, Regents of the University of Colorado* + +### Data + +1. Public data from NASA missions default to the **CC0 1.0** license, unless otherwise marked. +2. NASA guidance specifies that all data from NASA sponsored missions are to be reusable with a clear, open, and + accessible data license. It does not enforce a specific license, however. + * **CC0 1.0** is the license most widely used for public data within LASP. + * **CC-BY 4.0** is also used for public data in some missions (for example, TSIS-1); + this keeps the data open but asks the user to attribute the data source. + +For more information on licensing Earth data, please reference the +[EarthData Data Use and Citation Guide](https://www.earthdata.nasa.gov/engage/open-data-services-software-policies/data-use-guidance) + +For Heliophysics data, please reference the +[Heliophysics Data Management Handbook](https://science.nasa.gov/wp-content/uploads/2024/05/hpd-data-management-handbook-final1.pdf). + ## Useful Links * [Public license selector](https://ufal.github.io/public-license-selector/) From b1eed4958d7062b3c94ce9da6e3782171c11c790 Mon Sep 17 00:00:00 2001 From: Bryan Harter <41062454+bryan-harter@users.noreply.github.com> Date: Tue, 26 Aug 2025 21:37:23 +0000 Subject: [PATCH 2/2] Fixing the lint stuff --- docs/source/licensing.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/docs/source/licensing.md b/docs/source/licensing.md index 8098270..124554c 100644 --- a/docs/source/licensing.md +++ b/docs/source/licensing.md @@ -10,7 +10,7 @@ to use any part of the code legally. This guide provides options for choosing th ## Options for this guideline -### Software +### Software Licenses To avoid copyright concerns, it is recommended that: @@ -45,7 +45,7 @@ Some examples from groups at LASP: *NOTE: There is a NASA Open Source License: ; However, it DOES NOT satisfy the Free Software Foundation’s definition of open source.* -### Data +### Data Licenses A creative commons license can be used to restrict who can use data and how they use it. @@ -72,7 +72,7 @@ you’re distributing/producing. ## How to apply this guideline -### Software +### Software Licensing Guidelines 1. CU Venture Partners (CU lawyers) recommend using BSD-3 license. 2. Make sure that you put the license file in the root directory and call it `LICENSE` or `LICENSE.md` so that the code @@ -81,20 +81,19 @@ you’re distributing/producing. 3. Fill out the copyright, noting that it is NOT LASP, but *Regents of CU. Copyright (c) YYYY, Regents of the University of Colorado* - -### Data +### Data Licensing Guidelines 1. Public data from NASA missions default to the **CC0 1.0** license, unless otherwise marked. -2. NASA guidance specifies that all data from NASA sponsored missions are to be reusable with a clear, open, and - accessible data license. It does not enforce a specific license, however. - * **CC0 1.0** is the license most widely used for public data within LASP. - * **CC-BY 4.0** is also used for public data in some missions (for example, TSIS-1); - this keeps the data open but asks the user to attribute the data source. +2. NASA guidance specifies that all data from NASA sponsored missions are to be reusable with a clear, open, and + accessible data license. It does not enforce a specific license, however. + * **CC0 1.0** is the license most widely used for public data within LASP. + * **CC-BY 4.0** is also used for public data in some missions (for example, TSIS-1); + this keeps the data open but asks the user to attribute the data source. -For more information on licensing Earth data, please reference the -[EarthData Data Use and Citation Guide](https://www.earthdata.nasa.gov/engage/open-data-services-software-policies/data-use-guidance) +For more information on licensing Earth data, please reference the +[EarthData Data Use and Citation Guide](https://www.earthdata.nasa.gov/engage/open-data-services-software-policies/data-use-guidance) -For Heliophysics data, please reference the +For Heliophysics data, please reference the [Heliophysics Data Management Handbook](https://science.nasa.gov/wp-content/uploads/2024/05/hpd-data-management-handbook-final1.pdf). ## Useful Links