This is a website that attempts to offer new ways to understand the variety of open source subsurface geoscience code available for use that people think is valuable.
The basic idea is that within smaller communities it can be difficult to find applicable open source code for your problem. A lot of what code you use is based on word of mouth and stumbling upon someone else’s repository working on similar problems. This can be inefficient.
Awesome lists are a great way to source code specific to a domain, problem, or use case that others think is “awesome”, but they are limited in that they don’t show connections between projects or directly show you how popularity of projects might have changed over time.
If it was easier to understand what code is being most used, what code uses similar dependencies, and what projects are attracting the same groups of contributers, community participants might be nudged into more impactful contributions more often.
You can understand more about the value & vision of this project by checking out this slide presentation on Observablehq.com.
It was initially created as part of the Transform 21’ hackathon put on by The Software Underground or SWUNG.
SWUNG, or the Software Underground, is a digital first non-profit society focused on code & rocks. To quote their front page:
The place for scientists and engineers that love rocks and computers. The Software Underground is a grass-roots community of digital subsurface professionals. We are academic and applied geologists, geophysicists, engineers, and others — Welcome!
This site was created by taking a fork of the Lawrence Livermore National Laboratory’s open source software catalog and changing a bunch of stuff to make it useful for SWUNG.
Check out the README.
Check out the instructions in this issue.
Also, the plan is to eventually automatically pull in any repository that on github.com that is a part of AWESOME OPEN GEOSCIENCE awesome list. Awesome lists are a standardized way to share code that many people think is useful to a particular problem, domain, or use case.
Check out the issue board . There will be a separate contributions instructions soonish.