In the next RFC meeting, we will discuss the following RFC:
* Create a proper command-line runner for MediaWiki maintenance tasks
https://phabricator.wikimedia.org/T99268
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:
* UTC: Wednesday 21:00
* US PDT: Wednesday 14:00
* Europe CEST: Wednesday 23:00
* Australia AEST: Thursday 07:00
-- Tim Starling
[x-posted announcement]
Hello,
A reminder that the online office hour hosted by the Wikimedia Language
Engineering team is happening later today at 14:30 UTC. You can join the
hangout or watch the session from:
https://plus.google.com/u/0/events/cuunke6rbmqpetvslv6jlakbhnc
Please note, due to the limitation of Google Hangouts there are few seats
available. So please let us know before hand if you would like to
participate on the hangout. We will also be on the IRC channel
#wikimedia-office to take questions. Please see below for the event
details, local time and original announcement.
Thanks
Runa
== Details ==
# *Event*: Wikimedia Language Engineering office hour session
# *When*: June 10th, 2015 (Wednesday) at 14:30 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150610T1430)
# *Where*: https://plus.google.com/u/0/events/cuunke6rbmqpetvslv6jlakbhnc and
on IRC #wikimedia-office (Freenode)
# *Agenda*: Content Translation
<https://www.mediawiki.org/wiki/Content_translation> updates and open Q & A
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Thu, Jun 4, 2015 at 10:20 AM
Subject: Next Language Engineering Office Hour is on 10th June 2015
(Wednesday) at 1430 UTC
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia
developers <wikitech-l(a)lists.wikimedia.org>, MediaWiki internationalisation
<mediawiki-i18n(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration
[Public]" <glam(a)lists.wikimedia.org>
Hello,
The next office hour of the Wikimedia Language Engineering team (now part
of Editing) is scheduled for next Wednesday, June 10th at 14:30 UTC.
However, this time instead of only IRC we are hosting it as an online
discussion over Hangout/Youtube. Given the limitation of Google Hangouts,
there will be limited seats for joining into the Hangout. Hence, do let us
know (on the event page
<https://plus.google.com/u/0/events/cuunke6rbmqpetvslv6jlakbhnc>) if you
would like to participate on the Hangout. The IRC channel #wikimedia-office
and the Q&A channel for the youtube broadcast will also be open for
interactions during the session.
Our last online round-table session was held a few months back with the
editors of the Catalan Wikipedia. You can watch the recording here:
https://www.youtube.com/watch?v=vHu3vdlE1X8 .
Please read below for the event details and do let us know if you have any
questions.
Thank you
Runa
== Details ==
# *Event*: Wikimedia Language Engineering office hour session
# *When*: June 10th, 2015 (Wednesday) at 14:30 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150610T1430)
# *Where*: https://plus.google.com/u/0/events/cuunke6rbmqpetvslv6jlakbhnc
and on IRC #wikimedia-office (Freenode)
# *Agenda*: Content Translation
<https://www.mediawiki.org/wiki/Content_translation> updates and open Q & A
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Tomorrow I'm going to make another attempt at switching us over to
a new labs controller host. That won't break anything for running labs
instances, but it will probably have some or all of the following
effects on wikitech users:
1) Wikitech will go into maintenance mode
2) Wikitech sessions will end and you'll have to re-log in
3) New logins may fail (briefly, if the keystone switch goes poorly)
4) Instance creation/deletion and status queries may fail
I'll send an 'all clear' after this switch is finished or abandoned.
-Andrew
Migrating thread to wikitech-l.
-Adam
On Tue, Jun 9, 2015 at 7:17 AM, Brian Gerstle <bgerstle(a)wikimedia.org>
wrote:
> Yeah, this was more of an ad-hoc thing so that we could cherry-pick things
> to go in our next release. I wouldn't recommend trying this to model pull
> requests, since, like you said, it would require submitting another patch
> to merge your "PR" branch.
>
>
> On Tue, Jun 9, 2015 at 6:51 AM, Joaquin Oltra Hernandez <
> jhernandez(a)wikimedia.org> wrote:
>
>> Yo can you expand on how to use this to do branch-driven development?
>> Seems like you could get something similar to PRs by doing this.
>>
>> I guess you have to do a merge patch later to master?
>>
>> On Tue, Jun 9, 2015 at 12:21 AM, Gergo Tisza <gtisza(a)wikimedia.org>
>> wrote:
>>
>>> On Mon, Jun 8, 2015 at 3:10 PM, Brian Gerstle <bgerstle(a)wikimedia.org>
>>> wrote:
>>>
>>>> For anyone iOS or gerrit inclined I just created a "4.1.5" release
>>>> branch and submitted a patch
>>>> <https://gerrit.wikimedia.org/r/#/c/216861/> using "git review 4.1.5".
>>>>
>>>> This was done by:
>>>>
>>>> 1. Pushing a new branch to gerrit
>>>> 1. git push -u origin HEAD:4.1.5
>>>> 2. Submitting the patch to the newly created branch
>>>> 1. commit some changes...
>>>> 2. git review 4.1.5
>>>>
>>>> Step #1 requires push permissions for your target repo.
>>>>
>>>
>>> If there is future work to be done on the branch (backports etc.) it's a
>>> good idea to change defaultbranch in .gitreview to avoid accidents (that
>>> branch will be used if you run git review without a branch name).
>>>
>>
Sorry if this is the wrong list, please feel free to distribute as
appropriate...
Details (developing) here:
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Computational_Biology/E…
Message from Jo McEntyre:
We are organising a Wikipedia-Europe PMC hackathon on 4th Sept on the
genome campus, around the Wikipedia Science conference:
https://wikimedia.org.uk/wiki/Wikipedia_Science_Conference.
With Daniel Mietchen, the three themes we have identified are:
- contributing datasets e.g. data citations, text-mined entities from
Europe PMC to Wikidata & possibly seeing this pushed through to some
Wikipedia pages
- import of full text articles into Wikisource and potential
highlighting named entities
- pushing PMID-PMCID-DOI mapping to Wikidata/Wikipedia
We would very much like you to attend!
Now that I finally have JS previewing for wikicode working a bit better...
I present a new user script:
https://en.wikipedia.org/wiki/User:TheDJ/ActualLivePreview.js
If your window is wider then 1200px, it will split it in half and show you
your edit surface and your content preview side by side, automatically
updating the preview !
How cool is that :)
Please test it, and let me know, if you think we should add something like
this to core !
DJ
Hi everybody!
More than six months ago, Wikimedia migrated its bug report management
from Bugzilla to Phabricator.
At the same time, Bugzilla was turned read-only (but still allowed
users to log in to access and manually migrate votes or saved searches)
and moved to the address old-bugzilla.wikimedia.org.
Before that migration, users were asked to join Phabricator and were
made aware of required steps and limitations [1].
This was done via a banner on top of Bugzilla, emails on wikitech-l@,
announcements on en.wp Village Pump, and two emails to all Bugzilla
users who had logged in since October 2013 [2].
Now after everybody had more than six months to switch to Phabricator,
old-bugzilla.wikimedia.org is planned to get switched off on June 22nd
[3] (as keeping Bugzilla running requires maintenance like applying
security updates).
Thanks to John and Daniel, a static HTML version of old-bugzilla exists
at
https://static-bugzilla.wikimedia.org [4].
It allows to still access those historical Bugzilla reports and the
related history/activity.
Please note that you can still claim the activity of your Bugzilla
account imported into Phabricator [5] after switching off old-bugzilla,
as this functionality does not rely on old-bugzilla being available.
I'd like to thank John & Daniel for all their work creating static-bz!
Cheers,
andre
[1] https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Missing_data
[2] https://phabricator.wikimedia.org/T618
[3] https://phabricator.wikimedia.org/T95184#1327072
[4] https://phabricator.wikimedia.org/T85140
[5] https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugz…
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
> Again, the same problem with the infobox and lead image, but there
> was a gallery that popped over and I was quite pleased with that.
I'm glad to hear, thank you :)
> I published the article with no categories, because the categories didn't
> line up this time as they did in the Spanish-Dutch case.
Yes - categories adaptation works only if directly corresponding category
pages can be found in both languages. We may make it smarter in the
not-so-far future.
> Thinking over my experience, I would prefer you incorporate the Wikidata
item info to build the infobox, rather than the source article.
Using Wikidata for infoboxes would be ideal, of course. This requires
better adaptation of infoboxes to Wikidata, and this must be done by the
communities, but some work is being done in that direction.
> I was working on a painting, but a generic biography infobox has already
been done with the PrepBio tool (from Magnus) so you could use that:
https://tools.wmflabs.org/magnustools/prepbio.php
Thanks, I'll consider it. (We are already using another tool by Magnus in
the dashboard, if you haven't noticed ;) )
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
2015-06-06 20:28 GMT+03:00 Jane Darnell <jane023(a)gmail.com>:
> Thanks for your thoughtful answerrs, which are certainly enlightening. I
> tried it again today, this time to translate an article from English to
> Dutch. Again, the same problem with the infobox and lead image, but there
> was a gallery that popped over and I was quite pleased with that. I
> published the article with no categories, because the categories didn't
> line up this time as they did in the Spanish-Dutch case. Thinking over my
> experience, I would prefer you incorporate the Wikidata item info to build
> the infobox, rather than the source article. This would be a good trigger
> for people to update the Wikidata item should they notice any differences.
> I was working on a painting, but a generic biography infobox has already
> been done with the PrepBio tool (from Magnus) so you could use that:
> https://tools.wmflabs.org/magnustools/prepbio.php
>
> On Sat, Jun 6, 2015 at 6:55 PM, Amir E. Aharoni <
> amir.aharoni(a)mail.huji.ac.il> wrote:
>
> > Hi Jane,
> >
> > Thanks for trying ContentTranslation and providing feedback. Replies
> > inline.
> >
> > > I decided to translate a short article from Spanish to English
> >
> > Currently the extension is configured for translation *from* English, but
> > not *to* English. This will probably be changed soon to allow translation
> > to English, but there will be a proper separate announcement about this.
> >
> > > Then I tried to enable it for my 'Dutch userpage and
> > > got the extension up and running for Spanish-Dutch but couldn't find
> > which
> > > link was the "from" link and the "to" link (a couple of tries and I got
> > the
> > > dashboard up and running).
> >
> > The easiest ways to open the dashboard are:
> > 1. Hovering over the Contributions link at the top personal bar and
> > clicking "Translations".
> > 2. Opening the article that you want to translate and finding the
> language
> > into which you want to translate in the interlanguage links list. (It's
> > guessed automatically; for example, it's suposed to appear there if you
> > selected it in ULS.)
> >
> > > Then I found myself in the Visual editor
> >
> > It's not *the* VisualEditor, but *a* visual editor - a very simple
> WYSIWYG
> > editor. (It's possible that in the future it will be *the* VisualEditor,
> > but there's no solid plan for it yet.) There are several reasons for
> doing
> > it this way, see
> > https://www.mediawiki.org/wiki/Content_translation/Documentation/FAQ .
> >
> > > and tried to wikify some text with no luck.
> >
> > It doesn't support wiki syntax, as explained above. It supports simple
> > formatting and adding links (the links support is being rewritten right
> now
> > to be more stable and intuitive). Because it is not supposed to be a
> > full-fledged article editing environment, it only provides the most basic
> > formatting tools. For full-fledged wikification you can use the wikitext
> > editor or the VisualEditor, whichever you wish.
> >
> > > I then clicked on one
> > > of the reference links and lost my work.
> >
> > This is definitely a bug! Usually references work pretty well. Sorry
> about
> > that. Which article was it?
> >
> > > I restarted the page and saved
> > > some basics, but was disappointed that there was no translation of the
> > > infobox or the image, which was what I was hoping for.
> >
> > We don't support infoboxes yet. It's very challenging technically, so for
> > now we just ignore them, but we hope to have support for them in the
> > future. Currently, ContentTranslation is mostly for the articles' prose,
> > links, categories and images.
> >
> > It is supposed to support images. In fact, in the real-life demos that
> I'm
> > doing it's the feature that experienced Wikipedians usually love the
> most.
> > Unfortunately, it cannot support an image that is a part of an infobox.
> >
> > > Thanks for all of your work on this, because I do believe translating
> > > existing content is a direction that I personally want to take in the
> > > Wikiverse in general.
> >
> > Thank you very much again for the testing and the feedback! We'll do our
> > best to address the bugs.
> >
> >
> > --
> > Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> > http://aharoni.wordpress.com
> > “We're living in pieces,
> > I want to live in peace.” – T. Moore
> >
> > 2015-06-05 12:41 GMT+03:00 Jane Darnell <jane023(a)gmail.com>:
> >
> > > Amir,
> > > This tool is great in theory and sounds wonderful but I am personally
> > > having some trouble putting it into practice.The short video was VERY
> > > helpful, but I am afraid I still ran into some problems on my second
> > > attempt at a translation. Here is a roundup of links:
> > >
> > >
> >
> https://upload.wikimedia.org/wikipedia/commons/e/ee/Content_Translation_Scr…
> > >
> > > I decided to translate a short article from Spanish to English but
> since
> > my
> > > Spanish is almost zero I first tried to change the translation
> interface
> > to
> > > English but no luck. Then I tried to enable it for my 'Dutch userpage
> and
> > > got the extension up and running for Spanish-Dutch but couldn't find
> > which
> > > link was the "from" link and the "to" link (a couple of tries and I got
> > the
> > > dashboard up and running). Then I found myself in the Visual editor
> > > (yikes!) and tried to wikify some text with no luck. I then clicked on
> > one
> > > of the reference links and lost my work. I restarted the page and saved
> > > some basics, but was disappointed that there was no translation of the
> > > infobox or the image, which was what I was hoping for.
> > >
> > > Here's the original:
> > >
> > >
> >
> https://es.wikipedia.org/wiki/La_sala_del_concejo_del_ayuntamiento_de_%C3%8…
> > > Here's the result (all I got was the Wikidata item link, lead sentence
> > and
> > > the category)
> > > https://nl.wikipedia.org/wiki/Raadskamer_in_het_stadhuis_van_Amsterdam
> > >
> > > Wikimagic added the Dutch infobox already, but shouldn't this be
> possible
> > > to do from the dashboard?
> > >
> > > Thanks for all of your work on this, because I do believe translating
> > > existing content is a direction that I personally want to take in the
> > > Wikiverse in general.
> > > Jane
> > >
> > > Thanks,
> > > Jane
> > >
> > > On Thu, Apr 30, 2015 at 3:23 PM, Amir E. Aharoni <
> > > amir.aharoni(a)mail.huji.ac.il> wrote:
> > >
> > > > [ cross-posted to MediaWiki-i18n, Wikimedia-L and Wikitech-L ]
> > > >
> > > > Dear Wikimedians,
> > > >
> > > > The 2000th article that was written using the ContentTranslation
> > > extension
> > > > was published today.
> > > >
> > > > Article #2000 was translated from English to Greek, and it's about
> > > Škocjan
> > > > Caves, a UNESCO World Heritage site in Slovenia.
> > > >
> > > > Original: https://en.wikipedia.org/wiki/%C5%A0kocjan_Caves
> > > > Translated:
> > > >
> > > >
> > >
> >
> https://el.wikipedia.org/wiki/%CE%A3%CF%80%CE%AE%CE%BB%CE%B1%CE%B9%CE%B1_%C…
> > > >
> > > > In case you're wondering what ContentTranslation is, here's a brief
> > > > summary: ContentTranslation is an extension that helps Wikipedia
> > editors
> > > to
> > > > create articles quickly and easily by translating them from other
> > > > languages. It's being developed by the Language Engineering team. Its
> > > > design started in the summer of 2013 and its coding started in early
> > > 2014.
> > > > You can find more info at https://www.mediawiki.org/wiki/CX as well
> as
> > > in
> > > > the following blog posts:
> > > > *
> > > >
> > >
> >
> http://blog.wikimedia.org/2015/01/10/content-translation-beta-coming-soon/
> > > > * http://blog.wikimedia.org/2015/01/20/try-content-translation/
> > > > *
> > > >
> > >
> >
> http://blog.wikimedia.org/2015/04/06/content-translation-improved-my-edits/
> > > > *
> > http://blog.wikimedia.org/2015/04/08/the-new-content-translation-tool/
> > > >
> > > > Some more data about ContentTranslation:
> > > > * Our first deployment was in mid-January to Catalan, Spanish,
> > > Portuguese,
> > > > Esperanto, Norwegian Bokmal, Danish, Indonesian and Malay. Now we
> > support
> > > > 43 languages, and this number is growing every week as we extend the
> > > > deployment (a special thank-you to the Ops and Release Engineering
> > > people,
> > > > who continuously and tirelessly support our deployment effort).
> > > > * In all the Wikipedias in which ContentTranslation is deployed, it
> is
> > > > currently defined as a Beta feature, which means that it is only
> > > available
> > > > to logged-in users who opted into it in the preferences.
> > > > * The 1000th article was written on April 10th, so it took much less
> to
> > > get
> > > > to 2000 than to 1000.
> > > > * The language into which the most articles were translated is
> Catalan:
> > > > 762. The Catalan Wikipedia community always had a strong inclination
> to
> > > > translation, it was the first one that volunteered to test the tool
> in
> > > labs
> > > > in the summer of 2014 and provided a lot of useful feedback, and it
> > also
> > > > has good machine translation support thanks to the Freely-licensed
> > > Apertium
> > > > engine.
> > > > * The second most popular target language is Spanish. It started
> slowly
> > > in
> > > > the first couple of months, but it's quickly growing since March.
> > > > * Other target languages that are quickly growing lately are French,
> > > > Portuguese and Ukrainian.
> > > > * The language from which the largest number of articles is
> translated
> > is
> > > > English. It is followed by Spanish, from which a lot of articles are
> > > > translated to the closely related Portuguese and Catalan.
> > > > * The total number of people who published at least one translated
> > > article
> > > > into any language is 663.
> > > > * Of more than 2000 articles that were created, about 60 were
> deleted,
> > so
> > > > we have a reason to think that the quality of the created articles is
> > > > pretty OK.
> > > > * In Catalan we see that ContentTranslation has some influence on the
> > > > number of articles created per day - it was usually between 60 and 90
> > > > before 2015, and in January and February it was over a 100. It's too
> > > early
> > > > to say how does it influence other languages, but we are optimistic
> ;)
> > > > * A community discussion about enabling the tool in the French
> > Wikipedia
> > > > ended with 50 "votes" in support of the tool and 0 "votes" against it
> > ;)
> > > >
> > > > Some of our plans for the coming months are:
> > > > * Enabling more languages, including big ones like English, Russian
> and
> > > > Italian, as well as right-to-left languages.
> > > > * Improving the support for links.
> > > > * Creating support for smart suggestions of articles to translate, as
> > > well
> > > > as "task lists" for translation projects.
> > > > * Starting to get the tool out of beta status :)
> > > >
> > > > I'd like to thank all the Wikimedia volunteers around the planet who
> > are
> > > > participating in this effort by translating articles, translating the
> > > > extension's user interface, testing the tool, assisting other
> > wikipedians
> > > > to translate, organizing translation workshops, reporting useful
> bugs,
> > > > submitting patches, and generally proving day after day what an
> > > incredible
> > > > community they are - hard-working, massively-multilingual, helpful,
> > > > patient, creative and talented.
> > > >
> > > > Thank you - we have a lot more to achieve together \o/
> > > >
> > > >
> > > > --
> > > > Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> > > > http://aharoni.wordpress.com
> > > > “We're living in pieces,
> > > > I want to live in peace.” – T. Moore
> > > > _______________________________________________
> > > > Wikimedia-l mailing list, guidelines at:
> > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> > > > Wikimedia-l(a)lists.wikimedia.org
> > > > Unsubscribe:
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
> > > _______________________________________________
> > > Wikimedia-l mailing list, guidelines at:
> > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> > > Wikimedia-l(a)lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
> > >
> > _______________________________________________
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> > Wikimedia-l(a)lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>
I would like some more eyes on https://phabricator.wikimedia.org/T94307.
Since its inception, page status indicators have one major drawback;
automatic sorting cannot be disabled.
It purports to give placements control as it sorts by indicator name,
but this proves difficult, as none of the templates invoking idicators
allow passing the name. And even then, order is not guaranteed due to
the used sorting algorithm.
So while in theory, it would make more sense to leave sorting be
govenrned by local consensus, we are now stuck with a solution that
essentially does not allow any order control at all.
I submitted a patch that disables sorting, but the task and patch are
stalled. So please, more voices and solutions on how we can solve this.
Regards,
--
Erwin Dokter
Risker wrote:
I've drifted in and out of the VE discussion, and have participated at
> wildly
variable levels over the past few years.
>
> I found this to be a very interesting and informative read - especially as
> it came from people new to the entire history. It's good to have fresh eyes
> on a situation. Thank you for your work on this, it was
> quite enlightening.
>
Heartily seconded. Thank you!
SJ