From 8fe2a6abc236a98e5cc17ad7db373d0ac3f6a2d7 Mon Sep 17 00:00:00 2001 From: Zach Steindler Date: Wed, 20 Sep 2023 12:08:41 -0400 Subject: [PATCH] Follow-on update to SIG process Based on feedback from https://github.com/ossf/tac/pull/182 Signed-off-by: Zach Steindler --- process/sig-lifecycle.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/process/sig-lifecycle.md b/process/sig-lifecycle.md index c3ef3e6a..ca465f5a 100644 --- a/process/sig-lifecycle.md +++ b/process/sig-lifecycle.md @@ -14,6 +14,9 @@ The SIG life cycle begins with interested contributors deciding to undertake thi ## To become `Active`: +* There must be a proposal of the focus, intent, goals, and/or deliverables of the SIG + * This could be in an Issue of the governing body's repository, a shared document, or in a README of the SIGs repository (if they have one) +* The initial membership should be at least 3 individuals from 2 different organizations * A governing body must agree to govern the SIG * The governing body may have its membership vote, with notice given at the meeting prior to the vote @@ -23,6 +26,7 @@ The SIG life cycle begins with interested contributors deciding to undertake thi * SIGs may have regular meetings separate from their governing body, if so: * They should appear on the OpenSSF calendar * They should have a document with upcoming agendas and notes from past meetings +* If the SIG starts to produce code, they should consider becoming a [project](./project-lifecycle.md) instead ## To become `End-of-Life`: