Knative working group

Most community activity is organized into working groups.

Working groups follow the contributing guidelines although each of these groups may operate a little differently depending on their needs and workflow.

When the need arises, a new working group can be created. See the working group processes for working group proposal and creation procedures.

The working groups generate design docs which are kept in a shared drive and are available for anyone to read and comment on. The shared drive currently grants read access to knative-users@ and edit and comment access to the knative-dev@ Google group.

Some working groups (mostly those with a plug-in or extension model) end up responsible for a set of GitHub repos, one for each extension. This allows for easier dependency management; in these cases, one or more repo prefix names will be recorded as canonical “extension names” to allow WGs to be responsible for their own namespace without needing to get TOC approval for each repo name.

Additionally, all working groups should hold regular meetings, which should be added to the shared knative calendar WG leads should have access to be able to create and update events on this calendar, and should invite knative-dev@googlegroups.com to working group meetings.

Calendar import

If you’re using Google Calendar, the above should work. If you’re using some other system (Apple Calendar or Outlook, for example), here is an iCal export of the community calendar.

Working Groups

The current working groups are:

API Core

API resources, validation, and semantics.

Artifact Link
Charter TODO (historical, was created before formal WG process)
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Wednesdays 10:30a-11:00a PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repos knative/serving
Slack Channel #serving-api
Github Team WG Leads @knative/api-core-wg-leads
  Leads Company Profile
Dave Protasowski VMware dprotaso
  Emeritus Leads Profile Duration
Dan Gerdesmeier dgerd 2019-2020
Matt Moore mattmoor 2018-2021

Client

Client, CLI, client libraries, and client conventions

Artifact Link
Charter Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesdays, alternating between 10:30a-11:00a Pacific and 3:30p-4:00p Central European every two weeks
Calendar Invitation
Meeting Notes Notes
Document Folder Folder
Repos knative/client, kn-plugin-*
Slack Channel #cli
Github Team WG leads @knative/client-wg-leads
  Leads Company Profile
David Simansky Red Hat dsimansk
Navid Shaikh VMware navidshaikh
Roland Huß Red Hat rhuss
  Emeritus Leads Profile Duration
Naomi Seyfer sixolet 2018-2021
Dmitriy Kalinin cppforlife 2018-2020

Documentation + User Experience

User Experience concerns across Knative components and Knative documentation, especially the Docs repo.

Artifact Link
Charter / Mission Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesday from 9:30-10:30am PST
Calendar
Meeting Notes Notes
Roadmap Roadmap
Document Folder Folder
Slack Channel #user-experience + #docs
Github Repository /ux + /docs
Github Team WG leads @knative/ux-wg-leads
  Leads Company Profile
Omer Bensaadon VMware omerbensaadon
Carlos Santana IBM csantanapr

Eventing

Event sources, bindings, FaaS framework, and orchestration

Artifact Link
Charter / Mission Enable asynchronous application development through event delivery from anywhere.
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Wednesdays 9:00a-9:30a PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repos knative/eventing, eventing-*
Slack Channel #eventing
Github Team WG leads @knative/eventing-wg-leads
  Leads Company Profile
Lionel Villard (Technical) IBM lionelvillard
Ahmed Abdalla (Execution) Red Hat devguyio
  Emeritus Leads Profile Duration
Grant Rodgers (Technical) grantr 2020-2021
Ville Aikas (Technical) vaikas 2018-2021

Event Delivery

Event delivery data plane.

Artifact Link
Charter Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesdays 8:30a-9:00a PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repos knative/eventing, knative/eventing-contrib, (shares eventing-*)
Slack Channel #eventing-delivery
Github Team WG leads @knative/channel-wg-leads
  Leads Company Profile
Matthias Wessendorf Red Hat matzew

Eventing Sources

Event producers and frameworks.

Artifact Link
Charter Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesdays 8:30a-9:00a PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repo prefixes (shares eventing-* with the eventing WG)
Slack Channel #eventing-sources
Github Team WG leads @knative/source-wg-leads
  Leads Company Profile
Scott Nichols VMware n3wscott
Lionel Villard IBM lionelvillard

Networking

Inbound and outbound network connectivity for serving workloads. Specific areas of interest include: load balancing, routing, DNS configuration and TLS support.

Artifact Link
Charter TODO (historical, was created before formal WG process)
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Thursdays at 9:00a-9:30a PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repos net-*
Slack Channel #networking
Github Team WG leads @knative/networking-wg-leads
  Leads Company Profile
Kenjiro Nakayama Red Hat nak3
Zhimin Xiang Google ZhiminXiang
  Emeritus Leads Profile Duration
Nghia Tran tcnghia 2018-2021

Operations

Managing, assessing system health and maintaining Knative clusters

Artifact Link
Charter Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesdays at 10:00am PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repo prefixes
Slack Channel #operations
Github Team WG leads @knative/operations-wg-leads
  Leads Company Profile
Vincent Hou IBM houshengbo

Productivity

Project health, test framework, continuous integration & deployment, release, performance/scale/load testing infrastructure

Artifact Link
Charter Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Thursdays, 10am PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repo prefixes actions-*
Repos knative/hack, knative/test-infra, knative-sandbox/.github, knative-sandbox/kperf, knative-sandbox/reconciler-test, knative-sandbox/knobots, knative-sandbox/actions-downstream-test
Slack Channel #productivity
Github Team WG leads @knative/productivity-wg-leads
  Leads Company Profile
Chi Zhang Google chizhg
Scott Nichols VMware n3wscott

Scaling

Autoscaling behavior of Knative Serving

Artifact Link
Charter TODO (historical, was created before formal WG process)
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Wednesdays at 9:30am PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repo prefixes
Slack Channel #autoscaling
Github Team WG leads @knative/autoscaling-wg-leads
  Leads Company Profile
Markus Thömmes Red Hat markusthoemmes
Victor Agababov Google vagababov

Security

Security concerns across Knative components

Artifact Link
Charter / Mission Charter
Forum knative-dev@
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Tuesdays at 9am PST
Calendar
Meeting Notes Notes
Document Folder Folder
Repo prefixes
Slack Channel #security
Github Team WG leads @knative/security-wg-leads
  Leads Company Profile
Evan Anderson VMware evankanderson
Julian Friedman IBM julz

Emeritus Working Groups

Build

  Leads Profile Duration
Jason Hall ImJasonH 2018-2019

Observability

  Leads Profile Duration
Mustafa Demirhan mdemirhan 2018-2019

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.