KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
EGL
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Even one of the simplest of standards, EGL, is too complex for feasible implementation in the safety environment, where complexity refers to: number of API functions, types of their parameters, state-machine model and object-management model. This complexity only increases when even some of the extensions are added to the core-standard specification.
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
The issue body is the available starting point; no repository file, test, or entry point is named. Clarify which safety-environment change is expected for EGL and define completion criteria for the API, parameter, state-machine, and object-management complexity 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
- 20/100