Django 3.2 Upgrade: Roles and Communication

 

Team and Roles

 

 

 

 

@Jeremy Bowman

Project Tech Lead

@Natalia Berdnikov

Project Manager

Arbi-BOM squad at Arbisoft, led by @Jeremy Bowman

Development, reviewing, deployment, verification

Owning squads at edX

Develop, review, merge, or test, depending on selection in https://openedx.atlassian.net/wiki/spaces/AC/pages/2891841748

Open edX Community members

Development

Open edX Core Committers

Development, review, merging

Community Engineering at edX, led by @Sarina Canelake (Do Not Use) (Deactivated):

Promote with the community, encourage Core Committers candidates to participate

edX Engineering Directors, JP

Stakeholder

@Nimisha Asthagiri (Deactivated)

Stakeholder

edX Build Test Release Working Group

Stakeholder

Open edX Community Members

Stakeholder (consumers of named releases)

Communication

 

Tracking and Reporting

All tickets are pulled into the Upgrade Board. It includes tickets withinhttps://openedx.atlassian.net/browse/BOM-1878 (by Arbi-BOM), tickets with django-3.2 label (from owning squads), and OSPR tickets with DU3.2 tag in the title (from the Open edX community). Issues available for the Open edX community to help with (and PRs for work they’ve already started) will also be collected in the Django 3.2 Upgrade GitHub Project board.