Hi,
I wondered about some things around the Chinese variant conversion:
* When a person uses a search engine, do the links in the results point
directly to one of the variants? That is, does it point to
https://zh.wikipedia.org/zh-cn/Article_name , etc., or simply to
zh.wikipedia.org/wiki/Article_name ? I guess that among Chinese-speaking
people Google is not necessarily as ubiquitous as elsewhere, so there is
probably a separate answer for each search engine.
* If for any search engine the answer above is "yes", does anybody have an
idea about how does that search engine guess the preferred variant? Usage
of simplified / traditional characters in the search query? Geolocation?
Preferred language settings in the browser ("Accept-Language")? Preferences
in the search engine itself? A combination of all of the above? Something
else?
* Does any of the search engine show direct links to country-based variants
- zh-cn, zh-hk, zh-tw, zh-sg, zh-mo? Or to the more generic zh-hans and
zh-hant?
* For users who didn't log in, is the variant selection remembered in a
cookie or in localStorage?
I cannot easily test any of these things myself, because I don't speak
Chinese, I'm not familiar with Chinese search engines, and I don't live in
a Chinese-speaking country (and geolocation matters). But since I care
about language, I'm very curious about this.
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Forwarding.
Pine
---------- Forwarded message ----------
From: Kirill Lokshin <kirill.lokshin(a)gmail.com>
Date: Sun, May 21, 2017 at 5:41 PM
Subject: [Affiliates] Recognition of the Wikimedia Tool Developers Group
To: Wikimedia Movement Affiliates discussion list <
affiliates(a)lists.wikimedia.org>, Wikimedia Mailing List <
wikimedia-l(a)lists.wikimedia.org>
Hi everyone!
I'm very happy to announce that the Affiliations Committee has recognized
the Wikimedia Tool Developers Group [1] as a Wikimedia User Group. The
group is international cooperative of developers who create freely-licensed
tools for improving the Wikimedia projects.
Please join me in congratulating the members of this new user group!
Regards,
Kirill Lokshin
Chair, Affiliations Committee
[1] https://meta.wikimedia.org/wiki/Wikimedia_Tool_Developers_Group
_______________________________________________
Affiliates mailing list
Affiliates(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/affiliates
We just completed another great Wikimedia Hackathon with a ton of great
work happening across many different areas and projects.
>From a release engineering perspective this can also be a bit scary :).
The normal 'train' deployment is scheduled for this week starting
Tuesday May 23rd (per usual).
However, we request that due to the large variance of changes going out
this week please be on the alert and let us know if you see anything out
of the ordinary.
How? We (Release Engineering) have a tracking task per weekly deploy.
This week's is: https://phabricator.wikimedia.org/T163512
Comment on that task or add a subtask to it to indicate a blocker. We'll
respond accordingly. As you can see there's also a number of blockers
being tracked.
Thank you,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
**** DEADLINE EXTENSION****
Due to several requests the SEMANTiCS 2017 conference extends its
submission deadlines.
3rd Call for Research & Innovation Papers
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems
Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc
The Research & Innovation track at SEMANTiCS welcomes the submission of
papers on novel scientific research and/or innovations relevant to the
topics of the conference. Submissions must be original and must not have
been submitted for publication elsewhere. Papers should follow the ACM
ICPS guidelines for formatting
(http://www.acm.org/sigs/publications/proceedings-templates) and must
not exceed 8 pages in lenght for full papers and 4 pages for short
papers, including references and optional appendices.
Research & Innovation Papers are published within ACM ICP Series.
Important Dates (Research & Innovation)
* Abstract Submission Deadline: extended: May 31, 2017 (11:59
pm, Hawaii time)
* Paper Submission Deadline: extended: June 7, 2017
(11:59 pm, Hawaii time)
* Notification of Acceptance: July 3, 2017 (11:59 pm,
Hawaii time)
* Camera-Ready Paper: August 14, 2017 (11:59 pm,
Hawaii time)
For details please go to: https://2017.semantics.cc/calls
or contact the Research and Innovation Chairs:
Catherine Faron Zucker, faron [@] i3s.unice.fr, Université Nice Sophia
Antipolis
Rinke Hoekstra, rinke.hoekstra [@] vu.nl, Vrije Universiteit
Amsterdam/University of Amsterdam
As in the previous years, SEMANTiCS’17 proceedings will be published by
ACM ICP (pending).
SEMANTiCS 2017 will especially welcome submissions for the following hot
topics:
* Data Science (special track, see below)
* Web Semantics, Linked (Open) Data & schema.org
* Corporate Knowledge Graphs
* Knowledge Integration and Language Technologies
* Data Quality Management
* Economics of Data, Data Services and Data Ecosystems
Following the success of previous years, the ‘horizontals’ (research)
and ‘verticals’ (industries) below are of interest for the conference:
Horizontals
* Enterprise Linked Data & Data Integration
* Knowledge Discovery & Intelligent Search
* Business Models, Governance & Data Strategies
* Semantics in Big Data
* Text Analytics
* Data Portals & Knowledge Visualization
* Semantic Information Management
* Document Management & Content Management
* Terminology, Thesaurus & Ontology Management
* Smart Connectivity, Networking & Interlinking
* Smart Data & Semantics in IoT
* Semantics for IT Safety & Security
* Semantic Rules, Policies & Licensing
* Community, Social & Societal Aspects
Data Science Special Track Horizontals
* Large-Scale Data Processing (stream processing, handling large-scale
graphs)
* Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
* Communicating Data (Data Visualization, UX & Interaction Design,
Crowdsourcing)
* Cross-cutting Issues (Ethics, Privacy, Security, Provenance)
Verticals
* Industry & Engineering
* Life Sciences & Health Care
* Public Administration
* e-Science
* Digital Humanities
* Galleries, Libraries, Archives & Museums (GLAM)
* Education & eLearning
* Media & Data Journalism
* Publishing, Marketing & Advertising
* Tourism & Recreation
* Financial & Insurance Industry
* Telecommunication & Mobile Services
* Sustainable Development: Climate, Water, Air, Ecology
* Energy, Smart Homes & Smart Grids
* Food, Agriculture & Farming
* Safety, Security & Privacy
* Transport, Environment & Geospatial
For details please go to: https://2017.semantics.cc/calls
*https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-17
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-17>*
*= 2017-05-17 =*
== Call outs:==
* Please comment on the Reading team's Reading List service RfC:
https://phabricator.wikimedia.org/T164990
* Please update extensions you maintain to add a compatibility policy!
** see https://lists.wikimedia.org/pipermail/wikitech-l/2017-May/088190.html
** if you are not sure, just go with 'rel'
== Reading ==
=== Web ===
* Dealing with fallout from Parser element update.
* Some wikiove: Thank to RelEng for your assistance and SWAT deploys to
return things to normal <3
* Some prevalent log errors fixed.
* Investigating EventLogging duplication bugs with a view to looping in
Analytics.
* Upcoming: We'll be deploying some print styles to the mobile site for
offline use cases; We will be setting up a TextExtracts HTML service (
https://phabricator.wikimedia.org/T165017 ) on REST.
==== Reading Infrastructure ====
* Reading List service RfC: https://phabricator.wikimedia.org/T164990
* doc day: compatibility policy field for mw.org {{Extension}} template
** see https://lists.wikimedia.org/pipermail/wikitech-l/2017-May/088190.html
** please update your extensions pages! (if you are not sure just go with
'rel' )
* Page Content Service planning
==== Android ====
* Breakage related to parser output change appears all clear.
* CSS/JS cross-platform integration work continues.
* Beta release planned for next week.
* Current release board:
https://phabricator.wikimedia.org/project/view/2352/
==== iOS ====
* Last Week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Enhanced search visibility: https://phabricator.wikimedia.org/T130159
*** Update feed design: https://phabricator.wikimedia.org/T141767
* This Week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Analytics https://phabricator.wikimedia.org/T164801
*** Update `In the news` feed logic and design:
https://phabricator.wikimedia.org/T148739
*** Other bug fixes & enhancements
== Editing ==
=== Parsing ===
* https://gerrit.wikimedia.org/r/#/c/333997/ will be merged next week
(minor breaking change in preprocessor -- announcement in tech news 2 weeks
+ editors have been fixing up affected pages)
* Linter fixes necessary to redeploy it on large wikis not yet complete --
expecting to have them done end of week
* This update is a repetition of what has already been mentioned on the
relevant gerrit patches and phab tickets. Parsoid can now handle the
mw-parser-output <div> core change -- by requesting the api to not wrap
output of action=parse. The ParsoidBatchAPI change to do this is part of
1.30.0-wmf.2 and needs to ride the m/w train with the corresponding core
patch.
* https://gerrit.wikimedia.org/r/#/c/354059/ <-- heads up to Flow, CX, VE,
MCS folks; require a +1 from you all
=== Language ===
* No blockers.
* ContentTranslation OOjs UI migration continue.
* CX API end point migration work in progress in services team.
== Research ==
* Reader segmentation test survey went out on 15 May
** https://phabricator.wikimedia.org/T131949
== German Technical Wishlist ==
* Preparing for the Vienna Hackathon.
* RevisionSlider is now a default feature on all wikis.
== Wikidata ==
* Preparing for the Vienna Hackathon.
* Had to work around a Travis/HHVM bug:
https://gerrit.wikimedia.org/r/353872
* Cleaning up user-facing messages in the constraint checks API:
https://phabricator.wikimedia.org/T164354
* Moving forward with the "forms of a lexeme entity" UI:
https://phabricator.wikimedia.org/T160052
== Fundraising Tech ==
* Looking at disabling TLS1.0 - PCI has deprecated it for a while now
** What is the plan for the main cluster?
* Updating thank you letters and sending code
* Fixing currency display in Civi
* Library-ization work
* Preparing for a decent-sized CentralNotice deploy
== Technical Operations ==
* '''Blocking'''
** None
* '''Blocked'''
** No one
* Updates
** Work ongoing on goals (Kubernetes, SE Asia caching PoP, Swift)
** SMW has been removed from wikitech
** Preliminary support for Debian Stretch in labs (on a per project basis)
** HHVM 3.18 rolled out in production
- my apologies for cross-posting -
Hey all,
tomorrow the RevisionSlider [1] will be available as a default feature for
all users on all wikis. The RevisionSlider adds a slider view to the diff
page so that you can easily move between revisions. The slider view is
collapsed by default, and will load by clicking on it. It can also be
turned off entirely in the user preferences. The RevisionSlider has been a
default feature on German, Arabic and Hebrew Wikipedia for 6 months and a
beta feature on all wikis for 8 months. In addition to the users of the
default feature, the extension is used by more than 38K beta feature users
[2] and we have spent the past months addressing the issues raised.
The feature fulfills a wish from the German Community’s Technical Wishlist
[3], is inspired by DerHexer's revisionjumper gadget [4] and based on a
prototype <https://meta.wikimedia.org/wiki/Community_Tech/RevisionSlider>by
the WMF's Community Tech Team
<https://meta.wikimedia.org/wiki/Community_Tech> [5].
Thanks to everyone who tested RevisionSlider and gave valuable feedback to
improve the feature! We hope that RevisionSlider will continue to serve all
contributors well.
Lea (for WMDE's Technical Wishes team)
[1] https://www.mediawiki.org/wiki/Extension:RevisionSlider
[2] https://grafana.wikimedia.org/dashboard/db/mediawiki-revisionslider
[3] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes
[4] https://en.wikipedia.org/wiki/User:DerHexer/revisionjumper
[5] https://meta.wikimedia.org/wiki/Community_Tech/RevisionSlider
--
Lea Voget
Product Manager Technical Wishlist
Produktmanager Technische Wunschliste
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hi, the Wikimedia Foundation has published a draft of its Annual Plan
FY2017-18
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/…>
and it welcomes your review.
I want to highlight here the improvements that we are proposing to the
developer events (co)organized by the WMF. From local to global:
The Technical Collaboration team proposes to combine multiple activities
(often disconnected) in a single program focusing on onboarding new
developers
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/…>.
We
want to work with the Wikimedia technical community to bring a new wave of
developers to our projects, and events play an important role.
Local developer events
We want to support developers and organizations willing to reach out to
specific groups and geographies. We are hoping to see many local developer
meetups and small hackathons or workshops around the World, starting small
and simple. We should be able to offer introductory materials, contacts
with Wikimedia developers in the region, maybe travel budget to send
experienced volunteers to help mentoring the in the bigger events, maybe
travel budget to invite the best newcomers to our regional and global
events.
Adding tech to regional Wikimedia events
Last year we experimented organizing technical workshops in WikiArabia, and
others have done similar efforts in other regional events (for instance, a
small hackathon next to WikiConference India). We want to work with the
organizers of these regional events in order to attract experienced
Wikimedia developers and newcomers, organize developer activities, and also
improve the collaboration between the technical and non-technical
contributors in these regions.
Better retention of newcomers at the Wikimedia and Wikimania hackathons
Although we don't expect major changes in the organization of the Wikimedia
Hackathon and the hackathon at Wikimania, we want to focus better on new
developers onboarding and retention. In every Hackathon we meet many new
developers, but the retention rates are very low. We want to review what we
can do before, during, and after these apparently successful events in
order to retain newcomers better. One hypothesis is that we should focus
call for participation, scholarships, and Wikimedia Foundation
participation in providing a great experience to new volunteers who have
gone through local and regional events, and also "junior" developers coming
from wiki projects through the development of bots, gadgets, tools,
templates.
A smaller and more focused Wikimedia Developer Summit
After some discussions between Community Engagement, Technology, and
Product, we have decided to propose a different approach for the Wikimedia
Developer Summit. Organized by the Technology department as part of
their technical
community building
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/…>
efforts, we want the Summit to finally become the venue where the toughest
technical problems are discussed between the stakeholders directly related.
We want to reduce the size/budget of the event, separate it from the WMF
AllHands, and define its main themes well in advance.
A Program Committee <https://phabricator.wikimedia.org/T160996> would
decide these main themes to be discussed at the Summit. We also want to
explore the possibility of tackling some of these themes at the Wikimedia
Hackathon and Wikimania, where we could get most stakeholders involved with
just a little extra effort (since many of them would be attending anyway).
We believe that this approach will serve better the Wikimedia technical
community that we have, and also the the community that we want to have,
with a new wave of developers joining our various projects.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil