[x-posted announcement]
Hello,
The next online office hour session of the Wikimedia Language team is
scheduled for next Wednesday, June 15th, 2016 at 13:00 UTC. This session is
going to be an online discussion over Google Hangouts/Youtube with a
simultaneous IRC conversation. Due to the limitation of Google Hangouts,
only a limited number of participation slots are available. Hence, do
please let us know (on the event page
<https://plus.google.com/u/0/events/cd1bfs8111cbd4lmegqthma65c8>) if you
would like to join in the Hangout. The IRC channel #wikimedia-office and
the Q&A channel for the youtube broadcast will be open for interactions
during the session.
Our last online round-table session was held in March 2016. You can watch
the recording here: https://www.youtube.com/watch?v=0FrowkpBEnQ
I would also like to mention that our team is currently inviting feedback
for Content Translation via a community consultation
<https://www.mediawiki.org/wiki/Content_translation/Community_Consultation_J…>
which will conclude on June 22nd, 2016. We will make a note of any related
feedback received during this session and review it along with the other
comments received on-wiki.
Please read below for the event details, including local time and do let us
know if you have any questions.
Thank you
Runa
== Details ==
# Event: Wikimedia Language team's office hour session
# When: June 15, 2016 (Wednesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160615T1300)
# Where: https://plus.google.com/u/0/events/cd1bfs8111cbd4lmegqthma65c8 and
on IRC #wikimedia-office (Freenode)
# Agenda:
- Updates from the Language team and Q & A.
- Content Translation community consultation:
https://www.mediawiki.org/wiki/Content_translation/Community_Consultation_J…
--
Language Engineering Manager
Outreach and QA Coordinator
Wikimedia Foundation
We usually don't post job openings in mailing lists, but I am making an
exception with this one because our best candidate *might* be subscribed /
idling here.
Developer Advocate
http://grnh.se/asv1wu
Your help spreading the news are also appreciated.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi Romaine,
Yes, the search box on the wikipedia.org portal only shows results for the
language that you're currently searching in (which can be changed by
selecting a new language in the dropdown located in the search box). We
don't yet have the ability to search in all wikis at once but we'd like to
have that capability in the future.
I agree completely with your second point, the language question is a
difficult one. We have so many English readers that the search box is used
quite a bit on the portal, but quite a few other visitors click on one of
the primary language links around the globe and then (presumably) do their
search on that particular wiki. We visualize this information on our Portal
Dashboard <http://discovery.wmflabs.org/portal/#action_breakdown>, if
you're curious to find out more.
We fully intend to use translatewiki.net to help with our sister project
descriptive text once we get the framework setup on the Portal side to
incorporate the push files from translatewiki as they get updated.
Thanks again for the questions and compliments! :)
Cheers,
Deb
--
Deb Tankersley
Product Manager, Discovery
Wikimedia Foundation
On Tue, Jun 7, 2016 at 6:33 PM, Romaine Wiki <romaine.wiki(a)gmail.com> wrote:
> Hi Deb,
>
> Thanks!
>
> I just realised that also the search bar is based on detected language.
> This is logic, but at the same time I miss the option to search in all
> Wikipedias at once, instead of only the one language.
>
> The question about the language is a bit complex for me, especially the
> second part/option of the question. I am just thinking that if I visit an
> internet café or I use the laptop from an other language speaking friend, I
> would like the option to read the page in my own language, instead of the
> browsers language. Of course the detected language is a good starting point
> for most people.
>
> If I visit the portal page and I see a search option, and I do want to
> search something, I would try the search on the portal page. (But I am 100%
> sure that other people see their own language mentioned first and click on
> it.)
>
> About the to be translated text from sister projects, can
> translatewiki.net be used as for many other translations of system
> messages?
>
> Thanks for the work! :-)
>
> Romaine
>
>
>
>
> 2016-06-07 17:51 GMT+02:00 Deborah Tankersley <dtankersley(a)wikimedia.org>:
>
>> Hi Romaine,
>>
>> We're glad you like the new page functionality! I've opened up a ticket
>> <https://phabricator.wikimedia.org/T137215> to fix the Dutch phrase
>> translation typo, thanks for letting us know. :)
>>
>> For your comment about adding in an option to change the language, I'm
>> curious about something, as this has come up before. Would you prefer to
>> use the portal page in the language that is detected (as we do now) or in a
>> different language but not actually searching on that language's wiki?
>>
>> For instance, if your preferred language is Dutch: would it make sense
>> for you to click on that language link on the portal page to go to
>> nl.wikipedia.org and then do a search? Or, even if the browser's
>> language is detected as Dutch (nl) would you rather use the portal page to
>> search in a different language, like English?
>>
>> Yes, thanks for asking, the sister project links will be translated and
>> we have a ticket <https://phabricator.wikimedia.org/T136441> open to get
>> that started. We wanted the descriptive text to be visible on the page to
>> give more insight into the sister projects, even though we don't have the
>> text translated yet.
>>
>>
>> Cheers,
>>
>> Deb
>>
>>
>> --
>> Deb Tankersley
>> Product Manager, Discovery
>> Wikimedia Foundation
>>
>> On Tue, Jun 7, 2016 at 5:13 AM, Romaine Wiki <romaine.wiki(a)gmail.com>
>> wrote:
>>
>>> Hi Deb,
>>>
>>> Great improvement!
>>>
>>> Looking at the page, I only notice one major error. My language is Dutch
>>> (nl), and so my browser/computer system is set that way. However the phrase
>>> is spelled wrong: it says: "De vrieje encyclopedie" while it should say "De
>>> vrije encyclopedie". So: vrieje -> vrije. "vrieje" is not a Dutch word. Can
>>> this be fixed?
>>>
>>> Further I would recommend one thing to be added to the page. Because
>>> large parts of the word visit Wikipedia through internet cafés and
>>> computers elsewhere, I would suggest in the top right/left corner an option
>>> to change the language.
>>>
>>> And one final question: will the bottom section of the page also be
>>> translatable?
>>>
>>> Thanks!
>>> Romaine
>>>
>>>
>>>
>>> 2016-06-07 0:05 GMT+02:00 Deborah Tankersley <dtankersley(a)wikimedia.org>
>>> :
>>>
>>>> Hello,
>>>>
>>>> The Discovery team recently updated the wikipedia.org portal page to
>>>> detect what the visitor's browser's preferred language(s) are and then
>>>> arrange the language links around the globe to match those language
>>>> preferences.
>>>>
>>>> Earlier this year, we ran a successful A/B test
>>>> <https://www.mediawiki.org/wiki/Wikipedia.org_Portal_A/B_testing#A.2FB_test:…>
>>>> that proved promoting our visitor's preferred languages resulted in
>>>> increased visibility and interest into these projects. Also, the display of
>>>> '*The Free Encyclopedia*' phrase is now localized to the visitor's
>>>> first preferred browser language. If there isn't a translation available,
>>>> the phrase will be displayed in English (view a screenshot
>>>> <https://commons.wikimedia.org/wiki/File%3AWikipedia_portal_top_10_links_re-…>)
>>>> as it currently is today.
>>>>
>>>> Additionally, a new A/B test
>>>> <https://www.mediawiki.org/wiki/Wikipedia.org_Portal_A/B_testing#A.2FB_test:…> will kick
>>>> off this week to determine if the listing of languages by article count can
>>>> be displayed in a more modern and streamlined way without decreasing usage
>>>> of the links. Our goal is to promote easy scrolling through the long list
>>>> of languages by article count, but in a dropdown format while also
>>>> providing greater discovery of the sister wiki project links.
>>>>
>>>> More information on past and future work can be found on the wiki page
>>>> <https://www.mediawiki.org/wiki/Wikipedia.org_Portal> as well as the
>>>> sprint <https://phabricator.wikimedia.org/tag/discovery-portal-sprint/>
>>>> and backlog
>>>> <https://phabricator.wikimedia.org/tag/discovery-portal-backlog/>
>>>> boards. We're always interested in receiving constructive feedback
>>>> from the community: if you have a question or comment, please start a discussion
>>>> on the talk page
>>>> <https://www.mediawiki.org/wiki/Talk:Wikipedia.org_Portal>.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Deb
>>>> --
>>>> Deb Tankersley
>>>> Product Manager, Discovery
>>>> Wikimedia Foundation
>>>>
>>>> _______________________________________________
>>>> Wikitech-ambassadors mailing list
>>>> Wikitech-ambassadors(a)lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Wikitech-ambassadors mailing list
>>> Wikitech-ambassadors(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>>>
>>>
>>
>> _______________________________________________
>> Wikitech-ambassadors mailing list
>> Wikitech-ambassadors(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>>
>>
>
> _______________________________________________
> Wikitech-ambassadors mailing list
> Wikitech-ambassadors(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
>
On Wed, Jun 8, 2016 at 4:48 PM, Antoine Musso <hashar+wmf(a)free.fr> wrote:
> On 08/06/16 18:47, Antoine Musso wrote:
>
>> Le 08/06/2016 à 15:02, Antoine Musso a écrit :
>>
>>>
>>> The operation team has worked hard this European morning to backup
>>> files, investigate the raid issue and setup a new host.
>>>
>>> We are in the process of reinstalling everything on the new host and
>>> bring back Jenkins and Zuul on it.
>>>
>>> No ETA yet, since a 5 years old boxes must have hidden issues which
>>> makes it hard to estimate how long it would need to fully recover.
>>>
>>
>> A status update:
>>
>> Ops (Jaime, Faidon, Mark, Chris) had a disk replaced and the raid array
>> is rebuilding right now. Should take roughly an hour from now. If the
>> disk and raid are confirmed to be fine, we would bring back Jenkins and
>> Zuul.
>>
>> A new server has been installed contint1001. Jenkins data are being
>> copied there. We would need to adjust a few network rules and update IP
>> address in configuration files then attempt to switch to that new setup.
>>
>> Main task is:
>> https://phabricator.wikimedia.org/T137265
>>
>
> The CI service is back since 19:00 UTC after a disk got replaced and the
> RAID array rebuild successfully.
>
Thanks hashar and everyone who helped out.
Cheers,
Katie
>
> The issue might well occurs again and we would move the various services
> out of the server (gallium).
>
> --
> Antoine Musso
>
>
>
>
> _______________________________________________
> QA mailing list
> QA(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa
>
--
@wikidata
There is talk in some communities about the wg-globals going away later this year, but I can't find anything in the tech updates or mw.org
Is there any definite time-line for the removal?
Thanks,
Strainu
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-06-08
= 2016-06-08 =
== Product ==
=== Editing ===
==== Collaboration ====
* Blocked - None
* Blocking - Working on External Store on Beta
* Updates
** Expanding our API to fetch notifications by specific pages.
** Working on expandable Echo bundles
** Split Flow Vagrant role to mitigate some issues with Flow having a lot
of MediaWiki-Vagrant dependencies.
==== Language ====
* Blocked: None
* Blocking: None
* Updates:
** Work on ContentTranslation, Compact Language Links continue.
==== Parsing ====
* Parsoid use of service-runner: working with Marko to deal with final
steps (puppet updates, testing in beta cluster).
* Followup RFC for Tidy replacement scheduled today (Wed, Jun 8).
* Released Parsoid 0.5.1 debian package last week.
==== Multimedia ====
* Not blocked, not blocking
* New repository set up for experimental new extension for file annotations
* UploadWizard fixes moving along apace
* Gallery slideshow patch looking nicer, proceeding
=== Reading ===
==== Reading Infrastructure ====
* AuthManager goes live this week!
https://lists.wikimedia.org/pipermail/wikitech-l/2016-June/085871.html
==== Reading Web ====
* Fixing issues with lazy loading images and refs
* AB test of Popups extension ("Hovercards") on hu.wiki in progress (50%
now)
==== Android ====
* Beta release this past Monday (6/6).
https://lists.wikimedia.org/pipermail/mobile-l/2016-June/010250.html
* Working hard on the feed. No dependencies on other teams for this for
the moment.
* On the horizon (Q3): UI updates for cohesiveness and ease of use.
==== Mobile Content Service ====
* Deployed first three feed-related endpoints. Not publicly available yet.
Use labs instance if needed. Still adjusting response format.
==== Community Tech ====
* Testing PageAssessments on Beta Labs (
https://www.mediawiki.org/wiki/Extension:PageAssessments)
* Working on CopyPatrol tool on Tool Labs (
https://tools.wmflabs.org/plagiabot/)
* No blockers
==== iOS ====
* No update
== Technology ==
=== Analytics ===
* We're blocking the Release team on its goal to move deployment to scap3,
we're trying to prioritize and get it done but it might not fit until early
next quarter.
* Pageview API is still throwing 500 errors despite the throttling down to
10 requests per second, we've had an update to the AQS compaction (and an
update to SSDs from spinning slowpokes) under testing for a while, so far
the numbers look about an order of magnitude better.
* Ongoing: normalizing and loading all history from all mediawiki dbs into
Druid
* The team will be at its offsite next week, and Madhu and Dan will be at
Wikimania, Andrew taking vacation after the offsite. Our offsite is in
Berlin and we're working out of WMDE's offices, so if they need us for any
in-person hacking, we're there :)
=== Technical Operations ===
* '''Blocking'''
** Language Engineering on Parallel corpora dumps
https://phabricator.wikimedia.org/T127793
* '''Blocked'''
** None
* '''Updates'''
** ORES is deployed in production. Try it out in http://ores.wikimedia.org
** Got a few problems with services on SCB today
** A jessie appserver passed smoke tests, we are moving towards upgrading
the mw* fleet to jessie now.
** GTID 100% deployed on core dbs. Labs/analytics/dbstore needs work.
** Insecure POST block still coming up June 12 (this weekend)
=== Services ===
* service cluster services outage today
** approx 15 mins
** stil under investigation
* Cassandra partial outage last week during move to 2.2.6
**
https://wikitech.wikimedia.org/wiki/Incident_documentation/20160531-RESTBase
* MathML by default
** hit some initial bumps, should be good now
=== Security ===
* Two usability bugs for Ex::OATHAuth in progress (T136988, T136989)
* Two-factor usability survey on hold until after AuthManager is enabled
* Fix for T129738 will be deployed this week
* Reviews: Use of wheels for deployment by Analytics
=== Research ===
* Wikilabels downtime --
https://wikitech.wikimedia.org/wiki/Incident_documentation/20160531-wikilab…
=== Discovery ===
* '''Blocking''': none
* '''Blocked''': none
* ElasticSearch 2.3 upgrade is finished
* TextCat demo: https://tools.wmflabs.org/textcatdemo/
* Portal now has language detection and sorting
* Investigation of how long the typical portal session is:
https://phabricator.wikimedia.org/T134301
=== Wikidata ===
* Working on MediaInfo and support for structured data on commons
* Deploying ArticlePlaceholder to 3 more wikis tomorrow (June 9)
https://phabricator.wikimedia.org/T135624 (guwiki, lvwiki, nnwiki)
=== RelEng ===
* '''Blocking''': None as far as we know
* '''Blocked''': Reading Infra - AuthManager (blocks 1.27 release)
* '''Updates''':
** REMINDER! Migrate your things to scap3:
https://phabricator.wikimedia.org/project/view/1824/
*** What have you touched? Please migrate! :)
** Phabricator update going out this week (was postponed):
https://phabricator.wikimedia.org/T135068
=== Fundraising tech ===
* Trying to get payments onto 1.26 before 1.25 EOLs
** pondering what to do for the future, including even divorcing
DonationInterface from MW entirely
* Testing new processor in Israel, Japan and Ukraine
* Ready to test new PayPal integration method
* Enhancing fraud & dos mitigation measures
* more work to get off ActiveMQ
* CentralNotice
** potential translation bug rendering banners:
https://phabricator.wikimedia.org/T137247
** listing old cookies to unset or migrate to LocalStorage:
https://phabricator.wikimedia.org/T132640
There is a possible disk failure of our main CI host, 'gallium'. It is
being investigated at:
https://phabricator.wikimedia.org/T137265
We are very sorry for the inconvenience.
Major updates will be sent to the lists with minor updates/investigation
on the task linked above.
Thanks to Kunal and Yuvi for responding so far.
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hi all,
the Reading Infrastructure team will try to enable AuthManager [1] in WMF
production this week, with the following schedule:
- group0 Tuesday 22:00 UTC (yes, that's pretty much now)
- group1 Wednesday 22:00 UTC
- group2 Thursday 22:00 UTC
I apologize for the very late notice. I realize that such a change should
ideally be fixed long before, advertised via the Tech news etc, but
omitting that seemed like the lesser of two evils. We believe we need to
get AuthManager into the 1.27 release as having to support two completely
different authentication systems in the LTS release would be an
unreasonable burden and risk; to do that, we need to test it in production
in very short order, otherwise the release will be delayed a lot due to
vacations and Wikimania; and we weren't sure until very recently whether we
are able to keep to this schedule.
If all goes well, switching AuthManager on should have very little visible
effect (see earlier announcements [2][3]), but with a change of this
complexity all rarely goes well. If you see authentication-related
problems, please ping or cc Brad Jorsch (IRC: anomie) and me (IRC: tgr). If
we are not around and things break badly, you can revert by setting
wgDisableAuthManager to true in wmf-config.
Gergő
https://www.mediawiki.org/wiki/User:Tgr_(WMF)
[1] https://www.mediawiki.org/wiki/Manual:SessionManager_and_AuthManager
[2] https://lists.wikimedia.org/pipermail/wikitech-l/2016-June/085835.html
[3] https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085725.html
