[Wikitech-l] Try out MediaWiki Vagrant
Vagrant is a command-line tool for automatically provisioning virtual machines according to scripted specifications. The mediawiki-vagrant project bundles together specifications for quickly and easily provisioning a virtual machine running MediaWiki, suitable for development work. I announced it a few months ago, when I had something nominally useful to share. Some people found it useful, but it was something I had cobbled together in a hacky way as I was learning Vagrant, and I wasn't very happy with the end result. In the intervening months, I got a lot of useful suggestions, and became more proficient in writing Vagrant and Puppet configurations, so I decided to do things over. There's a lot more work to do (better profiling tools!), but I think it works quite well now, so I would appreciate some testing and feedback from others. Installation instructions are available here: http://www.mediawiki.org/wiki/Vagrant I hope you check it out, and that you find it useful. Feedback would be much appreciated. I'd also like to publicly thank Yurik for testing this extensively on Windows and providing detailed logs when things broke. Thanks, Yurik! -- Ori Livneh ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC: Alternative domains for Commons
What about inserting another domain just to prevent confusion and to keep current redirects, which would ONLY allow api, such as commons.api.wikipedia.org the *.api.project would just be some kind of universal api gateway for all domains On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org wrote: On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote: Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-) http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains Please share your comments. commons.wikipedia.org already redirects to commons.wikimedia.org (for historical reasons, maybe), so that has to be considered. Yes, it redirects. But to solve the problem I'm describing, the API would need to be served from commons.wikipedia.org. I think what you're proposing is also kind of confusing and I'm wondering if there aren't better ways to approach the problem. I'm open to suggestions, but I'd rather not wait until CentralAuth gets completely redesigned and rewritten. -- Juliusz ___ 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] RFC: Alternative domains for Commons
How is that meant to pervent confusion? you are just sticking a extra .api in the address. On Thu, Mar 28, 2013 at 5:41 PM, Petr Bena benap...@gmail.com wrote: What about inserting another domain just to prevent confusion and to keep current redirects, which would ONLY allow api, such as commons.api.wikipedia.org the *.api.project would just be some kind of universal api gateway for all domains On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org wrote: On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote: Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-) http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains Please share your comments. commons.wikipedia.org already redirects to commons.wikimedia.org (for historical reasons, maybe), so that has to be considered. Yes, it redirects. But to solve the problem I'm describing, the API would need to be served from commons.wikipedia.org. I think what you're proposing is also kind of confusing and I'm wondering if there aren't better ways to approach the problem. I'm open to suggestions, but I'd rather not wait until CentralAuth gets completely redesigned and rewritten. -- Juliusz ___ 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
Re: [Wikitech-l] RFC: Alternative domains for Commons
or MAYBE, even more evil: commons.wikimedia.api.wikipedia.org -- where first two domains commons.wikimedia would point to existing domain, that would actually allow you to enable this gateway instantly on all projects for all domains, so that you could use api of fr.wikisource using wikispecies domain: fr.wikisource.api.wikispecies.org I don't know if that is actually good for anything :) but it would surely allow you to bypass cookie restrictions everywhere (for api's only). On the other way, I think we could just think of using some different technology than cookies to avoid mess with DNS On Thu, Mar 28, 2013 at 8:41 AM, Petr Bena benap...@gmail.com wrote: What about inserting another domain just to prevent confusion and to keep current redirects, which would ONLY allow api, such as commons.api.wikipedia.org the *.api.project would just be some kind of universal api gateway for all domains On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org wrote: On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote: Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-) http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains Please share your comments. commons.wikipedia.org already redirects to commons.wikimedia.org (for historical reasons, maybe), so that has to be considered. Yes, it redirects. But to solve the problem I'm describing, the API would need to be served from commons.wikipedia.org. I think what you're proposing is also kind of confusing and I'm wondering if there aren't better ways to approach the problem. I'm open to suggestions, but I'd rather not wait until CentralAuth gets completely redesigned and rewritten. -- Juliusz ___ 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] RFC: Alternative domains for Commons
because right now commons.wikipedia.org is already redirecting to wikimedia if you change this behavior now, you may confuse some people who were expecting it to redirect... but I don't really care On Thu, Mar 28, 2013 at 8:44 AM, K. Peachey p858sn...@gmail.com wrote: How is that meant to pervent confusion? you are just sticking a extra .api in the address. On Thu, Mar 28, 2013 at 5:41 PM, Petr Bena benap...@gmail.com wrote: What about inserting another domain just to prevent confusion and to keep current redirects, which would ONLY allow api, such as commons.api.wikipedia.org the *.api.project would just be some kind of universal api gateway for all domains On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org wrote: On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote: Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-) http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains Please share your comments. commons.wikipedia.org already redirects to commons.wikimedia.org (for historical reasons, maybe), so that has to be considered. Yes, it redirects. But to solve the problem I'm describing, the API would need to be served from commons.wikipedia.org. I think what you're proposing is also kind of confusing and I'm wondering if there aren't better ways to approach the problem. I'm open to suggestions, but I'd rather not wait until CentralAuth gets completely redesigned and rewritten. -- Juliusz ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC: Alternative domains for Commons
A small issue in this proposition: sub-subdomains are not currently covered by the https certificate. ~s Le Thu, 28 Mar 2013 08:41:41 +0100, Petr Bena benap...@gmail.com a écrit: What about inserting another domain just to prevent confusion and to keep current redirects, which would ONLY allow api, such as commons.api.wikipedia.org the *.api.project would just be some kind of universal api gateway for all domains On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org wrote: On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote: Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-) http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains Please share your comments. commons.wikipedia.org already redirects to commons.wikimedia.org (for historical reasons, maybe), so that has to be considered. Yes, it redirects. But to solve the problem I'm describing, the API would need to be served from commons.wikipedia.org. I think what you're proposing is also kind of confusing and I'm wondering if there aren't better ways to approach the problem. I'm open to suggestions, but I'd rather not wait until CentralAuth gets completely redesigned and rewritten. -- Juliusz ___ 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
Re: [Wikitech-l] Try out MediaWiki Vagrant
This is awesome, I've used it as a total MediaWiki noob to poke around at the internals. One suggestion I'd have is to include a script that populates some sample data in the db (pages, users, edits, etc.). Does anyone have such a thing, should we dump a particularly active test setup from somewhere, or would we need to make something new? On Thu, Mar 28, 2013 at 2:18 AM, Ori Livneh o...@wikimedia.org wrote: Vagrant is a command-line tool for automatically provisioning virtual machines according to scripted specifications. The mediawiki-vagrant project bundles together specifications for quickly and easily provisioning a virtual machine running MediaWiki, suitable for development work. I announced it a few months ago, when I had something nominally useful to share. Some people found it useful, but it was something I had cobbled together in a hacky way as I was learning Vagrant, and I wasn't very happy with the end result. In the intervening months, I got a lot of useful suggestions, and became more proficient in writing Vagrant and Puppet configurations, so I decided to do things over. There's a lot more work to do (better profiling tools!), but I think it works quite well now, so I would appreciate some testing and feedback from others. Installation instructions are available here: http://www.mediawiki.org/wiki/Vagrant I hope you check it out, and that you find it useful. Feedback would be much appreciated. I'd also like to publicly thank Yurik for testing this extensively on Windows and providing detailed logs when things broke. Thanks, Yurik! -- Ori Livneh ___ 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] Next Bugday: Skin and page rendering, April 2nd, 16:30 - 20:30 UTC
Hi, Please join us on the next Wikimedia Bugday: Tuesday, April 02, 2013 from 16:30 UTC until 20:30 UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging skin and page rendering bug reports [3] as proposed on the Bugsquad project talk page [4]. Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved in the community or to give something back. This is part of a weekly QA activity [5], so we encourage you to triage throughout the week and record your activity on the bug day etherpad [6]. This information and more can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20130402 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage I look forward to seeing you there! andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat [3] https://www.mediawiki.org/wiki/Bug_management/Triage/20130402 [4] https://www.mediawiki.org/wiki/Project_talk:WikiProject_Bug_Squad#Bug_Day_Topics_for_April_25280 [5] https://www.mediawiki.org/wiki/QA/Weekly_goals [6] http://etherpad.wmflabs.org/pad/p/BugTriage -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikidata queries
We have a first write up of how we plan to support queries in Wikidata. Comments on our errors and requests for clarifications are more than welcome. https://meta.wikimedia.org/wiki/Wikidata/Development/Queries Cheers, Denny P.S.: unfortunately, no easter eggs inside. -- Project director Wikidata Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. +49-30-219 158 26-0 | http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
Le 27/03/13 15:35, Andre Klapper a écrit : OpenStack also have live graphs at http://status.openstack.org/bugday/ for their bugdays (e.g. https://wiki.openstack.org/wiki/BugDays/20121213BugSquashing ), but I have no idea about the implementation, plus bugdays look dormant there. If anybody has contacts to OpenStack, I'd be interested to know. Do hangout on IRC in #openstack-infra during US business days. The folks there are most probably maintaining this :-] As usual, just introduce yourself, state you are related to Wikimedia and you will receive a warm welcome! -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
On Wed, 2013-03-27 at 15:35 +0100, Andre Klapper wrote: OpenStack also have live graphs at http://status.openstack.org/bugday/ for their bugdays (e.g. https://wiki.openstack.org/wiki/BugDays/20121213BugSquashing ), but I have no idea about the implementation, plus bugdays look dormant there. If anybody has contacts to OpenStack, I'd be interested to know. Thanks to Luis for making contact! Thierry Carrez answered that the code to generate those graphs is at https://github.com/ttx/bugdaystats , and There is a stats file refresh that runs regularly (like in a crontab) and then client-side code to generate dynamic graphs from those static stats. So if anybody feels like playing with it, go ahead! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikidata queries
How will be the queries formatted? Do I understand it correctly that a QueryConcept is a JSON object? Have you considered using something more in line with the format of action=query queries? Though I guess what you need is much more complicated and trying to fit it into the action=query model wouldn't end well. Petr Onderka [[en:User:Svick]] 2013/3/28 Denny Vrandečić denny.vrande...@wikimedia.de: We have a first write up of how we plan to support queries in Wikidata. Comments on our errors and requests for clarifications are more than welcome. https://meta.wikimedia.org/wiki/Wikidata/Development/Queries Cheers, Denny P.S.: unfortunately, no easter eggs inside. -- Project director Wikidata Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. +49-30-219 158 26-0 | http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ 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] Try out MediaWiki Vagrant
On Thu, Mar 28, 2013 at 7:18 AM, Ori Livneh o...@wikimedia.org wrote: I hope you check it out, and that you find it useful. Feedback would be much appreciated. I have tried it at two Mac machines, it worked without any problems. Željko ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Try out MediaWiki Vagrant
I tried it out on my Windows XP, and on `vagrant up` it promptly took all the 1.5 GB of free space on disk C: and crashed (I purposefully keep my system partition small). Is it possible to make it write the big files (the downloaded OS image and the virtual disk) into somewhere else than %userprofile%? I know VirtualBox can do that, as I have two VMs set up in this way. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Try out MediaWiki Vagrant
Ori, thanks for the great dev environment :) As mentioned in another email, I would like to have the following added to default vagrant installation. Having default dev environment would allow us to quickly get new developers up to speed almost without any walk-through steps. * redirect from / to /w/index.php * xdebug to debug from host's IDE * unit testing frameworks, and maybe even some scripts to run php and other unit tests * easy way to add extensions - menu driven would be nice, or at least git clone and add the required() :) * SQL access - either phpMyAdmin, or routing SQL ports to host's tools, or both, or ... * reset script to quickly restart apache/memcached/etc (is it possible to do it from host?) * Direct root access to the client's file system from the host (in windows -- \\precsie64\root\...) * php update.php - is it possible to do it from host? vagrant mwupdate ? Thanks!!! On Thu, Mar 28, 2013 at 4:15 PM, Bartosz Dziewoński matma@gmail.comwrote: I tried it out on my Windows XP, and on `vagrant up` it promptly took all the 1.5 GB of free space on disk C: and crashed (I purposefully keep my system partition small). Is it possible to make it write the big files (the downloaded OS image and the virtual disk) into somewhere else than %userprofile%? I know VirtualBox can do that, as I have two VMs set up in this way. -- Matma Rex __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://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] RFC: Alternative domains for Commons
On Thu, Mar 28, 2013 at 8:45 AM, Petr Bena benap...@gmail.com wrote: I don't know if that is actually good for anything :) but it would surely allow you to bypass cookie restrictions everywhere (for api's only). On the other way, I think we could just think of using some different technology than cookies to avoid mess with DNS Adding just one domain doesn't seem like a big mess. I'm not sure when we'll have a different technology other than cookies and I'm also afraid that the workaround I described in the RFC won't work forever (if it does work now, we'll know in a few days). -- Juliusz ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC: Alternative domains for Commons
On Thu, Mar 28, 2013 at 9:59 AM, Seb35 seb35wikipe...@gmail.com wrote: A small issue in this proposition: sub-subdomains are not currently covered by the https certificate. That would make only commons.api.wikipedia.org not work, but not commons.wikipedia.org, right? -- Juliusz ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC: Alternative domains for Commons
Le Fri, 29 Mar 2013 00:45:03 +0100, Juliusz Gonera jgon...@wikimedia.org a écrit: On Thu, Mar 28, 2013 at 9:59 AM, Seb35 seb35wikipe...@gmail.com wrote: A small issue in this proposition: sub-subdomains are not currently covered by the https certificate. That would make only commons.api.wikipedia.org not work, but not commons.wikipedia.org, right? Yes. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Try out MediaWiki Vagrant
On Thursday, March 28, 2013 at 4:41 PM, Yuri Astrakhan wrote: As mentioned in another email, I would like to have the following added to default vagrant installation. Having default dev environment would allow us to quickly get new developers up to speed almost without any walk-through steps. * redirect from / to /w/index.php This is already set up. Is it not working for you? * xdebug to debug from host's IDE Installation of Xdebug is also already in, but not the IDE integration and URL trigger that you described to me the other day. I'll look into it. Tracking here: https://bugzilla.wikimedia.org/show_bug.cgi?id=46677 * unit testing frameworks, and maybe even some scripts to run php and other unit tests phpunit is also already installed. A helper script for running unit tests from the host environment would make sense. * easy way to add extensions - menu driven would be nice, or at least git clone and add the required() :) Punting on this one. It'll be a headache to maintain. Adding the require_once( .. ) call by hand is not too much work, no? * SQL access - either phpMyAdmin, or routing SQL ports to host's tools, or both, or ... * reset script to quickly restart apache/memcached/etc (is it possible to do it from host?) OK, can do. * Direct root access to the client's file system from the host (in windows -- \\precsie64\root\...) * php update.php - is it possible to do it from host? vagrant mwupdate ? I'll look into making this easier. Vagrant provides hooks for plug-ins to add subcommands. Having a MediaWiki plug-in that allows a set of maintenance tasks to be run from the host sounds promising. Tracking here: https://bugzilla.wikimedia.org/show_bug.cgi?id=46676 On Thu, Mar 28, 2013 at 4:15 PM, Bartosz Dziewoński matma@gmail.com (mailto:matma@gmail.com)wrote: I tried it out on my Windows XP, and on `vagrant up` it promptly took all the 1.5 GB of free space on disk C: and crashed (I purposefully keep my system partition small). Is it possible to make it write the big files (the downloaded OS image and the virtual disk) into somewhere else than %userprofile%? I know VirtualBox can do that, as I have two VMs set up in this way. Yes, this should be handled better. Thanks for the report. Tracking it here: https://bugzilla.wikimedia.org/show_bug.cgi?id=46675 -- Ori Livneh ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
