To the right mailing list this time.
---------- Forwarded message ----------
From: Roan Kattouw <rkattouw(a)wikimedia.org>
Date: Tue, Sep 22, 2015 at 2:27 PM
Subject: 1.26wmf24 deployment update
1.26wmf24 is being deployed to WMF wikis this week. This includes changes
to Echo from wmf22 and wmf23 that were reverted or held back over the past
two weeks.
The highlights are:
- The notification flyout split
<https://phabricator.wikimedia.org/T108190> (into alerts/messages) is
back.
- You can now choose to receive a notification when someone sends you an
email <https://phabricator.wikimedia.org/T56130> using Special:Emailuser
(thanks to Umherirrender for the patch!).
- The orange user talk page alert now goes away immediately when you
click "Mark all as read"
<https://phabricator.wikimedia.org/T106033> and when
you view your user talk page <https://phabricator.wikimedia.org/T107655>.
- Pre-filling the title and content of a new Flow topic using URL
parameters now works again <https://phabricator.wikimedia.org/T112037>.
wmf24 will be rolled out according to the standard deployment schedule:
- Tuesday 18:00-20:00 UTC: test wikis (mediawiki.org
<https://www.mediawiki.org/>, testwiki <https://test.wikipedia.org/>,
test2wiki <https://test2.wikipedia.org/> and testwikidata
<https://test.wikidata.org/>)
- Wednesday 18:00-20:00 UTC: non-Wikipedia wikis
- Thursday 18:00-20:00 UTC: Wikipedias
Today's deployment to test wikis was delayed. It hasn't happened yet as of
this writing, but it's likely to happen in the next hour or so.
Whoops, I sent the last couple weeks' worth of deployment updates to the
wrong list. Sorry about that!
---------- Forwarded message ----------
From: Roan Kattouw <rkattouw(a)wikimedia.org>
Date: Wed, Sep 16, 2015 at 2:16 PM
Subject: 1.26wmf23 deployment update
1.26wmf23 is being deployed to WMF wikis this week. There are no new
changes to Echo: Echo is was rolled back to 1.26wmf21 because of a nasty
bug in Safari <https://phabricator.wikimedia.org/T112552> and performance
issues <https://phabricator.wikimedia.org/T112401>; these issues are now
fixed, but Echo will remain frozen this week. We will re-deploy the
notification flyout changes and the other changes from wmf22 and wmf23
along with wmf24 in next week's cycle.
As for things that are actually rolling out this week:
- The button that switches between the wikitext editor and VisualEditor
in Flow has been redesigned <https://phabricator.wikimedia.org/T101316>.
Both editors are now the same size, to make the switch smoother.
- "Mark as resolved" has been moved up
<https://phabricator.wikimedia.org/T110083> to the top half of the
actions menu for Flow posts.
- Translations for the Topic namespace were added in Orya and Korean.
wmf23 is being rolled out according to the standard deployment schedule:
- Tuesday 18:00-20:00 UTC: test wikis (mediawiki.org
<https://www.mediawiki.org/>, testwiki <https://test.wikipedia.org/>,
test2wiki <https://test2.wikipedia.org/> and testwikidata
<https://test.wikidata.org/>)
- Wednesday 18:00-20:00 UTC: non-Wikipedia wikis
- Thursday 18:00-20:00 UTC: Wikipedias
Flow will start appearing more widely soon when we release a feature to
allow users on certain wikis to opt into Flow on their user talk pages.
The most common thing you'll probably want to do on a Flow page is post
a new topic.
For Pywikibot, that is pretty easy, since they have Flow support now.
See https://www.mediawiki.org/wiki/Manual:Pywikibot/Flow .
For on-wiki scripts, you can use MessagePoster (you don't need to know
if it's a Flow board ahead of time!):
---
var title = new mw.Title( 'titleString' );
var posterPromise = mw.messagePoster.factory.create( title );
posterPromise.done( function ( poster ) {
poster.post( 'This is the topic title', 'This is the body of a message
posted with MessagePoster' );
} );
---
Depend on 'mediawiki.messagePoster' and 'mediawiki.Title'.
In some cases, you might want to check if a link is already there (e.g.
to see if a warning template already included links to a particular
policy). You can use prop=links for this.
Flow is based on an infinitely-scrollable list of topics, each of which
is its own page. So to use prop=links, you may need to loop through a
set of recent enough topics (e.g. 25) then combine them into a
prop=links request, e.g.
https://www.mediawiki.org/w/api.php?action=query&titles=Topic:Sojpiv245cuiw…
.
pywikibot has support for looping through topics.
Some bots need to check the header of a page for wikitext (e.g. a bot
exclusion template). This can be done with view-header, but I don't
think pywikibot has support for that yet (but it can be done directly).
See
https://www.mediawiki.org/w/api.php?action=flow&format=jsonfm&page=Talk%3AF…
.
A better way to do this would be templatelinks, but I'm not sure if
there is an API to show templates PageX transcludes.
For other questions, contact us at #wikimedia-collaboration . Or, if a
certain tool needs Flow support and you're not sure where to start, you
can file a bug (you can also reply here, but a ping in IRC would be
appreciated).
Matt Flaschen
Perhaps interesting to those who see opportunities for gamification on
Wikipedia projects.
"Games like World of Warcraft give players the means to save worlds, and
incentive to learn the habits of heroes. What if we could harness this
gamer power to solve real-world problems? Jane McGonigal says we can, and
explains how."
https://www.youtube.com/watch?v=dE1DuBesGYM
Pine