/
2021-10-06 TAC Minutes

2021-10-06 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

Member

Representing



Member

Representing



Member

Representing



Member

Representing



Member

Representing



Member

Representing



@Alex Vul (Deactivated)

ODIM (sandbox)



@Frank Brockners 

Cisco



@Ranny Haiby 

Samsung



@Anil Guntupalli 

Verizon



@djhunt 

IBM



@Robert Varga

ODL (TAC)



@Anil Kapur 

Juniper



@Kalyankumar Asangi

Huawei



Szymon Golebiewski 

TF (incubation)



@FREEMAN, BRIAN D

AT&T



@Lingli Deng 

China Mobile



@Timothy Verrall (Deactivated) 

Intel



@cl664y@att.com

ONAP (TAC)



@Marc Fiedler 

Deutsche Telekom



TBD 

Red Hat



@ChangJin Wang

ZTE



@Martin Jackson

Walmart



@Walter.kozlowski

Anuket (TAC)



@Christian Olrog Atlassian

Ericsson



@Morgan Richomme

Orange



@Xiaojun Xie

China Telecom



@Dhananjay Pavgi 

Tech Mahindra



@Olaf Renner

Nokia



@Qihui Zhao

XGVela (sandbox)



@Ed Warnicke

FD.io (TAC)



@Ramesh Nagarajan

Google





















TBD

Amdocs



LF Staff: @Kenny Paul, @Sandra Jackson (Deactivated) , @Brandon Wick,  @LJ Illuzzi @Casey Cain

Others: @Tina Tsou (Deactivated)@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.

  • Roll Call

  • Action Items Review

  • Agenda Bashing

  • General Topics

    • LF IT and Project Responsibilities (@Morgan Richomme on behalf of Orange)

    • Credly Badging Program 

      • Template data - community help needed

      • Graphics

      • Automation

    • ONE Summit

      • Register

      • Recommended sessions??

  • Recurring Updates

  • Any Other Topics

Minutes

LF IT and Project Responsibilities

  • recent toolchain breakage following an update from LFIT - affected documentation

  • 3 identified concerns:

    • inadequate notification of upgrade was provided - how can upgrade notifications be more clearly communicated, and can the community influence the schedule?

    • concerns that tooling is not under community control - are there tools that can/should be under community control?  Is it possible to have shared control?

    • community involvement in the process needs to be more tightly coupled - European coverage should help, still trying to secure a resource; is there a more interactive trouble resolution process outside of tickets?

  • Suggestion for Projects to come up with what the optimum state would be with regards to support/infrastructure

  • limitations regarding legal responsibilities related to infrastructure access and management acknowledged

  • Discussion of pursuing commercial support in a SaaS context

    • Size and scope of community needs are significant  

    • Maturity of communities noted - most in this space were new to open source, not much experience originally. Now deep expertise in many areas.

    • Fd.io notes that their community has taken on support responsibilities they would prefer that someone else manages in order to get the level of stability and access they want.

    • @Casey Cain owes @FREEMAN, BRIAN D@Morgan Richomme a cup of coffee if we have this same conversation a year from now. 

    • ONAP will be taking this issue to the LFN GB at this month

Next meeting

  • conflict with the LFN GB meeting on Oct 20, 2021 

  • #AGREED meeting on Oct 20, 2021 to be cancelled. next meeting will be on Nov 3, 2021 

Credly Badging Program

  • Discussion of "Skills" column

    • required field for API, but "Skills" not necessarily relevant to what we are doing.

    • Suggestion to make it generic enough to apply to a broad category of experience

    • @Ed Warnicke shared his Credly credentials to demonstrate an example of somewhat generic text for skills

@djhunt will take a 1st pass at filling in the Credly Badging Program page Nov 3, 2021 

ONE Summit

TAC Community Schedule 

  • Reminder for TAC members to sign up to attend a TSC call from a different community.