You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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
ODL XFD.io
TF (incubation)
OPNFVX@Eyal FelstaineAmdocs
Samsungx

@Anil Guntupalli

Verizon
CiscoXIntelx
AT&TX

IBM


Red Hat
ONAP
China Mobile

TBD

Juniper
ZTE
Deutsche Telekom
Huawei
Ericsson
OPX (sandbox)xChina Telecom
VodafoneXOrange



@David Sauvageau

Bell Canada
Türk Telekomx


Tech Mahindra
Nokia
TBDVMware

LF Staff: Casey CainKenny Paul Brandon Wick , Trevor BramwellJim Baker

Others:

Agenda

  • Start the Recording
  • Show the Antitrust Policy
  • Roll Call
  • Action Items Review
  • Agenda Bashing
  • General Topics
    • Virtual Technical Event Planning for ONES, Technical Meetings, and 2021 Planning
    • LFN Scaleability
  • Any Other Topics

Minutes

LFN Scaleability

  • Jason Hunt talked about the inbound project pipeline for LFN and how Linux Foundation Networking would scale to support those projects.
    • How do we grow the LFN to make it a multi-project umbrella and what does it mean to be a member of the umbrella?
    • How do we manage expectations of resources and funding? 
  • Brian Freeman Does the board recognize that if we add more projects, we have less funding for the other projects?
    • Do we have our membership fees go up by 5% if we add a new project?
    • Membership is not necessarily growing for new projects who join
    • Ranny Haiby suggested that there may be an expectation from LF leadership that the number of projects may grow but not necessarily the overall budget.
      • There may be a scenario where projects mature they would require less resources.
      • Brian Freeman How would that work?  I don't think that scales for all projects.
        • We should be making sure that the projects are not just shifting from one project to another and that there is a sufficient amount of development resources assigned to each project.  There has been a trend of as new projects come online we lose developers on another project.
    • Jason Hunt In general, we need to find a way to be more efficient, and clear about where and how we will apply resources. 
  • Kenny Paul As a point of reference in general the LFN provides a more high-touch availability of resources (both infrastructure and project management support) than other projects in the LF spectrum.   Also this is highly likely be a topic of discussion at the  Governing Board meeting.
  • Jim Baker shared a WIP document on the service level proposal for Project membership tiers
    • each tier provides additional level of services
    • one school of thought that projects should receive more staff support up front and have that tail off as the projects move up the tree versus getting more support.
  • Lifecycle doc will ultimately need to be updated to reflect not only Project maturity, but also service levels
  • Ranny Haiby believes that projects can step up and reduce the high-touch requirements of staff.
  • Jim Baker provided the example of LFAI which has more that a dozen highly active capital "P" Projects and only a single LF staff project manager serving all of them because the projects are far more self-staffed, versus LFN which has 5 project managers plus a release manager supporting 6 highly active Projects.

Jason noted that he and Ranny were on vacation next week and ask for a volunteer to represent the TAC on the SPC call 

Virtual Technical Event Planning for ONES, Technical Meetings, and 2021 Planning

  • Casey Cain talked about the need to start planning for ONES, and the 2020 Technical Meetings.  We also need to take a look at what 2021 will look like.
    • It's likely that events will remain virtual for the first half of 2021.
    • Asks that if you have interest in participating in coordinating and planning committee, please join the mailing list.
  • Brandon Wick We are changing our technical events from a 2-day event to a 3-day event and making it a bit shorter.  We are also shifting to an EST time zone to capture a broader audience. 
  • For ONES we will be using a tool called INXPO for hosting the event.
    • All talks will be recorded 
    • We are not going to include an unconference track.  We found that they were not really used in a virtual space.
  • Technical Events
    •  Normally a 2-day event following ONES.  We decided to make this event a bit shorter and make it 3 days instead.  This eased the burden of participation. 
    • We do not plan to hold the technical events during the same week as ONES because it could be a bit draining to attend ONES and the Technical Events.
    • Right now we are looking at  &  

Action items

  •  
  • No labels