Participants: chiroptical, jappiejappie
Putting together some initial ideas for the Hackathon
Notes:
- Primary goal should be learning something new
- With the new "Stage" channels we can probably just use Discord. This is on-brand because I imagine some of us will work on Discord bots
- Keep the scope small for the first incarnation, no reason to bite off more than we can chew
- Choose the cross section of "Streaming Tools" AND "Functional Programming" will keep the scope small
- That being said, I think it is fine if projects don't fall in this category
- People
- volunteers: friends who can direct people to chat/voice channels
- mentors: friends who want to be team leads, they should submit project descriptions and rate their projects on a beginner friendly to advanced scale
- offer github issues at various levels for your project and then people can claim them
- could help prevent people who wander in from taking a lot of time to set up/onboard on your project
- presenters (?): maybe we have a few talks on getting started with FP or Streaming
- participants/viewers: friends who want to help others on their projects
- Can we continue to use the "Elm Code of Conduct" for the Hackathon?
- Each project should have a Discord "Category" with appropriate text/voice channels
- We should have a "Help" category for people to find various announcements and ask questions
- For mentors/presenters we should ask them to submit abstracts early so we can choose some
- how do we rate them?
- should we prefer beginner friendly projects to advance ones?
- should we have some thresholds for projects:participants? i.e. if 100 people come, N projects would be appropriate
- Should we seek funds? What would do with funds if we had them?
- What are the participant limits for our Discord currently?
Goals for next meeting
- Set a date
- Build some basic marketing materials
- Build some forms in google for mentors/presenters