From adb887aa79e81f5ee5392be433e66e14b80ccbba Mon Sep 17 00:00:00 2001 From: Holly Auten Date: Thu, 5 Jun 2025 14:51:15 -0500 Subject: [PATCH 1/3] remove year --- LICENSE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LICENSE b/LICENSE index 0e84d474d..884ddd4fd 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2016-2017 Lawrence Livermore National Security +Copyright (c) Lawrence Livermore National Security Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal From f3b12ab11033229daad3d091a944874ea6d40b2c Mon Sep 17 00:00:00 2001 From: Holly Auten Date: Thu, 5 Jun 2025 14:51:21 -0500 Subject: [PATCH 2/3] add gem --- Gemfile | 1 + 1 file changed, 1 insertion(+) diff --git a/Gemfile b/Gemfile index 6c7bba6d1..9864b4cca 100644 --- a/Gemfile +++ b/Gemfile @@ -10,3 +10,4 @@ gem 'webrick' gem "jekyll-github-metadata" gem "jekyll-feed" gem "kramdown-parser-gfm" +gem "fiddle" From 6b07fe0c33fba40e40b7eb19aa6e208431139111 Mon Sep 17 00:00:00 2001 From: Holly Auten Date: Thu, 5 Jun 2025 14:51:26 -0500 Subject: [PATCH 3/3] add link --- about/licenses/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/about/licenses/index.md b/about/licenses/index.md index 1890b8b86..dee79af76 100644 --- a/about/licenses/index.md +++ b/about/licenses/index.md @@ -113,7 +113,7 @@ If your repository was approved for release under a different open source licens If your project has more than one license, then you must include *all* of the relevant licenses in your repository. We recommend that you name them with descriptive suffixes. For example, if your project is dual licensed under Apache-2.0 and MIT, you should have top-level `LICENSE-APACHE` and `LICENSE-MIT` files. -Because GitHub does not automatically detect multiple licenses, we recommend *also* adding a top-level `COPYRIGHT` file with a summary of license details. GitHub's "view license" link will then point to this file. You can look at [Spack](https://github.com/spack/spack) and its `README.md`, `COPYRIGHT`, and `LICENSE-*` files for an example of how to organize a project with two licenses. +Because GitHub does not automatically detect multiple licenses, we recommend *also* adding a top-level `COPYRIGHT` file with a summary of license details. GitHub's "view license" link will then point to this file. You can look at [Spack](https://github.com/spack/spack) and its `README.md`, `COPYRIGHT`, and `LICENSE-*` files for an example of how to organize a project with two licenses. See also the Linux Foundation's [recommendations for copyright notices](https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects). ## Other Considerations