2020-07-01 TAC Minutes
Attendees & Representation (default sort: member first name)
TAC Members and Project representatives should mark their attendance below
Non-TAC project reps do not count towards meeting quorum
X = Present | P = Proxy (Indicate in the table with @name for @name
Member | Representing | Member | Representing | Member | Representing | |||
---|---|---|---|---|---|---|---|---|
@Abhijit K | ODL | x | @Ed Warnicke | FD.io | @Prabhjot Singh Sethi | TF (incubation) | ||
@Al Morton | OPNFV | x | @Eyal Felstaine | Amdocs | @Ranny Haiby | Samsung | X | |
@Anil Guntupalli | Verizon | @Frank Brockners | Cisco | @Timothy Verrall (Deactivated) | Intel | |||
@FREEMAN, BRIAN D | AT&T | x | @djhunt | IBM | x | @thomas nadeau | Red Hat | |
@cl664y@att.com | ONAP | x | @Lingli Deng | China Mobile | TBD | Juniper | ||
@ChangJin Wang | ZTE | @Marc Fiedler | Deutsche Telekom | @Kalyankumar Asangi | Huawei | |||
@Christian Olrog Atlassian | Ericsson | x | @Mike Lazar | OPX (sandbox) | @Xiaojun Xie | China Telecom | ||
@Davide Cherubini | Vodafone | x | @Morgan Richomme | Orange | x | |||
@David Sauvageau | Bell Canada | @Oguzhan Ceylan | Türk Telekom | x | ||||
@Dhananjay Pavgi | Tech Mahindra | @Olaf Renner | Nokia | TBD | VMware |
LF Staff:
@David McBride
@Jim Baker
@Brandon Wick
@Trishan de Lanerolle
Others:
@Timo Perala
Agenda
Start the Recording
Show the Antitrust Policy
Roll Call
Action Items Review
Agenda Bashing
General Topics
TAC Vice-Chair Election
LFN Developer Recruitment Initiative
LFN Cross-Community Integration, Demos, etc.
Any Other Topics
Minutes
Vice-Chair Election
@Ranny Haiby won the election! Congratulations Ranny and thanks for stepping up.
Developer Recruitment Initiative
From discussions at the virtual event
3 segments
Casual developer
Building a pipeline in academia
Encouraging more corporate contributions
Group formed to focus on this challenge
Key focus: Awareness, Recognition, Tooling
Badging through Acclaim:
Digital badges perhaps for committers and mentorship program participants
@Mike Woster to explore this at the LF level
John Mertic has worked with LF training team to create a badge hierarchy
@FREEMAN, BRIAN D College students/young developers may find this useful for substantiating their skills.
Univ Arizona has a professor lead program
@Ranny Haiby a repo check-in is a clear indicator of contribution and is publicly viewable - no need to over do badging
@djhunt Use LF Insights to trigger a contributor badge?
What is "significant contributor mean"?
@Abhijit K How can outside people interpret these badges?
ISM has a series of badges that lead to a architect level (eg. public speaking, code development...)
@cl664y@att.com Bottleneck is the committers in the process - perhaps a certificate on Linkedin that would be a differentiator in the recruiting process
@FREEMAN, BRIAN D F2f meeting used to have awards for top contrib, etc. - seemed to have dropped off
@Abhijit K What is the cost of these badges? No cost for the badges - staff costs are the real cost
Getting the right criteria uniformly across the projects
Volunteers: @Abhijit K @djhunt @cl664y@att.com
LFN Cross-Community Integration, Demos, etc
@Ranny Haiby How can we have more examples of real LFN cross-project collaboration?
@Brandon Wick ONS events include demo ideas from the community - cross project proposals are ranked higher for inclusion
10 demos in the pipeline for virtual demo formats of upcoming ONES
How can we institutionalize sharing across communities?
Without to much over head - K8s SIGs are an example - eg. Security is a common interest area
@cl664y@att.com Yes - security spans all software and potentially have best practices to share across projects
@Al Morton CNTT RA-1 (Baldy) requirements have 70 unique line items around security
@cl664y@att.com What about the release cadence topic across LFN? This is a tricky topic.
@Morgan Richomme Running and managing the testing process in ONAP are leveraging OPNFV framework - so perhaps this is another area for collaboration
Also includes the process of building the CI toolchains
Dependency management is another area that might be a fruitful area for sharing best practices