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

docs: update contributing/sigs-and-committees

Browse source
This commit is contained in:
Skyler Grey 2024-05-05 16:37:53 +00:00 committed by Anonymous User
parent 5bf22ba64d
commit 01aaf10d61
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
contributing/sigs-and-committees.md
View file

@ -1,8 +1,8 @@
---
title: SIGs and Committees
description:
description: What are they? How do they differ?
published: true
date: 2024-05-05T16:35:17.642Z
date: 2024-05-05T16:37:51.902Z
tags:
editor: markdown
dateCreated: 2024-05-05T16:35:17.642Z
@ -12,10 +12,14 @@ dateCreated: 2024-05-05T16:35:17.642Z
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.
For more information on SIGs, what SIGs exist, and how to join one, please see [our full page on SIGs](/contributing/sigs).
## 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.
For more information on committees, what committees exist, and how to join one, please see [our full page on committees](/contributing/committees).
## 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.