The Parsing team at the Wikimedia Foundation that develops the Parsoid
service is deprecating support for node 0.1x. Parsoid is the service
that powers VisualEditor, Content Translation, and Flow. If you don't
run a MediaWiki install that uses VisualEditor, then this announcement
does not affect you.
Node 0.10 has reached end of life on October 31st, 2016  and node
0.12 is scheduled to reach end of life December 31st, 2016 .
Yesterday, we released a 0.6.1 debian package  and a 0.6.1 npm
version of Parsoid . This will be the last release that will have
node 0.1x support. We'll continue to provide any necessary critical bug
fixes and security fixes for the 0.6.1 release till March 31st 2017 and
will be completely dropping support for all node versions before node
v4.x starting April 2017.
If you are running a Parsoid service on your wiki and are still using
node 0.1x, please upgrade your node version by April 2017. The Wikimedia
cluster runs node v4.6 right now and will soon be upgraded to node v6.x
. Parsoid has been tested with node 0.1x, node v4.x and node v6.x and
works with all these versions. However, we are dropping support for node
0.1x right away from the master branch of Parsoid. Going forward, the
Parsoid codebase will adopt ES6 features available in node v4.x and
higher which aren't supported in node 0.1x and will constitute a
Subramanya Sastry (Subbu),
Technical Lead and Manager,
 Node.js Long Term Support schedule @ https://github.com/nodejs/LTS
It's that time of year again; the holiday season.
Different from last year:
In the interest of both 1) giving engineers full time off at the end of the
year (not needing to be aware of what code they wrote is being deployed)
and 2) to keep the site reliable during our end-of-year fundraising
pushes there will be 2 weeks (instead of just 1) at the end of December
that are NO DEPLOYS weeks.
Here's the basic outline from now until mid-January (by week):
* Nov 7th: normal
* Nov 14th: normal
* Nov 21st: (Thanksgiving)
** All week: no train
** Mon/Tues: SWATs only
** Wed/Thur/Fri: NO DEPLOYS
* Nov 28th: normal
* Dec 5th: normal
* Dec 12th: normal
* Dec 19th: NO DEPLOYS (XMAS)
* Dec 26th: NO DEPLOYS (XMAS)
* Jan 2nd: normal (with train)
* Jan 9th: no train, SWATs only (but no one from RelEng is garaunteed to
* be around) (DevSummit+All Hands)
* Jan 16th: resume normalcy (Monday is MLK Day)
As always, the canonical location for deployment information is at:
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Arlo and myself have been working on a new MediaWiki extension to expose
Parsoid's "lint errors" to users.
A little bit of background, Parsoid has a linter that identifies some
issues in wikitext that while may not result in user-facing errors, are
still not wanted in wikitext. An example might be
[[File:Example.png|foo|bar|baz]]. In this case, "foo" and "bar" are
ignored, and "baz" is the actual caption - but the bogus image options
should be removed. Other errors include missing end tags, obsolete HTML
tags, fostered content, etc.
The main advantage of this over tracking categories is that we know the
location in the wikitext so it should be easier to identify the error
and fix it, as well as knowing whether the issue was caused via a
template or not.
The main ticket tracking deployment is
My name is Mayank Jindal. I am third year undergraduate student
currently studying at Indian Institute of Technology, Kharagpur. I want to
take part in Gsoc-2017 from Wikimedia.
I have knowledge of C, C++, JAVA, Python, Android app development and Web
development and beginner in *Machine Learning, Artificial Intelligence.*
I am very enthusiastic to learn new skills which would be required.
Kindly guide me to proceed further.
Third year undergraduate student,
Indian Institute of Technology Kharagpur
Mobile : +91- 7076670299 || 8875432718
Google Code-in 2016 just started:
In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
mailing lists by onboarding newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!
Thanks to all mentors who have already registered & provided tasks!
You have not become a mentor yet? Please do consider it.
It is fun and we do need more tasks! :)
* Think of easy tasks in your area that you could mentor.
Areas are: Code, docs/training, outreach/research, quality
assurance, and user interface. "Easy" means 2-3h to complete for
you, or less technical ~30min "beginner tasks" for onboarding).
* OR: provide an easy 'clonable' task (a task that is generic and
could be repeated many times by different students).
* Note that you commit to answer to students' questions and to
evaluate their work within 36 hours (but the better your task
description the less questions. No worries, we're here to help!)
For the full info, please check out
and ask if something is unclear!
Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects!
Andre Klapper | Wikimedia Bugwrangler