xref: /aosp_15_r20/external/vulkan-validation-layers/GOVERNANCE.md (revision b7893ccf7851cd6a48cc5a1e965257d8a5cdcc70)
1*b7893ccfSSadaf Ebrahimi## Vulkan Validation Layers Repository Management
2*b7893ccfSSadaf Ebrahimi
3*b7893ccfSSadaf Ebrahimi# **Open Source Project � Objectives**
4*b7893ccfSSadaf Ebrahimi
5*b7893ccfSSadaf Ebrahimi* Alignment with the Vulkan Specification
6*b7893ccfSSadaf Ebrahimi  - The goal is for validation layer behavior to enforce the vulkan specification on applications. Questions on specification
7*b7893ccfSSadaf Ebrahimiinterpretations may require consulting with the Khronos Vulkan Workgroup for resolution
8*b7893ccfSSadaf Ebrahimi    - [Core Specification](https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html)
9*b7893ccfSSadaf Ebrahimi    - [Header Files](https://www.khronos.org/registry/vulkan/#headers)
10*b7893ccfSSadaf Ebrahimi    - [SDK Resources](https://vulkan.lunarg.com)
11*b7893ccfSSadaf Ebrahimi* ISV Enablement
12*b7893ccfSSadaf Ebrahimi  - Updates of validation layer functionality should be available in a timely fashion
13*b7893ccfSSadaf Ebrahimi  - Every effort will be made to be responsive to ISV issues with validation layers
14*b7893ccfSSadaf Ebrahimi* Cross Platform Compatibility
15*b7893ccfSSadaf Ebrahimi  - Google and LunarG collaboration:
16*b7893ccfSSadaf Ebrahimi    - Google: Monitor for Android
17*b7893ccfSSadaf Ebrahimi    - LunarG: Monitor for desktop (Windows and Linux)
18*b7893ccfSSadaf Ebrahimi    - Continuous Integration: HW test farms operated by Google and LunarG monitor various hardware/software platforms
19*b7893ccfSSadaf Ebrahimi* Repo Quality
20*b7893ccfSSadaf Ebrahimi  - Repo remains in healthy state with all tests passing and good-quality, consistent codebase
21*b7893ccfSSadaf Ebrahimi  - Continuous Integration: Along with Github, HW test farms operated by Google and LunarG perform pre-commit cloud testing
22*b7893ccfSSadaf Ebrahimion pull-requests
23*b7893ccfSSadaf Ebrahimi
24*b7893ccfSSadaf Ebrahimi# **Roles and Definitions**
25*b7893ccfSSadaf Ebrahimi* Contributor, Commenter, User
26*b7893ccfSSadaf Ebrahimi  - Submitting contributions, creating issues, or using the contents of the repository
27*b7893ccfSSadaf Ebrahimi* Approver
28*b7893ccfSSadaf Ebrahimi  - Experienced project members who have made significant technical contributions
29*b7893ccfSSadaf Ebrahimi  - Write control: Approve pull/merge requests (verify submissions vs. acceptance criteria)
30*b7893ccfSSadaf Ebrahimi* Technical Project Leads
31*b7893ccfSSadaf Ebrahimi  - Lead the project in terms of versioning, quality assurance, and overarching objectives
32*b7893ccfSSadaf Ebrahimi  - Monitor github issues and drive timely resolution
33*b7893ccfSSadaf Ebrahimi  - Designate new approvers
34*b7893ccfSSadaf Ebrahimi  - Ensure project information such as the Readme, Contributing docs, wiki, etc., kept up-to-date
35*b7893ccfSSadaf Ebrahimi  - Act as a facilitator in resolving technical conflicts
36*b7893ccfSSadaf Ebrahimi  - Is a point-of-contact for project-related questions
37*b7893ccfSSadaf Ebrahimi
38*b7893ccfSSadaf EbrahimiThe technical project leads for this repository are:
39*b7893ccfSSadaf Ebrahimi* **Mark Lobodzinski** [[email protected]](mailto:[email protected])
40*b7893ccfSSadaf Ebrahimi* **Tobin Ehlis** [[email protected]](mailto:[email protected])
41*b7893ccfSSadaf Ebrahimi
42*b7893ccfSSadaf Ebrahimi# **Acceptance Criteria and Process**
43*b7893ccfSSadaf Ebrahimi  - All source code to include Khronos copyright and license (Apache 2.0).
44*b7893ccfSSadaf Ebrahimi    - Additional copyrights of contributors appended
45*b7893ccfSSadaf Ebrahimi  - Contributions are via pull requests
46*b7893ccfSSadaf Ebrahimi    - Project leads will assigning approvers to contributor pull requests
47*b7893ccfSSadaf Ebrahimi    - Approvers can self-assign their reviewers
48*b7893ccfSSadaf Ebrahimi    - For complex or invasive contributions, Project Leads may request approval from specific reviewers
49*b7893ccfSSadaf Ebrahimi    - At least one review approval is required to complete a pull request
50*b7893ccfSSadaf Ebrahimi    - The goal is to be responsive to contributors while ensuring acceptance criteria is met and to facilitate their submissions
51*b7893ccfSSadaf Ebrahimi    - Approval is dependent upon adherence to the guidelines in [CONTRIBUTING.md](CONTRIBUTING.md), and alignment with
52*b7893ccfSSadaf Ebrahimirepository goals of maintainability, completeness, and quality
53*b7893ccfSSadaf Ebrahimi    - Conflicts or questions will ultimately be resolved by the project leads
54