Hacksessions organising checklist

[crangelsmith]

REG runs monthly sessions where we come together and contribute to upstream open-source repositories. The sessions take place 2-5 pm every third Friday of the month. The organisation of these sessions are done in the #hut23-hacksession-organising slack channel, a public channel #open-source-hacksessions is available for announcements and running the session.

Zoom link can be found in the calendar event.

On the first Monday of the month, a reminder will be sent to #hut23-hacksession-organising asking for a volunteer organiser. We should have a rotation to share the work.

Organisation checklist:

• [ ] Create a new issue with the date of the hack session and copy this checklist. This issue will document the full session. Assing issue to the person organising that month.
• [ ] Check Turing meeting room is booked (should be Cipher).
• [ ] Advertise the session (or check the workflow has sent messages to the following channels):
  • [ ] REG slack channels
  • [ ] General
  • [ ] #open-source-hacksessions
  • [ ] Any other channel of interest
• [ ] Send reminders to Slack channels the week of the event (or check the workflow has done this).
• [ ] Run the event
• [ ] Collect contributions to the session in the issue relevant to the session.
• [ ] Update the main page with new contributions https://github.com/alan-turing-institute/research-engineering-group/wiki/Open-source-hacksessions

---

Template email/slackchannel:

Hello [placeholder],

REG runs monthly sessions where we come together and contribute to upstream > open-source repositories. The idea is to fence off time dedicated to contributing > upstream and to do it together for joy and sociality. We hope to give back to >many of the tools we use and learn about new packages by helping them out. >Everyone is welcome to come and work on something they want to contribute to >or join an effort someone else has already started.

The next session is happening on [placeholder date] and you are all invited. We >start at 2 pm [placeholder room] and hybrid [add Zoom link] ). Come by and contribute to your >favourite open-source project or team up with someone else! We'll discuss what >everyone is working on in #open-source-hacksessions.

You can see the outcome of previous hack sessions in here.

We will be there all Friday afternoon, join us for some or all of it.

---

[mhauru]

New checklist now that we have Slack automation:

• [ ] Create a new issue with the date of the hack session and copy this checklist. This issue will document the full session. Assing issue to the person organising that month.
• [ ] Check Turing meeting room is booked (should be Cipher).
• [ ] Check that the Slack workflow for advertising is doing its thing (reminders should go out a week before and the day of)
• [ ] Run the event
• [ ] Collect contributions to the session in the issue relevant to the session.
• [ ] Update the main page with new contributions https://github.com/alan-turing-institute/research-engineering-group/wiki/Open-source-hacksessions