On 11/13/2013 01:22 PM, Quim Gil wrote:
Wikimedia's Engineering Community team is responsible for developing
clear documentation for MediaWiki. All of our documentation is written
collaboratively in wiki pages, involving all kinds of profiles, from WMF
professional developers to anonymous users.
On 10/31/2013 01:14 AM, Matthew Flaschen wrote:
// Load jquery.ui.button so button styles work in wikitext
mw.loader.using( 'jquery.ui.button' );
Commons is now doing this conditionally, only if the CSS class is
present on the page (or specifically the HTML from wikipage.content).
See
Thanks Brad,
I'm wondering if it wouldn't make sense to have a dedicated bugday at
the end of the sprint?
Strainu
2013/11/13 Brad Jorsch (Anomie) bjor...@wikimedia.org:
Note these are my own thoughts and not anything representative of the team.
On Wed, Nov 13, 2013 at 6:55 AM, Strainu
Let's see what sorts of bugs crop up? In my (limited) experience, the most
common issues are probably article content which renders poorly as a PDF
for some reason. Those bugs aren't easy to fix in a bug day sprint, since
they tend to crop up slowly over time as people use the service and
On Mon, Nov 11, 2013 at 1:51 AM, Tim Starling tstarl...@wikimedia.orgwrote:
On 08/11/13 03:40, C. Scott Ananian wrote:
Basically, every major piece of WP should have a module owner.
[...]
Certain people 'own' larger collections of modules -- like there are
subsystem owners in the linux
And I'll add that there's another axis: gwicke (and others?) have been
arguing for a broader collection of services architecture for mw. This
would decouple some of the installability issues. Even if PDF rendering
(say) was a huge monster, Jimmy MediaWiki might still be able to simply
install
On Mon, Nov 11, 2013 at 1:51 AM, Tim Starling tstarl...@wikimedia.orgwrote:
My concern with this kind of maintainer model is that RFC review would
tend to be narrower -- a consensus of members of a single WMF team
rather than a consensus of all relevant experts.
I'd also like to point out
On 11/13/2013 08:27 AM, Željko Filipin wrote:
On Fri, Oct 25, 2013 at 8:07 PM, Quim Gil q...@wikimedia.org wrote:
See Top closers and Top openers of all-time, last year and last month
at http://korma.wmflabs.org/browser/top.html
PS: yes, this information should appear at
On 11/13/2013 08:49 AM, Mark A. Hershberger wrote:
On 11/13/2013 05:44 AM, Nathan Larson wrote:
TL;DR: How can we collaboratively put together a list of non-spammy sites
that wikis may want to add to their interwiki tables for whitelisting
purposes; and how can we arrange for the list to be
On 11/13/2013 04:21 PM, Tyler Romeo wrote:
MediaWiki participates in a number of student competitions and programs as
an open source mentor (such as GSoC, Code-In, etc.). Today I ran into
another one: Facebook's Open Academy Program.
https://www.facebook.com/OpenAcademyProgram
I'm not
On Thu, Nov 14, 2013 at 12:18 PM, Quim Gil q...@wikimedia.org wrote:
With my hat of third party wiki admin I personally agree with all this.
Another possibility further down in the roadmap:
Imagine a World in which you could transclude in your wiki content from
a subset of this interwiki
On Wed, Nov 13, 2013 at 07:21:01PM -0500, Tyler Romeo wrote:
MediaWiki participates in a number of student competitions and programs as
an open source mentor (such as GSoC, Code-In, etc.). Today I ran into
another one: Facebook's Open Academy Program.
On 11/14/2013 09:53 AM, Nathan Larson wrote:
Is there reason to think that a decentralized system would be likely to
evolve, or that it would be optimal? It seems to me that most stuff in the
wikisphere is centered around WMF; e.g. people usually borrow templates,
the spam blacklist, MediaWiki
Just got this when trying to read an article. Not sure if anyone is doing
anything, but if you are, you might have broken something.
If you report this error to the Wikimedia System Administrators, please include
the details below.
Request: GET
Just got this when trying to read an article. Not sure if anyone is doing
anything, but if you are, you might have broken something.
If you report this error to the Wikimedia System Administrators, please include
the details below.
Request: GET
On Thu, Nov 14, 2013 at 2:05 PM, Derric Atzrott
datzr...@alizeepathology.com wrote:
The issue seems to be confined to Wikipedia. I am not seeing it affect
Mediawiki.org
Additionally the issue seems to be affecting more than just the English
language Wikipedia. The lojban language
I get an error, and beneath it there is a message that says Your cache
administrator is: nobody Looks like there is a bug on it that's 4 or 5
years old ;)
On Thu, Nov 14, 2013 at 2:10 PM, Nathan Larson
nathanlarson3...@gmail.comwrote:
On Thu, Nov 14, 2013 at 2:05 PM, Derric Atzrott
On Thu, 2013-11-14 at 13:50 -0500, Derric Atzrott wrote:
If you report this error to the Wikimedia System Administrators, please
include
the details below.
Request: GET http://en.wikipedia.org/wiki/Johnny_the_Homicidal_Maniac, from
10.64.32.106 via cp1067 cp1067 ([10.64.0.104]:3128),
On Thu, Nov 14, 2013 at 7:18 PM, Andre Klapper aklap...@wikimedia.org wrote:
Thanks! The Operations team is currently working on it and there likely
will be an analysis available at
https://wikitech.wikimedia.org/wiki/Incident_documentation afterwards.
See also #wikimedia-tech,
On Thu, Nov 14, 2013 at 8:13 AM, C. Scott Ananian canan...@wikimedia.orgwrote:
And I'll add that there's another axis: gwicke (and others?) have been
arguing for a broader collection of services architecture for mw. This
would decouple some of the installability issues. Even if PDF rendering
We were dealing with cascading site issues due to excessive database
queries, and are still investigating the root cause, but site should
be recovered by now.
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
On 11/06/2013 03:18 PM, Quim Gil wrote:
The next RFC review meeting is planned for November 20.
Wednesday, November 20, 2013 at 10:00 PM UTC at #wikimedia-meetbot
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-11-20
There are no RFCs scheduled yet. Seeing how the previous
I would like to announce the release of MediaWiki 1.21.3, 1.20.8 and
1.19.9. These releases fix 2 security related bugs that could affect users
of MediaWiki. Download links are given at the end of this email.
* Kevin Israel (Wikipedia user PleaseStand) identified and reported two
vectors for
In the MW extension development I'm doing, I'm thinking of writing some
operations that use [[Comet_(programming)]] to deliver continuous
updates to the client, rather than the Ajax pattern of one request, one
response.
Has anyone messed with this? Any code I should crib from, or advice or
Wouldn't WebSocket be the better choice for a full duplex channel?
On 14/11/13 21:12, Lee Worden wrote:
In the MW extension development I'm doing, I'm thinking of writing
some operations that use [[Comet_(programming)]] to deliver continuous
updates to the client, rather than the Ajax pattern
On Thu, Nov 14, 2013 at 6:12 PM, Lee Worden worden@gmail.com wrote:
Has anyone messed with this? Any code I should crib from, or advice or
cautionary tales? Also, if it develops into something useful, I could
split it out for others to use.
I have not messed with it personally, but I
On 2013-11-14 5:22 PM, Tyler Romeo wrote:
On Thu, Nov 14, 2013 at 6:12 PM, Lee Worden worden@gmail.com wrote:
Has anyone messed with this? Any code I should crib from, or advice or
cautionary tales? Also, if it develops into something useful, I could
split it out for others to use.
I
On Thu, Nov 14, 2013 at 10:12 PM, Daniel Friesen dan...@nadir-seen-fire.com
wrote:
Basically in the end your best bet is probably to just use something
other than PHP for this.
The native implementations for both Socket.IO's and SockJS' servers are
in Node.JS.
So that's probably the best
Hi Everyone,
As an applicant of FOSS-OPW Round 7, I took a deep and profound interest
in one of the featured projects Complete the MediaWiki development course
at Codeacademy. I chosen I am planning to focus and contribute to this
project.
***Project Synopsis***
The project is about
29 matches
Mail list logo
