Page History

...

LF Staff: LJ Illuzzi

Agenda

• LF Antitrust Policy

• 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 CCCFOSS Governance project: confidential-computing/governance: Confidential Computing Consortium Governance Documents (github.com)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)
          • EasyCLA- https://docs.linuxfoundation.org/lfx/easycla
        • 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

    • Technical Steering Committee

...

• 2022 LFN Cross-Community Strategic Collaboration Event March 14-15

• 2022 LFN Developer & Testing Forum June

  • 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
  • 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

Action Items

Future Agenda Items

...