...
- 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
- 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:
- 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.
...