You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Meeting Recording

Meeting Chat File

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


Attendees

Name

Company

Daniel Havey

Microsoft
































LF Staff: LJ Illuzzi David McBride

Agenda

  • LF Antitrust Policy

  • Meeting note taker

  • Welcome to new attendees

  • Release Management Consultation - Hour 2
  • LFN 2023 Budget

  • General Topics (cover as needed)

    • Use Cases

    • Roadmap

    • Project structure

      • Governance

      • Technical Steering Committee

  • Review PRs

Minutes/Updates

Release Management Consultation -

  • 2 hours in total are needed to complete the consultation/Training
  • Hour 2: 08/31
  • Community Release Manager
    • 1-2 people from community
  • RM for LFN Projects - David McBride
    • Dedicated RM does not scale - No RM is chaos - Find a middle ground
    • Need - a stable, effective, repeatable process.
  • Projects of projects - dependencies
  • chat: looks like the current L3AF "release process" (such as it is) is documented at https://github.com/l3af-project/governance/blob/main/docs/RELEASE_PROCESS.md. I'm guessing there are gaps we will hear about in this presentation.
  • L3AF is a project of projects: L3aF-arch, l3afd, epf program repo
  • Interop
    • 1 proj w/mult releases: for eg: Linux/Windows.
  • MUST adhere to release schedule
  • L3AF project: New, release every 10-12 weeks
    • Currently no releases
  • More mature - longer release periods
    • Linux kernel - 4 times a year
  • Signoff process
    • TSC is not necessarily responsible for regular release signoff
      • The task may be delegated to another body
  • Use the principle of minimum viable governance
  • What about the PR around release?

Action Items

Future Agenda Items

  • No labels