Apply suggestions from code review

Signed-off-by: Mihai Maruseac <mihai.maruseac@gmail.com>
ossf · Jun 22, 2024 · f040bdd · f040bdd
1 parent c5a4e4d
commit f040bdd
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/process/Technical_Initiative_Lifecycle.md b/process/Technical_Initiative_Lifecycle.md
@@ -21,7 +21,7 @@ flowchart TD
 
 The process is designed to be flexible to enable a Project to move in and out of a Working Group as deemed appropriate by the TAC.
 
-A SIG can be developed within a WG or Project to address a specific need. Note that a SIG cannot produce code or specifications.
+A SIG can be developed within a WG or Project to address a specific need. Note that a SIG purpose is not to primary produce code or specifications (it can produce them as secondary goals, or as experimental POCs).
 
 # II. Lifecycle
 

diff --git a/process/sig-lifecycle.md b/process/sig-lifecycle.md
@@ -22,7 +22,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 or specifications, they must migrate to a [project](./project-lifecycle.md) instead
+* If the SIG starts to produce code or specifications, they should consider becoming a [project](./project-lifecycle.md) instead, especially if this becomes the main scope of the SIG.
 
 ## To become `Incubating`: