KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
EGL: finite-state-machine model
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Finite state machines defined by EGL, OpenGL and other standards have relatively large number of states and transitions between them, making it complex to properly specify them in safety-critical terms and to test them sufficiently, especially for higher levels of safety, such as car-industry ASIL C and D.
For reference, general issue "EGL" is defined as issue #35.
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 by reading the general EGL issue, #35, and then review this issue's request for a finite-state-machine model. The issue does not name files, tests, or a concrete change, so the scope and an observable definition of done need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100