Changes between Version 36 and Version 37 of SecurityTeam


Ignore:
Timestamp:
Sep 10, 2026, 2:36:34 AM (5 days ago)
Author:
Sarah Boyce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SecurityTeam

    v36 v37  
    22
    33This page is used by the security team to help with process of analyzing and replying to security reports.
     4
     5== How to add a member to the Security Team ==
     6
     7Once there is agreement from the team that the new member can join, they can be added to the Security Team.
     8
     9You will need:
     10* Their preferred email address
     11* Their GitHub username
     12
     13If you do not have permissions to do any of the below, email ops@djangoproject.com
     14* Add their GitHub account to the [https://github.com/orgs/django/teams/django-security-team Security Team] on GitHub.
     15* Add them to the [https://groups.google.com/a/djangoproject.com/g/security/members Security Team] Google group.
     16* Add them to the DSF slack workspace with access to #security-private private Slack channel
     17* Add them to the Security Team on the [https://www.djangoproject.com/admin/members/team/ Django website]. Before they can be officially added on the website as a member of the team, they will need DSF membership. [https://docs.google.com/forms/d/e/1FAIpQLSd5lbWxAO-sylEEjHVKBNIpmHlhdJRf0_LCo8glnLUWd-Q2Sw/viewform Nominate them for DSF membership] if they are not already a member.
     18* Add them to the Security Team on the [https://github.com/django/dsf-working-groups/blob/main/active/security.md working group] as a "Report triager"
     19
     20Finally send a welcome email to the new member with security@djangoproject.com in cc.
     21
     22The welcome email can be found in Django's private security repository wiki.
    423
    524== Canned Responses ==
Back to Top