`singularity::experimental`
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
As singularity-eos moves towards production, we should perhaps differentiate production-ready capabilities, with capabilities we're experimenting with. A namespace like singularity::experimental might work nicely.
Thanks to @chadmeyer for the suggestion.
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
The issue names no files, tests, or entry points. Start by surveying how existing capabilities and namespaces are organized in singularity-eos, then determine the production-versus-experimental boundary and define what completion for a singularity::experimental namespace would mean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100