| Info |
|---|
DRAFT |
| Table of Contents |
|---|
...
The list of important properties of the OpenXT Project Platform that are subject to governance supervision is maintained in a separate document: OpenXT Platform Properties.
OpenXT Layers
The OpenXT Project software utilizes the composable software layers provided by OpenEmbedded in order to isolate customizations, such as hardware, GUI environments and distributions.
All OpenXT Layers are subject to OpenXT Governance as described in this document. The OpenXT layers Layers create modular governance contexts for specific use cases, target markets and operational models, with a narrowed set of stakeholders and increased prospects of stakeholder alignment within individual layers.
The OpenXT Project applies the layering mechanism to support the coexistence of multiple use cases within a common codebase. This enables maximization of collaboration on common components while also enabling non-aligned stakeholder requirements to be satisfied in different layers.
...
- Switching display and input (surfman) layer <<To do: Link to the RFC for this layer here when ready>>
- Compositing display and input (Qt) layer <<To do: Link to the RFC for this layer here when ready>>
...
Derivative works
Derivative works use the OpenXT Platform and ... <<Text required here>>
Project Meetings
The OpenXT Project shall hold monthly telephone Community Conference Call meetings on the third Thursday of every month at 4pm UTC. If the date of the call falls upon a legal holiday then an alternative date, not more than two weeks distant from the intended calculated date , may be appointed instead by the Governance Boardselected.
The Community Conference Call is public and open to all members of the OpenXT community.
Notification of the Community Conference Call shall should be sent by a member of the Governance Board to the mailing list at a time between one week and one day prior to the call. The Notification shall include the timing of the call and the telephone access information for the call.
The Community Call will be hosted by a member of the OpenXT community.
Project Governance Board
The OpenXT Project shall have a Governance Board of seven appointed individuals.
...
Board members accept the responsibility of actively building consensus within the community.
Changes to the Board
The legitimacy of the Board and its decisions depends upon the composition of the Board reflecting the balance of stakeholders within the OpenXT Project.
A Board member may retire from their position on the Board by expressing a request to do so to the Governance Board. Such a request should preferably be issued by cryptographically signed email to the Project mailing list.
...
A Board member will be required to step down from their position in any of the following circumstances:
...
if the remainder of the Board unanimously agrees that sufficient cause exists for removal, acting in the best interests of the Project.
Vacancies on the Board shall be filled by a public vote of the majority of the remaining members of the Board. The vote shall follow the Voting Process described in this document and shall commence at the time the vacancy occurs.
The legitimacy of the Board and its decisions depends upon the composition of the Board reflecting the balance of stakeholders within the OpenXT Project.
Change within the Project
...
A vote will be required if it becomes clear that consensus on the decision resolution cannot be achieved between members of the Governance Board in the Board Consensus Building Process. The purpose of the Voting Process is to document the positions of the Board members and record the concluding decision for the proposal.
...
Voting will be done with an indication of "yay", "nay" or "abstain" by each Board member. Each Board member is granted a single vote. Any member can elect to vote "abstain" without a requirement to provide a reason. Absent board members who do not provide a vote will be recorded as "absent". Voting may not be done by proxy. The records of all the votes will be recorded in the JIRA ticket.
...
Attend the monthly Community Call.
Provide guidance and direction to project contributors on how to address challenges presented by proposed changes in order to seek solutions that are acceptable and desirable to all the project stakeholders and in alignment with the OpenXT Project Purpose.
Participate in the Board Consensus Building Process, the Voting Process and in Changes to the Board.
- Ensure that OpenXT Project decisions are recorded.
For each Community Call at least one member of the Governance Board shall:
...
Repository Maintainers, Source Code Committers
Repository Maintainers, Source Code Committers are the gatekeepers, managers and performers of updates to the canonical copies of the project software source code.
Appointment of Repository Maintainers, Source Code Committers
Picked by rouletteTBD. (FIXME)
Changes to Repository Maintainers, Source Code Committers
Replaced by rouletteTBD. (FIXME)
Responsibilities of Repository Maintainers, Source Code Committers
...
- Collect and understand the perspectives of affected stakeholders.
- Send a written RFC to the OpenXT mailing list.
- Discuss the RFC on the monthly OpenXT community call.
- Publish revised RFC to the mailing list.
- Finalize and accept the RFC on the next community call.
- If consensus exists on the list/call, one Board member (other than the proposer) records the decision and consensus in a JIRA ticket.
- If no consensus on the list/call, the proposer escalates the decision to the Board via JIRA ticket. The Board uses the "Board Consensus Building Process" defined in this document.
...