Page MenuHomePhabricator

Assure that documentation about communities and engagement processes is relevant and up to date
Open, Stalled, NormalPublic

Description

Team goal, to maximise the utility of all documentation that is related to community engagement processes, for the benefit of all movement participants

  • Consult stakeholders, about their painpoints, requests, and triumphs, for this type of documentation
  • Decide on a vision for this documentation
  • Define the scope of the documentation we (CE dept) maintain, assist with, or utilize
  • Create an Index & Table of Contents of these pages
  • Determine the best locations for the existing & missing documentation
  • Create tasks for all gaps and outdated pages (if too big to fix in the moment)

Event Timeline

Quiddity triaged this task as Normal priority.Aug 27 2018, 7:57 PM
Quiddity created this task.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 27 2018, 7:57 PM
Qgil added a subscriber: Qgil.Sep 19 2018, 12:04 PM

What about polishing this task as a goal and making it a team goal for the next quarter?

About the description. This is the "backbone" goal that we discussed, correct? If it is, I think these tasks are key:

  • Agree on the vision for this documentation. I realize that after talking so much about ity, we might not even have the same idea in mind. I'm thinking of a manual with an index maintained in one public wiki, with an appendix for WMF internal documentation located in office.wiki.
  • Define the scope of the documentation we maintain. What falls in, what falls out.
  • Define an index for this documentation, to be initially located at the "Working_with_communities" page. By index I mean a classical index. I think our inspiration should be Wikibooks. In comparison, "Map of the English Wikipedia's help pages" looks like a documentation dystopia? :)
  • Decide a location of this documentation that makes sense. Anything not WMF internal should be probably public and be in one wiki. Internal WMF documentation should link to public pages, not overlap / duplicate them.
Qgil moved this task from Backlog to To do on the CommRel-Documentation board.Sep 21 2018, 2:51 PM
Qgil added a project: Goal.
Quiddity updated the task description. (Show Details)Oct 3 2018, 12:51 AM
Quiddity updated the task description. (Show Details)Oct 3 2018, 12:56 AM
Qgil updated the task description. (Show Details)Oct 4 2018, 11:22 AM

I'm not sure how sequential or parallel you expect this process to be, but I suggested to start with stakeholders and vision.

Qgil added a comment.Oct 11 2018, 10:21 AM

About scope, one task to challenge our assumptions:

Find, gather and centralize documentation about best practices concerning replying to newcomers on Help Desks.

Would this piece of documentation be within scope or not, and why?

About scope, one task to challenge our assumptions:
Find, gather and centralize documentation about best practices concerning replying to newcomers on Help Desks.
Would this piece of documentation be within scope or not, and why?

Researching the existing documentation that each community had produced for the benefit of WMF work, yes that is within our Team's remit. Writing instructions for the communities, no. Suggesting changes to communities own documentation based on what we find, maybe.

Quiddity updated the task description. (Show Details)Feb 20 2019, 5:48 PM
Quiddity updated the task description. (Show Details)
Quiddity changed the task status from Open to Stalled.Apr 10 2019, 2:58 AM