Skip to content

Clarify delegation of security-related policies to the Security Subproject #281

@afshin

Description

@afshin

The Jupyter Security subproject, as currently recognized in the governance docs, has the same rights and responsibilities as other Jupyter subprojects. But the nature of the work they do (cf. a draft charter) often cuts across multiple subprojects and would ordinarily require either:

  • a Jupyter Enhancement Proposal (JEP) for the SSC to vote on
  • a change to these governance docs for the SSC + EC to vote on

To improve the friction this process can cause in creating coherent security strategies, we should update these governance docs with a short mission statement to indicate the consent of the EC and the SSC to delegate security policies to this subproject.

Once the Jupyter Security subproject as a group have an idea of what they think the language in the governance docs should be, someone from that team could open a PR here and open a vote to continue.

Please comment here if you have thoughts on this issue, or comment on the PR linked above.

cc: @krassowski @choldgraf @rpwagner because we spoke about this subject during EC office hours yesterday (12 June 2025).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions