Page Comparison

...

Attendees & Representation. Please add your name to the attendance table below.

LF Staff: LJ Illuzzi

Agenda

• LF Antitrust Policy

• Meeting note taker

• Welcome to new attendees

• R1 Finale Release Discussion
  • Do we stick with v1.0.0 or something like v .5.0.0
• OpenSSF scorecard: https://bestpractices.coreinfrastructure.org/en/projects/6075

• PR Review (as needed)

  • Use same version of go on windows as on ubuntu in CI/CD by dthaler · Pull Request #143 · l3af-project/l3afd (github.com)
• Project updates for Nov 14 LFN Governing Board Meeting
• Website (l3af.io) updates for R1 release
• Tracking l3af interest over time (>14 days) https://github.com/marketplace/actions/github-repo-stats

• General Topics (cover as needed)

  • Use Cases

  • Roadmap

Minutes/Updates

• R1 Release Status
  • Update Go, better docs- confirm if this is in alignment with Nov 2 release.
  • Target R1 release date is Nov 2
  • R1 Release MAC
  • PR Review if needed
  • Project updates for Nov 14 LFN Governing Board Meeting
    • Draft Slides
    • Project representative at the meeting
  • Website (l3af.io) support
    • Choices are: 
      • DIY (Gitlab/Netlify, etc.)
      • Open ticket with LF Creative Services (CS) team and specify changes
    • How does ONAP's website work? ONAP opens a CS ticket
    • Proposed Next Steps to update l3af.io:
      1. Create a wiki page or google doc detailing changes (community effort)
      2. Open CS ticket (LJ)
      3. Invite assigned CS team member to design session(s) to talk through changes

  Action Items

  PRs for 1.0 release

  • https://github.com/l3af-project/l3afd/pull/128
  • https://github.com/l3af-project/l3afd/pull/120
  • https://github.com/l3af-project/l3afd/pull/114
  • https://github.com/l3af-project/l3af-arch/pull/44
    • Not for R1: Match the Go versions between Windows and Linux
    • Added: Production Deployment Guide
    • toDo: Create new PR for version
      • Planning to re-write the way L3AFd loads eBPF programs in the next release.
      • Should this be R0.9 instead of R1?
      • REST APIs will not change, but how programs are written will change dramatically.
      • Call it 1.0 (Because it is already being used in production) and the next release will be 2.0 
        • Marketplace will not start until R2.0 because of the breaking change in eBPF program APIs
      • 2 PRs left
        • doc link and fix version
      • Media package delivered to the MAC
        • Teaser for new R1 blog (non-blocking)
        • Jason Nieszto create bullet list of R1 release facts for blog teaser
      • Update OpenSSF scorecard
        • AI: Jason to create an account there and send Dave the userid number
        • AI: Dave to grant Jason edit privileges on the badge
        • AI: Jason to then update the answers to the remaining questions in the badge
      • Governing Board meeting
        • Updated slides
          • fix logo on front slide
          • add something about "what we are doing well"
            • Roadmapping
            • Release Management
            • OpenSSF badging
        • Ajayto present slides
          
          • Slides will be presented by host, you will be provided a copy
    • Updates for website
      • Get ready before media blasts go out
    • How do we track interest in L3AF over time
      • Monitoring interest after releases and announcments
      • Visitors from GitHub?
        • Only a 14 day history
      • Walk through LFX insights tool
        • Much more data than Github
    • Use Github discussions if you want to keep history
      • Slack loses history in 90 days

  Action Items

  Future Agenda Items