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.

Nemo

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 mailto: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
<http://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 mailto:jforrester@wikimedia.org | @jdforrester

---

Wikitext-l mailing list Wikitext-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitext-l

On Wed, 2014-11-05 at 08:21 +0100, Federico Leva (Nemo) wrote:

Subramanya Sastry, 04/11/2014 23:05:

...

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.

Thanks. This sounds like a very good definition of a task, so I've appended it to the previous list of candidate tasks: https://www.mediawiki.org/wiki/Talk:Google_Code-in#Parsoid_bugs

It can be polished there and will certainly come handy sooner or later.

Thank you!

Would be awesome if somebody was willing to mentor so we can move that to https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks

Note that shared mentorship means less workload for everybody - would that be an option?

And in contrast to last year, this year mentors can also be based in Brazil, Italy and Quebec (but students cannot).

Cheers, andre

On Wed, 2014-11-05 at 09:31 -0600, Subramanya Sastry wrote:

On 11/05/2014 01:21 AM, Federico Leva (Nemo) wrote:

...

Thanks. This sounds like a very good definition of a task, so I've appended it to the previous list of candidate tasks: https://www.mediawiki.org/wiki/Talk:Google_Code-in#Parsoid_bugs

It can be polished there and will certainly come handy sooner or later.

Thanks. Added links to the two bullets that needed it.

Also thanks. Now we "just" need a mentor? Would be lovely if somebody (or a team to share the work) would find the time. :)

andre

[Redirecting conversation about TemplateData to wikitech-l; wikitext-l is for parser and Parsoid discussion.]

On 6 November 2014 22:56, Andre Klapper aklapper@wikimedia.org wrote:

Could there be any Template(Data) related tasks that could be worked on by Google Code-In students? For example something like "Fix five Templates from the list at XXXX by doing YYYY"?

I'm happy to help setting up such tasks if somebody volunteers to mentor (more than one mentor means less work for everybody) and if somebody could add some boilerplate text at

https://www.mediawiki.org/wiki/Google_Code-in_2014#Common_instructions_for_t...

​It's possible, though writing TemplateData needs a reasonably strong grasp of the local community's expectations about template usage and all of the complexities that goes with that.​ CC'ed to Elitre and WhatamIdoing in case they might be interested in mentoring.

​J.