Page Comparison

...

LF Staff: LJ Illuzzi

Agenda

• LF Antitrust Policy

• Meeting note taker

• Welcome to new attendees

• TAC meeting Recap & Followup

• Contributors list as requested by TAC
  • https://github.com/orgs/l3af-project/people
  • TAC feedback for L3AF: (1) L3AF Project Induction - LF Networking - LF Networking Confluence

• General Topics (cover as needed)

  • Use Cases

  • Roadmap

  • Project structure

    • Governance

    • Technical Steering Committee

Minutes/Updates

• We are inducted into the LFN!
  • Congratulations everyone!
  • LJ: Need a TAC rep to represent the project on the TAC as a sandbox project. Not a voting seat.
    • Also a MAC Marketing Advisory council to help with PR, media blasts, etc
      • Meet once a month
      • Will have Brian come in and talk about a MAC seat
    • Immediate need is to show progress on condition from TAC.
      • Report back to TAC ASAP.
    • Vicky: open issues to address this. We can form a committee if needed.
    • LJ: Governing board on Mar. 16th. We need to wrap up and respond before then.
      • May not be possible.
    • Vicky: Not sure if that is possible. Haven't looked at the governance repo in a while.
      • Don't know scope of work yet.
    • Dave: Condition was to have specifically the process as to how someone becomes a commiter and who they are.
      • We could get that done by next week.
    • Vicky: We should crib from existing link and modify.
    • Dave: We have similar examples.
    • Vicky: Plenty of examples. Won't need to tweak a lot. FIDO does things a little differently
      • Lot's of projects, just pick one.
    • LJ: Typically a conglomeration depending on the needs of the community.
      • Pick what makes most sense and run with it.
    • Vicky: We will build our own lego set from other documents.
    • Dave: Most relevant for next week: Section 3.2.2.2. Committer life-cycle
      • https://github.com/l3af-project/governance/issues
    • Jason: Pretty close already
    • Dave: Code owners file needs to have individuals by GitHub ID
      • Code owners file will always match the code owners
      • Package repo doesn't follow that right now.
    • Vicky: I will come up with a draft and send a PR.
    • Dave: Approvers on your PR. Majority of members must approve then it will count as a TSC decision.
    • Karan: Have primary and secondary.
    • Dave: Who are the TSC members? Not resolved.
      • Technical Steering Committee (TSC)
    • Erik - remove Bala, include me.
    • Karan: Add contrib or code owner file.
      • Would that be you Vicky?
      • Vicky: Yes, happy to do that.
    • Jason: This should be in governance repo so we can track.
    • Vicky: Issue updated.
• LJ: Please provide pointer when we can get back to the TAC with an update
• Vicky: Yes, will make some specific guidance to move forward ASAP
• L

Action Items

Future Agenda Items

...