This quarter we will make VE the default mobile editor on at least 3 wikis. This task is about deciding those 3 wikis*.
//Note//: we will be running an [A/B test](https://phabricator.wikimedia.org/T221195) with these wikis. This means we need to prioritize wikis that have more mobile edit volume/behavior to increase the sample size of each group.
- We're striving to **make editing on mobile web simpler** 
- We think contributors will have more success editing on mobile VE given it offers a more structured and visual experience than wikitext. Attributes we think are especially important in a context where time and space //can// be less abundant than on desktop
- Difficultly: VE is not the default on mobile; this has meant the overwhelming majority of mobile editors do not interact with it. 
- This makes improving the experience difficult when the majority of mobile contributors are **not** represented in the [quantitative data](https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report#Usage_of_common_editing_features) we've been using to inform our product decisions
- By making the VE the default editing experience we intend to:
# Increase our understanding of the expectations and needs of a broader range of contributors editing on mobile
# Learn whether VE, in its current state, is a "better"  mobile editing experience than wikitext
# Learn how turning on VE as the default mobile editing interface impacts overall edit completion rate
- Enough existing mobile editing behavior (as measured by: mobile edit sessions)
- Community consent (potential proxy: % of edits made using VE)
- Language: RTL and LTR represented
- We have a relationship with someone in this wiki
- Not going to conflict with another team's work
###Definition of "done"
- [x] **Share**: with Editing Team
- [x] **Confirm**: the set of wikis we are focusing on have no objection to VE as mobile default
- [ ] **Publish**: wikis we will be trialing mobile VE as default editor with on MediaWiki
- [ ] What are the implications of choosing these wikis on our ability to run an A/B test? Time? Precision?
- [ ] How many edit session will we need in our sample size to complete an A/B test in 4 weeks with .95 power (assuming we will not need finer precision than we're currently using for [section editing A/B test](https://docs.google.com/document/d/1qHltnDJtTvBfze4iLGO-oEhgqmm6HFkQjvrW4WxmMBM/edit#heading=h.bfpp9rr6aoti))
-- [ ] Is 3 wikis a necessary constraint considering the scale we'll need to achieve the significance within this time frame?
- [ ] Do the wikis selected meet the criteria we've identified as important?
- [ ] What are the consequences of collaborating with a wiki on this initiative and T221816?
1. **Editing Team annual goal**: [Audiences 2018-19 Annual Plan](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/Audiences#Outcome_3:_Mobile_Contribution#Output_3.4)
2. **Edit sessions recorded in May 2018** | [source](https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report)
| **Editor** | **Edit sessions** | **% of total** |
| //VE// | 20,643 | ~1.0% |
| //Wikitext// | 1,912,178 | ~99% |
3. **"Better mobile editing experience"**: as measured by overall edit completion rate
4. [Mobile edit sessions per wiki](https://docs.google.com/spreadsheets/d/1fOh6IIphJLYZiykUXCT33AfJRzxw4OE64gXvxav86-Q/edit#gid=0)
5. [Target-wikis/Q4 sheet](https://docs.google.com/spreadsheets/d/1juUIPPUkeJn7G7Y3nNOY66uiL-1pD3KYYi1EcI0DXVQ/edit#gid=0).