Forwarding. Please take this opportunity to ask questions!
Pine
-- Forwarded message --
From: Siko Bouterse sboute...@wikimedia.org
Date: Sep 18, 2014 3:30 PM
Subject: [Wikimedia-l] Upcoming help sessions for drafting Individual
Engagement Grant proposals
To:
Dear all,
We're building a Firefox addon to perceptually match images in Commons
against images found elsewhere, so that people can see that they come
from Commons even if they appear on other web sites.
https://moqups.com/jonaso/lopej41Z has a quick mockup.
On
I should point out that any sysops, importers, stewards etc. who use
Special:Import should not enable the HHVM beta feature, as importing does not
currently work on HHVM [1].
Only once that issue is fixed, and the API is running via HHVM, will I be able
to get excited...
TTO
[1]
Hi,
great news indeed!
Wiadomość napisana przez Ori Livneh o...@wikimedia.org w dniu 19 wrz 2014, o
godz. 03:39:
You can enable HHVM by opting in to the beta feature. This short animated
gif will show you how: http://people.wikimedia.org/~ori/hhvm_beta.gif.
The link to discussion on the
Hi,
On Fri, Sep 19, 2014 at 9:47 AM, Jonas Öberg
jo...@shuttleworthfoundation.org wrote:
According to EugeneZelenko who tried to grant this right, it could not
be granted through the normal interface. Question then: is
apihighlimits included in the bot flag, or how can the apihighlimits
Yes, the 'apihighlimits' *permission* is included in the 'bot' *group*
(and the 'sysop' group, too). You can see available groups and the
permissions they are assigned on
https://commons.wikimedia.org/wiki/Special:ListGroupRights
--
Bartosz Dziewoński
Thanks Bartosz and Petr, much appreciated, this clears up the question nicely :)
Sincerely,
Jonas
On 19 September 2014 10:24, Bartosz Dziewoński matma@gmail.com wrote:
Yes, the 'apihighlimits' *permission* is included in the 'bot' *group* (and
the 'sysop' group, too). You can see available
Finally I managed to do it.
Thanks for the good advices!
El 09/05/2014 a les 06:43 PM, Krinkle ha escrit:
It couldn't be more simple I'm afraid. Replace get with post.
Note that both of these are just shortcuts to the more advanced $.ajax
method, so if the reduced set of options exposed in
Important Phabricator news:
A single migration timeline with all the important details is available.
https://www.mediawiki.org/wiki/Phabricator#Migration_timeline
A video-streamed session The Very Basics of Phabricator is scheduled for
Wednesday, September 24.
On Sep 18, 2014 10:19 PM, Daniel Zahn dz...@wikimedia.org wrote:
puppet will make it exec {git_update... .. command = '/usr/bin/git
remote update',
from our gerrit repo. i'm not 100% sure about the sync between
upstream and our gerrit repo, but Chase would know
git remote update doesn't
Now with blog post and some known faces. :)
https://blog.wikimedia.org/2014/09/18/new-foss-outreach-internships-female-technical-contributors/
Thank you to those who forwarded this email, and of course thank you to the
mentors and candidates that are becoming increasingly active.
On
I got past this error by adding a NULL at the end of the values in :
-- Create a dummy page to satisfy fk contraints especially with revisions
INSERT INTO mw_prefix.page
VALUES (0, 0, ' ', NULL, 0, 0, 0, 0, current_timestamp, NULL, 0, 0, NULL);
On Thu, Sep 18, 2014 at 6:11 PM, Bill Traynor
Please join us for the following tech talk:
Tech Talk: The Very Basics of Phabricator
Date: September 24
Time: 1800 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Phab+Tech+Talkiso=20140924T18p1=1440ah=1
Link to live YouTube stream http://www.youtube.com/watch?v=-fpkHyCGX1Y
IRC
Le 16/09/2014 17:29, Antoine Musso a écrit :
Something I have yet to figure out is to have the patch voted +2 to be
tested sequentially to ensure the queue of proposed changes works well
together. Should be dealt with this evening or at worse tomorrow.
I have did it by inserting a fake job
does gerrit have a notice banner you could post a short message on and then a
link to more detailed documentation?
On Sep 19, 2014, at 21:20 , Antoine Musso hashar+...@free.fr wrote:
Le 16/09/2014 17:29, Antoine Musso a écrit :
Something I have yet to figure out is to have the patch voted +2
quote name=Antoine Musso date=2014-09-16 time=17:29:48 +0200
* mediawiki/core is now using the branch of the proposed patchset. So if
you propose a patch for your extension against REL1_23, it will be
tested with core@REL1_23. Previously we always used master.
Thanks a ton, Antoine, this is
Hi,
I just merged https://gerrit.wikimedia.org/r/#/c/161584/ and branched
core to the commit before it. If someone could take care of branching
extensions that would be wonderful, otherwise I'll figure out how to do
that over the weekend.
Bugs tagged for 1.24 release:
Installed MediaWiki (git master) with Oracle 11 as the database. Post
installation, the MainPage does not display but shows instead:
Warning: oci_parse() expects parameter 1 to be resource, boolean given
in ...MediaWiki/includes/db/DatabaseOracle.php on line 1266 Warning:
oci_error() expects
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_September_22nd
A quick list of notable items...
== Tuesday ==
* MediaWiki deploy
Update: this is done. Mobile is now using OOJS for its classes and
event emitting.
I would appreciate if people could vigorously test things on beta labs.
We have already identified two issues [1,2] that seem to have been
caused by moving to OO.EventEmitter (I believe the issue is something
to do
20 matches
Mail list logo
