Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

MemberRepresenting
MemberRepresenting
MemberRepresenting
ODIM (sandbox)
Cisco
Samsung

@Anil Guntupalli 

Verizon

IBM


ODL (TAC)

@Anil Kapur 

Juniper
Huawei
Szymon Golebiewski TF (incubation)
AT&T
China Mobile
Intel
ONAP (TAC)
Deutsche Telekom

TBD 

Red Hat
ZTE
Walmart
Anuket (TAC)
Ericsson
Orange
China Telecom
Tech Mahindra
Nokia
XGVela (sandbox)
FD.io (TAC)
Google









TBD

Amdocs

LF Staff: Kenny Paul, Sandra Jackson , Brandon Wick,  LJ Illuzzi Casey Cain

Others: Tina TsouTimo 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 Brian FreemanMorgan 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  
  • #AGREED meeting on  to be cancelled. next meeting will be on  

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

ONE Summit

TAC Community Schedule 

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