On 06.12.2012 01:55, Chris Steipp wrote:
The same general idea should apply for Wikibase. The only difference is
that the core functionality of data editing is in Wikibase.
Correct, and I would say that Wikibase should be calling the same
hooks that core does, so that AbuseFilter can be
On 05.12.2012 22:06, Matthew Flaschen wrote:
More specifically, what if Wikidata exposed a JSON object representing
an external version of each change (essentially a data API).
This already exists, that's more or less how changes get pushed to client wikis.
It could allow hooks to register
Hi,
The report covering Wikimedia engineering activities in November 2012 is
now available.
Wiki version:
https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/November
Blog version:
https://blog.wikimedia.org/2012/12/06/engineering-november-2012-report/
Like last month, we're also
On Wed, Dec 5, 2012 at 10:45 PM, Jon Robson jdlrob...@gmail.com wrote:
This is long overdue and kudos to all involved.
I'm already noticing the more useful side effects such as the url
change, performance and the better formatted emails
On Wed, Dec 5, 2012 at 12:56 PM, Sumana Harihareswara
On Wed, Dec 5, 2012 at 2:57 PM, Brion Vibber br...@pobox.com wrote:
On Wed, Dec 5, 2012 at 11:53 AM, Chad innocentkil...@gmail.com wrote:
On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper aklap...@wikimedia.org
wrote:
bugzilla.wikimedia.org is operational again and is now running the
latest
On 06/12/12 18:06, Chad wrote:
On Wed, Dec 5, 2012 at 2:57 PM, Brion Vibberbr...@pobox.com wrote:
On Wed, Dec 5, 2012 at 11:53 AM, Chadinnocentkil...@gmail.com wrote:
On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapperaklap...@wikimedia.org
wrote:
Bah, plaintext 4 ever ;-)
Everything else is
Hi, thanks to the metrics reports now we know that the top bug fixers in
November were Nobody (228) and Wikidata bugs (83)... followed by Michael
Dale (28), Roan Kattouw (23), etc.
http://www.mediawiki.org/wiki/Community_metrics/November_2012#People
Even if the visible problem is a less
Reposting to wikitech-l, in case someone is interested:
http://www.cloudbees.com/webinars/getting-most-out-selenium-and-jenkins-cloudbees-sauce.cb
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Hello,
Earlier today I have slightly changed our review / test workflow on
mediawiki/core.git . That will let us do more tests and scale things in
the long term.
The new workflow is described on the wiki (including a flowchart):
https://www.mediawiki.org/wiki/Continuous_integration/Workflow
On Thu, Dec 6, 2012 at 7:07 PM, Quim Gil q...@wikimedia.org wrote:
Hi, thanks to the metrics reports now we know that the top bug fixers in
November were Nobody (228) and Wikidata bugs (83)... followed by Michael
Dale (28), Roan Kattouw (23), etc.
Hi,
is there already a schedule to update jQuery and jQuery UI to 1.9 or are
there problems at moment? I want to use the new tooltip widget of jQuery UI
1.9 [1].
Best regards,
Jan
[1] http://jqueryui.com/tooltip/
___
Wikitech-l mailing list
On 12/06/2012 05:22 AM, Daniel Kinzler wrote:
On 05.12.2012 22:06, Matthew Flaschen wrote:
More specifically, what if Wikidata exposed a JSON object representing
an external version of each change (essentially a data API).
This already exists, that's more or less how changes get pushed to
Antoine Musso hashar+...@free.fr wrote:
Earlier today I have slightly changed our review / test workflow on
mediawiki/core.git . That will let us do more tests and scale things in
the long term.
The new workflow is described on the wiki (including a flowchart):
On Thu, Dec 6, 2012 at 10:52 PM, Tim Landscheidt t...@tim-landscheidt.de
wrote:
That is all. The slow unit tests are no more run on patchset submission.
We really need them.
The tests philosophy is there is an issue with this change.
The Jenkins philosophy is automate as most as possible to
On 5 December 2012 05:19, Tim Starling tstarl...@wikimedia.org wrote:
The jobs were probably not parsing Pagina Principale, they were
probably parsing some page with an infinite loop of #lst invocations.
Sorry, I didn't get a backtrace.
On 6 December 2012 00:51, Platonides
Le 06/12/12 22:52, Tim Landscheidt wrote:
Why not just add (more) slaves? Computing power is much
cheaper than developer time.
Erik, everyone and I are eager to add more computing power. We are going
to use Vagrant virtual machines setup as Jenkins slaves. It takes a bit
more engineering to
Le 06/12/12 16:45, Guillaume Paumier a écrit :
Hi,
The report covering Wikimedia engineering activities in November 2012 is
now available.
Wiki version:
https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/November
Blog version:
On 06/12/2012 15:01, Sébastien Santoro wrote:
On Thu, Dec 6, 2012 at 10:52 PM, Tim Landscheidt t...@tim-landscheidt.de
wrote:
That is all. The slow unit tests are no more run on patchset submission.
We really need them.
The tests philosophy is there is an issue with this change.
The
On Thu, Dec 6, 2012 at 7:19 PM, Antoine Musso hashar+...@free.fr wrote:
(...)
If everything is fine, jenkins-bot will vote Code-Review +1 to let
everyone know that the change look fine. Else, it will vote Verified -1
preventing the patchset from being submitted.
Could you, pending the end of
19 matches
Mail list logo
