DEPRECATED: This page was used to build consensus during TSC composition discussions.

Preface:

The TSC’s business responsibilities as a governing body for ONAP are described in Section 2(h) of the ONAP Project a Series of LF Projects, LLC Technical Charter:

h. Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include:

i. coordinating the technical direction of the Project;
ii. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
iii. organizing sub-projects and removing projects;
iv. creating sub-committees or working groups to focus on cross-project technical issues and requirements;
v. appointing representatives to work with other open source or open standards communities;
vi. establishing community norms, workflows, issuing releases, and security issue reporting policies;
vii. establishing, maintaining and modifying policies to ensure the integrity, vetting and security of the ONAP Project code base; and
viii. subject to the requirements of Section 7 of this Charter, approving and implementing policies and processes for contributing (to be published onap.org) and coordinating with the Series Manager to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;}
ix. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
x. coordinating any marketing, events, or communications regarding the Project with the LF Projects Manager or their designee.

These mimic what you will find in virtually every other LFN Project Charter and were set up by the Linux Foundation to leave room for each TSC to do what they feel needs to be done to conduct business for their own specific Project. The point of the TSC 2.0 discussion is not to alter, diminish or add to the responsibilities already found in the Charter. It is instead about how to ensure those making ONAP's day-to-day business decisions are the best qualified to scale and lead a broad technical community that is reshaping face of telecommunications on a global scale

Suggested approach is to divide this up into the following logical steps

Establish what specifically should be expected from any TSC member in the context of their being on the TSC
Establish what part ( if any )the role of a company's participation, contribution, deployment, or usage of ONAP should play in the composition of the TSC
Address the operational aspects such as elections and how to handle attendance, vacancies, etc.
Vote on the actual language and amendments to the ONAP Technical Community Document
Kick off the TSC election

Expectation of TSC Members

Community leadership
- TSC members are expected to take on some manner of community leadership responsibility besides simply sitting on the TSC. Examples includes but are not limited to:
  - Project PTL
  - Subcommittee Officer
  - TSC work group or taskforce leader
  - Community Coordinator (TAC, MAC, SPC, SDO or other OSS)
  - LFN (or other OSS) Whitepaper editor/contributor
  - LFN (or other OSS) Event organizer
- Serving in such a leadership capacity is not a pre-requisite for eligibility to run for a seat on the TSC.
- The community leadership responsibility must serve the needs of the ONAP community as a whole and not the exclusive needs of the member's company
Active participation - In addition to voting, TSC members are expected to actively take part in fulfilling the TSC responsibilities defined in the charter. That may include (but is not limited to):
- Bringing forth proposals for improvements in the software or software development process.
- Proposing solutions to issues raised by the community and brought to TSC decision.
- Pulling in experts from their company or organization to help address issues brought before the TSC.
- Advocating for the adoption and use of ONAP by their company/organization or other OSS projects and use cases. Advocacy may take the form of public posts (blogs, articles, white papers, etc.) or direct communication with the relevant parties.
- Participate/Promote cross open source community opportunities i.e. 5G Super Blueprint, etc.
- Create a white paper explaining added value of ONAP
Dedicated work time
- TSC members are expected to dedicate at least 3-4 hours weekly on average to TSC work. If a potential member is not able to commit to such time investment, they should be discouraged from running as TSC candidates.

The Role of a Company in Determining the Composition of the TSC

All seats on the TSC are open to any qualified candidates irrespective of company name, size, type of business, industry vertical or LFN membership status
There shall be no provisions allowing a company to appoint members to the TSC
Companies should refrain from selecting "a candidate" to run while preventing other Active Community Member employees from also running.
There shall be no more than one person from the same or group of related companies as currently described in Section 4.4.1.4 of the Community Document on the TSC
- “Related Company” shall mean any entity (Company-A) which controls or is controlled by another entity (Company-B) or which, together, is under the common control of a third party (Company-C), in each case where such control results from ownership, either directly or indirectly, of more than fifty percent of the voting securities or membership interests of the entity in question; and “Related Companies” are entities that are each a Related Company as described above.
- Exceptions to the "one person" rule:
  - A sitting TSC member impacted by Merger & Acquisition activity may retain their seat until the next annual TSC election cycle
  - A sitting TSC member that may change their place of employment. In this situation a special election is to be held and the incumbent TSC member can run for the seat. If elected they may retain their seat until the next annual TSC election cycle.

Operational Aspects Related to TSC Composition

"Active Community Members" as currently defined in Section 4.1.1.1 of the Community Document shall remain as the qualifications for both candidacy and voting for the TSC
- Anyone from the ONAP community with twenty (20) or more measurable contributions during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities
- If an individual does not meet the Active Community Member criteria, they can be granted that status if they can demonstrate that a combination of both LFN and ONAP contributions meets the criteria for measurable contributions under this section. It is the responsibility of the community member to do so by providing that documentation to the onap-tsc list. Additional sources of information such as work with SDOs or other open source communities may also be taken into consideration at the full discretion of the TSC.
There shall be up to 25 seats on the TSC.
TSC members may assign a proxy that may both attend meetings and vote (either live or electronically) on their behalf
The TSC must be pre-notified of any proxy in advance of the meeting
- All proxies must be time-bound
- No "self-announced" proxies at the time of the meeting will be permitted
If any TSC member, without sending a proxy, misses any two consecutive regular TSC meetings, such member shall not be counted for quorum or voting purposes until she or he next attends.
If any TSC member, without sending a proxy, misses any four consecutive regular TSC meetings, that member shall be removed from the TSC automatically unless the TSC approves an exception.
In the event of the resignation or removal of a TSC member the TSC may either call for a new election, or choose to leave the seat open until the next scheduled election, by a simple majority vote of the TSC
TSC members that do not engage in a "community leadership" or "active participation" role after being given ample opportunity may be removed as a member of the TSC by a simple majority vote.
The regular TSC elections shall occur annually in May

Browser not supported