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:
...
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
| Info |
|---|
Suggested approach is to divide this up into the following logical steps
|
Expectation of TSC Members
...
- 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.
...