On 3 November 2014 15:10, Federico Leva (Nemo) <nemowiki@gmail.com> wrote:
James Forrester, 03/11/2014 20:58:
    Could you imagine mentoring some of these tasks?

Unfortunately, I think the VisualEditor world is too complicated at this
point to break off simple bugs without a lot more documentation (and
this is reflected in the lack of bugs tagged as "easy"). We've talked
about writing up a "crash course" to explain how things work, updating
https://www.mediawiki.org/wiki/VisualEditor/Design/Software_overview and
the like, but we're too far from that to be able to commit to GCI for
this year, sorry.

Your call, of course. But I think a good task might be: find and report one (or N) valid Parsoid bug(s). It's rather easy to find rendering errors in the Parsoid HTML simply by visiting random pages on parsoid-lb.eqiad.wikimedia.org (with the optional help of Kiwix + ZIM files). Of course it's most useful in languages which the devs look less at; on en.wiki probably not that useful.

Actually, it's not my call for the Parsoid team. :-) Subbu?

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

jforrester@wikimedia.org | @jdforrester