Add code jam activity #34
Conversation
| Participants will vote at the start of the event on which prompt they would like to solve, but all participants should follow the same prompt. Some potential prompts include (details to come): | ||
|
|
||
| - Build a sandwich factory | ||
| - Emoji Recomremender 😄 |
There was a problem hiding this comment.
I assume that's supposed to be "recommender"?
There was a problem hiding this comment.
It was actually spelled that way on purpose to highlight the light-hearted nature of the event.
There was a problem hiding this comment.
Oh, alright, fun. My brain just died trying to read it thinking it was supposed to be a real word lol.
| - Place like 10 more ideas here | ||
| # Mentor Duties | ||
|
|
||
| Mentors should be present and floating around the event. Mentors should help participants form teams, decide what they want to do, and provide inspiration tailored to the specific skills of each participant as needed. Mentors should introduce participants to relevant technologies they might find useful and accessible based on their background and what they want to accomplish. Some ideas for potential solutions should be pre-prepared and suggested to struggling groups as needed. |
There was a problem hiding this comment.
Should there be an optional workshop (or workshops) on some technology (or technologies) we think might be useful? It would be good for new/prospective members without any experience, and could make the event more welcoming to less confident students. It would also probably help decrease the workload for mentors.
If you remember what Wes posted a while back, the "coding workshop" brought in a more diverse selection of participants. Maybe we could try implementing that here?
There was a problem hiding this comment.
So I actually am going to send you guys a long message that is tangential to this in slack soon
|
Just stopping in to say this is really cool! We had an awesome code jam last year and it's great to see it formalized so nicely!! Great job Richie (and reviewers/contributors)! |
|
@Bad-Science Anything preventing us from merging this in? Like to do any housekeeping in |
5 participants
This activity was created as part of the Mozilla Campus Clubs program. We aim to test it during the first week of classes. In short, it is designed to reach out to new members and facilitate internal community development. See the README for details.
There is also a user-facing slide deck (reveal.js). This desk is designed to be shown by the event organizers at the start of the event. The slide deck will be updated to reflect any changes suggested in the README. To view and suggest changes to the slides, visit https://slides.com/richieyoung/rcos-code-jam and make a comment.
In general, we should start documenting successful activities and make a better habit of documenting process to prevent knowledge gaps and share what we do with other open source communities.