{"action":"opened","issue":{"url":"https://api.github.com/repos/computationclub/computationclub.github.io/issues/105","repository_url":"https://api.github.com/repos/computationclub/computationclub.github.io","labels_url":"https://api.github.com/repos/computationclub/computationclub.github.io/issues/105/labels{/name}","comments_url":"https://api.github.com/repos/computationclub/computationclub.github.io/issues/105/comments","events_url":"https://api.github.com/repos/computationclub/computationclub.github.io/issues/105/events","html_url":"https://github.com/computationclub/computationclub.github.io/issues/105","id":325470009,"number":105,"title":"Organise next meeting","user":{"login":"mudge","id":287,"avatar_url":"https://avatars0.githubusercontent.com/u/287?v=4","gravatar_id":"","url":"https://api.github.com/users/mudge","html_url":"https://github.com/mudge","followers_url":"https://api.github.com/users/mudge/followers","following_url":"https://api.github.com/users/mudge/following{/other_user}","gists_url":"https://api.github.com/users/mudge/gists{/gist_id}","starred_url":"https://api.github.com/users/mudge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mudge/subscriptions","organizations_url":"https://api.github.com/users/mudge/orgs","repos_url":"https://api.github.com/users/mudge/repos","events_url":"https://api.github.com/users/mudge/events{/privacy}","received_events_url":"https://api.github.com/users/mudge/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-22T21:28:50Z","updated_at":"2018-05-22T21:28:50Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"### As soon as you're assigned\r\n\r\n- [ ] Assign yourself this issue! (If you're not a member of [London Computation Club](https://github.com/computationclub) on GitHub, ask someone on Slack to add you.)\r\n- [ ] Make sure you have access to the [Buffer](http://buffer.com) account for the club - this is how you'll tweet. (Ask on #general in Slack and someone will DM you the credentials.)\r\n- [ ] Make sure you can commit to the Computation Club website repository (Ask on #general in Slack and an administrator will add you to the organisation.)\r\n\r\n### The day after you're assigned\r\n\r\n- [ ] Remove the previous meeting’s chapter from Slack (if scanned; you may need a Slack admin user to do this)\r\n- [ ] Encourage a write up of the previous meeting in Slack\r\n- [ ] Add a link to the previous meeting’s write up to the: \r\n  * [ ] [wiki homepage](https://github.com/computationclub/computationclub.github.io/wiki/Home/_edit)\r\n  * [ ] [wiki sidebar](https://github.com/computationclub/computationclub.github.io/wiki/_Sidebar/_edit)\r\n  * [ ] [meetings.yml file](https://github.com/computationclub/computationclub.github.io/edit/master/_data/meetings.yml)\r\n- [ ] Announce the write-up!\r\n  * [ ] Slack\r\n  * [ ] The mailing list\r\n  * [ ] Twitter\r\n\r\n### Same day / A few days later (but not too long!)\r\n\r\n- [ ] Double check with Leo that Geckoboard is able to host on the planned date; if not:\r\n  * [ ] Make a Doodle poll with potential dates\r\n  * [ ] Announce the poll on Slack\r\n  * [ ] Announce the poll on the mailing list\r\n  * [ ] Announce the poll on Twitter\r\n  * [ ] Pick a date\r\n- [ ] Identify the next chapter(s) to read for the next meeting (or any reading material for a non-book meeting)\r\n- [ ] Create an online event using an appropriate service that allows us to measure attendance.  We prefer to add it to [Attending.io](https://attending.io) as Lanyrd is too unreliable. Add information about how to access the venue (e.g. entering through HelloFresh).\r\n- [ ] Announce the meeting!\r\n  * [ ] Slack\r\n  * [ ] The [mailing list](https://groups.google.com/forum/#!forum/london-computation-club)\r\n  * [ ] Twitter\r\n- [ ] Add the next meeting to the Computation Club website by [editing the meetings.yml file](https://github.com/computationclub/computationclub.github.io/edit/master/_data/meetings.yml). Make sure your YAML is well-formatted - don't leave any colons in titles, for example!\r\n- [ ] Try to get a copy of the chapter scanned and put it on Slack as a single .pdf file ([Office Lens](https://itunes.apple.com/gb/app/office-lens/id975925059?mt=8) app might be useful to \"scan\" chapters with your phone)\r\n\r\n### A day or two before the meeting\r\n\r\n- [ ] Remind people about the next meeting\r\n  * [ ] Slack\r\n  * [ ] The [mailing list](https://groups.google.com/forum/#!forum/london-computation-club)\r\n  * [ ] Twitter\r\n- [ ] Find a volunteer to open and close the meeting using our [standard opening](https://github.com/computationclub/computationclub.github.io/wiki/Starting-a-meeting) and [closing remarks](https://github.com/computationclub/computationclub.github.io/wiki/Running-a-retrospective)\r\n- [ ] Find a volunteer to share the chapter during the meeting via AirPlay\r\n- [ ] Find a volunteer for REPL exercises via AirPlay\r\n- [ ] [Update the meeting checklist template](https://github.com/computationclub/computationclub.github.io/edit/master/.github/issue_template.md) based on your experiences using it. Maybe we've missed something, or the timings need to be improved?\r\n- [ ] Open a new issue with the above template, called \"Organise next meeting\".\r\n\r\n### At the meeting\r\n\r\n- [ ] Pick an organizer for the next meeting\r\n\r\n### Finally\r\n\r\n- [ ] Mark this issue as done! Excellently executed!\r\n"}}
{"actor":{"display_login":"mudge"}}