[Wikitech-l] Extension registration next steps
Hi! Tim merged my patch[1] which implements the extension registration RfC[2]. For extensions (and skins!) to use this they need to be converted to have extension.json (or skin.json) files. A maintenance script, convertExtensionToRegistration.php, has been written to do this, but there may be some edge cases that need some manual tweaking. How should we go about migrating extensions? I've come up with a few different ideas: 1. Package the extension registration code into an extension which can be used by people who want to run newer copies of extensions on old MediaWiki versions. We would then convert extensions to the extension.json format and remove the PHP entry points. 2. Similar to #1, but package the extension registration code in each individual extension, like was done with the i18n migration. I don't really like this idea because a change to the code requires updating every single extension. 3. Convert all extensions to extension.json, but continue to maintain PHP entry points with duplicated information if the extension wants to maintain old compatibility. I'm personally leading towards option #1. Thoughts? Once we have a migration plan decided, I'll start working on updating documentation and other fun stuff. [1] https://gerrit.wikimedia.org/r/#/c/166705/ [2] https://www.mediawiki.org/wiki/Requests_for_comment/Extension_registration Thanks, -- Legoktm ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] A new extension of content tree about Wikipedia
Krinkle krinklemail at gmail.com writes: I'm not sure we should implement collapsible sections for desktop. If built and instrumented, one may find that users use it a fair bit and it may be better-than-nothing as solution for certain use cases. But I don't think collapsible sections would be an adequate feature for those use cases. Our table of contents is in desperate need of improvement. Having that be more accessible throughout the reading experience would be a big step forward[1] (much like the Wikipedia iOS app). Having a proper TOC means users don't have to collapse/expand anything. This would allow users to have a birds eye view of the document at all times, jump to any section at any time, whilst still being able to scroll through the document top to bottom as one would expect. From a performance viewpoint (as opposed to usability) we can still do optimisations such as not loading images until a section is accessed (lazy-load). What is the differences between an extension and a gadget? Eallan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Analytics] Office Hours for EventLogging Dashboarding
We will talk about Limn dashboards only. On Wed, Jan 7, 2015 at 8:47 PM, Gilles Dubuc gil...@wikimedia.org wrote: Are we talking about limn dashboards or will this cover other dashboarding tools as well? On Wed, Jan 7, 2015 at 11:11 PM, Kevin Leduc ke...@wikimedia.org wrote: Reminder, the Analytics Engineering team has office hours Wednesday next week to assist with EventLogging and Dashboards. If you're at the San Francisco office, you can join us in room R35 Chambers. If you have any questions about the event, let me know. Thanks! On Mon, Dec 22, 2014 at 12:51 PM, Kevin Leduc ke...@wikimedia.org wrote: Please join the Analytics Engineering team for... Office Hours: EventLogging Dashboarding Hosts: Dan and Nuria Date: January 14 Time: 20:00 UTC - Convert to Local Time http://www.timeanddate.com/worldclock/fixedtime.html?msg=EventLogging+and+Dashboarding+Office+Hoursiso=20150114T20p1=%3Aah=1 Hangout: https://plus.google.com/hangouts/_/wikimedia.org/a-batcave IRC: #wikimedia-analytics Description: Teams need metrics on how their product or feature is performing, then they need to visualize those metrics. This is accomplished with instrumenting code with EventLogging, mashing data with some queries and setting up a Limn Dashboard. The Analytics Engineering team is open for office hours to answer questions about the process, help solve any issues and listen to feedback on the process. Feel free to drop in the Goolge Hangout linked above or ask questions on the IRC channel during our Office Hours. ___ Analytics mailing list analyt...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics ___ Analytics mailing list analyt...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Pre-scheduling all the MWDS 2015 sessions in the main room
If you want to propose a session for the main room of the MediaWiki Developer Summit, then make sure it is fit to compete for a slot at https://phabricator.wikimedia.org/T85632 RobLa and I are coordinating this exercise and we want to have the main room fully pre-scheduled by the end of next Monday, Jan 12. The rest of the schedule is open, meaning that anybody can book a slot as long as it is available. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] maintenance.php files in symlinks context problem
Hi! I access as a system root. I have loaded 1.23 in /wiki I have symlinked it in my /home/wiki-site/www directories. It works without problem. However, when I try php maintenance/sqlite.php (or other .php files) --conf /home/wiki-site/www/LocalSettings.php (or without this -conf addition) I get the same response: Warning: require_once(__DIR__/Maintenance.php): failed to open stream: No such file or directory in /wiki/maintenance/sqlite.php on line 24 Fatal error: require_once(): Failed opening required '__DIR__/Maintenance.php' (include_path='.:/usr/local/php5/lib/php') in /wiki/maintenance/sqlite.php on line 24 - I also installed some wikis without sysmlink. I such a case if I enter php maintenance/dumpBackup.php --full .xml I get: Access denied for user 'root'@'localhost' (using password: NO) The same if I enter php maintenance/dumpBackup.php --dbuser user --dbpass pass --full .xml Thank you for the help. jefsey ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Frustration about Canvas
Ok, Ricordisamoa, it runs, thanks for suggestion and your boldness while reading my DIY js code ;-) ! Alex 2015-01-08 0:33 GMT+01:00 Ricordisamoa ricordisa...@openmailbox.org: It's about https://it.wikisource.org/wiki/MediaWiki:Gadget-cornersAlpha.js, isn't it? This change https://it.wikisource.org/w/index.php?diff=1499050oldid= 1498642 should do the job. Il 07/01/2015 10:21, Alex Brollo ha scritto: While dragging a little bit into canvas, I successfully upload into a canvas a cropped clip of the image of a djvu page into it.source, just to crash into a DOM exception The canvas has been tainted by cross-origin data while attempting do access to pixel data with both getImageData() and toDataURL() methods. Again, it seems a CORS issue. Am I wrong? Is there some doc about this issue? Alex brollo ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
