Updates to FAQ and Licenses based on recent user questions

about/faq.md

@@ -199,21 +199,22 @@ Now that your project is on GitHub, make sure users and contributors can find it
   {% include components/accordion.html title='How do I let people know about my new repo?'  slug='publicize' content=accordionContent %}
 
 {% capture accordionContent %}
-Submit a pull request! This website is a GitHub repo just like any other LLNL open source project. News is housed in the [`_posts` directory](https://github.com/LLNL/llnl.github.io/tree/main/_posts), and templates are found in the [LLNL/.github repo](https://github.com/LLNL/.github). See [Contributing Guidelines](../contribute) for more information.
+Yes, you can give external contributors Write access to your GitHub repo. Anyone with Admin access to your repo can enable this: Settings > Collaborators > Manage access > Add people > enter their username and select.
+
+If you don't already have Admin access to your repo, contact [[email protected]](mailto:[email protected]) to request it.
 
-Before contributing, please contact [[email protected]](mailto:[email protected]) with your idea or if you have questions about whether your proposed content requires the LLNL review and release process.
 {% endcapture %}
   {% assign accordionContent = accordionContent | markdownify %}
-  {% include components/accordion.html title='How do I contribute news or other content to this website?'  slug='contribute-here' content=accordionContent %}
+  {% include components/accordion.html title='Can non-LLNL developers/collaborators contribute to my project?'  slug='collaborators' content=accordionContent %}
 
 {% capture accordionContent %}
-Yes, you can give external contributors Write access to your GitHub repo. Anyone with Admin access to your repo can enable this: Settings > Collaborators > Manage access > Add people > enter their username and select.
+If the owner/admin of a repo leaves the project, another team member(s) with a GitHub account must take over the Admin role.
 
-If you don't already have Admin access to your repo, contact [[email protected]](mailto:[email protected]) to request it.
+If you need help re-assigning permissions in your repo, contact [[email protected]](mailto:[email protected]) to confirm the user's departure and successor(s).
 
 {% endcapture %}
   {% assign accordionContent = accordionContent | markdownify %}
-  {% include components/accordion.html title='Can non-LLNL developers/collaborators contribute to my project?'  slug='collaborators' content=accordionContent %}
+  {% include components/accordion.html title='How do I change ownership of a specific repo?'  slug='new-owner' content=accordionContent %}
 
 {% capture accordionContent %}
 
@@ -277,5 +278,13 @@ Refer to individual projects for their requirements on accepting contributions.
   {% assign accordionContent = accordionContent | markdownify %}
   {% include components/accordion.html title='How do I contribute to an LLNL repo?'  slug='contribute-repo' content=accordionContent %}
 
+{% capture accordionContent %}
+Submit a pull request! This website is a GitHub repo just like any other LLNL open source project. News is housed in the [`_posts` directory](https://github.com/LLNL/llnl.github.io/tree/main/_posts), and templates are found in the [LLNL/.github repo](https://github.com/LLNL/.github). See [Contributing Guidelines](../contribute) for more information.
+
+Before contributing, please contact [[email protected]](mailto:[email protected]) with your idea or if you have questions about whether your proposed content requires the LLNL review and release process.
+{% endcapture %}
+  {% assign accordionContent = accordionContent | markdownify %}
+  {% include components/accordion.html title='How do I contribute news or other content to this website?'  slug='contribute-here' content=accordionContent %}
+
 </div>
 <!-- END: Accordions -->

about/licenses/index.md

@@ -158,6 +158,12 @@ The Spack example mentions a [`COPYRIGHT`](https://github.com/spack/spack/blob/d
 
 For more information on using SPDX in your code, see the [SPDX website](https://spdx.org/licenses/).
 
+### Source file license headers
+
+Header requirements can vary depending on the chosen license. Most open source licenses (e.g., Apache 2.0, MIT,  GPL) do not strictly require license headers in each file, while others (e.g., LGPL-3.0) do. In any case, brief headers are recommended to ensure that whichever license you choose is also included with the source code, especially if those files are re-used.
+
+For example, visit the [Spack](https://github.com/spack/spack) or [Flux](https://github.com/flux-framework) projects to see how the different source files are labeled with headers depending on the license.
+
 ### Developer Certificate of Origin (DCO)
 
 As mentioned above, the default assumption for open source projects is ["inbound license = outbound license"](https://opensource.guide/legal/), i.e., contributors provide their code under the same license under which the code is distributed. If this is not enough assurance for your project, you may use the [Developer Certificate of Origin (DCO)](https://developercertificate.org/) with your project.