- Original Message -
From: "Rob Lanphier"
Newsgroups: gmane.science.linguistics.wikipedia.technical
To: "Wikimedia developers"
Sent: Tuesday, February 01, 2011 8:15 AM
Subject: Planned 1.17 deployment on February 8
If all goes well, you should only notice the improvement. If it doesn
- Original Message -
From: "Jan Paul Posma"
Newsgroups: gmane.science.linguistics.wikipedia.technical
To: "Janesh Kodikara" ; "Wikimedia developers"
Sent: Friday, January 28, 2011 3:00 AM
Subject: Re: Sentence-level editing / InlineEditorextensionupdate
>
>> Few bugs and a enchantemen
Fred Bauder wrote:
> This idea arose in the context of a discussion which generally addressed
> civility. The warnings would be civility warnings.
>
>> To that end, a warnings tool would be helpful,
>> supplementing or replacing the uw- templates with a MediaWiki
>> extension that requires that wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to announce the release of MediaWiki 1.16.2, which is a
security release. Two security issues were discovered.
An arbitrary script inclusion vulnerability was discovered. The
vulnerability only allows execution of files with names ending
I was planning on emailing him a patch, probably after I wrote some tests to
ensure I wasn't submitting him something with issues.
- Trevor
On Feb 1, 2011, at 1:41 PM, Platonides wrote:
> Trevor Parscal wrote:
>> There are 2 components to the JavaScriptDistiller library. One of them (the
>> Pa
Trevor Parscal wrote:
> There are 2 components to the JavaScriptDistiller library. One of them (the
> ParseMaster class) is 100% in sync with the official distribution. The other
> (the JavaScriptDistiller class) was originally based on the
> JavaScriptPacker::_basicCompression function. That fu
This idea arose in the context of a discussion which generally addressed
civility. The warnings would be civility warnings.
Fred
> To that end, a warnings tool would be helpful,
> supplementing or replacing the uw- templates with a MediaWiki
> extension that requires that warnings be acknowledged
Use jQuery.ajax (or it's wrapper functions such as jQuery.getJSON) to
cover all cross-browser issues.
And as indirectly suggested above. JSONP is the solution for cross-
domain scripting.
What it means is that that source (in this case toolserver) has a URL
parameter (say &callback=), the scr
On 01/02/11 19:42, Trevor Parscal wrote:
> In the former case, any changes should be strictly passed upstream.
> In the latter case, I think we should offer them upstream but realize
> that we have deviated from the original author's structure and
> possibly intentions enough that they may or may n
There are 2 components to the JavaScriptDistiller library. One of them (the
ParseMaster class) is 100% in sync with the official distribution. The other
(the JavaScriptDistiller class) was originally based on the
JavaScriptPacker::_basicCompression function. That function had some issues
that w
On 31/01/11 13:51, Roan Kattouw wrote:
>> > I can work around it in the extension, but we should watch out and make
>> > sure
>> > we've got regression tests covering any cases we find.
>> >
> Yes, we need minifier tests.
Isn't this an upstream issue? If so we could send them our patches.
--
On Tue, Feb 1, 2011 at 10:06 AM, Daniel Kinzler wrote:
> Hi all!
>
> what's the best way to get around the same original policy to fetch data
> from
> the toolserver with a XMLHTTPRequest in a Wikipedia gadget? Is there a best
> practice, a nice and easy, generally usable method? what would it tak
Hi all!
what's the best way to get around the same original policy to fetch data from
the toolserver with a XMLHTTPRequest in a Wikipedia gadget? Is there a best
practice, a nice and easy, generally usable method? what would it take to make
one?
I know that some gadgets have been doing this, but
On Tue, Feb 1, 2011 at 1:18 AM, Rob Lanphier wrote:
> We lost the game of rock/paper/scissors. :) We decided to do this very
> late U.S. west coast time so that our European and Australian contingents
> would be well rested in case there are problems. Given that we have key
> personnel pretty m
Rob Lanphier wrote:
> MZMcBride wrote:
>
>> Rob Lanphier wrote:
>>> If all goes well, you should only notice the improvement. If it
>>> doesn¹t go
>>> well, that¹s because there¹s something we missed, and that¹s where
>>> we¹d love
>>> your help. Please help us test this release! We have a te
2011/2/1 Rob Lanphier :
>> Can you explain why you're rolling out when it's the middle of the night
>> where Wikimedia is headquartered? I have a few different theories (site
>> traffic, time zones of the operations team, etc.), but a clarification here
>> would be good.
>
>
> We lost the game of r
16 matches
Mail list logo
