Publication process

Happy path

1. Submission received by tool vendor as a PR
2. Reviewer assign to self
3. Reviewer assign milestones "In review" milestone
4. Reviewer ensures there is no prior rejected submission for the same tool - search Out of Scope PRs
5. Reviewer completes review
6. Reviewer assigns to "iadawn Kevin White" (Team reviewer)
7. Reviewer assigns milestone "Team review"
8. Team reviewer completes review
9. Team reviewer assigns to "shawna-slh Shawn Lawton Henry" (Website manager)
10. Team reviewer assigns to milestone "Ready to publish"
11. Team reviewer sends successful email to vendor contact
12. Website manager merges PR and publishes
13. Website manager assigns milestone "Published"

Additional input from vendor

1. Reviewer assigns clears assignees
2. Reviewer sends email with requested information to vendor contact
3. Reviewer assigns to milestone "Waiting for vendor response"
4. Vendor responds
5. Reviewer assigns to self
6. Reviewer assigns to milestone "In review" or "Team review" as appropriate
7. Progress as for Happy path

Additional input from vendor after initial publication

If a change or a clarification to the features of the tool is received after the tool has been published, then follow this process.

1. Reviewer creates a new branch against the master branch
2. Reviewer makes and commits appropriate changes to the tool record
3. Reviewer creates a PR for the changes
4. Progress as from stage 6 in the Happy Path

Additional input required from Team

1. Reviewer assigns to "iadawn Kevin White" (Team reviewer)
2. Reviewer assigns to "Needs more attention" milestone
3. Team reviewer responds
4. Team reviewer assigns to Reviewer
5. Team reviewer assigns milestone "In review"
6. Progress as for Happy path

Spam submission

1. Reviewer determines that submission is spam
2. Reviewer assigns to "iadawn Kevin White" (Team reviewer)
3. Reviewer comments that submission is spam
4. Reviewer assigns milestone "Out of scope"
5. Team reviewer closes PR and deletes branch. Note that there is no way to delete the PR itself.

Not in scope

1. Reviewer determines that submission is not in scope
2. Reviewer clears assignees
3. Reviewer assigns milestone "Out of scope"
4. Reviewer responds to vendor contact

Vendor withdraws submission

1. Reviewer or Website manager clears assignees
2. Reviewer or Website manager assigns milestone "Withdrawn"

Email templates

• [TODO] Successful submission
• [TODO] Rejected submission - out of scope
• [TODO] Request for additional information