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

On 3 November 2014 05:18, Andre Klapper aklapper@wikimedia.org wrote:

Hi Parsoid & VisualEditor crew,

Google Code-In (GCI) will soon take place again - a contest for 13-17 year old students to contribute to free software projects.

Wikimedia wants to take part again. Last year's GCI results were surprisingly good - see https://www.mediawiki.org/wiki/Google_Code-in_2013

​[Snip]​

• Open VisualEditor tickets created in the last six months (if I got

your products and components right):

https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st...

Corrected link (in front-end we use ASSIGNED to mean "accepted"):​ https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st...

• Zero existing VisualEditor "easy" tickets (are they still valid? Are

they really self-contained, non-controversial issues with a clear approach? Could some of them be GCI tasks that you would mentor? If so, please tag them as described above!):

https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st...

​Corrected link, per above: https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st... — but there are still no such bugs

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.

J.