Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hacksessions organising checklist #20

Open
6 tasks
crangelsmith opened this issue Jan 10, 2024 · 1 comment
Open
6 tasks

Hacksessions organising checklist #20

crangelsmith opened this issue Jan 10, 2024 · 1 comment

Comments

@crangelsmith
Copy link

crangelsmith commented Jan 10, 2024

Overview

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.

Organisers should copy/paste the checklist below

  • 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 the cipher meeting room calendar not the meeting invite as sometime it says accepted but isn't).
  • 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
@crangelsmith crangelsmith converted this from a draft issue Jan 10, 2024
@crangelsmith crangelsmith changed the title Hack session organising checklist Hacksessions organising checklist Jan 10, 2024
@mhauru mhauru moved this from New, uncategorised to Standing in hut23-open-source-sa Feb 21, 2024
@mhauru mhauru added the private Issues that might need to be Turing-only or REG-only visible label Apr 17, 2024
@mhauru mhauru removed the private Issues that might need to be Turing-only or REG-only visible label Apr 30, 2024
@mhauru
Copy link
Collaborator

mhauru commented Jun 5, 2024

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

EDIT: Irrelevant, see OP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Standing
Development

No branches or pull requests

2 participants