Home

Docathon scheduled for 12/13/2019

12/6 - Sync meeting
12/11 - Training, record and post training
12/13 - Day of docathon

Summary	Description
Who	Azure DevOps Product team PMs and engineers - Jeff Beehler main point of contact
What	Spend a day to address outstanding GitHub issues for the vsts-docs-pr; goal is to close 80% or more issues. Current issue count is 894 (12/4)
Where	TBD, Online (Are we reserving any conference rooms for people to work in)
Why	GitHub issues identify customer pain points and we want to be customer advocates by addressing these issues.

Filter the list of issues by your subject matter expertise and Priority - use Labels to filter (demo in training)
Address the latest issues first working towards the oldest issues
Work on Pri2 issues second and then Pri3 issues, always working from latest to oldest.
Assign the issue to yourself to indicate to others that it is being addressed

Types of issues	How to close	Notes
Information is not accurate, needs update	Action 1 or 2	If issue requires 30 minutes or more to fix, do 2
Information is incomplete	Action 1 or 2	If issue requires 30 minutes or more to fix, do 2
Issue is a product suggestion	Action 3
Issue requires support	Action 4
Article has a broken link	Action 5
Correction suggested invalidates current guidance	Action 6

Fix the article by providing more information, clarifying information, or other. All articles to be fixed in the azure-devops-docs-pr repo (or possibily azure-devops-server-docs-pr repo). Enter a comment to the issuer that you are addressing the issue and then Close.
Open a backlog item - doc bug or User Story - to address the issue within the next 3 months (may need a followup meeting to triage these bugs/stories). Enter a comment to the issuer that you've created a backlog item to address the issue and then Close.
Refer issuer to Developer Community website (Product feature) and close the issue (canned response)
Refer issuer to Developer Community website (Support ) and close the issue (canned response)
Assign broken-link label and Assign the issue to a content writer to address (KathrynEE, ChComley, )
Close the issue as non-actionable and label as non-actionable. (canned response) Reasons for something being non-actionable: a. The guidance provided is correct b. Issuer doesn't provide sufficient information to take action (e.g., doesn't provide a topic as reference) c. Issue is so old the content has become irrelevant