Hi everyone!
The Echo notifications are wonderfully good idea! Is it possible to create
the Echo events inside my extensions? For example I want my voting
extension to produce Echo notifications to the contributors of the article
each time someone have voted for this article.
-----
Yury Katkov, WikiVote
This is RC4 for 1.21.0 due to be released on May 15, 2013. The
patches included since RC3 are after the download instructions.
While testing this release candidate, I discovered a bug in the
installer (Bug #47489) which I would like to get fixed before a final
release.
I've changed the list of bugs I would like to see fixed in the next
couple of weeks before release to 3 installer-only bugs:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=47489%2C46802%2C43817https://bugzilla.wikimedia.org/43817
Include short descriptions for extensions bundled in the release
https://bugzilla.wikimedia.org/46802
Enabling extensions during install process displays empty readonly
textbox on status page
https://bugzilla.wikimedia.org/47489
white screen after no db selection
I'll take a stab at these, but I appreciate any help you guys can give.
Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc4.tar.gzhttp://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.tar.gz
Patch to previous version (1.20.0), without interface text:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.patch.gz
Interface text changes:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc4.patch…
GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc4.tar.g…http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.patch.gz.s…http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc4.patch…
Public keys:
https://secure.wikimedia.org/keys.html
Patches included since RC3:
commit 29d3243339f836ad13a722762e4b0f7056ee3764
Author: Brad Jorsch <bjorsch(a)wikimedia.org>
Date: Sun Mar 3 22:35:05 2013 -0500
Add parser method to call parser functions
There is currently no straightforward way for anything to call a
parser function and get the result. This abstracts out that portion
of braceSubstitution() to allow this.
The immediate motivation for this patch is to close bug 41769
against Scribunto, see I0138836654b0e34c5c23daaedcdf5d4f9d1c7ab2.
Bug: 41769
Change-Id: I339b882010dedd714e7965e25ad650ed8b8cd48f
commit c81f3673423021c92a8e08a207236b4d48b0bc46
Author: Timo Tijhof <ttijhof(a)wikimedia.org>
Date: Tue Mar 26 18:59:07 2013 +0100
mw.loader: Guard against odd setTimeout behaviour in old Firefox
Bug: 46575
Change-Id: I80af730daa815f0c273fe942c570d1f0144bbbb1
commit d43c43727c0273ab9a861b39a70609bfbe14a801
Author: PleaseStand <pleasestand(a)live.com>
Date: Wed Apr 17 13:49:50 2013 +0000
Revert "Remove link to Special:ActiveUsers from Special:Statistics"
Special:ActiveUsers still seems to be in REL1_21, and
there is a pending change set (Ib43b4205) to add back
the special page on the master branch.
This reverts commit 4b2c7373f2ab6f701cbd7f371ad4b95829e34e70
Change-Id: I5669477091ada36ea28c33de1232d2b7e9d0b413
commit c6528bb73b99de3ae6a5f3d8493e9dc8a1eb9120
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:42:02 2013 -0700
Sanitize $limitReport before outputting
Prevents possible injection of "-->" and other HTML by extensions
using the ParserLimitReport hook.
bug: 46084
Change-Id: Id97b6668da6df3e5e4c0acefffa00c82cac3c44a
(cherry picked from commit 69f96f65dd99e54b84e489e7d957b7526653474c)
commit 73f30041f2cf4f5cac08bb3b37a38fa80832bec3
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:44:23 2013 -0700
Disable external entities in XMLReader
Temporarily disable loading entities in XMLReader when calling
read() with libxml_disable_entity_loader(true).
bug: 46859
Change-Id: I0b2ef270f15c7b4da17edee680bf7e2410919915
(cherry picked from commit 1ed76385c31f44c589f6e5a99c9c56f1f3f76728)
commit 9c902fb78536566c3deb85cc1bfb033074520e22
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:47:10 2013 -0700
Disable external entities in Import
Temporarily disable loading entities in XMLReader when calling
read() during import.
(cherry picked from commit 77a8d576918b6a47b80a67a3653662a2d705d6c3)
bug: 47251
Change-Id: I0b39386e6cf4ec0244aab8ebc4095922511e2964
Hi,
Reading the "2012-13 Plan", I see that multimedia is one the key
activities for Mediawiki. So I was wondering if there was already any
plan to integrate 3D model viewers, which would be for example very
interesting for anatomy articles, or simply 3D maths objects.
MediaGoblin[1] show that we already all the free software stack to do
that, however I don't have enough data to estimate development charges
of that kind of features into Wikimedia.
[1] https://en.wikipedia.org/wiki/GNU_MediaGoblin
--
Association Culture-Libre
http://www.culture-libre.org/
Hi,
My name is Yanna and I'm interested in this mobilizing Wikidata idea. I
have read the thread about the topic and I agree with the idea that we can
first use MobileFront to see the result. My suggestion regard to the
data-editing feature is that we should remove the column of edit button and
implement gestures recognition on each editable entry. The editing feature
can be called upon certain gesture. Currently I can think of two solutions:
1. long press gesture. After a long press is detected, the edit or add menu
should pop up, thus allowing the pressed entry to be modified. 2. Second
tap detect. When the user first tap the entry, it becomes highlighted. If
the highlighted entry is tapped again, then it turns to the state of being
modified. So that's basically my suggestions, I'd like to hear about your
opinions.
I have some experience with PhoneGap, using html/css to build native mobile
apps. I also have experiences with mobile app development (specifically ios
app), so I'm familiar with the mobile UI development. I think my experience
will help a lot in mobilizing Wikidata. I'm planning to apply for the GSOC
AND the Outreach Program for Women. I'm looking forward to some suggestions
about what I could contribute.
Thanks,
Yanna
---------- Forwarded message ----------
From: Jean-Frédéric <jeanfrederic.wiki(a)gmail.com>
Date: 21 April 2013 00:23
Subject: [Commons-l] UniversalSubtitles support
To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>
Hi list,
We used to have UniversalSubtitles [1] support on Wikimedia Commons
(and it was awesome)
Since the removal/deprecation/painful death of mwEmbed/multimedia beta
[2] this is gone.
Any chance we might have that back? If so, how? Who must be harrassed
to that end?
Thanks for your help,
(Not sure which list to send that − wikitech-l, wikivideo-l ? Feel
free to forward around)
[1] https://commons.wikimedia.org/wiki/Commons:Universal_Subtitles
[2] The help page about it was even deleted last month…
--
Jean-Frédéric
_______________________________________________
Commons-l mailing list
Commons-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/commons-l
Right now the MediaWiki namespace is protected from editing. However, if you add a template to a Mediawiki message and the template is unprotected, any user could edit the message by editing the template, creating a backdoor. There is no option to cascade protect MediaWiki messages on wiki, and there is no function in the MediaWiki software to cascade protect an entire namespace. Should this be fixed?
Techman224
Hi there,
I'm trying to find the Special:ActiveUsers page that used to show activity
statistics.
Where did it go? Has it been replaced by something better?
Thanks,
Micru
Is anyone able to look into this?
It's extremely slow and I can't find someone to fix it.
It's making me a very sad and unproductive panda :(
--
Jon Robson
http://jonrobson.me.uk
@rakugojon
https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013
Today is the last day to register for the Amsterdam hackathon (May
24-26) and request a scholarship.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Over the last week Željko and I changed the QA automated browser tests to
target test environments on the beta cluster as well as on test2wiki, where
they had been running for some time.
This was possible because of a number of improvements made to beta since
the QA Quarterly Review and the f2f meeting in SF in February:
* automatic updates to the beta database
* enabling Search on beta
* Varnish on beta to support MobileFrontend
* etc.
There is still more to do:
* get more extensions running and configured on beta
* change settings to more closely match prod and/or test2 as appropriate
* moar tests
Automated browser tests have a proven record of exposing real issues in the
test2wiki environment before code is put in production. Here are some of
the bugs we have identified by way of browser tests so far:
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu…
By running these tests in the beta cluster also, we gain both better test
coverage features in disparate environments and also a longer window to
identify issues, since beta is updated much more often than test2wiki.
As always, the current status of the browser test builds are available in
Jenkins at https://wmf.ci.cloudbees.com, and any changes to the status of
those builds are reported by wmf-jenkins-bot in #wikimedia-dev