KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
Extensions to the SC API do not have to meet all the requirements of the SCAP (Bug 16023)
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Daniel Herring 2016-09-19 07:57:28 PDT
The core SC API must meet all the requirements listed in the SCAP requirements but API extensions do not need to meet the requirements as the extension may not need to be used in a SC environment.
Comment 1 Erik Noreke 2016-09-20 00:19:11 PDT
Changing this to a Guideline as it is not a Khronos process. Non-Khronos APIs can also have extensions.
Comment 2 Erik Noreke 2016-09-20 13:07:25 PDT
Setting QA contact to non-member SCAP mailing list.
Comment 3 Erik Noreke 2016-09-26 07:45:06 PDT
Accepted per call 2016-09-26.
Language to be developed.
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
Use the issue discussion as the starting point; confirm the accepted guideline scope and the distinction between core SC APIs and extensions. Identify the relevant guideline location, then develop the wording and verify it against the stated SCAP requirements.
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
- Needs clarification
- Newbie friendliness
- 25/100