Add Working Groups Process
Signed-off-by: Chris Aniszczyk <caniszczyk@gmail.com>
This commit is contained in:
Chris Aniszczyk
parent
886b550378
commit
32ecbe6d87
|
|
@ -0,0 +1,11 @@
|
|||
# CNCF Working Groups
|
||||
|
||||
## Introduction
|
||||
|
||||
The purpose of working groups are to study and report on a particular question and make recommendations based on its findings. The end result of a working group may be a new project proposal, landscape, whitepaper or even a report detailing their findings. The intention of working groups is not to host a full project or specification. Working Groups can be formed at any time but must be sponsored by a TOC member and voted with a super majority vote by the CNCF TOC. The TOC can also shut down a working group with a super majority vote.
|
||||
|
||||
## Process
|
||||
|
||||
If you would like to submit a working group proposal, please submit a pull request to the working groups folder. As an example, you can see the other working group proposals here: https://github.com/cncf/toc/tree/master/workinggroups
|
||||
|
||||
You will also have to present to the CNCF TOC and wider community before your WG proposal will be voted upon by the TOC and community. You can request a presentation by filing an issue here: https://github.com/cncf/toc/issues
|
||||
|
|
@ -0,0 +1,34 @@
|
|||
# CNCF CI WG Proposal
|
||||
|
||||
## TOC Sponsor
|
||||
|
||||
Camille Fournier
|
||||
|
||||
## Objective
|
||||
|
||||
Explore the intersection of cloud native and CI technology. Discuss options for taking some of the cluster resources and dedicating them to supporting an open source CI system that can be used by CNCF projects for their CI needs.
|
||||
|
||||
## Goals and Expected Outcomes
|
||||
|
||||
* We believe that it would be good for us to provide CI services to projects who need or want to use them
|
||||
* We need to understanding what, if any, SLA we can promise projects for this system
|
||||
* We need to scope what features this system will provide; there is some concern around trying to promise testing the full cross-product of integration with all of the different CNCF projects
|
||||
* We want to come away with a recommendation for staffing to support building out this initiative given project needs and desired SLA
|
||||
|
||||
## Non Goals
|
||||
|
||||
* Run CI for CNCF projects
|
||||
* Recommend CI systems for CNCF projects
|
||||
|
||||
## Initial Interested Parties
|
||||
|
||||
* Camille Fournier (@skamille) [LEAD]
|
||||
* Chris McClimans (@hh) [Hippie Hacker]
|
||||
* Denver Williams (@dlx)
|
||||
* Taylor Carpenter (@taylor)
|
||||
* Lucina Stricko (@lixuna)
|
||||
* Jonathan Boulle (@jonboulle)
|
||||
* Clint Byrum (@spamaps)
|
||||
* Quinton Hoole (@quintonhoole)
|
||||
* Quanyi Ma (@genedna)
|
||||
* Gianluca Arbezzano (@gianarb)
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
# CNCF Networking WG Proposal
|
||||
|
||||
## TOC Sponsor
|
||||
|
||||
Ken Owens
|
||||
|
||||
## Objective
|
||||
|
||||
Explore cloud native networking technology and concepts around the container networking interface (CNI).
|
||||
|
||||
## Goals and Expected Outcomes
|
||||
|
||||
* Recommend CNI be adopted as initial network interface specification focused on connectivity and portability as an official CNCF project.
|
||||
* Adopt implementations of CNI that have traction in the cloud native ecosystem
|
||||
* Define cloud native networking patterns
|
||||
* Define the Policy framework and network services model
|
||||
* A network plugin author should be able to write one “plugin” (a container) that “just works” across all container orchestration (CO) systems.
|
||||
* Enable container orchestrator to present network interfaces to the users in a portable manner that is focused on connectivity initially.
|
||||
* Support dynamic provisioning and deprovisioning network primitives through this interface.
|
||||
* Support group of entities that are uniquely addressable that can communicate amongst each other. This could be either an individual container, a machine, or some other network service (e.g. load balancing, firewall, VPN, QoS, Service Discovery). Containers can be conceptually added to or removed from one or* more networks.
|
||||
* Focused on cloud native application patterns. This includes VM-based, Bare metal based, and FaaS (TBD) based.
|
||||
* Define policy framework for network isolation
|
||||
|
||||
## Non Goals
|
||||
|
||||
* Provide or dictate an implementation.
|
||||
* This includes dictating plugin lifecycle management
|
||||
* Plugin distribution
|
||||
* Protocol-level authn/authz
|
||||
* Plugin discovery
|
||||
* Not going to make a one network standard for all
|
||||
* Not going to focus on individual projects per service but rather projects that model network services and patterns not going to be prescriptive but more reference guidelines and patterns
|
||||
|
||||
## Interested Parties
|
||||
|
||||
* Ken Owens (@kenowens12) [lead]
|
||||
* Ben Hindman (@benh)
|
||||
* Alexis Richardson (@monadic)
|
||||
* Jonathan Boulle (@jonboulle)
|
||||
* Lee Calcote (@lcalcote)
|
||||
* Madhu Venugopal
|
||||
* Jie Yu
|
||||
* Deepak Bansal
|
||||
* John Gossman
|
||||
* Christopher Liljenstolpe (@liljenstolpe)
|
||||
* Bryan Boreham (@bboreham)
|
||||
* Minhan Xia (@freehan)
|
||||
* Daniel Nardo (@dnardo)
|
||||
* Pengfei Ni (@feiskyer)
|
||||
* John Belamaric (@johnbelamaric)
|
||||
* Thomas Graf (@tgraf__)
|
||||
* Jason Venner (@jvmirdel)
|
||||
* Doug Davis (@duglin)
|
||||
|
|
@ -0,0 +1,39 @@
|
|||
# CNCF Serverless WG Proposal
|
||||
|
||||
## TOC Sponsor
|
||||
|
||||
Ken Owens
|
||||
|
||||
## Objective
|
||||
|
||||
Explore the intersection of cloud native and serverless technology.
|
||||
|
||||
## Goals and Expected Outcomes
|
||||
|
||||
* Produce a whitepaper
|
||||
* Produce a serverless landscape
|
||||
* Explore specifications for serverless to propose to the CNCF
|
||||
* Bring recommendations to the TOC on serverless projects in CNCF
|
||||
|
||||
## Non Goals
|
||||
|
||||
* Define one serverless project to rule them all
|
||||
|
||||
## Initial Interested Parties
|
||||
|
||||
* Sarah Allen (Google)
|
||||
* Chris Aniszczyk (CNCF)
|
||||
* Chad Arimura (Oracle)
|
||||
* Ben Browning (Red Hat)
|
||||
* Lee Calcote (SolarWinds)
|
||||
* Amir Chaudhry (Docker)
|
||||
* Doug Davis (IBM)
|
||||
* Louis Fourie (Huawei)
|
||||
* Antonio Gulli (Google)
|
||||
* Yaron Haviv (iguazio)
|
||||
* Daniel Krook (IBM)
|
||||
* Orit Nissan-Messing (iguazio)
|
||||
* Chris Munns (AWS)
|
||||
* Ken Owens (Mastercard)
|
||||
* Mark Peek (VMWare)
|
||||
* Cathy Zhang (Huawei)
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
# CNCF Storage WG Proposal
|
||||
|
||||
## TOC Sponsor
|
||||
|
||||
Ben Hindman
|
||||
|
||||
## Objective
|
||||
|
||||
Explore cloud native storage technology and concepts.
|
||||
|
||||
## Goals and Expected Outcomes
|
||||
|
||||
* Produce a landscape
|
||||
* Explore specifications for storage to propose to the CNCF
|
||||
* Bring recommendations to the TOC on storage projects in CNCF
|
||||
|
||||
## Non Goals
|
||||
|
||||
* N/A
|
||||
|
||||
## Initial Interested Parties
|
||||
|
||||
* Ben Hindman (@benh) [lead]
|
||||
* Steven Tan (@stevenphtan)
|
||||
* Clinton Kitson (@clintonskitson)
|
||||
* Alex Chircop (@chira001)
|
||||
* Steve Wong (@cantbewong)
|
||||
* Venkat Ramakrishnan (@katkrish)
|
||||
* Gou Rao (@gourao)
|
||||
* Vinod Jayaraman (@jvinod)
|
||||
* Allen Samuels (@allensamuels)
|
||||
* Yaron Haviv (@yaronhaviv)
|
||||
Loading…
Reference in New Issue