...
Attendees
Jim Baker Ulrich Kleber Mark Beierl Scot Steele Georg Kunz Heather Kirksey Ildiko Vancsa Tom Van Pelt Al Morton Toshiyasu Wakayama Phil Robb sunku ranganath Trevor Cooper Bob Monkman Jonne Soininen William Diego Maza David McBride
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 15min | Interim TSC election plans |
|
| 10min | Conformance projects - what they deliver | ||
| 5min | Business Coordination Function | Followup on scope | |
| 20min | Release artifact discuss and agree | ||
| AOB? |
Notes
Interim Election Plans
- CNTT wishes that there is a good balance between operators and vendors
- Plan: CNTT wait until OPNFV elected Anuket TSC members are named, then add additional operators (5) and suppliers (2)
- Participating members of CNTT have reviewed and agreed to this approach
- OPNFV elections complete
- CNTT nominating complete
- Push TSC chair and subsequent milestones out to the following Tuesday Jim Baker
Business Coordination Function
- Over all organizational structure suggests the Business Coordination function is a part of the TSC and should be managed by the TSC
- Either a separate workgroup or TSC members driving an initiative
- Consensus: Keep it simple - they are necessary functions, TSC makes the decisions on how to accomplish the goals
Release Artifact Review and Decision
- What are RC and RI specifically?
- Is RI a recipe OR a running instance?
- A RI is NOT a platform - it is a recipe that allows anyone to follow the recipe and end up with a conformant implementation
- RI = a set of artifacts that allow others to build conformant instances
- RI is NOT a production ready instance
- RI is dependent on RC for completion of the testing process
- Additional work required to map the work onto projects/staffing and RA2 variants