KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
Approaches: safety-environment constraints
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Define constraints of the safety environment. The constraints should be simple and generic in the initial phase. For example, a rough description of the allowed complexity of a finite state machine mentioned in issue #38 would be sufficient, an approximate definition of non-safe, initialization and safety phases and similar.
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
Start with issue #38 and the repository’s existing safety-critical guidelines to identify the finite-state-machine example and the safety-environment concepts it depends on. Done means the initial guidance defines simple, generic constraints, including approximate complexity and non-safe, initialization, and safety phases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100