User:MSantos (WMF)/Parsoid Usage Confidence Framework

Goals
Turn on parsoid on self-contained and safe places to develop the framework for "Parsoid Usage Readiness". We are probably looking for a combination of:


 * Supported Extensions Coverage


 * Visual diff coverage


 * Linting errors (?)


 * Parsoid metrics


 * Performance (?)


 * Parsoid missing functionality in affected pages


 * Qualitative Reports (?)


 * Number of bugs (?)

The output of this framework should not force us to use "cold numbers" to deploy Parsoid for the sake of achieving the goal. We should use to enquiry more profound product questions.

Based on the combination of the metrics we should always have an answer for enabling Parsoid Read Views  for every wiki:


 * Not confident at all


 * Not confident


 * Somewhat confident


 * Confident


 * Extremely confident

Example:

With that we will be able to look at the reasons for not being confident with Parsoid and focus on its characteristics and architecture with a Product Strategy lens to mitigate the gaps that affect our confidence to deploy Parsoid for Read Views.

Immediate Goals

 * Deploy Parsoid in controlled and safe environments to enable learning and development of the "Parsoid Usage Readiness Framework"
 * Globally for specific wikis
 * First candidates are Wikitech DiscussionTools and Officewiki Read Views
 * Next English Wikivoyage DiscussionTools
 * Later Hebrew Wikipédia DiscussionTools
 * Allow users to opt-in to Parsoid in any wiki by using the ParserMigration extension

Open questions

 * Decide how many features we need to turn on to avoid community discontent


 * This is not about having 100% of wikitext features done, but does coverage matters?


 * What will be the target metrics to get parsoid read views on testwiki?


 * What is the amount of wikitext that users focus on DiscussionTools?