Akraino Best Practice for Upstream Dependencies
Akraino community consists of three types of projects, Feature, Integration (aka Blueprint) and Validation.
...
- The Upstream Sub-committee should make the above information accessible by appropriate format of documentation.
- Produce a document format that all projects can contribute into a single document.
- Produce a summary that can be shared with other communities.
Single Point of Liaison
The other role that TSC assigns to the Upstream Sub-committee is to be the single point of liaison to other communities and organizations. These may include upstream projects who want to know more about Akraino overall (rather than a specific project within Akraino), or larger open source communities and other industry or standard organizations interested in interactions with Akraino beyond a single project and in more stable long term arrangement.
Initially, the Sub-committee plan to initiate a series of talks by relevant organizations that overlap with Akraino's mission. For example, Openstack Edge working group, Kubernetes edge working group, ONF, ONAP edge working group, EdgeX (and other LF Edge projects), TIP, and ...
The Ambassador
We recommend that the Upstream Sub-committee act as an ambassador (See community technical document description of this role), but meetings can take place in any community meeting slots as appropriate, e.g. in the community meetings, in TSC meetings, but can also be hold during this Sub-committee meetings. All such meetings material should be consolidated into one place in the Upstream Sub-committee wiki and documentation for easy search and access.
...