| Table of Contents |
|---|
...
4.5 Responsibilities of the TSC
Subject to the Technical Charter, the TSC is responsible for:
- Defining Akraino’s release vehicles (such as a Coordinated Release) that align with the Project’s mission
- Fostering cross-project collaboration
- Serving as Akraino’s primary technical liaison body with other consortiums and groups
- Developing an architecture
- Setting simultaneous release dates
- Defining release quality standards
- Defining technical best practices and community norms (including the establishment and maintenance of a Development Process)
- Monitoring technical progress
- Mediating technical conflicts between Committers and PTLs
- Organizing inter-project collaboration
- Coordinating technical community engagement with the end-user community
Identifying and Recruiting Akraino Localized Organizations
4.5.1 Identifying and Recruiting Akraino Localized Organizations
The TSC shall be responsible for identifying and recruiting suitable organizations amenable to cooperation in establishing centers providing technical and marketing resources in geographically distinct areas to support Akraino blueprint teams and groups based in those areas. Such "localized" areas are typically characterized by language, time-zone, and international differences, for example the TSC might seek to establish a South America center, an Africa center, a Shenzhen center, etc.
When an organization has been identified, TSC members shall meet to discuss and evaluate the organization to determine its suitability, based on the following technical, marketing, and operational criteria:
- The organization must present a public website with goals and mission statement indicating a non-profit, open, collaborative nature, preferably with .org domain suffix. Examples include foundations, consortiums, development communities, user communities, etc.
- The organization must be a technical organization, with emphasis on open source software and hardware
- The organization must be engaged in sufficient marketing and promotional efforts, including online and social media. The organization must be able to incorporate Akraino web links, material, and blueprint documentation in substantial, appropriate, and prominent manner
- The organization may be associated with academic institutions
- The organization may have sponsor companies
- The organization must demonstrate support, or an acceptable plan of support, for a range of CPU types, including but not limited to x86, Arm, RISC, SoC (e.g. FPGA with CPU cores)
- The organization may provide working area(s), including WiFi or other Internet capable of online video/audio collaboration. Server and other development hardware resources are preferred but not required
- The organization must agree to comply with Policy and Operational Procedures as listed on the Akraino Regional Communities page
During the discussion and evaluation phase, the TSC may at its option nominate and vote to approve an Akraino representative to act as "point person" to work with the candidate organization's senior / authorized management to resolve concerns, negotiate objectives and requirements, gather facts and data, and otherwise act on behalf of the TSC. The point person may be a TSC member, subcommittee chair or co-chair, or other. The point person may recruit others to help with the effort. As one example, the TSC might designate the "Outreach Subcommitee" chair as the point person, who then might recruit helpers from other subcommittees or blueprint projects.
After the discussion and evaluation phase, including updates from the point person if one has been designated, the TSC shall vote to decide whether to formally engage with the candidate organization. Should the vote succeed, the TSC shall present the candidate organization, along with its evaluation results, to Akraino's parent Linux Foundation management for further, formal action.
4.6 TSC Subcommittees
The TSC, at its discretion, may establish subcommittees to assist the TSC with its responsibilities and provide expert guidance in technical subject areas (e.g., architecture or security).
...
The Chair or Co-Chair will be elected by members of the subcommittee as of the date the nomination process starts for the election.
4.6.1.3.1 Subcommittee Interim elections
In case a subcommittee Chair or Co-Chair steps down or isno longer able to perform subcommittee duties (for example, moved to a different company, no longer active in Akraino, etc), an interim election may be called by the TSC. The term of the subcommittee Chair or Co-Chair elected as a result of the interim election can be up to next full election.
Interim elections shall otherwise follow all the same procedures and use the same voting schemes as yearly elections.
4.6.1.4 Subcommittee Voter Eligibility
...