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