Skip to content

Commit 5ba9ffc

Browse files
committed
Update web community info to remove TOC and duplication of audience info
1 parent 66b02b0 commit 5ba9ffc

File tree

1 file changed

+0
-46
lines changed

1 file changed

+0
-46
lines changed

docs/community/governance.md

Lines changed: 0 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,6 @@ provides information about our various working groups.
3535
- [Steering Committee (SC)](https://github.com/knative/community/blob/main/STEERING-COMMITTEE.md):
3636
describes our steering committee.
3737

38-
- [Technical Oversight Committee (TOC)](https://github.com/knative/community/blob/main/TECH-OVERSIGHT-COMMITTEE.md):
39-
describes our technical oversight committee.
40-
4138
- [Annual reports](https://github.com/knative/community/tree/main/annual_reports):
4239
lists previous annual reports.
4340

@@ -56,9 +53,6 @@ how we manage pull requests.
5653
- [SC election process](https://github.com/knative/community/blob/main/mechanics/SC.md):
5754
elcection process for our steering committee.
5855

59-
- [TOC election process](https://github.com/knative/community/blob/main/mechanics/TOC.md):
60-
election process for our technical oversight committee.
61-
6256
- [Repository Guidelines](https://github.com/knative/community/blob/main/REPOSITORY-GUIDELINES.md):
6357
how we create and remove core repositories.
6458

@@ -91,43 +85,3 @@ If you want to add an event to the calendar please send an email to
9185
or post to the `#knative` channel in the CNCF [Slack](https://slack.cncf.io) workspace.
9286

9387
<iframe src="https://calendar.google.com/calendar/embed?src=knative.team_9q83bg07qs5b9rrslp5jor4l6s%40group.calendar.google.com&ctz=America%2FLos_Angeles" style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
94-
95-
## Knative's audience
96-
97-
Knative is designed for different personas:
98-
99-
![Diagram that displays different Audiences for Knative](images/knative-audience.svg)
100-
101-
### Developers
102-
103-
Knative components offer developers Kubernetes-native APIs for deploying
104-
serverless-style functions, applications, and containers to an auto-scaling
105-
runtime.
106-
107-
To join the conversation, head over to the
108-
[Knative users](https://groups.google.com/d/forum/knative-users) Google group.
109-
110-
### Operators
111-
112-
Knative components are intended to be integrated into more polished products
113-
that cloud service providers or in-house teams in large enterprises can then
114-
operate.
115-
116-
Any enterprise or cloud provider can adopt Knative components into their own
117-
systems and pass the benefits along to their customers.
118-
119-
### Contributors
120-
121-
With a clear project scope, lightweight governance model, and clean lines of
122-
separation between pluggable components, the Knative project establishes an
123-
efficient contributor workflow.
124-
125-
Knative is a diverse, open, and inclusive community.
126-
Your own path to becoming a Knative contributor can begin in any of the
127-
following components:
128-
129-
## Knative authors
130-
131-
Knative is an open source project with an active development community.
132-
The project was started by Google but has contributions from a growing number of industry-leading companies.
133-
For a current list of the authors, see [Authors](https://github.com/knative/serving/blob/main/AUTHORS).

0 commit comments

Comments
 (0)