Knative governance and community material.
Go to file
Evan Anderson 18a56776bb
Extend Schedule two rotations (#979)
2022-03-24 23:45:48 -07:00
.github fix link to mechanics doc (#887) 2022-01-11 11:27:14 -08:00
annual_reports Adds Knative 2020 Annual Report (#403) 2020-12-17 11:51:02 -08:00
docs Move docs contrib to help section (#557) 2021-04-27 14:38:53 -07:00
elections Update link in the SC end user election README (#901) 2022-01-20 13:02:35 -08:00
google-summer-of-code GSOC 22 Idea: Improve Knative Eventing Observability (#929) 2022-02-15 13:44:40 -08:00
groups Adopt K8s infra for gsuite mgmt (#905) 2022-02-23 10:34:40 -08:00
hack Add OWNERS_ALIASES for knative-sandbox (#586) 2021-04-29 11:54:56 -07:00
icons New Knative Brand Guidelines (#669) 2021-07-26 12:58:50 -07:00
mechanics Extend Schedule two rotations (#979) 2022-03-24 23:45:48 -07:00
peribolos Adds knative-sandbox/func-tastic repo to peribolos (#969) 2022-03-22 08:15:12 -07:00
working-groups Lionel stepping down from Eventing Kafka WG (#924) 2022-02-14 14:10:58 -08:00
.gitignore Copied from docs/contributing 2019-05-07 14:09:10 -07:00
ADOPTERS.MD Add Bloomberg L.P. as adopter (#896) 2022-01-17 11:48:29 -08:00
BRANDING.MD Copy logo PDF guidelines, including font and color guides, into the community branding guidelines. (#942) 2022-03-03 15:56:35 -08:00
CALENDAR.MD issue-767 (#814) 2021-10-28 09:40:27 -07:00
CODE-OF-CONDUCT.md point CoC to CNCF's CoC (#975) 2022-03-21 11:41:47 -07:00
CONSENSUS.md Create CONSENSUS.md (#595) 2021-05-10 12:22:59 -07:00
CONTRIBUTING.md Fix broken link (#882) 2022-01-05 07:41:32 -08:00
GOVERNANCE.md Define (charter) Steering and Trademark Committees (#277) 2020-09-24 10:48:40 -07:00
LICENSE add LICENSE file (#178) 2020-07-13 06:46:17 -07:00
OWNERS Add TOC to approvers for OWNERS_ALIASES (#914) 2022-02-03 09:42:21 -08:00
OWNERS_ALIASES Add Pablo Mercado (@odacremolbap) as Eventing approver (#939) 2022-03-17 05:26:48 -07:00
README.md fix the filename (#839) 2021-11-15 19:42:52 -08:00
REPOSITORY-GUIDELINES.md Add section about updating docs (#594) 2021-06-04 06:20:45 -07:00
REVIEWING.md Fix links, titles, frontmatter, and use fully qualified knative/docs URLs (#45) 2020-01-30 10:25:28 -08:00
ROLES.md Drop unnecessary occurrences of master (#525) 2021-03-10 07:51:25 -08:00
SECURITY.md Update SECURITY.md (#902) 2022-01-24 14:50:48 -08:00
SLACK-GUIDELINES.md Update SLACK-GUIDELINES.md (#548) 2021-04-27 09:34:53 -07:00
STEERING-COMMITTEE.md fix typo steering (#927) 2022-02-14 15:49:57 -08:00
TEAM-VALUES.md Fix links, titles, frontmatter, and use fully qualified knative/docs URLs (#45) 2020-01-30 10:25:28 -08:00
TECH-OVERSIGHT-COMMITTEE.md Add @n3wscott to TOC. (#890) 2022-01-13 08:49:12 -08:00
TRADEMARK-COMMITTEE.md Replace Omer Bensaadon with Evan Anderson as VMware Trademark representative (#848) 2021-11-18 22:27:23 -08:00
VALUES.md Fix links, titles, frontmatter, and use fully qualified knative/docs URLs (#45) 2020-01-30 10:25:28 -08:00
knative-sandbox-OWNERS_ALIASES Adds knative-sandbox/func-tastic repo to peribolos (#969) 2022-03-22 08:15:12 -07:00
logo-guidelines.pdf Copy logo PDF guidelines, including font and color guides, into the community branding guidelines. (#942) 2022-03-03 15:56:35 -08:00

README.md

Important. Before proceeding, please review the Knative community Code of Conduct.

If you any have questions or concerns, please contact the authors at knative-code-of-conduct@googlegroups.com.

Welcome!

Welcome to the Knative community!

This is the starting point for becoming a contributor - improving code, improving docs, giving talks, etc.

Other Documents

Introduction

Knative is a Kubernetes-based platform to deploy and manage modern serverless workloads. See the Knative documentation for in-depth information about using Knative.

Knative authors

Knative is an open source project with an active development community. The project was started by Google but has contributions from a growing number of industry-leading companies. For a current list of the authors, see Authors.

Authoring samples

Beyond the official documentation there are endless possibilities for combining tools, platforms, languages, and products. By submitting a tutorial you can share your experience and help others who are solving similar problems.

Community tutorials are stored in Markdown files under the community folder Community Samples. These documents are contributed, reviewed, and maintained by the community.

Submit a Pull Request to the community sample directory under the Knative component folder that aligns with your document. For example, Knative Serving samples are under the serving folder. A reviewer will be assigned to review your submission. They'll work with you to ensure that your submission is clear, correct, and meets the style guide, but it helps if you follow it as you write your tutorial.

Meetings and work groups

Knative has public and recorded monthly community meetings. You can see the agenda and links to previous recordings here.

Each project has one or more working groups driving the project, and Knative has a single technical oversight committee monitoring the overall project.

There's also a Knative Calendar that has all the Knative related meetings in one place.

How can I help

If you're looking for something to do to get your feet wet working on Knative, look for GitHub issues marked with the Help Wanted label:

Even if there's not an issue opened for it, we can always use more testing throughout the platform. Similarly, we can always use more docs, richer docs, insightful docs. Or maybe a cool blog post? And if you're a web developer, we could use your help in spiffing up our public-facing web site.

Questions and issues

If you're a developer, operator, or contributor trying to use Knative, the following resources are available for you:


Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.