I have an extension that affects wiki tables using JavaScript. In order for it
to work, I need it to load *before* one of the core JS modules,
jquery.tablesorter.
Is there a supported way to modify the ResourceLoader dependencies of
jquery.tablesorter?
Effectively I want to do something like:
Petr,
I'm interested in your approach here as I read your explanation page. I
personally use python and javascript, and don't find RCStream to
complicated. But I have half-built an application that in python reads the
RCStream, pumps it into a redis queue, gets the text of the diff for each
On 01/14/2015 04:57 PM, James Douglas wrote:
I'd love to hear your thoughts and learn about your related experiences.
What are your favorite code coverage tools and services?
PHPUnit has a useful code coverage tool and there are reports running
for core[1] and some extensions[2]. In my
Marc,
another message to this list this morning, is about a rebroadcast of the
RCstream with a json-xml format transform, so it seems like there is a
desire to transform and make available the RCstream.
Thanks for all your advice.
Make a great day,
Max Klein ‽ http://notconfusing.com/
On Mon,
Thanks for the suggestion to use position=top. I'll try that.
DanB
My email address has changed to d...@cimpress.com. Please update your address
book.
Cimpress is the new name for Vistaprint NV, the world’s leader in mass
customization. Read more about
It's not supported, but I see no reason why it couldn't work. You'd
probably want to do it from the ResourceLoaderRegisterModules hook (which
is fired after core modules are registered). Also, $moduleInfos is
protected (because you're not supposed to modify it :D), so you'd have to
cheat
I'd love to use coveralls for the iOS app! I've thought it (and Travis)
looked promising before, put seem especially relevant for mediawiki
projects which are all OSS.
One other JS testing lib you guys should check out is JSVerify
http://jsverify.github.io/, which is a port of Haskell's
And if you don't like XML either and can think of a different format,
let me know, I would like to add support for multiple formats, so that
programs that would need to access RC feed would need minimum of extra
dependencies.
On Thu, Jan 15, 2015 at 5:00 PM, Petr Bena benap...@gmail.com wrote:
[Crossposted to Wikitech-l]
Hello, all!
As a reminder, the planned partial downtime of the Labs network
filesystem for maintenance is today (January 15) at 18:00 UTC and is
scheduled to last up to 24 hours - but I have high hopes that it will be
much shorter than that.
In addition to the
+1 for property-based testing. JSVerify's Haskell-like syntax makes it
super easy to conjure up arbitrary generators.
On Thu, Jan 15, 2015 at 7:44 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
I'd love to use coveralls for the iOS app! I've thought it (and Travis)
looked promising before,
Hi folks,
Most of you probably heard about new stream of RC changes as
alternative to IRC: https://wikitech.wikimedia.org/wiki/RCStream
I simply found it complex beyond the edge of usability for most of
solutions that use low level languages or frameworks that don't
support modern technologies
- Original Message -
From: Rob Lanphier ro...@wikimedia.org
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so, who makes that decision? If not, what is our alternative
vision? Who is
On Thu Jan 15 2015 at 8:17:25 PM Jay Ashworth j...@baylink.com wrote:
- Original Message -
From: Rob Lanphier ro...@wikimedia.org
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so,
On Thu Jan 15 2015 at 8:05:18 PM Rob Lanphier ro...@wikimedia.org wrote:
So, where does that leave us? Do we need a BFDL? If so, who should
pick? Should it be someone in the project? Should the WMF hire
someone to lead this? If not, do we keep the committee? Do we just
let this be
On Thu, Jan 15, 2015 at 9:26 PM, Chad innocentkil...@gmail.com wrote:
On Thu Jan 15 2015 at 8:17:25 PM Jay Ashworth j...@baylink.com wrote:
- Original Message -
From: Rob Lanphier ro...@wikimedia.org
On the leadership front, let me throw out a hypothetical: should we
have
On Thu, Jan 15, 2015 at 9:32 PM, Chad innocentkil...@gmail.com wrote:
On Thu Jan 15 2015 at 8:05:18 PM Rob Lanphier ro...@wikimedia.org wrote:
So, where does that leave us? Do we need a BFDL? If so, who should
pick? Should it be someone in the project? Should the WMF hire
someone to lead
On Thu, Jan 15, 2015 at 8:04 PM, Rob Lanphier ro...@wikimedia.org wrote:
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so, who makes that decision? If not, what is our alternative
vision?
Rob Lanphier wrote:
So, here we are today. I believe no one would dispute the credentials
of every member of the group. Brion, Tim, and Mark have an extremely
long history with the project, being employees #1, #2, and #3 of the
WMF respectively, and all having contributed massively to the
There has been a lot of talk over the last year or so of how and when
to move MediaWiki to a service oriented architecture [0]. So much so
that it is actually one of the a marquee topics at the upcoming
Developer Summit.
I think the problem statement for the services RFC is dead on in
describing
On Thu, Jan 15, 2015 at 10:38 PM, Bryan Davis bd...@wikimedia.org wrote:
One of the bigger questions I have about the potential shift to
requiring services is the fate of shared hosting deployments of
MediaWiki. What will happen to the numerous MediaWiki installs on
shared hosting providers
On Jan 15, 2015 8:33 PM, Chad innocentkil...@gmail.com wrote:
On Thu Jan 15 2015 at 8:05:18 PM Rob Lanphier ro...@wikimedia.org wrote:
So, where does that leave us? Do we need a BFDL? If so, who should
pick? Should it be someone in the project? Should the WMF hire
someone to lead this?
On 16/01/15 15:04, Rob Lanphier wrote:
Still, the uncomfortable shrugging continues. The group is broader,
but still lacks the breadth, particularly in front end and in the
development of newer services such as Parsoid and RESTBase.
It appears that we won't be able to keep the members we
On Thu, Jan 15, 2015 at 10:57 PM, Tim Starling tstarl...@wikimedia.org wrote:
Sorry to labour the point, but the way to go about this at present is pretty
straightforward,
and it doesn't involve the architecture committee. You just convince the
management (Damon,
Erik, etc.) that it is a
On Thu, Jan 15, 2015 at 9:31 PM, Ori Livneh o...@wikimedia.org wrote:
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so, who makes that decision? If not, what is our alternative
vision? Who
95% is pretty extreme.
I have always questioned the balance being struck here, and would welcome
an adjustment of the minimum requirements to run MediaWiki. In many cases,
if we can just require shell access we can automate away the complexity for
the typical use cases.
- Trevor
On Thu, Jan 15,
On Thu, Jan 15, 2015 at 10:57 PM, Tim Starling tstarl...@wikimedia.org
wrote:
Committee members are skeptical of many of the current ideas floating
around at the moment, and have their own ideas about what things should be
priorities, but have no expectation that those ideas will be considered
On Jan 16, 2015 2:49 AM, Max Semenik maxsem.w...@gmail.com wrote:
On Thu, Jan 15, 2015 at 10:38 PM, Bryan Davis bd...@wikimedia.org wrote:
One of the bigger questions I have about the potential shift to
requiring services is the fate of shared hosting deployments of
MediaWiki. What will
On Thu Jan 15 2015 at 11:34:58 PM Brian Wolff bawo...@gmail.com wrote:
On Jan 16, 2015 2:49 AM, Max Semenik maxsem.w...@gmail.com wrote:
On Thu, Jan 15, 2015 at 10:38 PM, Bryan Davis bd...@wikimedia.org
wrote:
One of the bigger questions I have about the potential shift to
On Thu, Jan 15, 2015 at 10:57 PM, Tim Starling tstarl...@wikimedia.org
wrote:
On 16/01/15 15:04, Rob Lanphier wrote:
I believe no one would dispute the credentials
of every member of the group. Brion, Tim, and Mark have an extremely
long history with the project, being employees #1, #2,
On Thu, Jan 15, 2015 at 11:27 PM, Trevor Parscal tpars...@wikimedia.org
wrote:
95% is pretty extreme.
Can't agree on this, as the number covers:
- All curent shared host users
- Those who use an entry-level VPS and would suddenly discover that with
a few extra node services their RAM
Hi!
One of the bigger questions I have about the potential shift to
requiring services is the fate of shared hosting deployments of
MediaWiki. What will happen to the numerous MediaWiki installs on
shared hosting providers like 1and1, Dreamhost or GoDaddy when running
MediaWiki requires
Hi!
I am very new here so I would probably be saying a lot of generic things
which may or may not apply to the MW situation, if it is the latter
please feel free to either ignore, or, much better, educate me on where
I am wrong or what I am missing, but I hope it may be relevant.
So, where does
On 2015-01-15 11:41 PM, Rob Lanphier wrote:
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so, who makes that decision? If not, what is our alternative
vision? Who is going to define it? Is
Hi,
I was working to develop a theme [1] for Mediawiki. I was following the
Manual:Skinning page on Mediawiki site. I wanted to make some changes in
the footer area but could not find in the list. I am going to add a list in
the following section. Can anyone please tell me how can i show this
Hi everyone,
The current MediaWiki Architecture Committee[1] has its roots in a 2013
Amsterdam Hackthon session[2], where we
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Apologies for cross-posting
Call for Research Innovation Papers
Call for Research Innovation Papers
SEMANTiCS 2015
Transfer // Engineering // Community
11th International Conference on Semantic Systems
Vienna, Austria September 15-17, 2015
http://www.semantics.cc
Le 12/01/2015 17:31, Antoine Musso a écrit :
Hello,
I have crafted and enabled two new jobs:
* mediawiki-phpunit-hhvm
* mediawiki-phpunit-zend
Which are triggered whenever a patch is proposed to the repos:
mediawiki/core
mediawiki/vendor
Or the mobile related extensions:
(Alright...let's try this again!)
Hi everyone,
The current MediaWiki Architecture Committee[1] has its roots in a
2013 Amsterdam Hackathon session[2], where we had a pair of sessions
to try to establish our architectural guidelines[3]. It was there
that we agreed that it would be good to revive
On Thu, Jan 15, 2015 at 5:40 PM, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone,
The current MediaWiki Architecture Committee[1] has its roots in a 2013
Amsterdam Hackthon session[2], where we
Hehhow's that for a teaser. Well, now I'm committed to finishing this
email :-)
Stay
39 matches
Mail list logo
