2020-08-06 TSC Minutes
- Abhijit K
- Casey Cain
- Daniel De La Rosa
Date & Time
Aug 6, 2020; 10 pm Pacific
Attendees & Representation
TSC Members and Project representatives should mark their attendance below
X = Present | P = Proxy (Indicate below table with @name for @name )
TSC | Managed Projects | |||||||||
@Abhijit K | x | @Faseela K | AAA | BGPCEP | Controller | |||||
@Hema Gopalakrishnan | x | @Tejas Nevrekar | x | DAEXIM | Integration | Genius | X | |||
@JamO Luhrsen | P | @Luis Gomez Palacios | x | InfraUtils | LISP | MD-SAL | ||||
@balaji varadaraju | @Anil Shashikumar Belur | x | OVSDB | X | NetVirt | NetConf | ||||
@Arunprakash D | x | @Robert Varga | Neutron | ODL Parent | YANGtools | |||||
@Venkatrangan Govindarajan | x | OFP | X | JSON-RPC | ServiceUtils | |||||
Proxies: @Daniel De La Rosafor @JamO Luhrsen
Staff:
Others: @Daniel De La Rosa(Release Manager) @Chetan @karthikeyan Krishnan @Manoj Chokka Daya Kamath
Agenda
Start the Recording
Show the Antitrust Policy
Agenda Bashing, Roll Call, Action Items (5 min )
Releases (25 min)
Magnesium SR2 ( release as it is)
Aluminium branch and RC
Sodium SR4
Silicon Schedule
General Topics (25 min)
Infra
Vexhost Costs for last month
Managed Projects
Any Other Topics (5 min)
Minutes
Release
Magnesium SR2 .. Blocker NETCONF-716 was analyzed by JamO and Robert. Bottom line, no objection from TSC members present so please vote on SR2 approval
Aluminium branch and RC.. Branch cutting is done... RC coming according to Al checklist
Sodium SR4... Code freeze by Aug 10, 2020 .. Sodium Checklist
Silicon Schedule has been proposed... TSC will vote on this schedule after cut and lock branch is added
Infra
Bitergia support ending. https://lfanalytics.io is the new metrics platform.
Vexxhost costs
Latest update from today is that they are still trying to confirm some things with Vexxhost around billing. Steve Ira is involved and also looking at improving methods for tracking costs for the projects. @Casey Cain should have an update Aug 7, 2020
Managed Projects
@Abhijit K suggests that all PTLs should update the ODL Project Status.
@Casey Cain talked about marketing efforts that the project could make to get better visibility into deployments and additional use cases.
Engagement with the EUAG to get additional feedback from our users.
Developing for ODL video that could tie together documentation, training and marketing.
Refresh the "Using ODL" video?
Participating in a badging program and promoting end-users to showcase badging so we can get a better idea of trends and where to focus development efforts.
All members have a MAC rep. More engagement for ODL on the MAC and coordination of marketing strategy across the stack could benefit the project.
@Hema Gopalakrishnan mentions the fundamental issue is attracting more developers - so @Casey Cain suggestions is good.
Daya says that while there is some truth in some downstream managed projects being not responsive, it is a 2-way street given where we are in the OpenDaylight project lifecycle rather than just only talking about dependent managed projects. Her point was that the downstreams should have a say on the upstream changes if they introduce a lot of churn in the downstream projects and should have an approval process.
We can leverage the TSC Grievance process on Jira to tag community concerns for the TSC to address.