Akraino Upstream Sub-Committee

Meeting logistics:

~~#6 February 22, 2019. 8-9 AM Pacific.~~

...

Agreed: we will create a table / template for each project to fill in their upstream dependencies.
- Srini had an example related to ovs-dpdk (link...)
- Action: Bruce, Andrew, Yong Xin, Wenjing will look into more examples
- We will try to propose a format at the next meeting
- It will be a "release requirement" for each project to fill this template and document clear upstream dependencies
Discussed how multiple projects should coordinate their upstream activities when they have a common upstream community
- projects in Akraino are diverse in their needs. mostly, projects should work with upstream directly.
- projects may be using different versions of the same component
- projects may have different solutions to a common problem to the same upstream - we'd want to coordinate such activities within Akraino.
- may want discuss if projects within Akraino community can agree on a common solution to the same problem
Georg shared his experience of trying to track issues
- it's a relatively simple project with few developers, may not be general best-practice
- federating is difficult,
- JIRA seems to be the implied requirement,
- different projects may have different views
- Action: Invite a larger project (Wenjing)
Akraino presentation to upstream/external organizations (Wenjing)
- Action: create a draft (Wenjing)
- Looking for volunteers to help
Next meeting is moved to March 1

...

...