Organise next meeting

[tuzz]

As soon as you're assigned

• [x] Assign yourself this issue!
• [x] Make sure you have access to the Buffer account for the club - this is how you'll tweet. (Ask on #general in Slack and someone will DM you the credentials.)
• [x] Make sure you can commit to the computation club website repository

  A few hours after the meeting

• [x] Edit the Call for Proposals page to remove the proposal for the previous meeting. CFPs that were previously proposed but have not been run yet should be left in the list. (This step may get deleted depending on how we decide to run future votes.)
• [x] Remove the previous meeting’s proposal from the #votes Slack channel
• [x] Remove the previous meeting’s chapter from Slack (if scanned; you may need a Slack admin user to do this)

  The next day

• [x] Encourage a write up of the previous meeting in Slack
• [x] Add a link to the previous meeting’s write up to the:
  • [x] wiki homepage
  • [x] wiki sidebar
  • [x] meetings.yml file
  • [x] the books chapter listing, currently NTO
• [x] Remind people to propose any new topics or comment on existing ones if they’re interested, giving people a day or so to make suggestions
  • [x] Slack
  • [x] The mailing list
  • [x] Twitter

    Same day / A few days later (but not too long!)

[note: voting/proposals is now an ongoing process, so the separation should only be necessary if there's a real lack of stuff available to vote on]

• [x] Remind people to add/update their votes for proposals on Slack and announce it on
  • [x] Slack
  • [x] The mailing list
  • [x] Twitter
• [x] Double check that someone (Leo or Dan) at Geckoboard is able to host on the planned date and making other arrangements if need be

  A few days after that...

• [x] Find the most popular proposal and pick it as the winner
• [x] Add the next meeting to the series on Lanyrd (currently we meet fortnightly on a Tuesday 6.30-8.30pm)
• [x] Ask Tom Stuart to claim the newly created meeting so that he can set a custom URL. You don't need to wait for this to use the default URL though — it will redirect automatically
• [x] announce results!
  • [x] Slack
  • [x] The mailing list
  • [x] Twitter
• [x] Ensure someone is available to shepherd the topic at the next meeting (at least reading the chapter or some supplementary material)
• [x] Add the next meeting to the Computation Club website by editing the meetings.yml file. Make sure your YAML is well-formatted - don't leave any colons in titles, for example!
• [x] Try to get a copy of the chapter scanned and put on Slack

  A day or two before the meeting

• [x] Remind people about the next meeting
  • [x] Slack
  • [x] The mailing list
  • [x] Twitter
• [x] Update the meeting checklist template based on your experiences using it. Maybe we've missed something, or the timings need to be improved?
• [x] Copy the source of meeting checklist template to a new issue, called "Organise next meeting".

  At the meeting

• [x] Tell the shepherd that they need to select and assign someone to manage the checking in the new issue you created.

  Finally

• [x] Mark this issue as done! Excellently executed!

[Ryman]

@tuzz / @tomstuart mind assigning this to me /giving compclub membership?