-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fy23 redesign #616
Closed
Closed
Fy23 redesign #616
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
2b627cf
Update faq.md
cyndy-llnl 1b87d47
Update index.md
cyndy-llnl c1c4802
Update index.md
cyndy-llnl d409d2e
Update index.md
cyndy-llnl 63c1b21
Update dependencies.md
cyndy-llnl 4a379ba
Update popular-repos.md
cyndy-llnl 7073b10
Update contributors.md
cyndy-llnl e4785f0
Update index.md
cyndy-llnl 583dcd8
Update pages/about/faq.md
cyndy-llnl f253def
Update pages/about/index.md
cyndy-llnl f9367bc
title case on FAQ
hauten c94f822
add more S&TR links
hauten d07b7ff
remove 2020
hauten File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,62 +1,76 @@ | ||
| --- | ||
| title: About the LLNL Software Portal | ||
| layout: info | ||
| description: Learn about LLNL's open source software and why we're committed to creating open source codes whenever feasible. | ||
| permalink: /about/ | ||
| --- | ||
|
|
||
| ## {{ page.title }} | ||
| # {{ page.title }} | ||
| {: .page-header .no_toc} | ||
|
|
||
| * Table of Contents | ||
| {:toc} | ||
|
|
||
| ### Collaboration Fuels Our Culture | ||
| ## Collaboration Fuels Our Culture | ||
|
|
||
| Welcome to the Lawrence Livermore National Laboratory (LLNL) software portal — a hub for open source software (OSS) produced at the Lab. | ||
|
|
||
| <!-- Can the video display on-page at a small size and open to a lightbox for larger viewing? Or are we able to increase the width on this, esp. in a responsive way? (I'm open to ideas/options.) --> | ||
| <div class="videoPlayer"> | ||
| <iframe style="left-align" width="400" height="225" src="https://www.youtube.com/embed/nTxMn1NWHQU" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> | ||
| </div> | ||
|
|
||
| Welcome to the Lawrence Livermore National Laboratory (LLNL) software portal—a hub for open source software (OSS) produced at the Lab. | ||
|
|
||
| LLNL developers create and evolve software on a daily basis. Some of this software is used only internally; other components are licensed for use by external partners and collaborators; and still other software is released and actively developed out in the open on software-hosting platforms. This website is the gateway to all of it. | ||
|
|
||
| LLNL is a Department of Energy (DOE) institution, so we abide by the Federal Source Code Policy* that guides release of open source software (OSS). And not just because we have to but because we *want* to. Long before GitHub was founded, [we started releasing software](https://software.llnl.gov/visualize/) for public use and collaboration. | ||
|
|
||
| We often work with other national labs, universities, and industry partners. Working on these projects is a lot easier when we can share code directly. For example, building the next generation of supercomputers requires collaboration. The [Exascale Computing Project (ECP)](https://www.exascaleproject.org) uses OSS to develop the exascale ecosystem of apps, analytics, infrastructure, and so much more. The ECP is tackling a huge range of scientific areas, like precision medicine and nuclear physics. Future breakthroughs will likely owe some debt to the best practices and accelerated development made possible by OSS. | ||
|
|
||
| One of the great things about a large government organization is that we’re not motivated by profit. “The greater good” might sound like a cliché, but it’s true. LLNL’s national security mission governs our work, so our OSS portfolio of apps, libraries, compilers, and other tools support that mission. This includes everything from monitoring the performance of our supercomputers to making multiphysics codes run more smoothly. | ||
|
|
||
| Case in point: The DOE’s [Advanced Simulation and Computing (ASC) Program](https://asc.llnl.gov) leverages OSS to build, field, and integrate Linux clusters into production service at our [Livermore Computing supercomputing center](https://hpc.llnl.gov/). ASC is responsible for developing computer simulation capabilities that analyze and predict the performance, safety, and effectiveness of the nation’s nuclear stockpile. In other words, the stakes are high for ensuring our code is accurate. ASC leadership joined the DOE’s Office of Advanced Scientific Computing Research to establish a policy of using and distributing OSS to achieve the Program’s goals. With OSS, we can develop quickly and choose the best solutions. | ||
|
|
||
| This portal abounds with examples of projects that have found a home in the open source community. Access is key, which is why we jumped at the chance to index our software on [Code.gov](https://code.gov). You’ll find our work in the DOE [repo list](https://code.gov/#!/browse-projects?agencies=DOE), and we invite you to browse our projects on [GitHub](https://github.com/LLNL). | ||
|
|
||
| * The original policy memorandum is no longer available online. See [The People's Code blog post](https://www.cio.gov/2016/08/11/peoples-code.html) and [the archived policy on GitHub](https://github.com/WhiteHouse/source-code-policy). | ||
|
|
||
| ### Learn More About OSS at LLNL | ||
|
|
||
| * This website's [News Archive](/news/archive/) | ||
| * 18F guest post: [The Case for Open Source Software](https://18f.gsa.gov/2018/07/12/the-case-for-open-source-software/) | ||
| * *Science & Technology Review* coverage | ||
| * Cover story: [Ambassadors of Code](https://str.llnl.gov/2018-01/lee) | ||
| * [Commentary by Bruce Hendrickson](https://str.llnl.gov/2018-01/comjan18), LLNL Computing associate director | ||
| * Video (3:04): [Ambassadors of Code](https://youtu.be/nTxMn1NWHQU) | ||
| * Highlight: [Visualization Software Stands the Test of Time](https://str.llnl.gov/2021-05/brugger) | ||
| * Code.gov blog post: [OSS Spotlight: Lawrence Livermore National Laboratory and ZFS on Linux](https://medium.com/codedotgov/oss-spotlight-lawrence-livermore-national-laboratory-and-zfs-on-linux-6596fca6e5f6) | ||
| * LLNL news: [Spack, A Lab-Developed ‘App Store for Supercomputers,’ becoming Standard-Bearer](https://www.llnl.gov/news/spack-lab-developed-app-store-supercomputers-becoming-standard-bearer) | ||
| * 2020 LLNL Computing Virtual Expo materials | ||
| * Releasing Open Source Software at the Lab ([poster](https://computing.llnl.gov/sites/default/files/COMP_Poster_OSS.pdf)) | ||
| * Video: Open Source at LLNL (11:31) ([YouTube](https://youtu.be/kL4wIYhNVxE)) ([slides](https://computing.llnl.gov/sites/default/files/2020CompExpo_Open_Source.pdf)) | ||
|
|
||
| ### Other References | ||
|
|
||
| * [18F Handbook: GitHub](https://handbook.18f.gov/github/) | ||
| * [fisma-ready/github: Controls necessary for Federal use of GitHub](https://github.com/fisma-ready/github) | ||
| * [Guidance for Agency Use of Third-Party Websites and Applications](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/memoranda_2010/m10-23.pdf) | ||
| * [18F Blog: Facts about Publishing Open Source Code](https://18f.gsa.gov/2016/08/08/facts-about-publishing-open-source-code-in-government/) | ||
|
|
||
| ### Contact | ||
|
|
||
| Check out our [FAQ](faq). If you have other questions or would like to request a private repository, please don't hesitate to contact [Ian Lee](mailto:[email protected]) or our [LLNL GitHub admins](mailto:[email protected]). You can also find us on our mailing list: [[email protected]](mailto:[email protected]). | ||
| LLNL developers create and evolve software on a daily basis. Some of this software is used only internally, other components are licensed for use by external partners and collaborators, and still other software is released and actively developed out in the open on software-hosting platforms. This website is the gateway to all of it. | ||
|
|
||
| LLNL is a [Department of Energy (DOE)](https://www.energy.gov/national-laboratories){% raw %}{% endraw %} institution, so we abide by the [Federal Source Code Policy](https://www.energy.gov/articles/doe-federal-source-code-policy)*{% raw %}{% endraw %} that guides release of open source software (OSS). And not just because we have to but because we *want* to. Long before GitHub was founded, [we started releasing software](https://software.llnl.gov/visualize/) for public use and collaboration. | ||
|
|
||
| We often work with other national labs, universities, and industry partners. Working on these projects is a lot easier when we can share code directly. The [Exascale Computing Project (ECP)](https://www.exascaleproject.org){% raw %}{% endraw %} uses OSS to develop the exascale ecosystem of apps, analytics, infrastructure, and so much more. Future breakthroughs will likely owe some debt to the best practices and accelerated development made possible by OSS. | ||
|
|
||
| One of the great things about a large government organization is that we're not motivated by profit. "The greater good" might sound like a cliché, but it's true. LLNL's national security mission governs our work, so our OSS portfolio of apps, libraries, compilers, and other tools support that mission. This includes everything from monitoring the performance of our supercomputers to making multiphysics codes run more smoothly. | ||
|
|
||
| Case in point: The DOE's [Advanced Simulation and Computing (ASC) Program](https://asc.llnl.gov) leverages OSS to build, field, and integrate Linux clusters into production service at our [Livermore Computing high-performance computing center](https://hpc.llnl.gov/). ASC is responsible for developing computer simulation capabilities that analyze and predict the performance, safety, and effectiveness of the nation's nuclear stockpile. In other words, the stakes are high for ensuring our code is accurate. With OSS, we can develop quickly and choose the best solutions. | ||
|
|
||
| This portal abounds with examples of projects that have found a home in the open source community. Access is key, which is why we jumped at the chance to index our software on [Code.gov](https://code.gov){% raw %}{% endraw %}. You'll find our work in the DOE [repo list](https://code.gov/#!/browse-projects?agencies=DOE){% raw %}{% endraw %}, and we invite you to browse our projects on [GitHub](https://github.com/LLNL){% raw %}{% endraw %}. | ||
|
|
||
| \* The original policy memorandum is no longer available online. For details, please see | ||
| <!-- START: Buttons --> | ||
| * [The People's Code Blog Post](https://www.cio.gov/2016/08/11/peoples-code.html){% raw %}{% endraw %} | ||
| * [The Archived Policy on GitHub](https://github.com/WhiteHouse/source-code-policy){% raw %}{% endraw %} | ||
| <!-- END: Buttons --> | ||
|
|
||
| ## Learn More About OSS at LLNL | ||
| <!-- START: Quicklinks boxes --> | ||
| * [LLNL Software News Archive](/news/archive/) | ||
| * [The Case for Open Source Software](https://18f.gsa.gov/2018/07/12/the-case-for-open-source-software/){% raw %}{% endraw %} | ||
| * [OSS Spotlight: LLNL and ZFS on Linux](https://medium.com/codedotgov/oss-spotlight-lawrence-livermore-national-laboratory-and-zfs-on-linux-6596fca6e5f6){% raw %}{% endraw %} | ||
| * [Spack, A Lab-Developed ‘App Store for Supercomputers,’ becoming Standard-Bearer](https://www.llnl.gov/news/spack-lab-developed-app-store-supercomputers-becoming-standard-bearer){% raw %}{% endraw %} | ||
| <!-- END: Quicklinks boxes --> | ||
|
|
||
| ### *Science & Technology Review* coverage | ||
| <!-- START: Quicklinks boxes --> | ||
| * [Ambassadors of Code (cover story)](https://str.llnl.gov/2018-01/lee) | ||
| * [Ambassadors of Code (video, 3:04)](https://youtu.be/nTxMn1NWHQU){% raw %}{% endraw %} | ||
| * [Commentary by Bruce Hendrickson](https://str.llnl.gov/2018-01/comjan18), LLNL Computing associate director | ||
| * [Visualization Software Stands the Test of Time](https://str.llnl.gov/2021-05/brugger) | ||
| <!-- END: Quicklinks boxes --> | ||
|
|
||
| ### 2020 LLNL Computing Virtual Expo Materials | ||
| <!-- START: Quicklinks boxes --> | ||
| * [Releasing Open Source Software at the Lab (poster)](https://computing.llnl.gov/sites/default/files/COMP_Poster_OSS.pdf) | ||
| * [Open Source at LLNL (video, 11:31)](https://youtu.be/kL4wIYhNVxE){% raw %}{% endraw %} | ||
| * [Open Source at LLNL (slides)](https://computing.llnl.gov/sites/default/files/2020CompExpo_Open_Source.pdf) | ||
| <!-- END: Quicklinks boxes --> | ||
|
|
||
| ## Other Resources | ||
| <!-- START: Quicklinks boxes --> | ||
| * [18F Handbook: GitHub](https://handbook.18f.gov/github/){% raw %}{% endraw %} | ||
| * [Controls necessary for Federal Use of GitHub](https://github.com/fisma-ready/github){% raw %}{% endraw %} | ||
| * [Guidance for Agency Use of Third-Party Websites and Applications](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/memoranda_2010/m10-23.pdf){% raw %}{% endraw %} | ||
| * [Facts about Publishing Open Source Code](https://18f.gsa.gov/2016/08/08/facts-about-publishing-open-source-code-in-government/){% raw %}{% endraw %} | ||
| <!-- END: Quicklinks boxes --> | ||
|
|
||
| ## Contact | ||
| For more information, check out our [FAQ](faq). If you have other questions or would like to request a private repository, please don't hesitate to contact [Ian Lee](mailto:[email protected]) or our [LLNL GitHub admins](mailto:[email protected]). You can also find us on our mailing list: [[email protected]](mailto:[email protected]). | ||
cyndy-llnl marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| <div class="text-center"> | ||
| <a href="https://twitter.com/LLNL_OpenSource" class="twitter-follow-button" data-show-count="true">Follow @LLNL_OpenSource</a> | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cyndy-llnl What do you think about removing "2020" from this heading so it doesn't seem so outdated? The assets from the Expo are fairly evergreen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hauten That works! I'm a fan of including the date if something is "of a moment," but when it's evergreen, you'll entice more folks to use it when an older date is omitted.
One thing: Is that a change you're making or that you'd like me to make? Happy to participate however you prefer!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cyndy-llnl I made the change just now, thx