add link to fedramp

eeholmes · eeholmes · commit 56894750175b · 2022-10-22T08:41:25.000-07:00
diff --git a/GitHub-SOP.qmd b/GitHub-SOP.qmd
@@ -51,12 +51,10 @@ NOAA's official GitHub policy from 2017 may be found [here](images/NOAA-GitHub-U
 
 ### Background {#sec-background}
 
-In 2017, GitHub use was authorized for scientific products: [CIO memo authorizing GitHub use at NOAA](images/CIO-Memo-Use-of-GitHub-at-NOAA.pdf). Subsequently, in 2017, NOAA released official GitHub guidelines [here](images/NOAA-GitHub-Usage-Guidelines.pdf). Some individual centers and offices prepared local GitHub guidelines and SOPs to help their staff interested in using GitHub. See [references](@sec-references).
-
-Since 2017, a lot has changed. GitHub use has expanded greatly across NMFS and all the federal agencies ([link](https://nmfs-opensci.github.io/ResourceBook/content/github_in_gov.html#github-in-other-agencies)), and GitHub has become integrated into modern scientific workflow for a wide variety of reasons. The 2017 memo tells us what can be shared on GitHub (scientific products) but there is a need for guidelines that cover and recognize the wide variety of scientific work (and learning) that is done on GitHub and much has changed in the tools provided by GitHub since 2017. Local GitHub SOPs have been developed by individual centers (see [references](@sec-references)) to help their staff. These are very helpful, but not all centers have GitHub SOPs and even with these, staff are often confused by how to follow the guidelines in practice. For example, if I fork a repo in statistics workshop I am in, am I supposed to have a gold standard backup for that? What does it mean to keep NOAA work separate? I was told that private repos are not allowed, but someone at another center said *public* repos are not allowed? I work with confidential fisheries data; what are my options? I am developing an R or Python package with functions for making common plots but this is completely generic; what are my options? I am collaborating with a regional office on an assessment that will be released as an official report from my center; what are my options?
+In 2017, GitHub use was authorized for scientific products: [CIO memo authorizing GitHub use at NOAA](images/CIO-Memo-Use-of-GitHub-at-NOAA.pdf). Subsequently, in 2017, NOAA released official GitHub guidelines [here](images/NOAA-GitHub-Usage-Guidelines.pdf). Some individual centers and offices prepared local GitHub guidelines and SOPs to help their staff interested in using GitHub. See [references](@sec-references). Since 2017, a lot has changed. GitHub use has expanded greatly across NMFS and all the federal agencies ([link](https://nmfs-opensci.github.io/ResourceBook/content/github_in_gov.html#github-in-other-agencies)), and GitHub has become integrated into modern scientific workflow for a wide variety of reasons. The 2017 memo tells us what can be shared on GitHub (scientific products) but there is a need for guidelines that cover and recognize the wide variety of scientific work (and learning) that is done on GitHub and much has changed in the tools provided by GitHub since 2017. Local GitHub SOPs have been developed by individual centers (see [references](@sec-references)) to help their staff. These are very helpful, but not all centers have GitHub SOPs and even with these, staff are often confused by how to follow the guidelines in practice. For example, if I fork a repo in statistics workshop I am in, am I supposed to have a gold standard backup for that? What does it mean to keep NOAA work separate? I was told that private repos are not allowed, but someone at another center said *public* repos are not allowed? I work with confidential fisheries data; what are my options? I am developing an R or Python package with functions for making common plots but this is completely generic; what are my options? I am collaborating with a regional office on an assessment that will be released as an official report from my center; what are my options?
 
 :::{.callout-note}
-When the 2017 memo was written, GitHub was not Fedramp authorized. GitHub Enterprise became Fedramp authorized in 2018 and GitHub use expanded rapidly in other agencies (e.g. GSA and VA) using Enterprise. A number of the NOAA Fisheries science centers have a GitHub Enterprise account. The 2017 memo does not distinguish between GitHub (free) and GitHub Enterprise (paid). You can think of GitHub Enterprise as a secure private GitHub environment that you log into but functions otherwise mostly like the free GitHub once you are inside.
+When the 2017 memo was written, GitHub was not Fedramp authorized. GitHub Enterprise became [Fedramp authorized](https://government.github.com/fedramp-faq) in 2018 and GitHub use expanded rapidly in other agencies (e.g. GSA and VA) using Enterprise. A number of the NOAA Fisheries science centers have a GitHub Enterprise account. The 2017 memo does not distinguish between GitHub (free) and GitHub Enterprise (paid). You can think of GitHub Enterprise as a secure private GitHub environment that you log into but functions otherwise mostly like the free GitHub once you are inside.
 :::
 
 ### Scientific products
diff --git a/index.qmd b/index.qmd
@@ -51,12 +51,10 @@ NOAA's official GitHub policy from 2017 may be found [here](images/NOAA-GitHub-U
 
 ### Background {#sec-background}
 
-In 2017, GitHub use was authorized for scientific products: [CIO memo authorizing GitHub use at NOAA](images/CIO-Memo-Use-of-GitHub-at-NOAA.pdf). Subsequently, in 2017, NOAA released official GitHub guidelines [here](images/NOAA-GitHub-Usage-Guidelines.pdf). Some individual centers and offices prepared local GitHub guidelines and SOPs to help their staff interested in using GitHub. See [references](@sec-references).
-
-Since 2017, a lot has changed. GitHub use has expanded greatly across NMFS and all the federal agencies ([link](https://nmfs-opensci.github.io/ResourceBook/content/github_in_gov.html#github-in-other-agencies)), and GitHub has become integrated into modern scientific workflow for a wide variety of reasons. The 2017 memo tells us what can be shared on GitHub (scientific products) but there is a need for guidelines that cover and recognize the wide variety of scientific work (and learning) that is done on GitHub and much has changed in the tools provided by GitHub since 2017. Local GitHub SOPs have been developed by individual centers (see [references](@sec-references)) to help their staff. These are very helpful, but not all centers have GitHub SOPs and even with these, staff are often confused by how to follow the guidelines in practice. For example, if I fork a repo in statistics workshop I am in, am I supposed to have a gold standard backup for that? What does it mean to keep NOAA work separate? I was told that private repos are not allowed, but someone at another center said *public* repos are not allowed? I work with confidential fisheries data; what are my options? I am developing an R or Python package with functions for making common plots but this is completely generic; what are my options? I am collaborating with a regional office on an assessment that will be released as an official report from my center; what are my options?
+In 2017, GitHub use was authorized for scientific products: [CIO memo authorizing GitHub use at NOAA](images/CIO-Memo-Use-of-GitHub-at-NOAA.pdf). Subsequently, in 2017, NOAA released official GitHub guidelines [here](images/NOAA-GitHub-Usage-Guidelines.pdf). Some individual centers and offices prepared local GitHub guidelines and SOPs to help their staff interested in using GitHub. See [references](@sec-references). Since 2017, a lot has changed. GitHub use has expanded greatly across NMFS and all the federal agencies ([link](https://nmfs-opensci.github.io/ResourceBook/content/github_in_gov.html#github-in-other-agencies)), and GitHub has become integrated into modern scientific workflow for a wide variety of reasons. The 2017 memo tells us what can be shared on GitHub (scientific products) but there is a need for guidelines that cover and recognize the wide variety of scientific work (and learning) that is done on GitHub and much has changed in the tools provided by GitHub since 2017. Local GitHub SOPs have been developed by individual centers (see [references](@sec-references)) to help their staff. These are very helpful, but not all centers have GitHub SOPs and even with these, staff are often confused by how to follow the guidelines in practice. For example, if I fork a repo in statistics workshop I am in, am I supposed to have a gold standard backup for that? What does it mean to keep NOAA work separate? I was told that private repos are not allowed, but someone at another center said *public* repos are not allowed? I work with confidential fisheries data; what are my options? I am developing an R or Python package with functions for making common plots but this is completely generic; what are my options? I am collaborating with a regional office on an assessment that will be released as an official report from my center; what are my options?
 
 :::{.callout-note}
-When the 2017 memo was written, GitHub was not Fedramp authorized. GitHub Enterprise became Fedramp authorized in 2018 and GitHub use expanded rapidly in other agencies (e.g. GSA and VA) using Enterprise. A number of the NOAA Fisheries science centers have a GitHub Enterprise account. The 2017 memo does not distinguish between GitHub (free) and GitHub Enterprise (paid). You can think of GitHub Enterprise as a secure private GitHub environment that you log into but functions otherwise mostly like the free GitHub once you are inside.
+When the 2017 memo was written, GitHub was not Fedramp authorized. GitHub Enterprise became [Fedramp authorized](https://government.github.com/fedramp-faq) in 2018 and GitHub use expanded rapidly in other agencies (e.g. GSA and VA) using Enterprise. A number of the NOAA Fisheries science centers have a GitHub Enterprise account. The 2017 memo does not distinguish between GitHub (free) and GitHub Enterprise (paid). You can think of GitHub Enterprise as a secure private GitHub environment that you log into but functions otherwise mostly like the free GitHub once you are inside.
 :::
 
 ### Scientific products
