I had a look at Ukrainian captchas. Fine and funny, I'm eager to know what
is the source for the words :)
Nota bene:
* usage of proper nouns may cause difficulties;
* letters Л and П in cyrillic look very simmilar
*Vira Motorko*
Help save natural resources - please think twice before printing this
e-mail or any attachments.
Greetings!
I’m happy to announce that we just enabled Media Viewer by default on nine more pilot sites: Czech, Estonian, Finnish, Hebrew, Polish, Romanian, Thai, Slovak, and Vietnamese Wikipedias.
1. Overview
We’re releasing Media Viewer gradually, a few wikis at a time, to test it carefully before deploying to the next batch of sites. So far, the tool has been well received on our first pilot sites: Catalan, Hungarian and Korean Wikipedias, as well as on English Wikivoyage, as outlined below. Next Thursday, we plan to deploy to some of our first large wikis: Dutch, French, Japanese, Spanish and Swedish Wikipedias. Learn more about this release plan here:
https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Release_Plan
2. Metrics
We’re now logging about 336,000 image views per day on a global basis, as shown on this graph:
http://multimedia-metrics.wmflabs.org/dashboards/mmv
About half of these views are coming from the Hungarian Wikipedia, and the rest from Wikimedia Commons, English Wikipedia and other pilots. More metrics dashboards are available for selected sites on this page:
https://www.mediawiki.org/wiki/Multimedia/Metrics
3. Performance
We are now tracking image load performance globally, and fist results suggest that images take over a second to load on average (50th percentile), but can take up to 5 seconds when looking at worst case for most users (90th percentile), as shown in this graph:
http://multimedia-metrics.wmflabs.org/graphs/mmv_performance_image_global
We’re also encouraged by early comparisons of the time it takes to open an image with Media Viewer versus on a Commons File, the current default: the mean load times for these two methods seem to be very close, on the order of 2-3 seconds on a cold cache, as shown in this preliminary graph:
http://multimedia-metrics.wmflabs.org/dashboards/mmv#media_viewer_vs_file_p…
4. Surveys
We are now running surveys in multiple languages, to validate whether or not this feature is useful to readers and editors alike. Overall response so far is generally favorable. Here are the current results:
* English Survey: 64% find the tool useful, 12% don’t find it useful, 24% are not sure (50)
* Hungarian Survey: 47% find the tool useful, 47% don’t find it useful, 5% are not sure (268)
* Catalan Survey: 62% find the tool useful, 15% don’t find it useful, 23% are not sure (13)
We’re also starting new surveys in French, German and Portuguese. You can find links to live results and comments from all these surveys here:
https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Survey#Results
5. Usability
For the past few months, we have been running a series of usability studies, with positive results. Testers are typically able to complete most common tasks successfully, and they have helped us find new ways to improve the user experience for areas they found confusing.
https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Usability_testing
6. Your feedback
How can we improve Media Viewer? Are there any critical issues that should be addressed for this first release? Please let us know what you think of this tool — and join other users from around the world on this discussion page:
https://www.mediawiki.org/wiki/Talk:Multimedia/About_Media_Viewer
We’d also be grateful if you could take this quick survey, to let us know how Media Viewer works for you. It only takes a minute and means a lot to us:
https://www.surveymonkey.com/s/media-viewer-1?c=email
Many thanks to all the team and community members who made this launch possible!
Enjoy,
Fabrice — for the Multimedia Team
P.S.: New improvements take about 2 weeks to get deployed to all wikis. If you would like to test the latest version of Media Viewer, follow the test tips on this demo page on MediaWiki.org:
https://www.mediawiki.org/wiki/Lightbox_demo
_______________________________
Fabrice Florin
Product Manager, Multimedia
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:Fabrice_Florin_(WMF)
TL;DR: check on https://etherpad.wikimedia.org/p/BugTriage-Collection if
you see an old friend
Hello book lovers, I propose to hold a bug triage for old Collection
bugs. It's sad, but all the bugs of 4 years ago are still current;
what's worse, they're not even tracked because the bug tracker was deleted.
So, let's test them together again, everyone on their own wiki:
https://etherpad.wikimedia.org/p/BugTriage-Collection
If you want to help, add your name and your proposal of a date when to
meet on IRC.
See https://www.mediawiki.org/wiki/Bug_management/Triage for what a
triage is. You don't need to come on IRC, just writing on etherpad or
bugzilla something you know about one of those bugs is very valuable.
Note: this is only about the Collection extension itself. The backend
software to produce the actual PDF files (mwlib) is being superseded.
There are some 160 more bugs to retest for it, but we need a testing
area; I've asked about it at
<https://www.mediawiki.org/wiki/Thread:Talk:PDF_rendering/Test_instance_and_…>
Nemo
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_April_21st>
A quick list of notable items...
== Tuesday ==
* MediaWiki deploy
** group1 to 1.24wmf1: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf1>
* Flow:
** Archive and enable Flow on the Nearby Pages Beta Feature talk page
** <https://www.mediawiki.org/wiki/Talk:Beta_Features/Nearby_Pages>
** <https://www.mediawiki.org/wiki/Flow>
== Thursday ==
* MediaWiki deploy
** group2 to 1.24wmf1 (all Wikipedias)
** group0 to 1.24wmf2 (test/test2/testwikidata/mediawiki)
* Media Viewer:
** Third limited pilot release: Enable by default on a few small
pilot sites (batch 2: Czech, Estonian, Finnish, Hebrew, Polish,
Romanian, Slovak, Thai, Vietnamese)
** <https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Release_Plan#Timeline>
As always, questions and comments welcome,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hi!
Just dropping a short note that it is now finally possible to
subscribe to the weekly Tech News bulletin[1] via a web feed to ensure
a smooth, hassle-free delivery of every issue to a news aggregator of
your choice.
You can subscribe to an Atom[2] or RSS[3] feed, which should deliver a
new issue at 00:00 UTC every Monday.
At this point, the feed only provides the English version of the
bulletin, so you'll need to click one of the links on top of the page
to read a version in a different language — if you think that a
per-language feed is a good idea, please let us know!
The feed is now also subscribed to the English Planet Wikimedia[4], so
if you get your Wikimedia news that way, you'll also see a new issue
of Tech News on the Planet every Monday.
Feedback and questions are welcome :-)
== References ==
* [1] https://meta.wikimedia.org/wiki/Tech/News
* [2] https://meta.wikimedia.org/w/api.php?action=featuredfeed&feed=technews&feed…
* [3] https://meta.wikimedia.org/w/api.php?action=featuredfeed&feed=technews&feed…
* [4] https://en.planet.wikimedia.org/
Tomasz
Hi,
The report covering Wikimedia engineering activities in March 2014 is now
available.
Wiki version:
https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2014/March
Blog version:
http://blog.wikimedia.org/2014/04/18/engineering-report-march-2014/
We're also proposing a shorter, simpler and translatable version of this
report that does not assume specialized technical knowledge:
https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2014/March/summ…
Below is the HTML text of the report's summary.
As always, feedback is appreciated on the usefulness of the report and its
summary, and on how to improve them.
------------------------------------------------------------------
Major news in March include:
- an overview of
webfonts<https://blog.wikimedia.org/2014/03/07/webfonts-making-wikimedia-projects-re…>,
and the advantages and challenges of using them on Wikimedia sites;
- a series of
essays<https://blog.wikimedia.org/2014/03/25/seeing-through-the-eyes-of-new-techni…>
written
by Google Code-in students who shared their impressions, frustrations and
surprises as they discovered the Wikimedia and MediaWiki technical
community;
- Hovercards<https://blog.wikimedia.org/2014/03/26/hovercards-now-available-as-a-beta-fe…>
now
available as a Beta feature on all Wikimedia wikis, allowing readers to see
a short summary of an article just by hovering a link;
- a subtle typography
change<https://blog.wikimedia.org/2014/03/27/typography-refresh/>
across
Wikimedia sites for better readability, consistency and accessibility;
- a recap of the upgrade and
migration<https://blog.wikimedia.org/2014/03/28/wikimedias-road-to-bugzilla-4-4/>
of
our bug tracking software.
VisualEditor<https://www.mediawiki.org/wiki/Special:MyLanguage/VisualEditor/Portal>
<https://www.mediawiki.org/wiki/File:VisualEditor_-_2013-14_Q2%E2%80%93Q3_qu…>
<https://www.mediawiki.org/wiki/File:VisualEditor_-_2013-14_Q2%E2%80%93Q3_qu…>
Presentation slides from theVisualEditor team's quarterly review
meeting<https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…>
on
March 26
In March, the VisualEditor <https://www.mediawiki.org/wiki/VisualEditor> team
continued their work on improving the stability and performance of this
visual tool to edit wiki pages. They also added some new features and
simplifications, helping users edit and create pages more swiftly and
easily. Editing templates is now much simpler, moving most of the advanced
controls that users don't often need into a special version of that window.
The media dialog was improved and stream-lined to make it clearer what the
controls are for. The overall design of dialogs and controls was improved
to make it flow better, like double-clicking a block to open its dialog. A
new system for quickly and simply inserting and editing "citations"
(references based on templates) neared completion and will be enabled in
the coming month.
<https://www.mediawiki.org/wiki/File:Parsoid_review_Q3,_March_2014.pdf>
<https://www.mediawiki.org/wiki/File:Parsoid_review_Q3,_March_2014.pdf>
Presentation slides from the Parsoid team's quarterly review
meeting<https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…>
on
March 28
The Parsoid <https://www.mediawiki.org/wiki/Parsoid> team continued with a
lot of bug fixing and
tweaking<https://www.mediawiki.org/wiki/Parsoid/Deployments> of
this parsing program that converts wikitext to annotated HTML, behind the
scenes of VisualEditor. Media and image handling in particular was
improved. In the process, we discovered a lot of edge cases and
inconsistent behavior in the PHP parser, and fixed some of those issues
there as well.
We revamped our round-trip test server
interface<http://parsoid-tests.wikimedia.org/> that
compares the wikitext code of a page before and after it's been converted
into annotated HTML, and back into wikitext. We fixed some issues in the
round-trip test system, and improved our error logging system.
We also designed and implemented a HTML templating
library<https://en.wikipedia.org/wiki/Web_template_system> which
combines correctness, security and performance. This will notably be used
to evaluate HTML templating for translation messages and eventually wiki
content.
Editor engagement <https://www.mediawiki.org/wiki/New_editor_engagement>
This month the Core Features team focused on improvements to how the new
Flow <https://www.mediawiki.org/wiki/Flow> discussion system works with key
MediaWiki tools and processes. We made changes to the history, watchlist,
and recent changes views, adding more context and bringing them more in
line with what experienced users expect from these features. We released a
thank feature in Flow, allowing users to thank each other for posts, and
began work on a feature to close and summarize discussions. Lastly, we
continued work on rewriting the Flow interface to make it cleaner, faster,
and more responsive across a wide number of browsers/devices.
In March, the Growth <https://www.mediawiki.org/wiki/Growth> team primarily
focused on bug fixing, design enhancements, and refactoring of the
GettingStarted <https://www.mediawiki.org/wiki/Extension:GettingStarted>
and GuidedTour <https://www.mediawiki.org/wiki/Extension:GuidedTour>
extensions,
which were recently launched on 30 Wikipedias. We updated icons and button
styles, rewrote the interface text, and refactored the interface to be more
usable in non-English languages. We also began to refactor of the
GuidedTour API, in order to support interactive tours that are non-linear.
Non-linear tours will not depend on a page load to run, which will notably
enable better support for tours in
VisualEditor<https://www.mediawiki.org/wiki/VisualEditor>.
Last but not least, we made progress on measuring the impact of
GettingStarted<https://meta.wikimedia.org/wiki/Research:Onboarding_new_Wikipedians/Rollout>
across
all wikis where it is deployed, with results for the first 30 days of
editor activity expected in early April.
Mobile <https://www.mediawiki.org/wiki/Wikimedia_Mobile_engineering>
The Wikimedia Apps <https://www.mediawiki.org/wiki/Wikimedia_Apps> team
worked on logged-out editing to logged-in editing, and table of contents
refinements.
The Mobile web projects
<https://www.mediawiki.org/wiki/Mobile_web_projects> team
worked on the link inspector for VisualEditor on tablets, and a switch
between VisualEditor and wikitext on tablets. Both are in alpha.
During the last month, with the assistance of the Operations and Platform
teams, the Wikipedia Zero <https://www.mediawiki.org/wiki/Wikipedia_Zero> team
set up the upcoming Partners Portal and continued work on reducing image
size for the mobile web. Additionally, the team added Wikipedia Zero
detection to the Wikipedia for Firefox OS app, as well as contributory
features support for users on partner networks supporting zero-rated secure
connections. With the assistance of the Apps team, new features were added
to the forthcoming reboots of the Android and iOS apps; proof of concept
for full-text search was started on iOS.
Smart, the largest mobile operator in the Philippines, is giving access to
Wikipedia free of data charges through the end of April. We arranged a
meeting with local community members and Smart to explore ways to
collaborate in support of education. The partnerships team started to
review the 27 existing Wikipedia Zero partners, to update the
implementation, identify opportunities for collaboration in corporate
social responsibility (CSR) initiatives and get feedback on the program.
The account reviews will continue for the next few months.
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
https://donate.wikimedia.org
Hey all,
This is just a prior notice that with the merge of
https://gerrit.wikimedia.org/r/#/c/94614/ we've removed the preference for
"Remember my login" from your Special:Preferences. This preference was
removed because it is redundant to the "Remember me" checkbox on the login
form. This is also documented at
https://bugzilla.wikimedia.org/show_bug.cgi?id=52342
This will show up next week, first to mediawiki.org and test wikis Monday,
Tuesday to all non-Wikipedias, and Thursday to all Wikipedias. Thanks to
all the volunteers and staff who time to code/review/test this. :-)
Thank you,
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/