Introduction

...

The Technical Community consists of a Technical Steering Committee and contributors.

3   The Project

3.1 

...

 Roles 

3.1.1   Contributor

A Contributor is someone who contributes to a project. Contributions could take the form of code, code reviews, Wiki and documentation contributions,  Jira activities or other artifacts. Contributors work with a project’s Committer and the project’s sub-community. A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.

...

• The Committers will be the decision makers on all matters for a project including design, code, patches, and releases for a project.
• Committers are the best available individuals, but usually work full-time on components in active development.
• All project committers information such as name, company, and Contact information should be documented in the wiki under the project.

3.2 

...

 Operations

3.2.1   Project Decisions Making Process

Technical and release decisions for a project should be made by consensus of the Project's Committers.  If consensus cannot be reached, decisions are taken by majority vote of a project’s Committers.  Committers may, by majority vote, delegate (or revoke delegation) of any portion of such decisions to an alternate open, documented (wiki), and traceable decision making process.

...

3.2.2.1   Adding Committers

• Initial Committers for a project will be specified at the Project initiation by the TSC
• Committer rights are earned via contribution and community trust.
• New Committers should have a demonstrable established history of meritocratic contributions.

...

Active Contributors are the cornerstone of the TSC.

Anyone Active Contributors are any Nexoedge community member with fifteen (15) or more measurable contributions as assessed by the TSC during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities.

...

4.5   Responsibilities of the TSC

Subject to the Technical Charter, the TSC is responsible for:

• Defining Nexoedge’s release vehicles (such as a Coordinated Release) that align with the Project’s mission
• Fostering cross-project collaboration
• Serving as Nexoedge's primary technical liaison body with other consortiums and groups
• Developing an architecture
• Setting simultaneous release dates
• Defining release quality standards
• Defining technical best practices and community norms (including the establishment and maintenance of a Development Process)
• Monitoring technical progress
• Mediating technical conflicts between Committers
• Organizing inter-project collaboration
• Coordinating technical community engagement with the end-user community