22 lines
1.0 KiB
Markdown
22 lines
1.0 KiB
Markdown
|
---
|
||
|
|
title: SIG (special interest group)
|
||
|
|
id: sig
|
||
|
|
date: 2018-04-12
|
||
|
|
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
|
||
|
|
short_description: >
|
||
|
|
Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
|
||
|
|
|
||
|
|
aka:
|
||
|
|
tags:
|
||
|
|
- community
|
||
|
|
---
|
||
|
|
{{< glossary_tooltip text="Community members" term_id="member" >}} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
|
||
|
|
|
||
|
|
<!--more-->
|
||
|
|
|
||
|
|
Members within a SIG have a shared interest in advancing a specific area, such as architecture, API machinery, or documentation.
|
||
|
|
SIGs must follow the [SIG Governance](https://github.com/kubernetes/community/blob/master/sig-governance.md) guidelines but can have their own contribution policy and channels of communication.
|
||
|
|
|
||
|
|
For more information, see the [kubernetes/community](https://github.com/kubernetes/community) repo and the current list of [SIGs and Working Groups](https://github.com/kubernetes/community/blob/master/sig-list.md).
|
||
|
|
|