Cluster:Participation

From MCH2022 wiki
Revision as of 14:43, 30 May 2022 by Stitch (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Cluster:Participation
Name Participation

Roles In Cluster

  • Define the Code of Conduct
  • Mediate in case of breaches of the Code of Conduct
  • Around-the-clock first responder in cases where the social cohesion of the event is threatened
  • Advise crew (including security) on how to handle socially delicate situations
  • Provide a safe space for all people at the camp (orga and visitors)
  • Get people in need of (mental or social) support the proper support, e.g. on-site doctor
  • Identify cases where the social cohesion of the orga could use improvement and act or advise on it
  • To make MCH2022 an awesome experience for the next generation of hackers, and their nerdy parents:
    • Work with rest of orga to make families an integral part of the event
    • Coordinate child friendly activities and content
    • Organize Family Zone
    • (Possibly) arrange for professional child care
  • Gather all information that visitors (are expected to) need
  • Share the information in a structured form on the wiki
  • Write summaries for the booklet
  • Check wiki edits by other teams to ensure consistency with official information
  • Create a physical information center called info desk
  • Answer questions from visitors via digital communication (e.g. email)
  • Answer questions from visitors at the info desk
  • Direct people toward other visitor oriented sources of information (e.g. Press, Volunteers, Villages, NOC help-desk) if those are more appropriate.
  • Inquire internally with other teams if an answer cannot be found
  • Proactively provide visitors/community with relevant information, e.g. via blog, Twitter, or info sheets posted on site, to reduce the number of questions
  • Help villages (self-organized sub-events and/or people camping together) establish their presence
  • Write instructions for villages on how and where to send special requests (e.g. Power, NOC, On-Site), and how to integrate their village with the main event
  • Coordinate/plan which village goes where
  • Seek out villages with incomplete or vague wiki pages and encourage them to add more concrete information
  • Check whether villages adhere to imposed restrictions
  • Publish village locations on the map once this stabilizes
  • Preempt possible nuisance issues (e.g. loud music) and communicate and design accordingly
  • Be infodesk-like, but for village-specific needs.
  • Coordinate/plan needed resources and interfaces
  • Recruit volunteers
  • Optimize on-boarding experience
  • Match volunteers to tasks and shifts:
  1. Provide teams that have things that need doing with people to do it
  2. Provide people with spare time with things to do
  3. Try to optimize fun and efficiency by directing people towards tasks that fit their skills
  • Schedule volunteers and inform volunteers about what’s expected from them
  • Provide basic life necessities to volunteers that help out for more than just a few hours, e.g. food and drinks.
  • Express gratitude towards volunteers, e.g. by awarding goodies (t-shirts) and good food
  • Manage volunteers on site from early build-up to late tear-down
  • Schedule volunteer assignments according to priorities indicated by build-up, tear-down, and PL
  • Help teams structure their volunteer shifts
  • Keep a pool of volunteers available for unplanned ad-hoc tasks.