We gather every month on zoom with meetups organised using slack and email. To get the zoom meeting details you’ll need to join the slack workspace at uk-acm-sigsce.slack.com* by emailing Duncan Hull or Steven Bradley.
Meeting details are pinned in the
#general channel but not listed publicly to minimise the risk of hijacking by zoombombers, so please don’t share them publicly.
Once you’ve joined us on slack, please feel welcome to post to the
#paper-suggestions channel in the workspace for papers you’d like us to discuss in the future.
On email: as well as being posted to
@everyone on slack every month, notifications of our meetings are also emailed to two mailing lists:
- 🇬🇧 The UK uki-sigcse.acm.org mailing list, which you can subscribe to by emailing email@example.com with the text
subscribe uki-sigcse-members yourfirstname yoursecondnamein the body of your message
- 🌍 The worldwide sigcse.org members mailing list, which you can subscribe to by emailing firstname.lastname@example.org with the text
subscribe sigcse-members yourfirstname yoursecondnamein the body of your message
If you’d like to join the Canterbury subgroup, contact Janet Carter or Sally Fincher and for the Glasgow subgroup contact Quintin Cutts. We look forward to seeing you, wherever you go. You might also be interested in…
Joining the ACM.org
You don’t have to be a member of our parent organisation the Association for Computing Machinery (ACM) but you might like to consider joining it if you’re not already a member, see acm.org/membership/join. Membership has many worthwhile benefits. The ACM is a large global community that aims to advance computing as as science and a profession, see video below on Why I Belong to ACM:
Join the Raspberry Pi Foundation seminars
The Raspberry Pi Foundation runs a free monthly series of seminars on Computing Education Research, see raspberrypi.org/computing-education-research-online-seminars for details.
SIGCSE or SIGSCE?
Congratulations on spotting the typo (SIGSCE which should be SIGCSE) in our URL. Unfortunately, the typo is baked into the slack workspace URL now, so it’s not worth changing. Thanks to everyone who pointed out our mitsake.