Each IDA we plan to upgrade to Django 3.2 has an owning squad within edX.
Project Lead Jeremy Bowman (Deactivated) and Project Manager Natalia Berdnikov (Deactivated) have developed a “menu of options” for owning squads, offering various levels of involvement. Each squad can choose from options below how involved they want to be in the upgrade work.
Green cells indicate work that would be done by the project team, lead by Jeremy Bowman (Deactivated).
Yellow cells indicate work owning squad would do.
Participation Options
Options | Plan and Automate | Create PRs | Review | Merge | Deploy | Test |
|---|---|---|---|---|---|---|
1. Hands-off | By project team | By project team | By project team | By project team (with notice) | By project team | By project team |
2. Trust but verify | By project team | By project team | By project team | By project team (with notice) | Need to do | Need to do |
3. Review everything | By project team | By project team | Need to do | Need to do | Need to do | Need to do |
4. DIY | By project team | Need to do | Need to do | Need to do | Need to do | Need to do |
Participation Options Description
Option 1. Hand-off
Project team does everything (development through deployment and testing), owning squad is not involved, aside from possible advice if project team gets stuck and needs help. Project team will give owning squad advance notice before merging.
This option allows the owning squad to spend little to none time on this project, and concentrate on other work. This option is good for areas of code that don’t require too much domain knowledge and can be easily done by the project team.
Option 2. Trust but verify
Project team creates and (after providing advance notice) merges PRs, owning team deploys and tests.
This option is a compromise and allows the owning team to save time on development, while ensuring the end result.
Option 3. Review everything
Project team creates PRs, owning squad reviews, deploys, and tests.
This option is compromise and provides owning the owning team with the benefit of outsourcing the bulk of work to the project team, while still closely supervising end result and having full control over it. This option might be good for teams who have a more complex area of code.
Option 4. DIY
Owning squad does everything (use project plan and automation provided by project team, deployment, testing, etc.). Project team supervises timeline and status.
This option requires most time from the owning squad, while at the same time ensuring that upgrade is done exactly at the owning team wants. This option might be good for areas of code that require a lot of domain knowledge or are otherwise complex.