[00:03:36] 03(mod) Jenkins: Set up PHPUnit testing on MySQL backend - 10https://bugzilla.wikimedia.org/35912 +comment (10mflaschen) [00:04:00] 03(mod) VisualEditor: Cursor position should account for padding in alien inline blocks - 10https://bugzilla.wikimedia.org/48680 normal->minor (10Krinkle) [00:14:24] 03(NEW) Please upgrade the Bugzilla version - 10https://bugzilla.wikimedia.org/48736 normal; Wikimedia: Bugzilla; () [00:42:09] Is this the mediawiki support channel? [00:42:15] I have a question. [00:43:29] Now first, please note that I'm running mediawiki on wikinet. [00:43:48] My Wiki URL : http://mylittleponyfriendshipismagicwiki.wikinet.org/wiki/Main_Page [00:44:20] The question is... I tried to change the image above "Navigation" but it it didn't work. [00:44:20] It uploaded fine [00:44:26] but it didn't work. [00:46:51] I'm gonna find support elsewhere. [00:57:51] hey I am writting a mediawiki extension and the ajax seems to be blocked in it .. I am using MW 1.19 [00:58:33] I have checked with the logs and the ajax request was not there. I have check all the settings in default settings and local settings the ajax is perfectly allowed there .. [01:00:02] 03(NEW) Define rules for using Ganglia for individual tool statistics - 10https://bugzilla.wikimedia.org/48737 normal; Wikimedia Labs: tools; () [01:20:09] Anyone knows how to get ajax working for mediawiki Extensions (mw 1.19) [01:39:58] AdityaSastry__: What do you mean? [01:41:56] Thanks for responding susan [01:42:33] https://dpaste.de/Y1zPn/ -> code [01:43:06] I am trying to send data from my extension to a local php script.. but its not getting executed [01:43:34] I know this cause I have checked the easyPHP log and there is not mention of a post request there. [01:45:45] * Susan peeks. [01:46:03] Where are you putting this code? [01:46:39] In a javascript file which is loaded as a resource to my special page [01:47:30] Is the file being loaded? [01:47:36] Does alert(); work? [01:47:47] Yup .. I tried putting an alert before this [01:47:54] and that fires properly .. [01:48:16] I also tried putting a alert after this fragment of code but that is not fired [01:48:21] Did you make up method? [01:48:22] and the page is reloaded. [01:48:36] umm .. I didnt get you .. [01:49:02] https://dpaste.de/Y1zPn/ [01:49:06] Line 3 should be type:, I think. [01:49:11] Not method:. [01:49:58] Ohh yeah .. its type .. [01:50:08] But hey I copy pasted the code a while ago .. from the manual [01:50:23] Which page? :-) [01:50:26] So the one I am trying out is with type not method. [01:50:37] http://www.mediawiki.org/wiki/Manual:Ajax [01:50:57] That uses type. [01:51:17] Yup .. I pasted that exact code just a while ago .. and even that didnt work [01:51:19] Does that fix your issue? [01:51:34] :( no.. [01:52:04] this code runs fine when ran outside mw .. [01:52:38] Try jQuery.ajax({? [01:53:43] umm actually I am running this method from inside .. (function($){ .... })(jQuery); [01:54:00] That isn't what you pasted. [01:54:38] yeah that code that I pasted runs inside a function which runs inside this .. [01:54:53] Do you want me to paste the whole page code ? [01:56:11] If you'd like. [01:56:16] I don't really have the energy to debug this. [01:58:09] i dont think this needs debuging .. cause the server script that am trying to run works independently of mediawiki as of for now.. and hence I was able to test the client sided script outside MW as well. but now i started to integrate things and I started off with client sided script and this is not working [01:58:34] I actually remember reading somewhere in the manual once that ajax needs to be turned on .. [01:58:42] But i am unable to find that functionality [01:59:21] https://www.mediawiki.org/wiki/Manual:$wgUseAjax I guess. [02:00:31] ohh yes :D but its on by default :( [02:02:19] 03(mod) No language name for "no" code in "languages" tag - 10https://bugzilla.wikimedia.org/48424 +comment (10hazard_sj) [02:20:26] Hey could u tell me .. why no matter what I pass as the URL, the page is posted on itself using GET method ? [02:22:39] Hi, is it a good idea to follow this when extension writing? https://www.mediawiki.org/wiki/Manual:Coding_conventions/JavaScript [02:23:08] RAN1: yes, we have coding conventions for a reason [02:23:33] Kk, just double-checking. [02:24:13] odder: yes, otu of beta :) [02:24:25] odder: though no, those won't be the icons. Not Androidy enough [02:25:40] Ahah! [02:27:18] YuviPanda: Gareth supporting review branches may make you happy. But I just thought about something that might make you not so happy. [02:27:48] expensive flight tickets? :P [02:27:51] those make me pretty sad :P [02:28:08] DanielFriesen: did you run out of booze again? [02:28:09] YuviPanda: lol... Comments. [02:28:16] ? [02:28:19] on Gareth? [02:28:55] possible 1.21 will go release tonight? [02:29:36] I can't wait to get some Scribunto going on. :-) [02:31:06] YuviPanda: I don't intend to follow the same flat single level of comments that GitHub and Gerrit use. Gareth is going to record metadata on what comment is being replied to, support quoting, and have some smart handling of groups of comments. So GitHub/Gareth comments won't map to each other easily. [02:31:47] DanielFriesen: well, they won't 1:1 map, yeah [02:31:51] DanielFriesen: but... close enough? [02:32:01] DanielFriesen: plus the bot can record metadata of its own, no? [02:32:38] YuviPanda: Well the real issue is that a GitHub reply will break from what it's being replied to. [02:32:47] hmm? [02:33:00] the 'canonical' source for the code will still be GitHub [02:33:13] code updates in Gerrit won't go back... [02:33:18] Huh? [02:33:20] so people *shouldn't* update code in Gerrit... [02:33:30] if it started in GitHub [02:33:36] Ah... [02:33:37] hmm [02:33:48] Hmmm... [02:34:09] DanielFriesen: so that's technically impossible, since you can't push to the source branch on github if you aren't the owner [02:34:37] DanielFriesen: so my plan is to figure out a way to simply apply the gerrit patchset difference alone into github, and make that available as a one liner for people to copy paste [02:34:42] Talking about comments. [02:34:55] But that to does make me think. [02:35:24] or you could just stop using github >.> [02:35:33] Heh [02:36:27] why do people have opinions against using GitHub? [02:36:38] like, in additon to Gerrit, with Gerrit being canonical source of code? [02:36:46] DanielFriesen: also how is Gareth work coming along? [02:37:03] YuviPanda: You just came up with a pretty strong disadvantage. [02:37:13] Gerrit -> GitHub issue? [02:37:48] DanielFriesen: it's not an unsolveable issue [02:37:49] GitHub eliminates the collaboration from patchsets not allowing other people to update the review branch. [02:38:42] DanielFriesen: yeah, but we're not 'moving' to GitHub [02:39:07] DanielFriesen: people who are used to how GitHub works can use GitHub [02:39:14] and if they contribute enough, start using Gerrit [02:39:18] We're not, but it still means "Use GitHub and there's no collab" [02:39:30] DanielFriesen: well, Gerrit -> GitHub doesn't work right now [02:39:34] doesn't mean it won't ever [02:39:46] and besides, it's been like that for everything on GitHub ever [02:40:00] and it seems to be doing Okay for a lot of other open source projects [02:40:17] I can see it also disabling Gerrit features. [02:40:22] ? [02:41:45] Well first of all the merge commit message editing. I suppose not disable. But that's a critical feature that wouldn't be available. [02:41:57] Not in GitHub at least. [02:42:20] DanielFriesen: I think that can be fixed. [02:42:56] DanielFriesen: Other people can't push new 'code' but can edit contents of PRs [02:43:27] I can think of two ways of handling GitHub in Gareth. [02:45:59] A) On review sets disable making comments and set it up to mirror GitHub comments (with some extra style to draw attention to that fact). [02:46:12] 03(mod) Enter 2 times, Backspace 2 times : not deleted - 10https://bugzilla.wikimedia.org/48284 +comment (10nicolas.raoul) [02:47:30] DanielFriesen: that sounds bad, we should always have 2 way comments [02:48:16] 03(mod) Enter 2 times, Up, Delete : pawned - 10https://bugzilla.wikimedia.org/48285 +comment (10nicolas.raoul) [02:49:13] DanielFriesen: how far out is Gareth? [02:49:26] Far of course ;) [02:49:59] I don't think it would ever actually finish without something like a MediaWiki Development Chapter to support it's creation. [02:50:24] yeah, sigh [02:51:07] B) Whenever someone adds a pull request to GitHub create a review set on Gareth and close the GitHub PR with a "This pull request has been moved to a Gaerth review branch". Support GitHub auth as a method of login so GitHub users can trivially get into the interface their PR was moved to. [02:51:34] hmm, I like B) [02:51:38] provided there is auth [02:51:40] properly [02:51:45] and the interface isn't Gerrit-bad [02:51:55] Oh, nice, ok. [02:52:07] ;) I thought I was going to have to come up with a C) [02:53:13] DanielFriesen: :) [02:53:26] DanielFriesen: however, I suppose code pushes might still be useful [02:53:47] DanielFriesen: since otherwise people will have to setup completely new SSH / Infrastructure locally [02:53:49] for it to work [02:53:54] legoktm: thanks for the PR :D [02:53:55] YuviPanda: I don't expect an interface worse than GitHub... ;) heck I'm trying to out-do GitHub..... I started implementing flipping syntax highlighted diffs! [02:54:03] :D [02:54:05] nice! [02:54:13] I *Just* realized that GH doesn't have them [02:54:13] wah [02:54:31] YuviPanda: Oh no, actually that's the beauty of Gareth. [02:55:33] YuviPanda: Remember that Gareth fundamentally works on the standard git model of public repos for each user and pull requests which used to be done by email, etc... [02:56:01] DanielFriesen: hmm, so how does that work for people collaborating on the same patch? [02:56:07] I never figured how that works with Email PRs [02:56:46] YuviPanda: In other words... ;) Gareth will work from the start supporting their GitHub fork as a remote. [02:57:02] right. so code pushes won't be an issue that needs to be bot solved [02:57:02] nice [02:57:57] In fact the bot (or rather plugin) should probably be smart enough to auto-create the remote for the user. [02:58:24] Unfortunately it would probably be too invasive to make the small tweak to GitHub. [02:58:55] ie: They'll still have to add the webhook manually to take advantage of the most user friendly features. [02:59:09] Oauth + API should take care of it [02:59:15] especially if Gareth supports GH login [02:59:25] GitHub's API is complete and very adorable [03:00:04] Maybe... but I fear that the permissions necessary to modify a user's webhooks for a repo may be too invasive. [03:00:27] Asking for that kind of permission when someone logs in could scare some people off. [03:02:12] DanielFriesen: hmm, true [03:02:24] well, a bridge to cross when we get to it :) [03:02:40] 03(mod) PATH on webservers is just "/bin" for tools - 10https://bugzilla.wikimedia.org/48722 +comment (10tim) [03:04:02] DanielFriesen: do you know of any wrappers for the Gerrit API? [03:04:06] or i might have to write one now [03:04:14] no [03:04:21] I don't really touch Gerrit [03:04:27] :P [03:10:20] YuviPanda: I don't even see WebHook controls in GitHub's API... I only see subscription stuff that requires polling. [03:10:36] DanielFriesen: http://developer.github.com/v3/repos/hooks/ [03:12:43] 03(mod) PATH on webservers is just "/bin" for tools - 10https://bugzilla.wikimedia.org/48722 +comment (10gerritadmin) [03:12:45] 03(mod) $HOME isn't set on webservers, causes jsub to try /$JOBNAME.out as output file - 10https://bugzilla.wikimedia.org/48726 +comment (10gerritadmin) [03:14:27] YuviPanda: ^_^ Screw WebHooks... [03:14:38] ? [03:16:28] YuviPanda: They're great for supporting anyone and for manual config. But GitHub supports PubSubHubbub. We can just write some GitHub support to automatically go and register one of those subscriptions when a GitHub remote is added. [03:16:50] ah [03:16:51] yes [03:17:11] hmm that's going to scale much better [03:17:13] than webhoks [03:17:14] *hooks [03:18:02] As for how email collab works. [03:20:23] Classically you'd push stuff to a branch in your public repo. Then submit a pull request to a maintainer over email. They'd pull from there. If someone else wanted to contribute they'd pull from you, make a commit, then push it to their public repo. And send another email telling you and the maintainer to pull from them. [03:20:34] As for Gareth. [03:20:47] yeah, so that exact model works for GH as well. [03:20:53] hierarchical pull requests, so as sto say [03:32:37] After Gareth has fetched your remote you submit your review branch in the UI (well maybe... ;) there's still the fact I hope to add some magic that'll allow Gareth to magically -- based on your personal conventions for how you push commits to your public repo -- to automagically create review branches for you without manual work each time). Gareth holds this commit information in custom refs in the actual repo (like Gerrit does but maybe a litt [03:32:45] YuviPanda: ^ [03:33:08] it got cut off at 'maybe a litt' [03:33:42] Damnit I thought I fixed that. [03:34:03] ...(like Gerrit does but maybe a little cleaner). When someone else wants to contribute they'll pull from that ref in Gareth creating a local tracking branch. Make a commit, then push it to their public repo. Gareth will either automatically catch on by a webhook or pubsubhubub and do a fetch or they can tell it to fetch themselves. After fetching that commit can be added to the review branch manually ( ;) though more likely Gareth will automag [03:34:32] ... ( ;) though more likely Gareth will automagically catch on and add it for you). [03:34:34] so the review branch is on the 'canonical' repo [03:34:52] Sure, makes things easier. [03:35:55] DanielFriesen: hmm, right [03:35:58] Fun fact... fundamentally Gareth doesn't need any ssh or write support ;) [03:36:02] well, I hope it all gets implemented someday! [03:36:13] DanielFriesen: well, it just needs some form of git transport, I think? [03:36:27] Sure... ;) read-only http(s) [03:37:20] I may eventually add a little ssh. [03:37:55] hmm, do they have to host their own public repos? [03:39:10] Sure... but that can be anywhere. GitHub, Gitorious, private server, ;) you could even install something right along side Gareth and let people use that. [03:40:05] Though I may add optional hosting of personal clones in the future with ssh push. [03:40:28] Originally I had no intent to do that. [03:41:07] But after some though I decided I might need to do that to support secure private repos like a few that WMF uses. [03:41:44] yeah, I think that'll make things easier [03:42:37] YuviPanda: You might like my idea for the 'final' way of creating projects/repos inside Gareth. [03:46:09] YuviPanda: http://dpaste.org/ius2k/ [03:47:00] Repositories and branches are created using review sets ;) [03:47:33] hmm, nice! [03:47:40] but... feautiritis! [03:47:59] So anyone can make a request for them in-system and all someone needs to do is press accept. [03:48:19] This actually came out of a personal use case. [03:49:14] Our repo request process was a mess and slowed down getting new extensions in. [03:49:42] yeah, it hoepfully can be automated at some point [03:51:48] With this all you need to do is push your ext to a public remote. Create a review branch using the new project button. Do that using your public repository and attaching all the commits you've made to the review set. Then when someone hits a single accept button the final repo is created with all your commits inside. [03:52:48] And since you've got a public repo you don't need to hold back at all on development. [04:05:04] Hi. [04:11:15] YuviPanda: :D [04:11:24] hey Susan [04:11:27] hey legoktm :) [04:11:32] how goes GSoC? [04:11:41] they havent announced who got accepted yet [04:11:57] did you apply for anything else other than that? [04:12:15] stupidly, nope [04:12:28] ah [04:12:36] heavy contentionf or that one [04:15:18] legoktm: I should move that repo itself to Gerrit [04:15:29] legoktm: so that we can do PRs for that and have them come into Gerrit :D [04:15:43] lolololol [04:25:13] YuviPanda: would be nice if you package it so it can go on pypi and stuff [04:25:27] legoktm: the sync? why exactly? [04:25:37] legoktm: it's not really going to be useful for anyone other than us [04:25:52] other people use gerrit right? [04:26:08] they do?! :P [04:26:28] legoktm: pull request! :P [04:26:39] legoktm: oooh, also, have I told you about this idea for a 'Wiki Now'? :D [04:26:59] Similar to Google Now? [04:27:23] Susan: so idea is, you set a bunch of 'interests' and get notified of things that match it [04:27:36] Like SuggestBot? [04:27:40] yes [04:27:43] but not really [04:27:46] Right. [04:27:50] because this is aimed more at readers [04:27:52] and not at editors [04:28:03] and the plan is to implement this as an Android app wtih Push notifications [04:28:10] and a Google Glass thing [04:28:20] https://www.mediawiki.org/w/index.php?title=User%3AYuvipanda%2FGlass_apps&diff=693696&oldid=693583 [04:28:26] Susan: it's like suggestbot for non-editors [04:28:42] legoktm: mmm, that's nice! [04:28:53] legoktm: now that I think about it, Huggle on a phone / tablet would also be very nice [04:29:11] Susan: we could perhaps convert such users into editors at some point :) [04:29:18] Huggle on any console would be nice! [04:29:18] this is just something I'm playing around with, of course. [04:29:25] I would love to huggle with my Wiimote. [04:29:36] legoktm: i've never used Huggle :( [04:29:37] no windows [04:29:42] Kinect Huggle! [04:29:44] Swipe left to revert+warn, right to block [04:29:45] LOL [04:29:56] STiki is very similar [04:29:57] 'drop kick to block' [04:30:01] :P [04:30:13] 'smile like a psycho to warn' [04:30:31] 'kick in the balls to report to AN/I' [04:30:36] man that'll be hilarious :P [04:31:01] Susan: do you have any interest at all in the GitHub -> Gerrit stuff that's goin on? [04:33:14] In the sense that I might skim an e-mail about it. [04:33:18] But no real interest. [04:33:38] hmm, alright [04:34:34] 03(mod) Add JavaScript variable for whether user can edit the page - 10https://bugzilla.wikimedia.org/43790 +comment (10Matthew Flaschen) [04:50:24] Krinkle|detached: i responded to your issue :) [04:52:08] YuviPanda: Interesting work (GitHub-> Gerrit ) [04:52:22] Rtdwivedi: :D It helps people getting started a lot [04:52:30] and also helps attract contributors from other oss communities [04:52:34] everyone has GH already setup [04:53:10] True. [04:54:52] What's the idea? [04:55:11] Susan: open a pull request in GitHub, Gerrit patchset gets automatically created [04:55:17] Susan: Updated Pull Request, Patchset updated [04:55:21] (all automatic) [04:55:33] i'll work on two way comment sync next [04:55:45] mediawiki.org/wiki/User:Yuvipanda/G2G [04:56:07] Hmmm. [04:56:25] wouldn't it be better just to push to gerrit in the first place? [04:56:33] Susan: it's currently enabled for a bunch of repos where the owners had previously expressed interest [04:56:42] Susan: MobileFrontend, all of E3, and the browsertests [04:56:43] *push people [04:56:50] Comment duplication feels very... [04:57:11] YuviPanda: https://thomashaas.com/pages/collection-viennoiserie.php <- hyper-addictive. I'll buy you a dozen. [04:57:37] p858snake|l: removing barriers to having people contribute is always good [04:58:00] Not always. [04:58:09] But I agree that it'd be nice to integrate better with GitHub. [04:58:11] Or Bitbucket. [04:58:12] Or wherever. [04:58:19] Comment duplication feels... weird, though. [04:58:31] It feels like: edit conflict. [04:58:51] Susan: why? It's more like 'sync' than duplication.... [04:58:55] Amgine: that timed out [04:59:11] YuviPanda: I can understand why you'd want to do it. It just feels painfully inefficient. [04:59:18] alternatives? [04:59:23] YuviPanda: Are you planning to implement actual logging? [04:59:42] legoktm: i should. and make logs available over tools-labs http [04:59:49] legoktm: want to take a shot at it? :D or should I? [05:00:06] I'll take a look tomorrow, should be rather simple [05:00:16] legoktm: there's also a PHP script involved [05:00:18] that's not in the repo [05:00:20] i'll add it now [05:00:23] oh? :/ [05:00:26] legoktm: but it's super simple [05:00:33] legoktm: it just receives the pull request payload from GitHub [05:00:38] legoktm: and starts the job for sync.py [05:00:44] legoktm: it's like, 4 lines of code [05:00:44] YuviPanda: think decadent croiscent wrapped around super-fine dark chocolate. https://thomashaas.com/files/photos/Choc-Croissant-980x379.jpg [05:00:45] Oh is that your web hook? [05:00:50] legoktm: yup yup [05:00:56] p858snake|l: removing barriers to having people contribute is always good why not use a python one? [05:00:58] legoktm: so i need logging for that too [05:01:15] legoktm: didn't want to fight with tools-labs and python web [05:01:28] heh [05:01:30] :( [05:02:39] p858snake|l: once the entire workflow is implemented, I don't see it as too much of an obstacle [05:02:58] p858snake|l: you can comment on either thing, and (mostly?) push code to either thing [05:03:35] YuviPanda: in the future when more features are added to gerrit (revision tags seems to be a major one) [05:03:46] p858snake|l: besides, that's why I have been enabling it only for people who ask [05:04:03] Amgine: hmm, I might like that [05:04:13] Amgine: unsure how pastry deals with chocolate [05:04:25] Delightfully. [05:04:36] should try it next time! [05:04:55] p858snake|l: no reason to keep out the large community of people who are used to GitHub [05:05:04] it's an entry gateway, that is all. [05:06:13] p858snake|l: count(people-on-GH) > count(people-on-Gerrit) [05:06:31] plus... some of us prefer GitHub :) [05:06:47] (the mobile apps are primarily on GitHub so far, for example. Will move to Gerrit eventually) [05:06:53] 03(mod) Make brackets in section edit links accessible to CSS - 10https://bugzilla.wikimedia.org/48256 +comment (10liangent) [05:07:48] legoktm: have you done python web scripts in tools-labs? [05:07:55] yes [05:07:58] i think so [05:08:10] yes* [05:08:12] i have [05:08:42] legoktm: mmm, help me port the php script? :D [05:09:01] once you upload it :D [05:11:55] legoktm: done [05:12:28] er, where did you post it? [05:12:34] legoktm: push failed, rebasing noow [05:12:35] moment [05:12:39] loool [05:12:49] i merged your PR, didn't pull [05:12:51] pushed [05:14:01] oh thats simple [05:14:09] what does error_log() do? [05:14:18] legoktm: logs to ~/php_error.log [05:14:23] needs to be replaced by 'proper' logging :) [05:17:45] hm ok [05:19:49] 03(mod) Filter group from Special:LanguageStats when group is not a priority language - 10https://bugzilla.wikimedia.org/47879 +comment (10Santhosh Thottingal) [05:20:26] YuviPanda: $payload = json_decode( $_POST[ 'payload' ], true ); <-- what does the true do? [05:20:37] legoktm: return it as an array instead of as an 'standard object' [05:20:39] php is stupid [05:20:42] lol [05:20:50] associative array, rather [05:25:50] hm ok [05:26:07] think i got it [05:26:32] legoktm: can I add you to the project on tools labs? [05:26:46] sure [05:26:52] err, how do I do that? :D [05:27:22] https://wikitech.wikimedia.org/wiki/Special:NovaProject [05:27:28] Add user to service group [05:28:13] legoktm: done! [05:28:16] :D [05:29:04] https://github.com/yuvipanda/SuchABot/pull/3 [05:33:48] YuviPanda: that might need a bit of hacking, the script I wrote which calls qsub from python required modifying the environment since CGI's environment is different [05:34:02] mmm, right [05:34:25] can't we isolate and create our own? [05:35:00] legoktm: also, we can test this out :D Can you deploy this on tools labs and give me the URL? I can enable pushes to this for one of the repos [05:35:06] and then we can test by making stupid silly pull requests [05:35:14] http://dpaste.de/ILDKk/raw/ thats what i set up for legobot [05:35:29] and, sure :P [05:35:38] ah! [05:36:05] legoktm: also can you modify the perms on the CONFIG file to make it not be readable by anyone other than the user? :D [05:37:06] YuviPanda: er, whats the name of the project on tools again? [05:37:12] suchaserver [05:38:34] where is the config file stored? [05:41:51] legoktm: ~/.suchaconfig [05:41:57] no let me take care of it [05:41:58] * YuviPanda logs in [05:44:39] YuviPanda: the endpoint is http://tools.wmflabs.org/suchaserver/cgi-bin/receiver.py [05:45:28] legoktm: send pull requests to wikimedia/qa-browsertests [05:45:32] should trigger that url [05:45:41] live edit until it works ;) [05:45:47] <-- lazy [05:45:59] what? legoktm is lazy? [05:46:00] waaat [05:46:01] noo! [05:46:07] hmm, also permission issues now [05:46:08] hmm [05:48:39] oh? [05:48:58] I can't change ownership / group of files under the project [05:49:05] or permissions [05:49:05] weird [05:49:15] well unless theyre the local-user they cant access it i think. [05:49:33] YuviPanda: who /isn't/ lazy? [05:49:38] Jasper_Deng: legoktm! [05:49:45] wrong [05:50:04] -rw-r--r-- 1 yuvipanda svn 62 Apr 13 23:32 .suchabot.yaml [05:50:05] legoktm: ^ [05:50:12]