...
The Akraino Edge Stack Technical mission to focus on following areas
- 1. Create end to end configuration for a particular Edge Use case which is complete, tested and production deployable meeting the use case characteristics {Integration Projects - Blueprints}.
Production deployable means the blueprint has passed unit and integration testing and meets the blueprint’s use case characteristics. - 2. Develop projects to support such end to end configuration. Leverage upstream community work as much as possible to avoid duplication. {Feature Projects}
- 3. Work with broader edge communities to standardize edge apis {Upstream Open Source Community Coordination - For example, Socialization, so community tools and Blueprints can interoperate. This work can be a combination of an upstream collaboration and development within the Akraino community [i.e. a feature project]}
- 4. Encourage Vendors and other communities to validate Edge applications and Virtual Network Functions on top of Akraino blueprints {Validation Project - ensures the working of a Blueprint}
...
Community members will use a template for use case characteristics, blueprint family and blueprint approved by the TSC to describe the hardware, software, deployment configurations, workload characteristics when requesting the creation or modification of an Akraino Blueprint. The requestor should demonstrate the following aspects to the TSC:
- Each initial blueprint is encouraged 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 with the Akriano Edge Stack Charter
- Blueprint code that will be will be developed and used with Akraino repository should use only Open Source software components either from upstream or Akriano 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.
...
4 Technical Steering Committee
...
4.1 Akraino Community Active Contributors
...
The primary responsibility of the TSC Chair and Co-Chair are to represent the technical community in communications with the LF Akraino Edge Stack Fund of The Linux Foundation and to be responsible for:
Leading TSC meetings;
This responsibility may be delegated to another TSC Member (in such case, this is to be informed via the TSC email list)
Representing the technical community to external organizations.
These responsibilities may be delegated to another member of the technical community.
Lead the TSC in the execution of the TSCs responsibilities (section 4.3).
4.3.3 Coordinators
4.3.3.1 Coordinator Description
...
The decision to close the coordination area is created by a TSC decision (according to the TSC voting rules). Once a coordination area is updated, the coordination area will be removed from the Akraino Wiki.
4.4 TSC Operations
4.4.1 TSC Decision Making Process
...
There are no limits to the number of terms an individual can serve.
4.4.3 TSC Election Mechanics
...