codeformilwaukee / codeformilwaukee/hack-night-planning
Log Attendance & improve communications from Hack Nights
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
**update**
We are still interested in: "2. keep in touch with interested community members."
It would be good to keep in touch with what projects people are working on
---
**original**
We'd like to
1. track attendance
2. keep in touch with interested community members.
### potential strategy
1. One-question google poll to grab email from every attendee
2. Short google poll to ask “what did you work on” “did it go well” “other feedback” after a hack night
- open it up in the last 30 mins of hack night
- be sure to share it out during closing remarks
- Take all email addresses that haven’t responded and prompt them with an email within 24-48 hours linking to that survey
3. Get info on new members
- For all new email addresses that we don’t recognize, ask for name / pronouns / basic information in short follow-up google poll
### long-term strategies
We can also think about in-depth longitudinal surveys once we nail down the basics.
[ edit ] - we are moving this last part to #15
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.