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

Update WG Lifecycle #212

Merged
merged 2 commits into from
Nov 16, 2023
Merged

Update WG Lifecycle #212

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
66d3488
Update WG Lifecycle
lehors Nov 3, 2023
702d1c1
Address several comments and include leftover changes
lehors Nov 3, 2023
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
33 changes: 24 additions & 9 deletions process/working-group-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,29 @@ However, if no existing effort covers the topic feel free to make use of the exi

Please note that running a WG successfully requires an extended effort. Be prepared to commit at least several hours per week for a year or more.

The WG Life Cycle begins with establishing commitments from other interested contributors then making a proposal to the TAC. If accepted, the WG will begin as `Incubating`. This is a boot strapping phase for the group to adopt OpenSSF community policies and norms. Once those are met the group becomes `Active` and will be fully recognized in OpenSSF. Either upon completing its objectives or no longer making forward progress a project will move to `End-of-Life`. The details for each phase follow.
The WG Life Cycle begins with establishing commitments from other interested contributors then making a proposal to the TAC. If accepted, the WG will begin as `Sandbox`. This is a boot strapping phase for the group to define and document what their goals are.
Once the WG has further defined its goals and garnered enough support it can apply to move to 'Incubating' stage. This is the phase for the WG to adopt OpenSSF community policies and norms. Once those are met the group becomes `Graduated` and will be fully recognized in OpenSSF. Either upon completing its objectives or no longer making forward progress a project will move to `Archived`. The details for each phase follow.

## To become `Incubating`:
## To become `Sandbox`:

* Proposal of scope for review by TAC
* This is to help ensure limited overlap with existing WG
* This is to help ensure limited overlap with existing WGs
* Have at least 3 interested individuals from different organizations supporting the proposal
* TAC will vote to approve or provide constructive guidance

## Once `Sandbox`:

* The TAC will add the WG to the list of WGs to its README.
* If the WG has meetings at this stage:
* They should appear on the OpenSSF calendar
* The WG should have a document with upcoming agendas and notes from past meetings
* The WG should develop a charter or mission statement defining its goals and seek a TAC sponsor.

## To become `Incubating`:

* Have a charter or mission statement for review by TAC
* Have met at least 5 times
* For these, meeting notes (or ideally recordings) are public
* For these, meeting notes (or ideally recordings) must be public
* Have at least 5 interested individuals from at least 3 different organizations attending regularly
* 1 TAC sponsor
* TAC sponsor agrees to attend WG meetings regularly
Expand All @@ -33,31 +48,31 @@ The WG Life Cycle begins with establishing commitments from other interested con
* Can request funding/other resources (subject to TAC/GB approval)
* NOTE: _At the time of this draft, funding and resources beyond collaboration tools have not been established in the OpenSSF. WGs should expect that their main resource is the community contributions they are able to recruit._

## To become `Active`:
## To become `Graduated`:

* Have received TAC approval of the README.md per `Incubating` requirements above
* Have met at least 4 times over a period of at least 2 months since becoming `Incubating`
* Have at least 5 regular members from at least 3 different organizations attending regularly as recorded in meeting minutes.
* Request TAC approval. TAC will vote to approve or provide constructive guidance

## To remain `Active`:
## To remain `Graduated`:

A WG is expected to continue operating per the above guidelines, and to provide the TAC with quarterly status updates, and to approach the TAC when seeking approval of substantial changes (such as when accepting or promoting new Projects).

## Once `Active`:
## Once `Graduated`:

* (same as incubating, plus)
* Have at least annual goals and metrics for success

## To become `End-of-Life`:
## To become `Archived`:

* Work has stopped
* The WG has completed its chartered deliverables
or
* The WG is no longer progressing on its deliverables as determined by the TAC
* In either case the TAC will vote to formally end the WG.

## Once `End-of-Life`:
## Once `Archived`:

* All significant artifacts should be archived as appropriate
* Meeting series removed from calendar, mail list closed, and any other administrative items
Expand Down
Loading