E4S-Project / E4S-Project/E4S-Project.github.io
Add prominent links to E4S-release spack environment files
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I get asked for links to these pretty regularly. We probably need to include some notes or examples on how to modify the base environments for use outside of our default container targets.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating the E4S-release Spack environment files and the website page where links belong; done means prominent links are available along with notes or examples for modifying the base environments outside the default container targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100