[Wikitech-l] Bugzilla cleanup

2010-05-13 Thread Chad
Good morning,

I'm planning some downtime for Bugzilla this weekend on Saturday
(I'll update later once I decide an actual time). There's quite a bit of
cleanup that needs to be done and I'm going to shut down BZ for
the duration so I don't send out a few thousand e-mails and spam
everyone's inboxes. Here's the primary list of things I plan to do:

- Remove deprecated keywords (fixed-in-cvs, etc)
- Remove keywords that aren't applicable (needs-review on closed bugs)
- Kill deprecated products (Issues, Logwood too? I think those can be
  moved to Wikimedia - Usage/Statistics)
- Consolidate version numbers (1.3.1, 1.3.2, etc to 1.3.x, for all non-recent
  versions)

If anyone else can think of other things to do while we're at it please
feel free to take a look at [[mw:Bugzilla cleanup]].

Thanks,

Chad

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread David Gerard
There's a few comments on the Wikimedia blog saying they can't access
en:wp any more using their BlackBerry. Though we tried it here on an
8900 and it works. Any other reports?


- d.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread Gregory Maxwell
On Thu, May 13, 2010 at 3:16 PM, David Gerard dger...@gmail.com wrote:
 There's a few comments on the Wikimedia blog saying they can't access
 en:wp any more using their BlackBerry. Though we tried it here on an
 8900 and it works. Any other reports?

Punching in http://en.wikipedia.org/  as I normally would...

It starts to render, but with an enormous grey area at the top like a
gigantic banner ad.  Then the browser crashes, I assume I've never
seen it do that before... it throws up a there was a problem
rendering this page, blanks the screen, and goes unresponsive.

Blackberry 8310, software v4.5.0.110 (Platform 2.7.0.90)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread Russell Blau
David Gerard dger...@gmail.com wrote in message 
news:aanlktin9qhcgvataegsdrwjuc-jegj-iwdg6f9oyt...@mail.gmail.com...
 There's a few comments on the Wikimedia blog saying they can't access
 en:wp any more using their BlackBerry. Though we tried it here on an
 8900 and it works. Any other reports?

Works fine using Opera Mini.

Trying to load any page on the native Blackberry Browser, with JavaScript 
disabled, results in a browser crash with message Uncaught exception: 
java.lang.ClassCastException  (after the page has fully loaded).  Trying 
with JavaScript enabled (while not logged in) results in HTTP Error 413: 
Request Entity Too Large, even on a page known to be very small.

This is for a Blackberry 8800 v.4.5.0.110.




___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread Ilmari Karonen
On 05/13/2010 10:55 PM, Russell Blau wrote:
 David Gerarddger...@gmail.com  wrote in message
 news:aanlktin9qhcgvataegsdrwjuc-jegj-iwdg6f9oyt...@mail.gmail.com...
 There's a few comments on the Wikimedia blog saying they can't access
 en:wp any more using their BlackBerry. Though we tried it here on an
 8900 and it works. Any other reports?

 Works fine using Opera Mini.

 Trying to load any page on the native Blackberry Browser, with JavaScript
 disabled, results in a browser crash with message Uncaught exception:
 java.lang.ClassCastException  (after the page has fully loaded).  Trying
 with JavaScript enabled (while not logged in) results in HTTP Error 413:
 Request Entity Too Large, even on a page known to be very small.

Error 413 generally means, in plain English, URL too long.  I'd 
suspect some script is trying to do an API query using a very long URL, 
and the fact that this only happens when JS is enabled lends support to 
this.

Assuming that the Blackberry browser doesn't have particularly good JS 
debugging support, it might be worth looking at the same page in e.g. FF 
+ Firebug, with JS and net debugging enabled, and looking for any 
requests with suspiciously long URLs.

I've no idea what might be causing the other problems, though.

-- 
Ilmari Karonen

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread Roan Kattouw
2010/5/13 Ilmari Karonen nos...@vyznev.net:
 Error 413 generally means, in plain English, URL too long.  I'd
 suspect some script is trying to do an API query using a very long URL,
 and the fact that this only happens when JS is enabled lends support to
 this.

 Assuming that the Blackberry browser doesn't have particularly good JS
 debugging support, it might be worth looking at the same page in e.g. FF
 + Firebug, with JS and net debugging enabled, and looking for any
 requests with suspiciously long URLs.

 I've no idea what might be causing the other problems, though.

413s are thrown by the *server*, not the client. An overlong URL would
cause 413s independent of whether it's Firefox or a Blackberry
requesting them.

Roan Kattouw (Catrope)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Vector skin not working on BlackBerry?

2010-05-13 Thread Robert Rohde
On Thu, May 13, 2010 at 1:39 PM, Roan Kattouw roan.katt...@gmail.com wrote:
 2010/5/13 Ilmari Karonen nos...@vyznev.net:
 Error 413 generally means, in plain English, URL too long.  I'd
 suspect some script is trying to do an API query using a very long URL,
 and the fact that this only happens when JS is enabled lends support to
 this.

 Assuming that the Blackberry browser doesn't have particularly good JS
 debugging support, it might be worth looking at the same page in e.g. FF
 + Firebug, with JS and net debugging enabled, and looking for any
 requests with suspiciously long URLs.

 I've no idea what might be causing the other problems, though.

 413s are thrown by the *server*, not the client. An overlong URL would
 cause 413s independent of whether it's Firefox or a Blackberry
 requesting them.

You'd think so, but it really is the client.

If you Google Blackberry 413 there is a long history of this error
happening on the Blackberry web client.  It appears that a 413 error
is the way that the Blackberry rendering engine responds to hitting
resource limits (e.g. memory or storage space).  The newer models tend
to avoid it by devoting more resources to browsing.

I would guess that the Javascript associated with Vector is using more
memory than the Monobook version did and this is causing an error for
people that used to have no trouble browsing Wikipedia before.

-Robert Rohde

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[Wikitech-l] js2 extensions / Update ( add-media-wizard, uploadWizard, timed media player )

2010-05-13 Thread Michael Dale
If you have been following the svn commits you may have noticed a bit of 
activity on the js2 front.

I wanted to send a quick heads up that describes what is going on and 
invite people to try things out, and give feedback.

== Demos ==

The js2 extension and associated extension are ruining on sandbox-9. If 
you view the source of a main page you can see all the scripts and css 
and grouped into associated buckets:

http://prototype.wikimedia.org/sandbox.9/Main_Page

I did a (quick) port of usabilityInitiative to use the script-loader as 
well.  Notice if you click edit on a section you get all the css and 
javascript, localized in your language and delivered in a single 
request. ( I don't include the save / publish button since it was just a 
quick port )

Part of the js2 work included a wiki-text parser for javascript client 
side message transformation:
http://prototype.wikimedia.org/s-9/extensions/JS2Support/tests/testLang.html

There are a few cases out of the 356 tests were I think character 
encoding is not letting identical messages pass the test and a few 
transformations that don't match up. I will take a look at those  edge 
cases soon.

The Multimedia initiative ( Neil and Guillaume's ) UploadWizard is a js2 
/ mwEmbed based extension and also enabled on in that wiki as well: 
http://prototype.wikimedia.org/sandbox.9/Special:UploadWizard


The js2 branch of the OggHandler includes Transcode support ( so embed 
web resolution oggs when embed at web resolution in pages ) This avoids 
720P ogg videos displayed at 240 pixels wide inline ;)
http://prototype.wikimedia.org/sandbox.9/Transcode_Test

The TimedMediaHandler of course include timed text display support which 
has been seen on commons for a while http://bit.ly/aLo1pZ ...
Subtitles get looked up from commons when the repo is shared::
http://prototype.wikimedia.org/sandbox.9/File:Welcome_to_globallives_2.0.ogv

I have been working with the miro universal subtitles efforts so we 
should have an easy interface for people to contribute subtitles with soon

Edits pages of course include the add-media-wizard which as been seen as 
a remote http://bit.ly/9P144i for some time also now also works as an 
extension

== Documentation ==

Some initial JS2 extension is in extensions/JS2Support/README
Feedback on that documentation would also be helpful.

--michael

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l