[Wikitech-l] jenkins: unit test whitelist
Hello, As you surely have noticed, the unit tests for mediawiki/core are no more run when a patch is submitted. I have just enabled a feature that whitelist people to have unit tests run for them on patch submission. The patch still need to be reviewed and approved with a CR+2 though. Basically any user with a @wikimedia.org or @wikimedia.de email address is whitelisted by default. I have also added a few contractors using their personal emails and several long term users. The related change is: https://gerrit.wikimedia.org/r/#/c/39310/ This is only enabled for mediawiki/core for now, I will look at applying such a whitelist on extensions too in January. There is no process to be added in the whitelist, I guess you could talk about it on IRC. If there is no obvious veto there, you could probably just amend layout.yaml in integration/zuul-config.git file and get it approved :) cheers, -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] jenkins: unit test whitelist
Just curious -- I probably missed it in a previous mail -- why are the tests switched off? To preserve processing power? To speed up tests for the whitelisted? Security concerns when running tests with arbitrary code? Other? Cheers, Denny 2012/12/19 Antoine Musso hashar+...@free.fr Hello, As you surely have noticed, the unit tests for mediawiki/core are no more run when a patch is submitted. I have just enabled a feature that whitelist people to have unit tests run for them on patch submission. The patch still need to be reviewed and approved with a CR+2 though. Basically any user with a @wikimedia.org or @wikimedia.de email address is whitelisted by default. I have also added a few contractors using their personal emails and several long term users. The related change is: https://gerrit.wikimedia.org/r/#/c/39310/ This is only enabled for mediawiki/core for now, I will look at applying such a whitelist on extensions too in January. There is no process to be added in the whitelist, I guess you could talk about it on IRC. If there is no obvious veto there, you could probably just amend layout.yaml in integration/zuul-config.git file and get it approved :) cheers, -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- 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] How to speed up the review in gerrit?
Hello! 28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts extensions. Since then I've corrected two of them (uploaded patch set 2), but after that, nobody did the review. As I understand, Gerrit will abandon changes after a month of inactivity, and it will come tomorrow... The changes are really simple. How to ask someone to really do the review? Does Gerrit have such function? Thanks in advance, Vitaliy Filippov ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
You could add people as reviewers, or personally ask someone to review, prefereably someone who worked on the extension in the past. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] (Roughly) 2 week delay for MediaWiki 1.21wmf7
This looks very well for us. Just one thing: Phase 4 of 1.21wmf7 should probably be Monday, January 14, not January 11. Cheers, Denny 2012/12/17 Rob Lanphier ro...@wikimedia.org Hi everyone, Because a number of people are planning to take time off for the holidays, I'd like to postpone the regular release cycle for 2 weeks, with 1.21wmf7 being a slightly longer window than normal, and 1.21wmf8 stretched out a little bit as well to accommodate MLK day (January 21). Here's what things will look like in the revised schedule: 1.21wmf7: * Wednesday, January 2 (test, test2, mediawiki.org, wikidata.org) * Monday, January 7 (non-Wikipedia) * Wednesday, January 9 (English Wikipedia) * Monday, January 11 (other Wikipedia) 1.21wmf8 * Wednesday, January 16 (test, test2, mediawiki.org, wikidata.org) * Wednesday, January 23 (non-Wikipedia) * Monday, January 28 (English Wikipedia) * Wednesday, January 30 (other Wikipedia) We would then resume the normal cadence Monday, February 4 when we deploy 1.21wmf9. The nice thing about doing things this way is that the cycle stretches out the time that 1.21wmf7 and 1.21wmf8 sit on test2 over the normal cycle, which gives us a little more time to notice problems. Any objections? I don't think there's room to keep the standard cycle, but there's plenty of tweaking around the edges we can make. Rob ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- 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] How to speed up the review in gerrit?
Le 19/12/12 11:57, vita...@yourcmc.ru wrote: Hello! 28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts extensions. Since then I've corrected two of them (uploaded patch set 2), but after that, nobody did the review. As I understand, Gerrit will abandon changes after a month of inactivity, and it will come tomorrow... The changes are really simple. How to ask someone to really do the review? Does Gerrit have such function? And the changes are: https://gerrit.wikimedia.org/r/#/c/39369/ add a dependency on mediawiki.legacy.wikibits. https://gerrit.wikimedia.org/r/#/c/25629/ Fix a bug: drafts didn't show up when creating new pages https://gerrit.wikimedia.org/r/#/c/25628/ Always display user's drafts on the edit form https://gerrit.wikimedia.org/r/#/c/25627/ Fix for PHP 5.4: add to function prototype -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
Matma Rex писал 2012-12-19 15:01: You could add people as reviewers, or personally ask someone to review, prefereably someone who worked on the extension in the past. Okay, I've just done it... So, do you mean all committers just add random reviewers when they see no reaction? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
Antoine Musso писал 2012-12-19 16:19: Le 19/12/12 11:57, vita...@yourcmc.ru wrote: Hello! 28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts extensions. Since then I've corrected two of them (uploaded patch set 2), but after that, nobody did the review. As I understand, Gerrit will abandon changes after a month of inactivity, and it will come tomorrow... The changes are really simple. How to ask someone to really do the review? Does Gerrit have such function? And the changes are: https://gerrit.wikimedia.org/r/#/c/39369/ add a dependency on mediawiki.legacy.wikibits. https://gerrit.wikimedia.org/r/#/c/25629/ Fix a bug: drafts didn't show up when creating new pages https://gerrit.wikimedia.org/r/#/c/25628/ Always display user's drafts on the edit form https://gerrit.wikimedia.org/r/#/c/25627/ Fix for PHP 5.4: add to function prototype Yes, exactly! I've just added the first one (added dependency..). Others are older.. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] jenkins: PHPUnit upgraded to 3.7.10
Hello, I have upgraded PHPUnit 3.7.10 on pour Jenkins installation. It already ran a full test suite of mediawiki/core without any trouble. If you get any trouble with it, please open a bug under Wikimedia Testing Infrastructure. For reference the bug requesting upgrade was: https://bugzilla.wikimedia.org/42724 -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
On 12/19/2012 07:24 AM, vita...@yourcmc.ru wrote: Antoine Musso писал 2012-12-19 16:19: Le 19/12/12 11:57, vita...@yourcmc.ru wrote: Hello! 28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts extensions. Since then I've corrected two of them (uploaded patch set 2), but after that, nobody did the review. As I understand, Gerrit will abandon changes after a month of inactivity, and it will come tomorrow... The changes are really simple. How to ask someone to really do the review? Does Gerrit have such function? And the changes are: https://gerrit.wikimedia.org/r/#/c/39369/ add a dependency on mediawiki.legacy.wikibits. https://gerrit.wikimedia.org/r/#/c/25629/ Fix a bug: drafts didn't show up when creating new pages https://gerrit.wikimedia.org/r/#/c/25628/ Always display user's drafts on the edit form https://gerrit.wikimedia.org/r/#/c/25627/ Fix for PHP 5.4: add to function prototype Yes, exactly! I've just added the first one (added dependency..). Others are older.. Try these tips: https://www.mediawiki.org/wiki/Git/Code_review/Getting_reviews -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
I've had patchsets that I submitted in August and they still haven't been merged. For example, the account creation API, which has actually been approved, but never merged. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Dec 19, 2012 at 1:30 PM, Sumana Harihareswara suma...@wikimedia.org wrote: On 12/19/2012 07:24 AM, vita...@yourcmc.ru wrote: Antoine Musso писал 2012-12-19 16:19: Le 19/12/12 11:57, vita...@yourcmc.ru wrote: Hello! 28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts extensions. Since then I've corrected two of them (uploaded patch set 2), but after that, nobody did the review. As I understand, Gerrit will abandon changes after a month of inactivity, and it will come tomorrow... The changes are really simple. How to ask someone to really do the review? Does Gerrit have such function? And the changes are: https://gerrit.wikimedia.org/r/#/c/39369/ add a dependency on mediawiki.legacy.wikibits. https://gerrit.wikimedia.org/r/#/c/25629/ Fix a bug: drafts didn't show up when creating new pages https://gerrit.wikimedia.org/r/#/c/25628/ Always display user's drafts on the edit form https://gerrit.wikimedia.org/r/#/c/25627/ Fix for PHP 5.4: add to function prototype Yes, exactly! I've just added the first one (added dependency..). Others are older.. Try these tips: https://www.mediawiki.org/wiki/Git/Code_review/Getting_reviews -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ 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] Clarification on unit tests requiring CR+2
Hello, We would like to clarify the reason we changed Jenkins to no longer run unit tests on patch submission. We had to defer code execution to after CR+2 for security reasons. If unit tests were ran on submission that meant anyone with a labs account could effectively get shell access on the server. Because LDAP accounts are now up for open registration (aka free Labs accounts, and by extend permission to submit patches to Gerrit), that also meant the whole world would be able to get shell access on the server (via PHP/Nodejs/ant/bash to infinity and beyond). This issue will be definitely solved by isolating tests in dedicated virtual machines for each run. We are investigating Vagrant. Restricting unit tests is simpler and faster to implement over all the Vagrant engineering. So running tests after CR+2 is a temporary measure until the implementation of Vagrant sandboxes in Jenkins builds is ready. So, in conclusion: Unit tests will be run again on patch submission once we have finished integrating Vagrant in Jenkins. -- The CI team Antoine Timo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Small tweak to Gerrit Verified category - tomorrow
On Dec 18, 2012, at 6:01 AM, Liangent liang...@gmail.com wrote: On Tue, Dec 18, 2012 at 12:45 PM, Chad innocentkil...@gmail.com wrote: Linting jobs will receive Verified ±1 votes. Unit tests jobs (triggered after someone votes CR+2, as it currently is) will receive Verified ±2 votes. Actually I prefer running unit tests on every new patchset as what we did in the past. Some issues in my code were caught by it. Afaik everybody prefers tests to be ran on submission, including yours truly. However this thread does not discuss that change. This change was made a few weeks back. Now that everything is in place we can elaborate on this. Antoine and I sent out a mai to wikitech-l just now: http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065202.html -- Krinkle ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Clarification on unit tests requiring CR+2
Sounds good to me. IMHO, if you're submitting a patch and haven't already run unit tests on that patch, you're probably doing something wrong. I've done that a few times myself, and could have avoided unnecessary patchset submissions if I had done so. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Dec 19, 2012 at 2:48 PM, Krinkle krinklem...@gmail.com wrote: Hello, We would like to clarify the reason we changed Jenkins to no longer run unit tests on patch submission. We had to defer code execution to after CR+2 for security reasons. If unit tests were ran on submission that meant anyone with a labs account could effectively get shell access on the server. Because LDAP accounts are now up for open registration (aka free Labs accounts, and by extend permission to submit patches to Gerrit), that also meant the whole world would be able to get shell access on the server (via PHP/Nodejs/ant/bash to infinity and beyond). This issue will be definitely solved by isolating tests in dedicated virtual machines for each run. We are investigating Vagrant. Restricting unit tests is simpler and faster to implement over all the Vagrant engineering. So running tests after CR+2 is a temporary measure until the implementation of Vagrant sandboxes in Jenkins builds is ready. So, in conclusion: Unit tests will be run again on patch submission once we have finished integrating Vagrant in Jenkins. -- The CI team Antoine Timo ___ 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] Clarification on unit tests requiring CR+2
On Wed, Dec 19, 2012 at 11:48 AM, Krinkle krinklem...@gmail.com wrote: Hello, We would like to clarify the reason we changed Jenkins to no longer run unit tests on patch submission. Thanks for this update. Also, cross-referencing Antoine's post on the interim whitelist solution for mediawiki/core: http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065191.html From that post: There is no process to be added in the whitelist, I guess you could talk about it on IRC. If there is no obvious veto there, you could probably just amend layout.yaml in integration/zuul-config.git file and get it approved :) So if you're a trusted dev already (as determined by your peers) and would like to get your tests run automatically on each patchset, but aren't on the wihtelist yet, you can submit a patch to do so against this file: https://gerrit.wikimedia.org/r/gitweb?p=integration/zuul-config.git;a=blob;f=layout.yaml;hb=HEAD That seems like a reasonable interim solution until we've got a more secure setup, especially once the whitelist works against extensions as well. Thanks for all your hard work on improving the setup while also making things more open for new developers. Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
On 12/19/2012 02:41 PM, Tyler Romeo wrote: I've had patchsets that I submitted in August and they still haven't been merged. For example, the account creation API, which has actually been approved, but never merged. Which one are you referring to, https://gerrit.wikimedia.org/r/#/c/18127/ ? On a simpler note, why does it have your name as Parent5446? https://gerrit.wikimedia.org/r/#/dashboard/278 Can someone fix this? Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
On Wed, 19 Dec 2012 22:55:24 +0100, Matthew Flaschen mflasc...@wikimedia.org wrote: On a simpler note, why does it have your name as Parent5446? https://gerrit.wikimedia.org/r/#/dashboard/278 Can someone fix this? There's a bug for that: https://bugzilla.wikimedia.org/show_bug.cgi?id=40061 I've been wanting to fix my name for ages as well... -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
Yep, that patch. If you notice, patches 8, 16, 18, 20, and 21 have all been approved, i.e., +2 on CR. But it's yet to have been merged. At the very least, its dependency has been merged. I'm not in a humongous rush or anything, I'm just pointing out that sometimes you really just have to wait it out. ;) *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Dec 19, 2012 at 4:58 PM, Matma Rex matma@gmail.com wrote: On Wed, 19 Dec 2012 22:55:24 +0100, Matthew Flaschen mflasc...@wikimedia.org wrote: On a simpler note, why does it have your name as Parent5446? https://gerrit.wikimedia.org/**r/#/dashboard/278https://gerrit.wikimedia.org/r/#/dashboard/278 Can someone fix this? There's a bug for that: https://bugzilla.wikimedia.** org/show_bug.cgi?id=40061https://bugzilla.wikimedia.org/show_bug.cgi?id=40061 I've been wanting to fix my name for ages as well... -- 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] How to speed up the review in gerrit?
On 12/19/2012 05:06 PM, Tyler Romeo wrote: Yep, that patch. If you notice, patches 8, 16, 18, 20, and 21 have all been approved, i.e., +2 on CR. But it's yet to have been merged. At the very least, its dependency has been merged. I'm not in a humongous rush or anything, I'm just pointing out that sometimes you really just have to wait it out. ;) Yeah, I don't have any clever suggestion, just ping people on IRC or email if some time elapses. Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
On 12/19/2012 04:58 PM, Matma Rex wrote: On Wed, 19 Dec 2012 22:55:24 +0100, Matthew Flaschen mflasc...@wikimedia.org wrote: On a simpler note, why does it have your name as Parent5446? https://gerrit.wikimedia.org/r/#/dashboard/278 Can someone fix this? There's a bug for that: https://bugzilla.wikimedia.org/show_bug.cgi?id=40061 I've been wanting to fix my name for ages as well... It turns out Parent5446 is his actual username. But if I didn't know better, it looks like some auto-generated gerrit ID. :) Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to speed up the review in gerrit?
Lol yes. Parent5446 is my actual username, although it is not my name in real life. :P *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Dec 19, 2012 at 5:15 PM, Matthew Flaschen mflasc...@wikimedia.orgwrote: On 12/19/2012 04:58 PM, Matma Rex wrote: On Wed, 19 Dec 2012 22:55:24 +0100, Matthew Flaschen mflasc...@wikimedia.org wrote: On a simpler note, why does it have your name as Parent5446? https://gerrit.wikimedia.org/r/#/dashboard/278 Can someone fix this? There's a bug for that: https://bugzilla.wikimedia.org/show_bug.cgi?id=40061 I've been wanting to fix my name for ages as well... It turns out Parent5446 is his actual username. But if I didn't know better, it looks like some auto-generated gerrit ID. :) Matt Flaschen ___ 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] Clarification on unit tests requiring CR+2
On 19/12/12 20:48, Krinkle wrote: This issue will be definitely solved by isolating tests in dedicated virtual machines for each run. We are investigating Vagrant. A VM seems overkill when it can be solved with standard user permissions + chroot (or even better, a bsd jail) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Follow / like MediaWiki @ social media
It's not completely sorted out but there has been a big progress in just a couple of days: https://www.mediawiki.org/wiki/Social_media Summary: follow like MediaWiki in your social networks to read promote MediaWiki Wikimedia tech news. * http://identi.ca/mediawiki * https://twitter.com/MediaWiki * https://www.facebook.com/MediaWikiProject These channels pay a lot of attention to critical mass. The more followers and shares/likes the more promoted you get (more or less). Your support is welcome. See also how we can redistribute your relevant updates: https://www.mediawiki.org/wiki/Social_media#Sharing_your_updates There are still some details to polish e.g. how to automate the process including Facebook ( Google+) or how to clear the FB mess. If you enjoy social media your ideas are welcome: https://www.mediawiki.org/wiki/Talk:Social_media -- Quim Gil Technical Contributor Coordinator @ 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
Re: [Wikitech-l] Clarification on unit tests requiring CR+2
(anonymous) wrote: This issue will be definitely solved by isolating tests in dedicated virtual machines for each run. We are investigating Vagrant. A VM seems overkill when it can be solved with standard user permissions + chroot (or even better, a bsd jail) With chroot you also have to spend a lot of thought into setting up (and tearing down) the (non-SQLite) databases and other auxiliary services; VMs are much easier to deal with and adapt in this regard. Travis CI is probably the most prominent example of the openness and diversity one can achieve with potentially rogue users. But whether chroot or VMs, Jenkins or whatnot, it would be very nice if WMF could finally commit some resources to this problem. The underlying security question was tabled months ago, and the solution to it isn't exactly rocket science as evidenced by the various existing services, but still hard work. Tim ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Secure Coding Documentation
Hi Everyone, I'd like to invite anyone interested to join in on a secure coding documentation sprint on Friday of this week (Dec 21st), from 11:30am - 12:30pm PST (19:30-20:30 UTC). If you're interested in joining, but can't make that specific time, let me know and we may hold more of these if there's interest. The goal of this sprint is to both help anyone who is interested learn about some specific security vulnerabilities, and update our documentation so that new developers can avoid these issues in the future. On Friday, I would like to address a couple of topics where we have very little documentation: * DOM-based XSS, and writing secure client side code. Closely related is general security for gadget developers. * Protecting private information (i.e., when do developers need to check if data has been deleted / suppressed) We'll spend a little time talking about each subject (and some specific issues we've seen recently), and I'll have a rough article outline in an etherpad. Then I would like everyone's help fleshing out the documents so they are clear and informative for other developers of all skill levels. I'll have both a google hangout for video, and an audio line for anyone who prefers to avoid closed technology. If you want to dial in, please let me know so I can get you a phone number in advance. Chris ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Demo for Concise Wikipedia proposal
Hi all, Since the Concise Wikipedia proposal[1] has been mentioned in the last two Signpost editions[2][3] (and after being nudged by Sumana), I figured I'd drop a note here in case anyone will be interested in trying out a demo I set up to explore the idea, espoused by many in the proposal discussion, that such a proposal should not be a separate project, but integrate with Wikipedia's lead/introduction sections instead. I called my demo Primerpedia (suggestions for better names welcome, see [4]), and it can be accessed here: http://waldir.github.com/primerpedia It uses the API to fetch the lead section of an article (currently only loading random articles is implemented), and displays it isolated, which should provide a good way to test its expected self-containing, summarizing properties, as defined in the MOS:LEAD guideline. I am aware of several shortcomings in the current implementation and plan to improve it further; any suggestions or issue reports are welcome at [5] or directly on this thread for convenience. --Waldir 1. https://meta.wikimedia.org/wiki/Concise_Wikipedia 2. https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-12-03/Discussion_report 3. https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-12-17/Discussion_report 4. https://github.com/waldir/primerpedia/wiki 5. https://github.com/waldir/primerpedia/issues ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Demo for Concise Wikipedia proposal
Le 20/12/12 05:15, Waldir Pimenta a écrit : I called my demo Primerpedia (suggestions for better names welcome, see [4]), and it can be accessed here: http://waldir.github.com/primerpedia I love it! I am a [[Special:random]] addict and offering only the first paragraph will let me get more random articles per minutes :-D I love the green Edit button. Maybe we should adopt your tool to replace / enhance Wikipedia main landing page at http://www.wikipedia.org/ A minor suggestion: maybe add a footer listing the license and the URL of the article. -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
