Making the license.txt available and understandable (GSA#141)

* Adding link to /license * Adding more context for non-tech folks. * pre-commit fixes * relative link.. one of these days I'll remember. Co-authored-by: pre-commit <[email protected]>
patrickhlauke · Aug 24, 2021 · eaed4a2 · eaed4a2
1 parent da3446a
commit eaed4a2
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/LICENSE.md b/LICENSE.md
@@ -15,6 +15,10 @@ Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability,
 
 Copyright © 2017-2018 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.
 
+### Software used by this project
+
+We have used other open source software libraries to build this project. For those who are interested we have listed these and the [exact license that they use here](/license/).
+
 ## The rest of this project is in the worldwide public domain
 
 As a work of the United States government, this project is in the public domain within the United States.

diff --git a/license/README.md b/license/README.md
@@ -1,5 +1,5 @@
-Licences of works that we leverage are listed in the `licenses.txt` file.
+Licences of works that we leverage are listed in the `licenses.txt` file. This software is all open source and we are listing it here for people who want to investigate specific packages used.
 
-To update the `licenses.txt` file, run `npm run generate-license-report` and commit the changes.
+We keep this file up-to-date. When new packages are added the `licenses.txt` file needes to be updated. Simply run `npm run generate-license-report` from the command line and commit the changes.
 
 See [README](../README.md) for more details.