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

Compare with Current View Page History

« Previous Version 6 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
ODIM (sandbox)
Cisco
Samsung

@Anil Guntupalli 

Verizon

IBM


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

TBD

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

LF Staff: Kenny PaulCasey CainHeather Kirksey, Sandra JacksonTrevor Bramwell , LJ Illuzzi

Others: 

Agenda

Minutes

SNAS & PNDA Archive

Code Management

  • Al Morton Is there any restrictions on subprojects using different tooling for code management?
  • Brian Freeman Agree that the TSC is accountable for Project & sub-project decisions
  • Ed Warnicke Also agree that the TSC is accountable. - The FD.io TSC cannot - by design - force a sub project to do something
  • Robert Varga TAC makes a recommendation, but Projects don't need to follow it.
  • Ranny Haiby TAC makes recommendations only - Project TSC's are responsible for making the decision on the tools.
  • Cedric Ollivier The decision should go down to the subprojects. 
  •  #agreed the TAC will help with recommendations to a Project, ultimately it is the Project TSC which makes the decisions for the Project.  TAC encourages project communities to collaboratively work out differences within the project before resorting to charter enforcement

TAC Composition and Goals 

Action items

  •  
  • No labels