User:Pavithraes/Sandbox/Technical documentation prioritization

Overview
The Documentation project on Phabricator is used to track technical documentation tasks across Wikimedia spaces.

A set of guidelines have been outlined to help improve the process of categorization and prioritization of these tasks.

Filing a technical documentation request
Requests for improvement of existing documentation, creation of new documentation and issues with automated documentation can be filed using Wikimedia's Phabricator instance in the #documentation project.

You can also use this form to create your task.

Ticket Content
A complete and unambiguous description of tasks is important for effective task tracking. The following are some points to consider while writing your task description.

For existing docs:


 * Clearly describe the problem. Some examples of documentation problems are: wrong information, missing steps, obsolete data, interface changes, etc.
 * Specify the exact location of the problem. You could provide links or point to the exact section that needs work.
 * State the information required to complete/improve the documentation.

For new documentation:


 * Define the purpose of the new document and list out the topics it should cover.
 * Try to mention a temporary location and title for the documentation.
 * Provide reference resources and a suitable genre for the documentation.

Additional points:


 * Suggest an author or assignee who can/will be working on the task.
 * If you have sufficient expertise in the domain, mention the level of knowledge, technologies, time and effort required to complete the task.
 * Make sure to add necessary tags, like good-first-bug,  javascript,  visualEditor, etc.

Prioritizing
A technical documentation request becomes a priority in the following cases, where X can be any project, task, process or tool.
 * There are repeated requests to create or improve the documentation for X.
 * The complete documentation of X is required for another process to work, or another task to be completed.
 * The steps described for X (a process) are wrong, incomplete or obsolete.
 * The structure/layout of information in the documentation of X makes it difficult to find important information.
 * X is auto-generated and is not updating properly.

Categorizing
The documentation workboard covers technical documentation requests across the various Wikimedia projects. Hence, requests are categorized into the following boards:

Location
A lot of Wikimedia's technical documentation can be found at the following locations:

After filing a ticket
It is important to respect the culture and values of an open-source community while using Phabricator. People from many places with different points of view and skill levels work together to surface issues and resolve them. Hence, make sure to be thoughtful about the people behind the tasks while interacting with it.

Changing status and priority
It takes time and energy to open a ticket, and equal energy should be spent in evaluating and prioritizing it. In Phabricator, a task is prioritized by assigning status and priority.

Following up
When you file a ticket in Phabricator, you are automatically subscribed to it and you will receive notifications when changes are made to the ticket. As the author of the task, it is your responsibility to:
 * Monitor the status of the task and the changes made to it.
 * Follow up on the task regularly.
 * Be open to feedback from the community and work with other collaborators to complete the task.

Continuous improvement
Technical documentation is never truly finished. There is always scope for improvement, updates and additions. So, don't hesitate to reopen a closed Phabricator task. Make sure to communicate with the author and take responsibility for the proposed improvements.

Closing a ticket
Even though technical documentation is never fully complete, we can close Phabricator tasks when there is a consensus that the documentation is satisfactory and sufficient.

We can close tickets when:
 * The requested update or improvement has been made to existing technical documentation.
 * New documentation is created that meets the requirements of the technical documentation style guide and meet the specifications of the ticket.

Examples

 * Improving existing documentation: T203858
 * New documentation request: T157241
 * In the following custom example, note that:
 * the #documentation tag has been added.
 * target audience has been mentioned.
 * time and technologies required have been specified.
 * useful resources and related tasks have been included.
 * the task has been assigned a Low priority because the request is nice to have.



Help
If you have queries or need help, contact:
 * wikitech-l@lists.wikimedia.org.