As promised in the meeting, here is are the minutes for the VisualEditor
weekly triage meeting on 2015-02-11.


*Item 1 – Release criteria*

The release criteria at
https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3_blockers/ were
considered. After a brief discussion, no changes were proposed.


*Item 2 – Review of nominated tickets*

Nominated tickets accepted:

… as corruption & stability issues:

   - https://phabricator.wikimedia.org/T76998 – Random removal of
   categories when using Safari
   - https://phabricator.wikimedia.org/T74048 – [Regression] VE corruption
   issue(?) moving pre-existing categories to the middle of the page
   - https://phabricator.wikimedia.org/T89025 – Using keyboard shortcuts
   (in multiple browsers) or the "Open menu" (in Firefox only) to copy a
   paragraph and a reference together causes selected content to be deleted
   (not cut) instead
   - https://phabricator.wikimedia.org/T88148 – class="wikitable wikitable"
   corrupted to class="wikitable"
   - https://phabricator.wikimedia.org/T74579 – Deleting from a
   paragraph-terminating node to a paragraph-terminating node (?) is throwing
   "Unbalanced set of replace operations found"
   - https://phabricator.wikimedia.org/T76715 – Same Category get added
   multiple times ,for every change in “Sort this page by default as” value
   - https://phabricator.wikimedia.org/T72375 – Deleting from an empty
   paragraph to the end of an inline node throws an exception
   - https://phabricator.wikimedia.org/T70537 – In production, sometimes
   page scrolling is not working and in the console Getting Error: offset was
   inside a handlesOwnChildren node in Firefox

… as performance issues:

   - https://phabricator.wikimedia.org/T88386 – ~50ms spent
   a.oo-ui-buttonElement-button
   - https://phabricator.wikimedia.org/T76523 – Show the VisualEditor
   toolbar/editor chrome immediately after the user clicks "edit", rather than
   blocking on waiting for the content to load
   - https://phabricator.wikimedia.org/T88650 – Support data-mw.body.id for
   reference contents
   - https://phabricator.wikimedia.org/T88623 – VisualEditor should load
   data-mw from a separate API call alongside the body content
   - https://phabricator.wikimedia.org/T87553 – API requests to
   action=visualeditor&paction=parse more than four times slower than requests
   directly to parsoid-lb


… as testing issues:

   - https://phabricator.wikimedia.org/T74398 – Actually run tests for
   MWHeadingNode / MWPreformattedNode

… as feature issues:

   - https://phabricator.wikimedia.org/T78202 – Wordbreak detection is
   faulty for selection starting just down-page of a single character
   - https://phabricator.wikimedia.org/T88337 – Tools should be able to
   specify a label for their appearance in the context menu
   - https://phabricator.wikimedia.org/T76398 – External link interface for
   link dialogue

… as dependencies:

   - https://phabricator.wikimedia.org/T66171 – Log Parsoid server-side
   save performance

… for investigation and re-triage:

   - https://phabricator.wikimedia.org/T74929 – Using browser native
   interactive spell-check when the changed word in the only item in the
   paragraph causes endless insertions in Firefox
   - https://phabricator.wikimedia.org/T65462 – Using browser native
   interactive spell-check tool causing repeated automatic deletion in Chrome


Nominated tickets rejected:

   - https://phabricator.wikimedia.org/T72665 – Tab/Shift-Tab behaviour in
   contexts other than lists (like tables)
   This is a nice-to-have feature but it isn't critical to any of the
   common edit workflows for the user groups targeted right now.
   - https://phabricator.wikimedia.org/T67589 – Up/down keys in table when
   you've selected a cell move left/right instead
   This is a nice-to-have feature but it isn't critical to any of the
   common edit workflows for the user groups targeted right now.
   - https://phabricator.wikimedia.org/T52616 – Improve VisualEditor's
   loading performance in Firefox
   This is really a tracker bug more than a specific call-to-action.
   - https://phabricator.wikimedia.org/T55825 – Reduce VisualEditor's
   memory usage
   This is a high-level tracker bug rather than a blocker; it needs child
   bugs with more specifics to be nominated as blockers.
   - https://phabricator.wikimedia.org/T53798 – There should be help links
   in every context - dialog boxes, inspectors, etc.
   We disagree with the premise; instead, there should only be help links
   where they are useful to explain the complexity of a control to the user.
   Most of this is already done, and the focus areas for this release don't
   have this level of complexity required.
   - https://phabricator.wikimedia.org/T88316 – Preview interface for link
   dialogue
   As a product decision, we decided to remove this as a blocker to the
   release, and instead focus on the citation improvements first before taking
   this on.
   - https://phabricator.wikimedia.org/T86693 – Alter the toolbar and
   dropdown menu design
   As a product decision, we decided to remove this as a blocker to the
   release; instead, this potentially will be part of our polish effort
   instead.


*Item 3 – Other business*

The process was very briefly discussed, without suggestion of changes.


Hope this is of interest. Next week's meeting will be at 16:00 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150218T08&p1=224&ah=1>
(08:00 PST) on Wednesday 18 February; hope to see many of you there.
Joining instructions are on mw:Talk:VisualEditor/Portal
<https://www.mediawiki.org/wiki/Talk:VisualEditor/Portal#How_to_join_the_triage_meetings>
for
those who didn't make it this week.

Yours,
-- 
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.

[email protected] | @jdforrester
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to