...
- Each initial blueprint is encouraged to take on at least two Committers from different companies
- Complete all templates outlined in this document
- A lab with exact configuration required by the blueprint to connect with Akraino CI and demonstrate CD. User should demonstrate either an existing lab or the funding and commitment to build the needed configuration.
- Blueprint is aligned with the Akriano Akraino Edge Stack Charter
- Blueprint code that will be developed and used with Akraino repository should use only Open Source software components either from upstream or Akriano Akraino projects.
- For new blueprints submission, the submitter should review existing blueprints and ensure it is not a duplicate blueprint and explain how the submission differs . The functional fit of an existing blueprint for a use case does not prevent an additional blueprint being submitted.
...
Below is a sample Blueprint template defining an Akriano Akraino species. The full template will be maintained on the Akraino Wiki.
...
- The Validation labs should be able to connect to Akriano Akraino Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Akraino Community on request.
- All Validation labs should be available most of the year for the community use and if the lab is not used for validation more than 3 consecutive months then it will be removed from the community list.
- Hardware and Network configuration used within the Validation labs should be declared and information should be documented in the wiki
- All the Validation labs addition, modifications or removable need to be approved by TSC
- All historic results (minimum of 1 year) of blueprint validation, Applications and VNF testing should be maintained in the wiki.
...
Submission of results to the Akriano Akraino community is optional in case of commercially sensitive applications.
...
A coordinator can act as the ambassador to external upstream communities in communicating the requirements need to be addressed in the upstream community on behalf of Akriano Akraino Feature or Blueprint project. TSC can appoint either Akriano Akraino level or project level coordinators to facilitate upstream coordination work. Coordinators can act as a technical liaison only and cannot represent strategy aspects of the Akriano Akraino which will be handled by TSC.
...
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 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.
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 (eThe 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 From time to time, (a) the TSC may amend or introduce alternative approaches to convene and run subcommittees and (b) decide to disband subcommittees that are no longer active or that no longer have any active members.
4.6.1 Membership
4.6.1.1 Subcommittee Membership Eligibility
...
Each subcommittee may elect a Chair and optionally a Co-Chair who is responsible for leading meetings and representing the subcommittee to the TSCthe subcommittee to the TSC.
4.6.1.3 Subcommittee Chair / Co-Chair Elections
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 The Chair or Co-Chair will be elected by members of the subcommittee as of the date the nomination process starts for the electionsteps 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 the 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
...