Skip to content

Latest commit

 

History

History
48 lines (34 loc) · 2.31 KB

Technical_Initiative_Lifecycle.md

File metadata and controls

48 lines (34 loc) · 2.31 KB
Raw

I. Overview

This document describes the Open Source Security Foundation (OpenSSF) lifecycle process for Technical Initiatives (TI) which include Working Groups (WG) (non-software and non-specification focused), Projects (developing code or specifications), and Special Interest Groups (SIG).

The authority that governs this process is as follows:

The parent organizational structure grants governance to the downward entity in the organizational structure. In turn the receiving Working Group, Project, or SIG reports health, participation, outcomes, statuses, etc up the chain.

flowchart TD
    A[Governing Board] <--> B[TAC]
    B <--> C[Working Group]
    B <--> E[Working Group]
    C <--> D[Project]
    B <--> F[Project]
    B <--> G[Project]
    E <--> H[Project]
    E <--> I[SIG]

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.

II. Lifecycle

All Technical Initiatives follow a common lifecycle, with 4 stages:

  • Sandbox - for new efforts within the Foundation seeking to get started out within a community of like-minded contributors
  • Incubating - for more mature and organized groups that have participated in the community for some period of time
  • Graduated - for mature efforts that have a proven track-record of deliverables and adding value to the community
  • Archived - for groups that either are feature-complete and retired, or that no longer has active contributions occurring
flowchart LR
    A[Sandbox] --> B[Incubating]
    B --> C[Graduated]
    C --> D[Archived]

Each type of TI has equivalent, but slightly different requirements and benefits, depending on their stage in the lifecycle as defined below:

To see what the expected requirements ("Gives") and benefits ("Gets") for a TI to achieve at a given lifecycle stage, refer to the TI Gives and Gets page for more information. Each lifecycle stage has listed what they must do or produce and a list of benefits for each level of maturity in our proceeses.