Skip to content

Latest commit

 

History

History
121 lines (101 loc) · 5.88 KB

organizational-structure-overview.md

File metadata and controls

121 lines (101 loc) · 5.88 KB
Raw

OpenSSF Governance & Org Structure

OpenSSF Charter

The overall governance of the OpenSSF is defined in the OpenSSF Charter.

Definitions

The OpenSSF is comprised of instances of the following categories of official groups:

  • The Governing Board (GB) oversees the budget and legal status/structure of the OpenSSF. Board meetings may or may not be open to the public.
  • Committees are formed by, and report to, the Board. Broadly speaking, Committees handle non-technical matters as needed by the GB, wherein a named set of people are tasked with handling a specific objective. Like the Board meetings, Committee meetings may or may not be open to the public.
  • The Technical Advisory Council (TAC) is responsible for the general success of all Technical Initiatives (defined below). TAC meetings are generally open to the public, with the exception of special sessions.
  • Technical Initiatives are groups formed in support of the overall mission of the OpenSSF. Technical Initiatives include Working Groups (WG), Special Interest Groups (SIG), Projects, and Services governed by their own Charters with various objectives, reporting relationships, and funding models described below.
    • All Technical Initiatives are open groups focused on a technical objective, with transparent proceedings that are open to the public, and vary in their objectives.
    • Technical Initiatives usually manage one or more GitHub repos of their own and may have separate meetings.
  • Working Groups (WG) are the primary organizational element of Technical Initiatives within the OpenSSF. Working Groups focus on developing deliverables such as guides, specifications, and educational material, or conducting initiatives such as an education outreach.
    • While a WG does not produce open source software as a primary artifact, it may oversee Projects that do.
    • A WG may also launch Special Interest Groups (SIG) to perform specific tasks other than creating software.
    • WGs often include some open source code, or use licensed software, in fulfilment of their Charter.
  • A Project is a Technical Initiative focused on the development and ongoing support of open source licensed software (source code) or specification and its supporting artifacts (technical documentation, etc).
  • Special Interest Groups (SIG) are bound to achieving a very specific goal. These groups may be terminated upon completion of their designating tasking or continued for larger and ongoing efforts. The creation of a SIG must dictate the focus, intent, goals, and deliverable(s) as appropriate. SIGs may report to a WG or directly to the TAC.
  • A Technical Deliverable is any technical content produced by a Technical Initiative, such as open source licensed software, a specification, or a technical guide.
    • Each Project shall have at least one Technical Deliverable including open source licensed software or specification; this is what defines a Project as distinct from other Technical Initiatives such as SIGs.
    • A Service is a publicly-run instance of software as a service, and is another form of Technical Deliverable distinct from the release of open source licensed software. This may be an operational output of a Technical Initiative in which software is either built or acquired to support or automate OSSF transactions.

The following table describes the main types of groups and their characteristics.

Initiative Expected lifespan Primary output Reporting relationship Economic model
Working Group (WG) unbounded not software to the TAC normative
Project unbounded software or specification either TAC or WG normative
Special Interest Group (WG) bounded not software either TAC or WG normative

TODO

  • define and document the governance relationships for affiliated projects: Alpha/Omega, GNU Toolchain Infrastructure
  • define Contributors in a consistent way, so that electorate membership can be consistently, and ideally procedurally, determined
  • define criteria for approving or disapproving the Charters of TAC-subordinate bodies

Organizational Chart

Legend:

  • rounded box: entity is created by the OpenSSF governing charter
  • square box: entity is created by the relevant body
  • logical groupings are by convention rather than by charter
flowchart LR
    GB([Governing Board])

    subgraph subC[Committees]
        direction LR
        Budget[Budget and Finance]
        Market[Marketing]
        Plan[Planning and Advisory]
        Policy[Public Policy]
    end
    GB <==> subC
    GB ==> TAC([Technical Advisory Council])

    subgraph WG[Working Groups]
        AI[AI/ML Security]
        BP[Best Practices]
        DEI[Diversity, Equity & Inclusion]
        EU[End Users]
        MM[Metrics & Metadata]
        REP[Securing Software Repos]
        SCI[Supply Chain Integrity]
        SCP[Securing Critical Projects]
        ST[Security Tooling]
        VD[Vulnerability Disclosures]
    end

    subgraph projects[Projects]
       Scorecard[Scorecard]
       BPB[Best Practices Badge]
       SI[Security Insights]
       SM[Security Metrics]
       Rstuf[Repository Service for TUF]
       Gittuf[gittuf]
       GUAC[GUAC]
       SLSA[SLSA]
       S2C2F
       Allstar[Allstar]
       Sigstore[sigstore]
       CS[Criticality Score]
       PA[Package Analysis]
       PF[Package Feeds]
       FI[Fuzz Introspector]
       Protobom[protobom]
       Sbomit[sbomit]
       OpenVEX[OpenVEX]
       OSV[OSV Schema]
    end

    TAC ==> WG
    TAC ==> Sigstore

    BP --> Scorecard
    BP --> BPB
    MM --> SI
    MM --> SM
    REP --> Rstuf
    SCI --> Gittuf
    SCI --> GUAC
    SCI --> S2C2F
    SCI --> SLSA
    SCP --> Allstar
    SCP --> CS
    SCP --> PA
    SCP --> PF
    ST --> FI
    ST --> Protobom
    ST --> Sbomit
    VD --> OpenVEX
    VD --> OSV
Loading