Over the last week Željko and I changed the QA automated browser tests to
target test environments on the beta cluster as well as on test2wiki, where
they had been running for some time.
This was possible because of a number of improvements made to beta since
the QA Quarterly Review and the f2f meeting in SF in February:
* automatic updates to the beta database
* enabling Search on beta
* Varnish on beta to support MobileFrontend
* etc.
There is still more to do:
* get more extensions running and configured on beta
* change settings to more closely match prod and/or test2 as appropriate
* moar tests
Automated browser tests have a proven record of exposing real issues in the
test2wiki environment before code is put in production. Here are some of
the bugs we have identified by way of browser tests so far:
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu…
By running these tests in the beta cluster also, we gain both better test
coverage features in disparate environments and also a longer window to
identify issues, since beta is updated much more often than test2wiki.
As always, the current status of the browser test builds are available in
Jenkins at https://wmf.ci.cloudbees.com, and any changes to the status of
those builds are reported by wmf-jenkins-bot in #wikimedia-dev
Hello and welcome to the latest edition of the WMF Engineering Roadmap
Update.
Highlights include:
* Mobile resubmitted to AppStore yesterday, still waiting on the Apple
Geniuses to approve ;)
* QA is turning all the tests running against betalabs green (they were
red from unexpected config differences); they're close.
* Echo will be rolling out on en, de, and fr wiki next week on Thursday
(the 25th)
* Platform has moved the Ceph and Vipscaler deploys to target in May
Full roadmap at:
https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Aoizbfxc5g6KdE…
(short: http://goo.gl/7611Q )
Best,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
What: Translation User Interface bug triage
Date: April 24 2013
Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://hexm.de/r0)
Channel: #mediawiki-i18n (Freenode)
Etherpad: http://etherpad.wikimedia.org/BugTriage-i18n-2013-04
Questions can be sent to: runa at wikimedia dot org
Hello,
The Language Engineering team would like to invite everyone for the
upcoming bug triage session on Wednesday, April 24 2013 at 1700 UTC
(1000 PDT). During this 1 hour session we will be using the etherpad
listed above to collaborate. We have already listed some bugs, but
please feel free to add more bugs, comments and any other related
issues that you’d like to see addressed during the session. You can
send questions directly to me on email or IRC (nick: arrbee). Please
see above for event details.
Thank you.
regards
Runa
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hello and welcome to the latest installment of the Deployment Highlights
email.
The full calendar for next week lives at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_April_22nd
For the week of April 22nd we have the following interesting
deployments:
== Monday ==
* MediaWiki 1.22wmf2 to English Wikipedia
* Wikidata client update on English Wikipedia. Completion of Wikidata
Phase II [0], which will allow for use of Wikidata properties in
infoboxes. There is also an FAQ[1] about Phase2 that might answer your
questions.
[0] http://meta.wikimedia.org/wiki/Wikidata/Technical_proposal#Phase_2:_Infobox…
[1] http://meta.wikimedia.org/wiki/Wikidata/Deployment_Questions#Phase_2_.28inf…
== Tuesday ==
* ArticleFeedbackTool will be renabled to "on" on a subset of English
Wikipedia, along with basic bugfixes to French and German Wikipedia.
Details: http://etherpad.wikimedia.org/AFT5-release
* Mobile:
** First use of CentralNotice to display banners for users of the WP
Commons Beta app.
** Deploy of a fix for the "X-Device" caching problem explained in
this[2] email. Basically, reduce the cache-miss rate by not varying
the cache by 21 different device types.
[2] http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067967.html
== Wednesday ==
* MediaWiki 1.22wmf2 to all Wikis
* Wikidata client update on all Wikipedia sites (tentative; depending on
success of English Wikipedia deployment on Monday).
== Thursday ==
* VisualEditor/Parsoid alhpa to be enabled on additional 14 wikis (but
not by default, still opt-in).
** WPs included: de, nl, fr, it, ru, es, sv, pl, ja, ar, he, hi, ko, zh
** Announcement:
http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-April/000201…
* Notifications: Releasing of the "Minimum Viable Product" on English
Wikipedia. See these two ([3] & [4]) messages from the Notifications
Product Manager, Fabrice Florin, outlining what features are
included.
[3] http://lists.wikimedia.org/pipermail/ee/2013-April/000373.html
[4] http://lists.wikimedia.org/pipermail/ee/2013-April/000390.html
** Full details:
http://etherpad.wikimedia.org/echo-release
== Everyday ==
And of course, every day includes the Lightning Deploy window, which
this week is ceremonially referred to as "Matt Walker's Deploy Window"
as he was a heavy (and courteous) user of these windows this past week.
Thanks and have a good weekend,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hi all,
This is a heads up that we've added a small new feature which hopefully
will make things less painful for users across the projects: the ability to
refresh the CAPTCHA you're presented without refreshing the entire page. It
should work everywhere ConfirmEdit can throw the image CAPTCHA at someone:
account creation, login, the edit form, etc. (It won't modify the simple
math CAPTCHA, and so on.)
The original enhancement request for this (
https://bugzilla.wikimedia.org/show_bug.cgi?id=14230) goes back to 2008. A
patch was submitted back in January by lalei:
https://gerrit.wikimedia.org/r/#/c/44376/
If you want to test this out yourself before it's deployed, you can use
http://toro.wmflabs.org/wiki/Main_Page
--
Steven Walling
https://wikimediafoundation.org/
Hi, please find 5 minutes for this survey:
http://www.doodle.com/minqnd6ngz9npfdv
In an *average* week, when are you more available to volunteer a couple
of hours? Multiple choices are good. No registration required.
VERY IMPORTANT: select your timezone!
Deadline: end of Sunday, May 21.
We want to organize activities for technical volunteers at the times
that suit you best. But we have contributors with different habits in
different parts of the World. This survey will help us covering better
everybody's preferences.
Thank you!
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
For info, given interest in the VisualEditor. :-)
---------- Forwarded message ----------
From: James Forrester <jforrester(a)wikimedia.org>
Date: 18 April 2013 17:32
Subject: Deploying alpha of VisualEditor to non-English Wikipedias
To: Coordination of technology deployments across languages/projects
<wikitech-ambassadors(a)lists.wikimedia.org>
All,
TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an
opt-in alpha. Your assitance is requested to inform your wikis about this
and help get the software translated.
Next week (on 25 April) we are going to deploy the alpha opt-in version of
the VisualEditor to some non-English Wikipedias in the same way that it
has been on the English Wikipedia since December 2012.
This will let users get familiar with the VisualEditor, give us feedback
on what works and what is broken, and help us prioritise further work
ahead of the planned deployment as a 'default' editor for all users which
we intend to do in a few months' time.
Due to a number of issues we have been unable to release VisualEditor to
non-English wikis until now, and we would very much like to get some great
feedback from as many wikis as possible - especially for extended Unicode
and RTL languages, but also other languages. Does the VisualEditor work in
your language? Does it gel with your wiki's workflow?
The initial languages we want to target are the "top 10" Wikipedias by way
of scale - de, nl, fr, it, ru, es, sv, pl, ja - plus selected others to
help us discover issues we anticipate: ar, he, hi, ko, zh. These will let
us test most of the locales we are concerned about. If this goes well, we
hope to deploy the opt-in alpha to all Wikipedias.
Please tell your wiki colleagues that this is coming, especially if your
wiki is in this list! Additionally, you can see how fully-translated the
software is into your language in the stats at TranslateWiki.Net[0] -
please encourage wiki colleagues to help translate the messages ahead of
the deployment!
As a note, we have just updated the VisualEditor integration so that the
"Edit" tab goes to VisualEditor, and there is an "Edit source" tab to go
to the wikitext editor.
This change (which affects the English Wikipedia opt-in deployment and
MediaWiki.org as well as the new deployments mentioned above) moves the
way that VisualEditor integrates with the wiki's workflow to be closer to
how it will appear when it is the 'default' editor. It is still easy to
use the wikitext editor if that is what you want to do - the "Edit source"
tab (at least for now) will be "above the fold" and not in the drop-down
menu on Vector.
Happy to answer any questions you might have!
Yours,
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
https://outreach.wikimedia.org/wiki/Education_Portal/Newsletter/April_2013/…
"Moodle is a free and open source learning management system (LMS).
James Neill has made some valuable contributions about how Moodle can be
used in conjunction with Wikiversity as a platform for open education.
To minimise the need for exporting/importing content from one learning
management system (LMS) class site to another and then to another
institution Wikiversity may be used as an open educational content
repository.
A moodle-plugin has been developed by Jan Luca (German Wikiversity) to
include content into Moodle hosted on Wikiversity by using a simple tag:
[Include-WV]<URL>[/Include-WV]. The plug-in can be tested on
http://sandbox.wikiversity.wmflabs.org/moodle. For further information
contact Jan Luca or Wvk. This move is part of an initiative to restart
German Wikiversity that seeks to invite new contributors to the project."
Thanks for working on this, Jan Luca and Wyk! I see the code is at
https://github.com/JanLuca/Moodle_Wikiversity_plugin . Are you looking
for help of any sort -- design, testing, localisation, etc.?
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi everyone!
So we've had some discussions that are summarized here:
http://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion/Summary
In this letter I want to point out to two projects that haven't been
organized by Wikimedias, but are still very useful for the people who think
about MW as of open source product:
1) http://www.mwusers.com - MediaWiki forum. Many people prefer forums to
mailing lists and wikipages like Support desk. Moreover, MWusers is now a
good Q&A database.
2) http://wikiapiary.com A wiki with various statistics about MediaWiki
installations and statistics about extensions. I see the huge potential in
this project although it's only several months old. Template:Extension on
mediawiki.org have finally turned to something useful when the link to
wikiapiary had been added there.
If WMF/Wikimedias interested in promoting MediaWiki not as WMF project but
as a piece of open source software, it can be beneficial to help those
projects with information support (i.e links from MediaWiki.org), funding
and cooperation.
-----
Yury Katkov, WikiVote