Meeting checklist

• Remove the proposal for the previous meeting from the Call for Proposals. CFPs that were previously proposed but have not been run yet should be left in the list
• Remove the previous meeting’s chapter from Slack (if scanned)
• Encourage a write up of the previous meeting
• Kick off a call for proposals giving people a day or so to make suggestions (announce on Slack, mailing list and Twitter. You’ll need access to the club’s buffer account for the latter - ask in Slack for help )
• Ensure someone is available to shepherd the topic at the next meeting (at least reading the chapter or some supplementary material)
• Kick off a vote for proposals on Slack and announce it (on Slack, mailing list and Twitter)
• Add the next meeting to the series on Lanyrd
• Ask Tom Stuart to claim the newly created meeting so that he can set a custom URL
• Double check that someone (Leo or Dan) at Geckoboard is able to host on the planned date and making other arrangements if need be
• Close vote and announce results (on Slack, mailing list and Twitter) by end of Friday following the previous meeting, so that whoever is leading the discussion has two weekends to prepare
• Add the next meeting to the Computation Club website
• Try to get a copy of the chapter scanned and put on Slack
• Remind people about the next meeting (on Slack, mailing list and Twitter) a day or two in advance