annotate services by their use case and/or organ
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 8
- Avg merge
- 44m
- Merged PRs (30d)
- 1
Description
Per request
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 file, test, or entry point is named. Start by inspecting the VHP4Safety Cloud Service Catalog and the existing service records to determine how use cases or organs are represented. Done means the requested annotations are defined and applied consistently, but the issue does not specify the target services or expected categories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100