{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/build/issues/489","repository_url":"https://api.github.com/repos/nodejs/build","labels_url":"https://api.github.com/repos/nodejs/build/issues/489/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/build/issues/489/comments","events_url":"https://api.github.com/repos/nodejs/build/issues/489/events","html_url":"https://github.com/nodejs/build/issues/489","id":175613976,"number":489,"title":"build group membership reminder!","user":{"login":"jbergstroem","id":176984,"avatar_url":"https://avatars.githubusercontent.com/u/176984?v=3","gravatar_id":"","url":"https://api.github.com/users/jbergstroem","html_url":"https://github.com/jbergstroem","followers_url":"https://api.github.com/users/jbergstroem/followers","following_url":"https://api.github.com/users/jbergstroem/following{/other_user}","gists_url":"https://api.github.com/users/jbergstroem/gists{/gist_id}","starred_url":"https://api.github.com/users/jbergstroem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbergstroem/subscriptions","organizations_url":"https://api.github.com/users/jbergstroem/orgs","repos_url":"https://api.github.com/users/jbergstroem/repos","events_url":"https://api.github.com/users/jbergstroem/events{/privacy}","received_events_url":"https://api.github.com/users/jbergstroem/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2016-09-07T21:43:38Z","updated_at":"2016-09-20T15:34:09Z","closed_at":null,"body":"Hi, build group. I thought it could be nice to revisit the membership list every now and then; especially seeing how we get \"default\" trust in the Node.js infrastructure as well as **access to stuff**. Take a moment and think about the last six months, what you've contributed or worked on; the meetings you've attended and then consider the coming six. If you're still keen and want to be an active member – a comment in this issue would be the perfect start.\r\n\r\n/cc: @jbergstroem, @geek, @ghostbar, @joaocgreis, @kenperkins, @mhdawson, @orangemocha, @othiym23, @phillipj, @rmg, @rvagg, @Starefossen, @TheAlphaNerd "},"comment":{"url":"https://api.github.com/repos/nodejs/build/issues/comments/248338821","html_url":"https://github.com/nodejs/build/issues/489#issuecomment-248338821","issue_url":"https://api.github.com/repos/nodejs/build/issues/489","id":248338821,"user":{"login":"jbergstroem","id":176984,"avatar_url":"https://avatars.githubusercontent.com/u/176984?v=3","gravatar_id":"","url":"https://api.github.com/users/jbergstroem","html_url":"https://github.com/jbergstroem","followers_url":"https://api.github.com/users/jbergstroem/followers","following_url":"https://api.github.com/users/jbergstroem/following{/other_user}","gists_url":"https://api.github.com/users/jbergstroem/gists{/gist_id}","starred_url":"https://api.github.com/users/jbergstroem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbergstroem/subscriptions","organizations_url":"https://api.github.com/users/jbergstroem/orgs","repos_url":"https://api.github.com/users/jbergstroem/repos","events_url":"https://api.github.com/users/jbergstroem/events{/privacy}","received_events_url":"https://api.github.com/users/jbergstroem/received_events","type":"User","site_admin":false},"created_at":"2016-09-20T15:34:09Z","updated_at":"2016-09-20T15:34:09Z","body":"So, summing up -- here's the replies from our current team:\r\n\r\nRemaining:\r\n - @jbergstroem\r\n - @TheAlphaNerd \r\n - @joaocgreis \r\n - @Starefossen \r\n - @phillipj \r\n - @geek \r\n - @mhdawson \r\n - @rvagg\r\n\r\nLeaving: \r\n - @orangemocha\r\n - @rmg \r\n - @ghostbar \r\n \r\nNo reply (implied leave):\r\n - @kenperkins \r\n - @othiym23 \r\n \r\nI'll keep this open for another few days giving people not having replied yet a chance to do so.\r\n\r\nTo those who are leaving: thank you for both your efforts and deciding to step down. You're obviously welcome back at any time should you find the time to help out! One of the main reasons I wanted to get this initiative going is to make sure we actively maintain and protect our infrastructure, including secrets. I will be re-rolling our shared test keys in as a result of closing this issue seeing how we haven't done so in almost a year.\r\n\r\nFinally, one thing I had in mind was perhaps creating a document that outlines responsibilities/areas of interest -- @Trott recently mentioned that he'd like to know how to generally ping if host $x goes down or host $y are experiencing problems. A list that for instance mentions pinging @mhdawson or @jbergstroem should ppc hosts  have issues would benefit all collaborators and likely improve the feedback when things go bad. I'll create another issue about this if people think its a good idea.\r\n\r\nAlso, feedback on this procedure is also greatly appreciated! "}}
{"actor":{"display_login":"jbergstroem"}}