Date

Attendees



Agenda

Minutes

  • Action items:
    • Will: haven't started working with devstack, currently going through docs
      • docs census: Docs Census what else do we need to fill out
      • while moving repos to LF gerrit, trying to understand user/ contributor experience
        • document process and make sure everything is in place
    • Sukhdev: documentation for 5.0 should work for 5.1
      • sent api docs to docs@
      • Jira changes still on hold
      • PTL on hold
    • Edward: has list of gerrit patches
    • Darien: New blog post in progress
    • Casey: need a quote for pricings for merch
    • Alex: not on call, come back for nightlies
  • Technical Work Stream doodle sent out
  • 5.1
    • adhoc process for making tungsten release from juniper release
    • pono will lead a team for documenting a tungsten release
      • alex levine, will stevens, sukhdev, paul carver, joseph, edward
    • will become a more reproducible process from a clean manifest
    • standing action item
    • sukhdev: process on opencontrail site, juniper says it's valid
      • if community can reproduce, then it's working
      • then we can move to tungsten namespace
    • randy: no clear way to know what's in the release (opencontrail)
      • no differentiation between opencontrail and tungsten at the moment
      • document not just process but where can we get a definitive list of what's in the release
      • work with sukhdev to redact and resend the list of differences
    • keep on the dev@ list
    • edward: developer sendbox
      • tag for 5.1
    • sukhdev: ask edward about cutting releases
      • delayed but no known bugs
    • vicky: email the marketing team about what you want in blog post about 5.1 release
    • darien: there's a blog posting schedule and I receive emails for marketing
  • ARB
    • sukhdev: how to seperate out projects into ui, controlplane, etc
      • setup a PTL for this
      • each PTL owns their respective code, or each repo gets a PTL?
      • hand off ownership to PTLs and getting rid of ARB
      • preemptive to dissolve ARB without another structure in place
    • vicky: how to open up so we can  start getting contributions
    • joseph: need people to lead
    • vicky: probably juniper folks to bootstrap projects, mentor the community
    • Joseph Gasparakis : volunteers to lead vrouter
    • Valentin Sinitsyn Prabhjot Singh Sethi Rudra Dubey  volunteer as well
    • casey: should migrate to this model
    • joseph: import for LFN TAC
      • moving to arb with mostly juniper to PTLs with different affiliations is a Good Thing
    • vicky: we're all in agreement
    • sukhdev: let people step up to lead the PTLs
      • there will be some uneasiness from Juniper people about handing over control to PTLs
      • suggets: have community start pushing code into PTL sections to show commitment
    • casey: agrees, PTLs should be submitting code
      • gives them technical expertise and weight in what to approve and how to guide advancement
      • transistion time, balance of juniper folks involvement with mentoring and growing PTLs
    • prabhjot: starts with juniper folks leading PTLs and then transition to active parts of community
    • will: how to work with juniper to lead open source development at first
      • figure out how to wane control to community
      • how to we work together to fulfill needs
    • casey: setup PTLs via blueprints and then figure out how leads
      • define committers, PTL, could list contributors
      • how to leverage outreach events and venues and have a place to point interested folks
      • will take a while to setup
      • set some plans and then bring proposal plans to TSC
    • sukhdev: within juniper they are moving towards monthly releases, next in june
      • community should be ready to address that
      • how do we want to deal with this?
    • vicky: reiterates, and points out the release team will be instrumental
    • casey: take release plans and figure out how to do a tungsten release
    • vicky: will still need to rely on juniper for the time being
    • sukhdev: all the work juniper is doing is upstream (less proprietary features)
    • edward: faster release schedule has been mentioned so good time to start thinking about it
    • casey: monthly is fast and could be good
      • can we get a release plan from juniper? and see how community responds
      • since we haven't developed a release plan, we might be able to leverage or at least feel it out
    • vicky: if this is going upstream, there should be public blueprints
      • can work with sukhdev to make sure blueprints are getting done appropriately
      • as TF, we have to find and document the process extensively
      • before we get to a release process, we'll need to have a good workflow for these things
    • casey: this should let the ARB/ PTL members train to become better
    • randy: juniper has resources for QA
      • TF cannot get to monthly releases until CI/ testing is working
    • casey: need to get the TWS meeting going because we don't have enough time for these issues
    • vicky: governance issue, so we need to have this go through the community
    • casey: lets move this to email
  • developing a legal subcommittee
    • review licensing to make sure we're within charter
  • accurately capturing minutes
    • need to have a check and sign off of minutes
    • post minutes within 24h of meeting
    • please be more active on writing minutes and not relying on primary note takes
  • CLA
    • CLA tool is active and required for gerrit.tungsten.io
    • not on for gerrit for opencontrails
    • vicky: what is the process for submitting CLAs?
      • tons of questions about CLA
      • cannot use automated CLA process yet
    • casey: let's move to email
    • vicky: more hands doesn't help at the moment
      • need to get CLA stuff sorted for opencontrail
    • casey: can only do manual process at the moment
    • vicky: undefined/ undocumented and need to work on this
      • too many open questions
    • will: old system doesn't necessarily work
      • new system has some bugs, can share when we've got time
      • will work with casey about smoothing bugs
      • old and new are both borked
    • casey: forwarding CLA emails internally, even though not responding on threads
      • continue discussion on lists
  • missed items moved to next week

Action items