Difference between revisions of "Starlingx/Initial Governance"
(Created page with "== StarlingX Initial Governance == The initial draft of this document with feedback from the reviewers [https://etherpad.openstack.org/p/stx-governance is on this Etherpad]....") |
|||
| Line 15: | Line 15: | ||
==== Core Reviewer ==== | ==== Core Reviewer ==== | ||
A Core Reviewer for a sub-project has the responsibility to review the changes proposed to the sub-project and help ensure that approved changes are inline with the sub-project's scope and the overall direction of the project and meet the minimum quality requirements of the project. Core Reviewers have the ability to approve code to be merged into the StarlingX repositories. Core Reviewers are active Contributors and participants in the project. Core Reviewers for a sub-project are appointed by the sub-project Technical Lead with input from other StarlingX Core Reviewers. Contributors can become Core Reviewers for multiple sub-projects. | A Core Reviewer for a sub-project has the responsibility to review the changes proposed to the sub-project and help ensure that approved changes are inline with the sub-project's scope and the overall direction of the project and meet the minimum quality requirements of the project. Core Reviewers have the ability to approve code to be merged into the StarlingX repositories. Core Reviewers are active Contributors and participants in the project. Core Reviewers for a sub-project are appointed by the sub-project Technical Lead with input from other StarlingX Core Reviewers. Contributors can become Core Reviewers for multiple sub-projects. | ||
| + | |||
| + | ==== Technical Lead ==== | ||
| + | A Technical Lead in StarlingX is a Core Reviewer who has additional responsibility for the overall technical direction of one or more of the sub-projects, under the guidance and direction of the Technical Steering Committee. Technical Leads are responsible for resolving disagreements between the sub-project's Contributors and Core Reviewers. The initial Technical Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis. | ||
| + | |||
| + | ==== Project Lead ==== | ||
| + | A Project Lead in StarlingX is responsible for the sub-project's work item list and facilitating the four opens within the sub-project. The Project Lead works with the Technical Lead to break down large work items for the team into Stories and Tasks. The Project Lead guides Contributors to the work items most needed by the sub-project, as defined by the Project Priorities established by the Technical Steering Committee. The initial Project Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis. | ||
| + | |||
| + | The same person can become a Technical Lead and Project Lead for a StarlingX sub-project. | ||
| + | |||
| + | ==== Technical Steering Committee ==== | ||
| + | The Technical Steering Committee is responsible for architectural decisions and making final decisions if sub-project Core Reviewers, Technical Leads or Project Leads disagree. It defines the overall project architecture and sets the overall Project Priorities. It will be comprised of 9 members who will be appointed at Launch but fully elected by the Contributors within the first year. | ||
| + | |||
| + | The initial Technical Steering Committee members will be: | ||
| + | * Brent Rowsell and Ian Jolliffe from Wind River | ||
| + | * Dean Troyer and Saul Wold from Intel | ||
| + | * TBD... | ||
| + | We are actively recruiting for additional Technical Steering Committee members | ||
Revision as of 20:38, 17 August 2018
Contents
StarlingX Initial Governance
The initial draft of this document with feedback from the reviewers is on this Etherpad.
Introduction
The StarlingX project is governed according to the "four opens", which are open source, open design, open development and open community. Technical decisions are made by technical contributors, technical leaders and by a respresentative Technical Steering Committee. Our community is committed to diversity, openness, and encouraging new contributors and leaders to rise up.
The StarlingX project is both a development project and an integration project. It includes new services that provide important features and combines them with components from many other Open Source projects into a complete Edge Cloud solution. To help manage the complexity of the project, we have divided the project up into several sub-projects, each with project and technical leadership, to help distribute the overall work and to acknowledge in the community that there are multiple ways to contribute to the project. The sub-project lifecycle is managed by the project's Technical Steering Committee who approve the creation of new sub-projects and the retirement of sub-projects that are no longer active.
Project Roles
StarlingX defines the following roles for the project.
Contributors
A Contributor to StarlingX is someone who has made a Contribution to the project within the last 12 months. Contributions can include merged code, test or document submissions, or serving in a leadership role as defined below. The project's Technical Steering Committee can grant Contributor status for other contributions at its discretion. Contributors are eligible to vote in Technical Steering Committee elections.
Core Reviewer
A Core Reviewer for a sub-project has the responsibility to review the changes proposed to the sub-project and help ensure that approved changes are inline with the sub-project's scope and the overall direction of the project and meet the minimum quality requirements of the project. Core Reviewers have the ability to approve code to be merged into the StarlingX repositories. Core Reviewers are active Contributors and participants in the project. Core Reviewers for a sub-project are appointed by the sub-project Technical Lead with input from other StarlingX Core Reviewers. Contributors can become Core Reviewers for multiple sub-projects.
Technical Lead
A Technical Lead in StarlingX is a Core Reviewer who has additional responsibility for the overall technical direction of one or more of the sub-projects, under the guidance and direction of the Technical Steering Committee. Technical Leads are responsible for resolving disagreements between the sub-project's Contributors and Core Reviewers. The initial Technical Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis.
Project Lead
A Project Lead in StarlingX is responsible for the sub-project's work item list and facilitating the four opens within the sub-project. The Project Lead works with the Technical Lead to break down large work items for the team into Stories and Tasks. The Project Lead guides Contributors to the work items most needed by the sub-project, as defined by the Project Priorities established by the Technical Steering Committee. The initial Project Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis.
The same person can become a Technical Lead and Project Lead for a StarlingX sub-project.
Technical Steering Committee
The Technical Steering Committee is responsible for architectural decisions and making final decisions if sub-project Core Reviewers, Technical Leads or Project Leads disagree. It defines the overall project architecture and sets the overall Project Priorities. It will be comprised of 9 members who will be appointed at Launch but fully elected by the Contributors within the first year.
The initial Technical Steering Committee members will be:
- Brent Rowsell and Ian Jolliffe from Wind River
- Dean Troyer and Saul Wold from Intel
- TBD...
We are actively recruiting for additional Technical Steering Committee members
