KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
EGL: extensions
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Standard-development model, in which there is core specification supplemented by extensions, may not be ideal for the safety environment. Main reasons are nature of safety-certification process and compactness of the implementation.
This issue is general. Titles of specific instances of this issue will be prefixed with the title of this issue.
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 #40 and the safety-certification and implementation-size concerns it names. Determine how extensions should be handled in a safety-critical specification model, then record a concrete guideline decision and identify any specific follow-up instances that need separate issues.
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