About the Knative community¶
This page provides links to documents for common Knative community practices and a description of Knative's audience.
This section links to documents about our values.
Knative project values: shared goals and values for the community.
Knative team values: the goals and values we hold as a team.
This section links to documents about how the Knative community is governed.
Knative has public and recorded monthly 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.
Governance: the Knative governance framework.
Community roles: describes the roles individuals can assume within the Knative community such as member, approver, or working group lead.
Working groups: provides information about our various working groups.
Steering Committee (SC): describes our steering committee.
Technical Oversight Committee (TOC): describes our technical oversight committee.
Trademark Committee: describes our trademark committee.
Annual reports: lists previous annual reports.
This section links to documents for common Knative community processes.
At the moment, these practices (except for the formation of Working Groups and Lazy Consensus) are recommendations that individual working groups can choose to adopt, rather than requirements. Each working group should document their processes; either in their own repo or in a pointer to these docs.
Reviewing and Merging Pull Requests: how we manage pull requests.
Working group processes: how working groups operate.
SC election process: elcection process for our steering committee.
TOC election process: election process for our technical oversight committee.
Repository Guidelines: how we create and remove core repositories.
Feature tracks: outlines the process for adding non-trivial features.
Golang policy: principles regarding the Golang version Knative tests and releases with.
Release principles: release principles including information about support and feature phases.
Release schedule: Knative past and future release dates.
Sunsetting features: process to sunset features that are getting no apparent usage, but are time consuming to maintain.
The Knative community calendar (iCal export file) contains events that provide the opportunity to learn more about Knative and meet other users and contributors. This includes Working Group, Steering Committee, and other community meetings.
Events don't have to be organized by the Knative project to be added to the calendar. If you want to add an event to the calendar please send an email to email@example.com or post to the #community channel in the Knative Slack workspace.
Knative is designed for different personas:
Knative components offer developers Kubernetes-native APIs for deploying serverless-style functions, applications, and containers to an auto-scaling runtime.
To join the conversation, head over to the Knative users Google group.
Knative components are intended to be integrated into more polished products that cloud service providers or in-house teams in large enterprises can then operate.
Any enterprise or cloud provider can adopt Knative components into their own systems and pass the benefits along to their customers.
With a clear project scope, lightweight governance model, and clean lines of separation between pluggable components, the Knative project establishes an efficient contributor workflow.
Knative is a diverse, open, and inclusive community. Your own path to becoming a Knative contributor can begin in any of the following components:
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.