auxolotl/wiki
20
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Activity

docs: create contributing/sigs-and-committees

Browse source
This commit is contained in:
Skyler Grey 2024-05-05 16:35:19 +00:00 committed by Anonymous User
parent 8b4f47a107
commit 5bf22ba64d
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
contributing/sigs-and-committees.md Normal file
View file

@ -0,0 +1,25 @@
---
title: SIGs and Committees
description:
published: true
date: 2024-05-05T16:35:17.642Z
tags:
editor: markdown
dateCreated: 2024-05-05T16:35:17.642Z
---
## What's a SIG?
SIGs, or "Special Interest Groups" are groups of people who focus on a particular area. They have specific projects and tasks with clear "things" as outcomes. For example, the Core Special Interest Group maintains vital packages and is involved in creating templates for new systems, and the Documentation Special Interest Group maintains the Wiki.
## What's a committee?
Committees handle the direction of the project in a particular area. For example, the Security Committee handles security in the whole project, setting guidelines for how SIGs should handle security.
## What's the difference?
SIGs are generally more focused, looking at their tangible projects specifically. Committees might have whole-project reach by setting guidelines for how SIGs operate, and normally have less tangible task and project outcomes.
## Where does this come from?
The ideas for commitees and SIGs are inspired by [the kubernetes governance](https://github.com/kubernetes/community). If you'd like to see how similar ideas work in practice we'd highly recommend looking at their community.