Knative governance and community material.
Go to file
Evan Anderson 87abd5c187
Initial commit of "Knative Migration-To-Core Process" (#229)
* Initial commit of https://docs.google.com/document/d/1M6v8w2td0QOnwZ0q-DJcX2qXva--XV9I3JBvZnTtWOQ/edit#

* Clean up warning message as well as actual links

* Clean up draft header to more formal language

* Clean up initial language to remove "graduation" terminology.
2021-03-26 09:06:20 -07:00
.github Drop unnecessary occurrences of master (#525) 2021-03-10 07:51:25 -08:00
annual_reports Adds Knative 2020 Annual Report (#403) 2020-12-17 11:51:02 -08:00
docs Automate creation of OWNERS_ALIASES (#532) 2021-03-18 23:09:54 -07:00
elections Drop unnecessary occurrences of master (#525) 2021-03-10 07:51:25 -08:00
hack Automate creation of OWNERS_ALIASES (#532) 2021-03-18 23:09:54 -07:00
icons Add icons for Serving and Eventing (#457) 2021-02-17 07:12:02 -08:00
mechanics Initial commit of "Knative Migration-To-Core Process" (#229) 2021-03-26 09:06:20 -07:00
peribolos Remove user deleted from GitHub (#543) 2021-03-23 11:21:17 -07:00
working-groups Check in initial VMT rotation (#535) 2021-03-19 02:35:54 -07:00
.gitignore Copied from docs/contributing 2019-05-07 14:09:10 -07:00
BRANDING.MD Be more explicit about not changing the logo (#417) 2021-01-25 06:25:54 -08:00
CODE-OF-CONDUCT.md Fix links, titles, frontmatter, and use fully qualified knative/docs URLs (#45) 2020-01-30 10:25:28 -08:00
CONTRIBUTING.md Drop unnecessary occurrences of master (#525) 2021-03-10 07:51:25 -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 owners 2019-05-08 16:11:50 -07:00
OWNERS_ALIASES Automate creation of OWNERS_ALIASES (#532) 2021-03-18 23:09:54 -07:00
README.md add trademark committee doc to "toc" (#534) 2021-03-22 09:00:54 -07:00
REPOSITORY-GUIDELINES.md Address grantr feedback on #149 (#151) 2021-03-11 10:37:26 -08: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
SLACK-GUIDELINES.md Run prettier after #123 (#124) 2020-04-22 07:08:40 -07:00
STEERING-COMMITTEE.md Drop unnecessary occurrences of master (#525) 2021-03-10 07:51:25 -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 Drop mattmoor from TOC groups (#519) 2021-03-08 11:09:23 -08:00
TRADEMARK-COMMITTEE.md Adds details about TM meeting (#480) 2021-03-04 10:54:16 -08:00
VALUES.md Fix links, titles, frontmatter, and use fully qualified knative/docs URLs (#45) 2020-01-30 10:25:28 -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 bi-weekly community meetings.

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

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.