Project Decisions Making Process
...
TSC is responsible for setting technical TF goals, identifying use cases, setting release guidelines and milestones. It will work with PTLs to develop and maintain project high level and detailed architecture. Project Committers will work within this technical and release guidance to deliver individual projects.
Within the project, Committers should operate by general consensus. If consensus cannot be reached within a reasonable timeframe, 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, and traceable decision making process.
Spec/Blueprint Submission
...
- A registered JIRA EPIC ticket reflecting requested blueprint/feature in the backlog of the TF Jira Feature project with following data
- Meaning full name and description
- Target release
- Assignee will be Blueprint/Feature Lead - person responsible for delivering all needed documentation, explanations, and also responsible for proper reflecting of achieved milestones of requested change in the TF Jira Feature project
- Detailed information as per Blueprint template to be submitted for review at tf-specs with TF Jira ID
- A suppliment optional detailed document, that talks about the design or other aspects enabling community members and reviewer to obtain better understand the proposal
- Feature Lead can mark the blueprint ready for review by moving Jira ticket to Selected for
TSCdiscussion column in the Kanban board of the TF Jira Feature project.
...