Suggestion: Start using Danger to suggest technical writers
Problem to solve
As the team grows and changes, can we make it easier for our engineers to assign/ping an appropriate technical writer for their MRs?
Proposal
I think we should look into expanding the Danger Roulette message to contain a line suggesting a technical writer. It can be as simple as choosing based on DevOps stage:
Are you including docs in this MR? If so, feel free to ping {technical writer}
(chosen due to {devops::stagename} label) when the docs are ready for review.
You may choose a different technical writer if desired, or if {technical writer} is OOO.
A future iteration could enable the ability to divide the work between is the current expert, and a TW new to the group/stage. Imagine 80% of the time the expert is suggested, 20% of the time the "apprentice" is suggested. As the new TW gets up to speed, it can go to 50/50, then 100% when the new TW is suitably up to speed, as an expanded idea.
There is no need to be strict about this. The Engineers seem to be making good use of the Danger Roulette, and they should be adding docs with feature changes already, so letting them know ALL the suggested reviewers at the same time and in the same place seems to make sense.