This page explains how documentation issues are reviewed and prioritized for the istio/istio.github.io repository. The purpose is to provide a way to organize issues and make it easier to contribute to Istio documentation. The following should be used as the standard way of prioritizing, labeling, and interacting with issues.
Issues should be sorted into different buckets of work using the following labels and definitions. If an issue doesn’t have enough information to identify a problem that can be researched, reviewed, or worked on (i.e. the issue doesn’t fit into any of the categories below) you should close the issue with a comment explaining why it is being closed.
|Needs Tech Review|
|Needs Docs Review|
|Needs UX Review|
The following labels and definitions should be used to prioritize issues. If you change the priority of an issues, please comment on the issue with your reasoning for the change.
If a single problem has one or more issues open for it, the problem should be consolidated into a single issue. You should decide which issue to keep open (or open a new issue), port over all relevant information, link related issues, and close all the other issues that describe the same problem. Only having a single issue to work on will help reduce confusion and avoid duplicating work on the same problem.
Depending on where a dead link is reported, different actions are required to resolve the issue. Dead links in the reference docs are automation issues and should be assigned a P1 until the problem can be fully understood. All other dead links are issues that need to be manually fixed and can be assigned a P3.