Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Akraino Upstream Sub-Committee

Meeting logistics:


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

Moved to:

#6 March 1, 2019. 8-9 AM Pacific.

Agenda:

  • Open
  • Review upstream dependency template
  • Invite a project to introduce their upstream issue tracking practice
  • Review Akraino presentation draft
  • Invite Kubernetes edge WG for a follow-up

#5 February 8, 2019. 8-9 AM Pacific.

Attendance:

  • Wenjing Chu (chair)
  • Andrew Wilkinson (ericsson)
  • Bruce Jones (intel)
  • Georg Kunz (ericsson)
  • Yong Xin (radisys)
  • Tina Tsou (arm)

Minutes:

  • 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 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

Minutes:

  • b
    • 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

Agenda:

  • Continue on a good practice of working among projects with the same upstream community (Andrew)
  • Examples of tracking work with upstream projects (Georg?)
  • Drafting Akraino overview slide deck with upstream relationships
  • Alternate to chair next meeting

...

  • Wenjing Chu (chair/huawei)

  • Tina

  • Yong Xin
  • Wenhui
  • Bruce?

Minutes:

  • The draft scope of work in the wiki reviewed.
  • Has consensus on the single point of liaison role, but there is confusion as where the work of best practice policy should go.
  • Suggested that coordinators don't have to be one per project, they probably share the same coordinator for the same upstream.
  • Agreed to revise it and present to TSC in its next meeting.

...

  1. Recap of the TSC F2F in Santa Clara, Dec 6-7, 2018.

    1. https://wiki.akraino.org/pages/viewpage.action?pageId=6128947

  2. Time reconfirmed: Fridays of every other week from 8:00-9:00 Pacific.

    1. Dec 28 cancelled

    2. Next meeting is Jan 12, 2019

  3. SubCommittee work streams

    1. Blueprint series - invite for deep dive in each blueprint’s upstream projects

    2. JIRA best practice with upstream

      1. https://www.atlassian.com/blogarchives/jira-5-remote-issue-linking?_ga=2.155033144.1034039649.1544751473-664009150.1542144963

      2. Experimentations and learn. How does at&t doing with airship? Call for volunteer to find out more.

    3. Upstream project landscape infographics. Call for volunteers.

      1. https://docs.google.com/presentation/d/1Ccgdnk0f8X76iKxx12D4pYu764VR-3IoocG1wHx1ZPg/edit#slide=id.p

    4. Related organizations / communities liaison

      1. Exchange series - invite for introduction/liaison presentations

      2. E.g. TIP, ONAP, Openstack, K8S, EdgeX, ONF…

      3. Prepare a slide deck for Akraino presentation to these groups

    5. Other documentation

  4. AOB

...