...
- 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 Developing an architecture,
- setting Setting simultaneous release dates,
- defining Defining release quality standards,
- defining Defining technical best practices and community norms (including the establishment and maintenance of a Development Process),
- monitoring Monitoring technical progress,
- mediating Mediating technical conflicts between Committers and PTLs,
- organizing Organizing inter-project collaboration,
- coordinating Coordinating technical community engagement with the end-user community
<nowiki>[text in orange below is proposed for TSC consideration, JHB 15Jan22]</nowiki>
4.5.1 Identifying and Recruiting Akraino Local Organizations
The TSC shall be responsible for identifying and recruiting suitable local organizations amenable to cooperation in establishing local centers providing technical and marketing resources in local areas to support Akraino blueprint teams and groups based in those areas. Local areas are typically geographically distinct, characterized by language, time-zone, and international differences, for example the TSC might seek to establish a South America 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:
-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.
-must be a technical organization, with emphasis on open source software and hardware
-must be engaged in sufficient marketing and promotional efforts, including online and social media. Must be able to incorporate Akraino links, material, and blueprint documentation in substantial and appropriate manner ("sufficient", "substantial", "appropriate" need defining)
-associations with academic institutions
-sponsor companies
-support for a range of CPU types, including but not limited to x86, Arm, RISC, SoC (e.g. FPGA with CPU cores)
-provision of a 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
After discussion and evaluation, including Q&A with candidate organization senior / authorized management, the TSC shall vote in order 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 LF Edge 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).
...