Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clarity wrt SIGs that need to be projects #348

Merged
merged 4 commits into from
Jun 28, 2024
Merged

Add clarity wrt SIGs that need to be projects #348

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c5a4e4d
Add clarity wrt SIGs that need to be projects
mihaimaruseac Jun 20, 2024
f040bdd
Apply suggestions from code review
mihaimaruseac Jun 22, 2024
1468b65
Accept revision
mihaimaruseac Jun 27, 2024
8220606
Update the changelog to match PR
mihaimaruseac Jun 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion process/Technical_Initiative_Lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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).
mihaimaruseac marked this conversation as resolved.
Show resolved Hide resolved

# II. Lifecycle

Expand Down
2 changes: 1 addition & 1 deletion process/sig-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 should consider becoming 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`:

Expand Down
Loading