Re: [Wikitech-l] Some Ideas About Technical Stuff/Community Relations Improvements
2008/12/12 Eugene Zelenko eugene.zele...@gmail.com: I don't think that blog is right place for such announcement. Especially Planet where technical issues will be mixed with non-technical ones. I think something more predictable and permanent like WMF wiki will do job better. The Wikimedia blog would be a good place for regular announcements, perhaps with links to leuksman.com, Jay willing. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Some Ideas About Technical Stuff/Community Relations Improvements
On Fri, Dec 12, 2008 at 5:23 AM, David Gerard dger...@gmail.com wrote: 2008/12/12 Eugene Zelenko eugene.zele...@gmail.com: I don't think that blog is right place for such announcement. Especially Planet where technical issues will be mixed with non-technical ones. I think something more predictable and permanent like WMF wiki will do job better. The Wikimedia blog would be a good place for regular announcements, perhaps with links to leuksman.com, Jay willing. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l For more on the story, the server admin log is also worth reading for what's going on in tech (less dev, more servers, however). https://wikitech.leuksman.com/view/Server_admin_log -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Future of Javascript and mediaWiki
that just means the minification is broken on their platform no? So we have to debug the minification on their platform not the debug output ... but sure as you mention a hundreds of single character whitespace lines will compress nicely. --michael Gregory Maxwell wrote: On Fri, Dec 12, 2008 at 6:37 PM, Michael Dale md...@wikimedia.org wrote: The debug switch would modify the HTML output to point at the individual files with a GET seed ie myscript.js??php= date()? or something of that nature bypassing the script loader altogether. The bulk of extra content is comments, code documentation and debug statements .. line preservation does not seem worth it. Debug output should be enabled via a GET debug argument, user preference or $wgConfigure variable. So you end up with a user who says the problem goes away when they enable debug. Yet they can't provide useful debugging info with the failing version because it's all garbled minification output. May I suggest an alternative perspective with respect to line numbering: Destroying line numbers doesn't reduce the post-gzipped size by much, it does not seem worth it. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Future of Javascript and mediaWiki
On Fri, Dec 12, 2008 at 6:58 PM, Michael Dale md...@wikimedia.org wrote: that just means the minification is broken on their platform no? So we have to debug the minification on their platform not the debug output ... but sure as you mention a hundreds of single character whitespace lines will compress nicely. No it could mean that they are getting a corrupted copy if the mainline JS though some broken cache between the backend and their browser, which is being avoided by fetching a separate debugging JS. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
