Adam, I'm happy to hear that VE is coming to mobile web.
I'd like to know more about what the plans are for user testing of VE on mobile. Would that happen in late Q2 at the earliest, and how much emphasis will there be on user testing mobile VE while it's in beta? My prime interest is in making sure that the transition out of beta is smooth and that end users have a good experience with mobile VE from the moment that it leaves beta. Thanks, Pine On Jul 27, 2015 10:12 AM, "Adam Baso" <ab...@wikimedia.org> wrote: > Cross posting to mobile-l. > > ---------- Forwarded message ---------- > From: Adam Baso <ab...@wikimedia.org> > Date: Mon, Jul 27, 2015 at 10:11 AM > Subject: Editing + Reading Meeting Notes > To: Wikimedia developers <wikitec...@lists.wikimedia.org> > > > Hi all, > > James Forrester, Florian, and I met Wednesday, 22-July-2015 to discuss the > Editing roadmap, with the backdrop of editing modes available in mobile web > and apps but both the mobile web and apps teams now being in the Reading > department. Notes: > > * FY 2015-2016: active Editing development for apps not planned > > * General plan is to replace the current mobile web editing experiences > with new (replacement) VE and wikitext editor maintained by the VE team for > mobile web > > * Q1: VE mobile prototyping (doesn't require Reading involvement) > > * Q2: Editing for mobile web replacement *coding* starting, but rollout on > mobile web would begin in some future quarter _after_ Q2 > > * Feature submission practices for volunteers submitting editing related > stuff for the mobile web for the time being (feature submissions > discouraged for now as it will end up being replaced; mainline VisualEditor > / next gen wikitext editing in collaboration with VE team would probably > make more sense) - > > ** Create task in reading-web Phabricator board and indicate the details > of what you were thinking to work on and roughly when. Add James Forrester > and Joaquin Hernandez to card. > > ** Reach out to James_F (Senior Product Manager, VisualEditor) and joakino > (Reading Web engineering product owner and tech lead) on #wikimedia-mobile > on Freenode to discuss the idea and to determine who would need to code > review and test > > * Code review for bugfixes for the existing mobile editing code should be > done by Reading Web, and code review plus testing should be done by Editing > as well. Ping joakino and James_F on IRC to figure out who to add to > bugfixes. > > * As the Editing team gets into the practice of submitting patches for > MobileFrontend to swap out the editor, as usual, tasks should be filed well > ahead of time in the reading-web Phabricator board so there's a heads up > about potential code review. Also, Editing and Reading should be tracking > Q2 and subsequent quarter planning together to ensure dependencies are > clearly defined and agreed upon. > > I also spoke to Roan from Collaboration after the Scrum of Scrums the same > day. Roan indicated that there isn't an emphasis on rolling out Flow to > mobile Wikipedias en masse for FY 2015-2016. And generally, when Flow does > become slated for rollout on the mobile Wikipedias and sister projects in a > broader sense it shouldn't require work - or anything substantial, anyway - > from the Reading team. > > -Adam > > > _______________________________________________ > Mobile-l mailing list > Mobile-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mobile-l > >
_______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
