15db71995Sopenharmony_ci# Vulkan Loader Repository Management 25db71995Sopenharmony_ci 35db71995Sopenharmony_ci## **Open Source Project Objectives** 45db71995Sopenharmony_ci 55db71995Sopenharmony_ci- Alignment with the Vulkan Specification and the Loader Specification 65db71995Sopenharmony_ci - [Vulkan Specification](https://github.com/KhronosGroup/Vulkan-Docs) 75db71995Sopenharmony_ci - [Loader Specification](loader/LoaderAndLayerInterface.md) 85db71995Sopenharmony_ci- IHV/ISV Enablement 95db71995Sopenharmony_ci - Updates of loader functionality should be available in a timely fashion 105db71995Sopenharmony_ci - Every effort will be made to be responsive to IHV/ISV issues with the loader 115db71995Sopenharmony_ci- Cross Platform Compatibility 125db71995Sopenharmony_ci - LunarG: Monitor for desktop (Windows and Linux) 135db71995Sopenharmony_ci - Continuous Integration: HW test farms operated by LunarG monitor various hardware/software platforms 145db71995Sopenharmony_ci- Repo Quality 155db71995Sopenharmony_ci - Repo remains in healthy state with all tests passing and good-quality, consistent codebase 165db71995Sopenharmony_ci - Continuous Integration: Along with Github, HW test farms operated by LunarG perform pre-commit cloud testing on pull-requests 175db71995Sopenharmony_ci 185db71995Sopenharmony_ci## **Roles and Definitions** 195db71995Sopenharmony_ci 205db71995Sopenharmony_ci- Contributor, Commenter, User 215db71995Sopenharmony_ci - Submitting contributions, creating issues, or using the contents of the repository 225db71995Sopenharmony_ci- Approver 235db71995Sopenharmony_ci - Experienced project members who have made significant technical contributions 245db71995Sopenharmony_ci - Write control: Approve pull/merge requests (verify submissions vs. acceptance criteria) 255db71995Sopenharmony_ci- Technical Project Leads 265db71995Sopenharmony_ci - Lead the project in terms of versioning, quality assurance, and overarching objectives 275db71995Sopenharmony_ci - Monitor github issues and drive timely resolution 285db71995Sopenharmony_ci - Designate new approvers 295db71995Sopenharmony_ci - Ensure project information such as the Readme, Contributing docs, wiki, etc., kept up-to-date 305db71995Sopenharmony_ci - Act as a facilitator in resolving technical conflicts 315db71995Sopenharmony_ci - Is a point-of-contact for project-related questions 325db71995Sopenharmony_ci 335db71995Sopenharmony_ciThe technical project leads for this repository are: 345db71995Sopenharmony_ci 355db71995Sopenharmony_ci- **Charles Giessen** [charles@lunarg.com](mailto:charles@lunarg.com) 365db71995Sopenharmony_ci- **Mark Young** [marky@lunarg.com](mailto:marky@lunarg.com) 375db71995Sopenharmony_ci 385db71995Sopenharmony_ci## **Acceptance Criteria and Process** 395db71995Sopenharmony_ci 405db71995Sopenharmony_ci- All source code to include Khronos copyright and license (Apache 2.0). 415db71995Sopenharmony_ci - Additional copyrights of contributors appended 425db71995Sopenharmony_ci- Contributions are via pull requests 435db71995Sopenharmony_ci - Project leads will assigning approvers to contributor pull requests 445db71995Sopenharmony_ci - Approvers can self-assign their reviewers 455db71995Sopenharmony_ci - For complex or invasive contributions, Project Leads may request approval from specific reviewers 465db71995Sopenharmony_ci - At least one review approval is required to complete a pull request 475db71995Sopenharmony_ci - The goal is to be responsive to contributors while ensuring acceptance criteria is met and to facilitate their submissions 485db71995Sopenharmony_ci - Approval is dependent upon adherence to the guidelines in [CONTRIBUTING.md](CONTRIBUTING.md), and alignment with repository goals of maintainability, completeness, and quality 495db71995Sopenharmony_ci - Conflicts or questions will ultimately be resolved by the project leads 50