2023-05-24 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 @Kenny Paul @Ranny Haiby @Sandra Jackson (Deactivated) @Andrew Grimberg @LJ Illuzzi

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

  • TAC Elections

    • Congratulations to @Olaf Renner 

    • Vice-Chairperson Election

  • Infosys vision for the LFN

  • Infrastructure

  • Induction Project Data Template

• Any Other Topics

Minutes

TAC Elections

• Congratulations to @Olaf Renner 

• The Vice-Chair election will begin today

Infosys Vision for the LFN

• @GNANAPRIYAC@infosys.com (Deactivated) shared Infosys's vision for engagement in the LFN.
  
  

  • @Girish Kumar noted that they are first looking to contribute to ONAP.  They will be looking at Orchestration flow like ETSI NFVO VNFM Adapter, etc

  • The TAC had continued discussions about participation in ONAP.

  • @Olaf Renner asked about the challenges to participating with some of the projects

    • @GNANAPRIYAC@infosys.com (Deactivated) working on the Telecom IT stack brought the greatest challenge. 

Infrastructure 

• @Casey Cain spoke about reviving the Infrastructure working group

• @Andrew Grimberg informed the TAC that we have received additional licenses for Atlassian products and will no longer required to migrate away from Confluence and Jira.

• @Andrew Grimberg We now have the ability to trigger a GitHub Action with a Gerrit Change.

  • We now have the ability to migrate interested Projects from Jenkins to GitHub Actions.  As projects migrate to GitHub Actions, the LFN will see important cost savings.

  • @Andrew Grimberg Provided examples of the improvements to workflows.  The jobs are much more parallelized and reporting is clearer to address bug tracking. 

  • This new feature supports projects that use Gerrit.

  • Documentation is still in progress, but the tooling is largely feature complete

  • Olaf asked if GitLab support will be added in the future.

    • Andy noted that it would be fairly easy to add support, but nobody has requested the GitLab feature yet.  Most of our Projects use Gerrit/GitHub

• @Casey Cain spoke about forming an Infrastructure working group

  • @Muddasar Ahmed volunteered

  • @Casey Cain agreed to start a mailing list thread to kick off dicussions

Induction

• @Casey Cain shared that he will be presenting an updated Project Data Template at the next TAC meeting

• @Olaf Renner Should we schedule something to "market" the LFN to new projects?

  • We should have a short promotional marketing material 

  • There was general agreement to this and @Ranny Haiby took the action item to invite @Jill Lovato to come to the next TAC meeting to discuss. 

Action items