TSC Meeting Zoom link
Meeting Recording
Meeting Chat File
Attendees & Representation. Please add your name to the attendance table below.
Attendees | |
Name | Company |
Daniel Havey | Microsoft |
Wipro | |
Wipro | |
VK Group | |
Balachandra Kamat | Wipro |
Dave Thaler | Microsoft |
Jason Niesz | |
Santhosh Fernandes | |
Steve Laughman | Microsoft |
Satya Pradhan | |
Karan Dalal | Walmart |
Dhivya R | Walmart |
Rishabh Gupta | |
Ragalahari | |
Kanthi Pavuluri | |
LF Staff: LJ Illuzzi
Agenda
Meeting note taker
Welcome to new attendees
Upcoming Events
- CFP for Cloud Native eBPF Day Europe (CFP deadline February 21st)
General Topics (cover as needed)
Use Cases
Roadmap
Project structure
Governance
- Dave's list of topics:
- Which parts of governance are per-repo vs independent of repo? "governance" repo for repo-independent governance? (comparable from FOSS Governance project: http://fossgovernance.org)
- Licenses under which contributions can be accepted
- Code of Conduct and reporting process
- Security vulnerability reporting process (comparables: governance/security-response-policies.md at main · confidential-computing/governance (github.com), ebpf-for-windows/SECURITY.md at master · microsoft/ebpf-for-windows (github.com))
- LFx Security- https://docs.linuxfoundation.org/lfx/security/overview
- Process for adding repos under github.com/l3af-project
- Process for selecting maintainers of each repo
- DCO (fyi: CLA vs. DCO: What's the difference? | Opensource.com)
- Diversity & inclusion policies (comparable: governance/diversity-and-inclusion-policies.md at main · confidential-computing/governance (github.com))
- Issue triage process
- Jason's list
- Review feedback on https://github.com/l3af-project/l3afd/pull/16
- Review feedback on https://github.com/l3af-project/l3af-arch/pull/10
- Dave's list of topics:
Technical Steering Committee
Minutes/Updates
Upcoming LFN Events-
- In Person (and virtual) in Porto Portugal, June 13 - 16
- Registration is open: Registration Page
- CFP for Cloud Native eBPF Day Europe (CFP deadline February 21st)
- Governance:
- Do we need a contributing file per repo or can we have 1 for everting
- Do we need a governance repo?
- Vicky: Governance repo. It's easier to find things if they are all in one place.
- Dave: CCC has a governance repo
- Jason: Governance repo can contain "all the standard stuff" no need for duplication of common items
- Vicky: Inheritance from the governance repo and a contrib.md in each repo
- Do we need a governance repo?
- Technical charter
- Governance repo can allow more licenses than what each repo does now
- Repos use different license's now
- Any OSI license should be considered (we don't ay that now)
- MIT, BSD, etc.
- Allows the TSC to make this decision.
- Must be noted in minutes and documented in repo
- KAran - current wording is fine. Don't need to add list of licenses
- Dave: bullet 1 says that license must be GPL only (XP root code)
- Would have to use the clause and TSC vote to override the current list to use MIT
- Karan: Change of wording is approved, but not implemented yet.
- Louis: Will dig the change out of legal
- Karan: after change then list will be 'recommended' license
- Dave: Argue that we don't recommend GPL
- Danie: Agree
- Dave: IANL, eBPF programs are usable on multiple platforms?
- If it is GPL then it is not usable on Windows
- Would have to write a new XDP root with a permissive license
- Karan: How to avoid GPL?
- Dependency mapping on 3rd party then the code has to be GPL
- Vicky: Create governance repo and have dialog there.
- How do these things integrate with the kernel. Aggregation or dependence
- Karan: There are ways to avoid GPL by avoiding certain code or functions
- Governance repo can allow more licenses than what each repo does now
- Do we need a contributing file per repo or can we have 1 for everting