1 of 19

CNCF TOC Meeting

March 9th, 2016

2 of 19

LF Antitrust Policy Notice

CNCF meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at CNCF meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2

3 of 19

Meeting Logistics

Time: March 9th 8AM (Pacific)

Phone/Internet:

3

4 of 19

TOC - Members Present Today

4

Company

Apache Software Foundation

Cisco

CoreOS

Joyent

Mesosphere

Weaveworks

Guest: Solomon Hykes, Michael Dolan

Note: TOC meetings shall require a quorum of two-thirds of the TOC total members to take a vote or make any decision. If a TOC meeting fails to meet the quorum requirement, discussions may proceed, however there shall be no voting or decisions.

Name

Camille Fournier

Ken Owens

Jonathan Boulle

Bryan Cantrill

Benjamin Hindman

Alexis Richardson

5 of 19

Agenda

  • Kubernetes Vote
  • TOC Member Nominations
    • Special Guest: Solomon Hykes
  • IP Policy Discussion (by Mike Dolan)
  • CNCF Cluster Update (by Bryan Cantrill)
  • Event Planning
  • Working Groups Update

5

6 of 19

Kubernetes

Motion carried: TOC accepts k8s into CNCF as Incubated Project

http://lists.cncf.io/pipermail/cncf-toc/2016-March/000080.html

TODO:

  • Announce Thursday this week
  • Define Incubated Project
  • List Assets (Sarah N)

6

7 of 19

TOC Member Nominations

Voting on TOC 7&8?

Status update from AR and BH

TOC members can nominate up to 2 people. Current Nominations: https://docs.google.com/document/d/1s-ZKZKBy3huaF2H0isjqaGOAZgwjy-XW_yQcswU0sUE/edit

Note: Candidates can be from academia or anywhere (don’t have to be CNCF members)

7

8 of 19

End User TOC Member

Voting on TOC 9

The CNCF Governing Board asks the TOC to elect an interim TOC member to represent the End User Technical Advisory Board until it’s fully formed

Voting timeline:

March 7- CIVS voting begins

March 11- CIVS voting ends

March 14- Result announced

End User Candidates: https://docs.google.com/document/u/1/d/1o_0gNcJ4-yfRiHGp_JHzVhtGqTQ7sNbvF1EwGHTqgls/edit

8

9 of 19

IP Policy (led by Michael Dolan)

11. IP Policy

(a) Any project that is added to the CNCF must have ownership of its trademark and logo assets transferred to the Linux Foundation.

(b) All code contributors will undertake the obligations set forth in the Apache contributor license agreement(s), altered only as necessary to identify CNCF as the recipient of the contributions, and which shall be approved by the Governance Board. See Apache Corporate Contributor License Agreement (https://www.apache.org/licenses/cla-corporate.txt) and Apache Individual Contributor License Agreement (https://www.apache.org/licenses/icla.txt). The process for managing contributions in accordance with this policy shall be subject to

Governance Board approval.

(c) All new inbound code contributions to the CNCF shall be (i) accompanied by a Developer Certificate of Origin sign-off (http://developercertificate.org) and (ii) made under the Apache License, Version 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0), such license to be in addition to, and shall not supersede, obligations undertaken under the contribution license agreement(s) provided for in (b) above.

(d) All outbound code will be made available under the Apache License, Version 2.0.

(e) All projects evaluated for inclusion in the CNCF shall be completely licensed under an OSI-approved open source license. If the license for a project included in CNCF is not Apache License, Version 2.0, approval of the Governing Board shall be required.

(f) All documentation will be received and made available by the CNCF under the Creative Commons Attribution 4.0 International License.

(g) If an alternative inbound or outbound license is required for compliance with the license for a leveraged open source project or is otherwise required to achieve the CNCF’s mission, the Governing Board may approve the use of an alternative license

for inbound or outbound contributions on an exception basis.

9

10 of 19

CNCF Cluster Update

Bryan Cantrill on the status of the CNCF Cluster

10

11 of 19

Event planning

KubeCon EU Panel

CollabSummit, any actions?

CoreOS Fest?

ContainerCon?

11

12 of 19

Workgroups Update

Workgroups for key pieces.

  • for open source projects, what the CNCF gives you -- (Alexis, BenH, Ken) + Bryan on Cluster
  • proposal process for new CNCF projects & incubation (ChrisA, Jon, Camille)
  • draft project development process (ChrisA, Bryan, Ken?)

Action: Discuss Status

12

13 of 19

Appendix

13

14 of 19

CNCF Projects

  • Anchor / Committed Projects
    • kubernetes
    • etcd
  • Other Interested Projects
    • prometheus?
    • openzipkin? (or: opentracing)
    • nats?
    • CNI
    • dockyard
    • …?

14

15 of 19

Workgroup 1: CNCF Project Voting?

  • Should we vote on an initial anchor or set of anchor projects in order to move faster? We can work on the development guidelines in parallel with projects as they get accepted vs crafting the perfect set of guidelines first

  • Should we vote on the proposal process to unblock us from accepting projects?
  • Simple proposal (see google doc)
    • Projects get proposed via email: cncf-proposals@lists.cncf.io
      • subject: “[PROPOSAL] project name”
    • Projects get accepted via a 2/3 supermajority vote of the TOC
    • All projects start in an incubator TLP
      • Graduating requires a 2/3 vote from the TOC

15

16 of 19

Workgroup 2: CNCF Development Process

  • Development Process (see google doc)

  • Who is interested in forming a small Working Group to tackle this? I don’t think it’s possible to do this over the normal TOC call

16

17 of 19

2, cont. CNCF Project Structure

  • How will CNCF projects be structured?
    • Top level projects (TLP) with sub projects?
    • TLPs have a PMC for disputes?

  • Should we have an incubator?
    • Should all projects require incubation before becoming an official CNCF project?

17

18 of 19

Workgroup 3: “who we are”

  • Defining the technical vision for CNCF?

  • How do we attract certain projects to the CNCF?

  • How do we handle projects having different development styles?
    • Should we come up with a “CNCF Way”

  • How do we make this not suck?

  • What else?

18

19 of 19

Thank You

19