philips-software / philips-software/cerberus
NFR gating for Cerberus
Open
Nobody has claimed this yet.
Trustful evedence
- Dominant language
- Java
- Stars
- 8
- Forks
- 6
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 1
Description
NFRs have to be defined for Cerberus, and gated with every commit.
@simaos, @aravind666 - can you please add to NFRs that we'd want to automatically gate?
Sample NFR:
- Relative & absolute thresholds of execution time for all functionality provided by Cerberus
Contributor guide
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 only identifies Cerberus and the requirement to gate NFRs on every commit; no files, tests, or CI entry point are named. Start by defining the NFR set with the requested contributors and locating the repository's commit-gating path; done means agreed execution-time relative and absolute thresholds are automatically enforced for every commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100