{"action":"created","issue":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/302","labels_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/302/labels{/name}","comments_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/302/comments","events_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/302/events","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/302","id":73060391,"number":302,"title":"TRIUMF computers","user":{"login":"r3dunlop","id":5428160,"avatar_url":"https://avatars.githubusercontent.com/u/5428160?v=3","gravatar_id":"","url":"https://api.github.com/users/r3dunlop","html_url":"https://github.com/r3dunlop","followers_url":"https://api.github.com/users/r3dunlop/followers","following_url":"https://api.github.com/users/r3dunlop/following{/other_user}","gists_url":"https://api.github.com/users/r3dunlop/gists{/gist_id}","starred_url":"https://api.github.com/users/r3dunlop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/r3dunlop/subscriptions","organizations_url":"https://api.github.com/users/r3dunlop/orgs","repos_url":"https://api.github.com/users/r3dunlop/repos","events_url":"https://api.github.com/users/r3dunlop/events{/privacy}","received_events_url":"https://api.github.com/users/r3dunlop/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-05-04T16:05:22Z","updated_at":"2015-05-19T21:23:11Z","closed_at":null,"body":"Now that we have moved the code, we have to make a decision how to treat the TRIUMF shared computers. The issue is that we have to set remote URL's (the accounts to be able to push to), while not opening up write access to everyone. As far as I can tell, there are three ways to get around this. \r\n**Method 1**: We create a Griffin github user who is part of the development team in the collaboration. \r\nEasy setup, easy to use. However, this user can push, but we somehow have to keep the password to this account within the development team or else there isn't a point in the first place\r\n\r\n**Method 2**: We put instructions up on the wiki showing everyone who wants to use those computers how to add their own url's and their own ssh keys to that computer. It isn't *that* difficult to do these things and it makes it so anyone can develop in this location.\r\n\r\n**Method 3**: The shared TRIUMF computer accounts are pull only accounts. This is the easiest method, but also means we can't just hop onto those computers during an experiment to modify code quickly (and still push it to the repo). This might be a good thing because the most mistakes we have made on this code have been developing on those accounts to get something to work quickly...\r\n"},"comment":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/comments/103670485","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/302#issuecomment-103670485","issue_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/302","id":103670485,"user":{"login":"r3dunlop","id":5428160,"avatar_url":"https://avatars.githubusercontent.com/u/5428160?v=3","gravatar_id":"","url":"https://api.github.com/users/r3dunlop","html_url":"https://github.com/r3dunlop","followers_url":"https://api.github.com/users/r3dunlop/followers","following_url":"https://api.github.com/users/r3dunlop/following{/other_user}","gists_url":"https://api.github.com/users/r3dunlop/gists{/gist_id}","starred_url":"https://api.github.com/users/r3dunlop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/r3dunlop/subscriptions","organizations_url":"https://api.github.com/users/r3dunlop/orgs","repos_url":"https://api.github.com/users/r3dunlop/repos","events_url":"https://api.github.com/users/r3dunlop/events{/privacy}","received_events_url":"https://api.github.com/users/r3dunlop/received_events","type":"User","site_admin":false},"created_at":"2015-05-19T21:23:11Z","updated_at":"2015-05-19T21:23:11Z","body":"Not a whole lot, that person is just in charge of password protection. I think to be safe we should NOT give this account write permissions to the main repo. I think if we can create pull requests with it it should be enough. I’m just afraid of us getting lax with the password, and having someone accidentally do something malicious to our base code.\n\n\n\n> On May 19, 2015, at 5:19 PM, SmithJK <notifications@github.com> wrote:\n> \n> To start off with, everyone who is on this thread.\n> What does running this account entail?\n> —\n> Reply to this email directly or view it on GitHub <https://github.com/GRIFFINCollaboration/GRSISort/issues/302#issuecomment-103669781>.\n> \n\n"}}