-
Notifications
You must be signed in to change notification settings - Fork 2
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
Post-workshop action items #189
Comments
Some attendees raised the question of staying in touch after the workshop. The current roundup mail does not include any info about our slack group. Should we mention that already? |
the feedback form needs to be updated before we can send out the roundup email to attendees / the thank you email to coaches @lislis do you know how to do update this? |
oh, it's part of the list anyway.. haha :D sorry |
@lislis I'm undecided on this one -- I'd like to keep the slack group as a place for people who continue to engage with the community / learners group (also remotely), but not as a catch-all for past attendees. Mentioning the slack group without an invite seems strange too. What do you think? |
I think if attendees have a way of talking to each other and the thing that connects them is Clojure/ ClojureBridge that's a good incentive to engage with the community. Wdyt? We can setup an invite thing on heroku similar to the web audio slack https://web-audio-slackin.herokuapp.com/ and paste the link into the email. |
@JohannaCarola the feedback form is in the google drive. Steps to update are:
That should be all. π€ |
@vsmart OK, thank you! Will try it tomorrow evening! π |
I sent the sponsors thank you email. |
I sent the attendee roundup email! :) |
@lislis that sounds good to me |
Sent out the goodies email β |
Coaches thank you sent! πͺ |
I also sent a quick speakers thank you. |
Let's take a moment to celebrate an amazing workshop we put on last weekend. π β¨
Now, there are some remaining action items:
Let's aim to wrap these up in the next 2 weeks so we can leave this workshop behind us and get some well-deserved rest ποΈ π€
The text was updated successfully, but these errors were encountered: