Update README.md
Soften language used when describing the PM Group
This commit is contained in:
caleb miles
GitHub
parent
41af954a5e
commit
1befe90e52
|
|
@ -1,44 +1,31 @@
|
|||
## Kubernetes PM
|
||||
## The Kubernetes PM Group
|
||||
|
||||
Kubernetes PM special interest group (SIG-PM) is a group within the Kubernetes Community, that is responsible for managing and maintaining the project roadmap and direction through ways other than writing code.
|
||||
### Focus
|
||||
|
||||
It has been established from the PM Working Group, following the same goals, principles, and statements; with regards to the [Kubernetes SIG general requirements](https://github.com/kubernetes/community/blob/master/governance.md#sig-governance).
|
||||
The Kubernetes PM Group is focused on a variety of challenges: from the qualification and successful management of user requests, one of the many tasks of product management, through the continued improvement of the processes used by the Kubernetes community to maintain the Kubernetes Project itself which more closely relates to traditional project or program management. Besides helping to discover both what to build and how to build it, the PM Group also helps to try and keep the wheels on this spaceship we are all building together; bringing together people who think about Kubernetes as both a vibrant community of humans and technical program is another primary focus of this group. Members of the Kubernetes PM Group can assume [certain additional](https://github.com/kubernetes/community/blob/master/project-managers/README.md) responsibilities to help maintain the Kubernetes Project itself. It is also important to remember that the role of managing an open source project is very new and largely unscoped for a project as large as Kubernetes; we are learning too and we are excited to learn how we can best serve the community of users and contributors.
|
||||
|
||||
The primary goal of the PM group is Product Management (PdM), considering Kubernetes as a product. Also, SIG PM covers the areas of Project Management (PjM) and Program Management (PgM) of Kubernetes.
|
||||
### Common activities
|
||||
- Collecting and generalizing user feedback to help drive project direction and priorities: delivering on user needs while enforcing vendor neutrality
|
||||
- Supporting collaboration across the community by working to improve the communication of roadmap and workload of other [Special Interest Groups](https://github.com/kubernetes/community#special-interest-groups-sig-and-working-groups)
|
||||
- Supporting the continued effort to improve the stability and extensibility of Kubernetes Project
|
||||
- Supporting the marketing and promotion of the Kubernetes Project through the [CNCF](https://www.cncf.io/)
|
||||
- Working with the [Kubernetes Release Team](https://github.com/kubernetes/community/tree/master/contributors/devel/release) to continually ensure a high quality release of the Kubernes Project
|
||||
- Supporting the creation of Kubernetes ecosystem through [the Kubernetes Incubator](https://github.com/kubernetes/community/blob/master/incubator.md)
|
||||
- Onboarding large groups of corporate contributors and welcoming them into the Kubernetes Community
|
||||
- Whatever is needed to help make the project go!
|
||||
|
||||
### Responsibilities
|
||||
### Contact us
|
||||
- via [slack](https://kubernetes.slack.com/messages/kubernetes-pm/)
|
||||
- via [Google Groups](https://groups.google.com/forum/#!forum/kubernetes-pm)
|
||||
|
||||
|
||||
* Work on the Kubernetes roadmaps, feature backlogs, etc. to define the development path, gaps and requirements of Kubernetes as a product;
|
||||
* Interact with the development teams, users, partners and upstream contributors to coordinate the community and business interests;
|
||||
* Constantly stay in touch with the Kubernetes Release team to track the Kubernetes per-iteration development, managing features release notes and related areas;
|
||||
* Provide support for Kubernetes marketing-related activities (CNCF and partners marketing, blog posts, meetups, conferences promotion, etc.)
|
||||
* Other responsibilities, defined on ad-hoc basis
|
||||
|
||||
### Regular meeting Time
|
||||
### Scheduled Meeting Times
|
||||
|
||||
TBD
|
||||
|
||||
### Mailing List:
|
||||
|
||||
[Kubernetes PM](https://groups.google.com/forum/#!forum/kubernetes-pm)
|
||||
|
||||
### Slack Channel:
|
||||
|
||||
[#kubernetes-pm](https://kubernetes.slack.com/messages/kubernetes-pm/)
|
||||
|
||||
|
||||
### Kubernetes PM Leadership Board
|
||||
|
||||
- Aparna Sinha apsinha@google.com, Google
|
||||
### Current leaders
|
||||
- Aparna Sinha apsinha@google.com, Google
|
||||
- Ihor Dvoretskyi ihor.dvoretskyi@gmail.com, Mirantis
|
||||
- Caleb Miles caleb.miles@coreos.com, CoreOS
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Caleb Miles caleb.miles@coreos.com, CoreOS
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue