Community Wishlist Survey 2019/Archive/Graduate 2017 wikitext editor and make it a full value editor

Add links
From Meta, a Wikimedia project coordination wiki

Graduate 2017 wikitext editor and make it a full value editor

NoN Outside the scope of Community Tech

  • Problem: We are using and testing the (new) 2017 wikitext editor since 2016. In the past year, nothing really big happened with this tool, although there are many (currently 121) open tickets on Phabricator. With fulfilling these requests and solving the problems (e.g. speed, stability, many CodeMirror-related bugs) we could finally have a modern, fast and VE-look alternative of the old editor. Let's speed it up and finally graduate this project!
  • Who would benefit: everybody who is using (or would like to use) the 2017 wikitext editor.
  • Proposed solution: solve every bug, fulfil requests and ask the community for more great ideas.
  • Phabricator tickets: main ticket is T104479, bugs are listed here.

Discussion

Quick evaluation notes: This is feasible and in-scope for the wishlist. I cannot, of course, make any commitments for any team, but I am certain that the Editing team agrees that it is time to do this. A few notes:

  • "Deployment" in this instance merely means moving the pref setting out of Special:Preferences#mw-prefsection-betafeatures and into the normal editing section at Special:Preferences#mw-prefsection-editing, while preserving each individual editor's own settings. It is a matter of a couple of announcements, changing a few help pages, and throwing the switch on the database.
  • However, phab:T202921 should be done first, because the current method of selecting which editing environment you're using is deeply confusing. (In the current prefs system, you can enable multiple editing environments, and it silently overrides your "wrong" choices.) With the resolution of phab:T30856 this week, and the conversion of all the prefs pages to OOUI earlier this year, there is nothing blocking the redesign of that small section in the editing prefs. This should be a relatively simple project.
  • Once the prefs are re-designed, and the tool is moved into the normal prefs, if any wiki that wants this editing environment to be presented to users as the first choice, they need only send a note to me about it, with a link to a discussion among the community members. But this is IMO a separate project, and should not require any effort from the Community Tech team.

Overall, this should be a quick and easy project. Whatamidoing (WMF) (talk) 18:39, 2 November 2018 (UTC)[reply]

Unfortunately, I think this is out of scope for Community Tech. This is an Editing team project, and it needs to be handled by that team. Sorry about that. -- DannyH (WMF) (talk) 02:15, 14 November 2018 (UTC)[reply]
Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2019/Archive/Graduate_2017_wikitext_editor_and_make_it_a_full_value_editor&oldid=24586684"