Kuadrant / Kuadrant/architecture
kuadrant policy API conventions
Open
- Dominant language
- No language data
- Stars
- 3
- Forks
- 16
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 2
Description
Define a set of conventions to use as part of our APIs
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository's existing architecture documents and API material, then determine the scope of the conventions to define. Done means the API conventions are documented with an agreed scope and clear guidance for their use.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100