We may not have the time / energy for Google code-in this year. Personally, I am travelling and on vacation over the next 5 weeks and would not be a good mentor and others are feeling a little overcommitted at this point. If any of the other Parsoid team members change their mind, we'll add ourselves as a participating project.

However, if someone else (outside the Parsoid team) wants to mentor students on the bug-finding idea (or a variant thereof) that Nemo proposed, please feel free to do so. We'll be available on IRC on #mediawiki-parsoid to answer questions generally.

If someone does take this up, based on this morning IRC's discussion, the following steps would be useful:

* Pick a specific browser, say, Chrome (to eliminate any browser-bug related issues)
* Install the gadget by Jackmcbarn that lets you look at parsoid html for a page
* If there is a diff seen, use the visual diff service to generate a visual diff for the page
* Use the visual diff to find the root cause of the diff and report a bug (if it is not already known).

One of the issues you are likely going to run into is: (a) find diffs because of known issues (b) find diffs that are all caused by the same newly reported underlying issue.

Subbu.

On 11/03/2014 05:13 PM, James Forrester wrote:

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
_______________________________________________
Wikitext-l mailing list
Wikitext-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitext-l