While there's not that many documentation tasks I feel like it might be a sensible idea to start creating tasks for specific areas that need documentation as it's clear the current system where there's minimal tracking of docs and no one specifically assigned to work on doc X doesn't work. If we want to go this route and have tasks for areas that need docs/docs that need modifying then I'd agree with creating a tag to go along with it.

@John Any objections?

No objections

In T9058#183528, @Reception123 wrote:

While there's not that many documentation tasks I feel like it might be a sensible idea to start creating tasks for specific areas that need documentation as it's clear the current system where there's minimal tracking of docs and no one specifically assigned to work on doc X doesn't work. If we want to go this route and have tasks for areas that need docs/docs that need modifying then I'd agree with creating a tag to go along with it.

@John Any objections?

This is a good idea, I think, based on the recent documentation-related tasks @Universal_Omega tagged. Could this tag also be used for tasks related to documentating MediaWiki Engineering or SRE (Infrastructure) incident reports, CVEs, or various other administrative report writing? Sometimes those can get quite involved, necessitating a task on Phabricator to assign a team member and track them through to completion. Or, alternatively, would a second tag for those sort of report writing tags be better?

Incident Reports and CVEs should be tracked as part of the original task, not requiring an additional task as until necessary follow up reports and learning is done, an incident shouldn’t be deemed resolved.

For protracted cases, a workboard column may be more appropriate than a tag.

In T9058#183674, @John wrote:

Incident Reports and CVEs should be tracked as part of the original task, not requiring an additional task as until necessary follow up reports and learning is done, an incident shouldn’t be deemed resolved.

For protracted cases, a workboard column may be more appropriate than a tag.

Ah, that makes sense, yeah. I agree that a workboard column would likely be more helpful for tracking and managing protracted incidents.

In T9058#183556, @Reception123 wrote:

Documentation created.

For @Dmehus's suggestion that would be a different tag if we wanted that, since that's quite different from docs.

Thanks!