2023-03-01 TAC Minutes

Attendees & Representation (default sort: member first name)

TAC Members and Project representatives should mark their attendance below 
Non-TAC project reps do not count towards meeting quorum

X = Present | P = Proxy  (Indicate in the table with @name for @name

LF Staff: Casey Cain LJ Illuzzi Kenny Paul Sandra Jackson (Deactivated) 

Community: Timo Perala 

Agenda

• Start the Recording
• We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
  • Antitrust Policy
• Roll Call
• Action Items Review
• Agenda Bashing
• General Topics
  • Summer Mentorship Deadline 03 Mar 2023 LFN Mentorship Program 
  • Developer & Testing Forum
    • Survey
  • Review Induction process
  • Quick Updates
    • Security Amy Zwarico 
    • 5G Muddasar Ahmed 
    • Ops Survey Casey Cain 
• Placeholder- agenda item for 03/15 meeting- EMCO project Healthcheck
• Any Other Topics

Minutes

Mentorships

• Casey Cain spoke about the opportunities for Mentorships and the current proposed timeline.

D&TF

• Casey Cain & Kenny Paul spoke about the details of the Developer & Testing Forum
  
  • Casey Cain encouraged everyone to fill out the Survey 
  • Kenny Paul talked about the attendance 
• Muddasar Ahmed There seems to be a lot of updates about the project, but not as many demos or collaboration.

LFN Induction

• Casey reviewed the proposed LFN Induction Template.
• A question was raised about organizations donating code to the community without the intent of maintaining the code themselves.
  • A discussion ensued about:
    • difference between code without governance versus code with governance
    • where that code should live.
  • Anyone can open source code; we need code attached to a specific project or group of maintainers.
• Continue the review the Induction process at the next meeting
  
  • Discussion around project overlap and code availability.

Action items