github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-08-26 19:48:56 +00:00
Code Issues Projects Releases Wiki Activity

remove references to working committee

Browse Source 
The working committee isn't part of the project's governance
at this point, so it makes sense to remove it from the front
of the community page.  Marketing discussions are happening instead on a
monthly basis and via mailing-list/slack.

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
This commit is contained in:
Eric Ernst 2019-01-16 14:58:09 -08:00
parent 926772feb5
commit 7a6f6edf37
1 changed files with 0 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -10,7 +10,6 @@
* [Contributor](#contributor) * [Contributor](#contributor)
* [Maintainer](#maintainer) * [Maintainer](#maintainer)
* [Architecture Committee](#architecture-committee) * [Architecture Committee](#architecture-committee)
* [Working Committee](#working-committee)
* [Vulnerability Disclosure](#vulnerability-disclosure) * [Vulnerability Disclosure](#vulnerability-disclosure)
# About Kata Containers # About Kata Containers
@ -82,21 +81,6 @@ Architecture Committee elections take place in September (3 seats available) and
The exact size and model for the Architecture Committee may evolve over time based on the needs and growth of the project, but the governing body will always be committed to openness, diversity and the principle that technical decisions are made by technical contributors. The exact size and model for the Architecture Committee may evolve over time based on the needs and growth of the project, but the governing body will always be committed to openness, diversity and the principle that technical decisions are made by technical contributors.
## Working Committee
The Working Committee is intended to make non-technical decisions and help influence the project strategy, including marketing and communications, product management and ecosystem support. Representatives are expected to be active contributors who are committed to the health and success of the project.
Recognizing the project will grow and change quickly in the first six months, and in order to encourage diversity and participation, the Working Committee will be forming up and finalizing its structure after the project launch.
Initial appointed members include:
- Amy Leeland ([`amyleeland`](https://github.com/amyleeland)), [Intel](https://www.intel.com).
- James Kulina ([`jmknyc06`](https://github.com/jmknyc06)), [HyperHQ](https://hyper.sh).
During this initial period, the participants will appoint a leader to help organize and run regular meetings, coordinate the various workstreams and help define the long-term structure. The initial task will be to determine 2018 plans and appropriate work streams, working groups and funding to execute on those plans.
The estimated size of the Working Committee is 7 members, but there is opportunity for more contributors to get involved in various sub-teams working on specific topics, such as product management or conformance. The Working Committee will meet regularly in an open forum with times and locations published in community channels.
# Vulnerability Disclosure # Vulnerability Disclosure
Vulnerabilities in the Kata Container project are managed by the Kata Containers Vulnerabilities in the Kata Container project are managed by the Kata Containers