...

Induction of new project needs to be brought as a proposal to the TSC.

Project Roles

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.

Committers

All committers from participating modules are listed as project committers.

...

Each project/module should strive for diversity of Committers representing different organizations as well as individuals. However Committer promotions are based on meritocracy and prioritize project/module contributions above other considerations.

Adding Committers

• Initial Committers for a project will be specified at project creation 
• Committer rights for a project are earned via contribution and community trust. Committers for a project select and vote for new Committers for that project.
• New Committers for a project should have a demonstrable established history of meritocratic contributions.

Removing Committers

• A Committer may voluntarily resign from a project by making a public request to the PTL to resign (via the project email list and cc to tsc@lists.tungsten.io ).
• A Committer for a project who is disruptive, or has been inactive on that project for an extended period (e.g., six or more months) may have his or her Committer status revoked by the project’s Project Technical Leader or by 2/3 supermajority vote of the project’s committers.
• The Project Technical Leader is responsible for informing the Technical Steering Committee (TSC) of any committers who are removed or resigned via the email list: tsc@lists.tungsten.io.

Former committers removed for reasons other than being disruptive may be listed as ‘Emeritus Committers’.  That title expresses gratitude for their service but conveys none of the privileges of being a Committer.

Project Technical Leader

A project is required to elect a Project Technical Leader (“PTL”). The PTL acts as the de facto spokesperson for the project.

...

* For faster turn arround time, Contributors can choose to split/organise the Code changes in a way to submit separate reviews for individual modules

Release Management

Checkpoints Submitted On-Time

Release manager and PTLs will coordinate to ensure work submissions in projects meets the milestones set as per TSC approved release plans.

Projects must submit the information required for release checkpoints on-time corresponding to associated milestones. Submissions must be correct and adequate, as judged by the release manager and TSC. Inadequate or missing submissions will result in grievance.

will propose milestones and associate a timeline to the delivery for a release. PTLs will coordinate with Release Manager to track progress of deliverables proposed and accepted corresponding to their Projects.

PTLs and Release Manager should operate on consensus for following

delays with respect to achieving certain milestones of a project, and propose a plan for any of the following action:

• Dropping of Drop a blueprint out of a release in the event of unacceptable delays or due to bad quality of work delivered
• Propose a delay in the scheduled release date to TSC in event of time need to:
• Accomodate a feature delivery important for the release
Achieve reasonably release stablitywork plan to cover on the missed milestone dates
• Propose to accomodate delay needed to:
  • Achieve important feature deliver
  • Achieve reasonable release stability

Documentation

Projects are required to produce a user guide, developer guide and release notes for each release.