Difference between revisions of "Teams"
| Line 17: | Line 17: | ||
* See how many team members your team _must_ have and for what, and how many would be nice to have (and for what). | * See how many team members your team _must_ have and for what, and how many would be nice to have (and for what). | ||
* Speak to other, related teams (see orga picture) on a regular basis, so you know what is happening. | * Speak to other, related teams (see orga picture) on a regular basis, so you know what is happening. | ||
| + | |||
| + | == Teams == | ||
| + | {{TeamList}} | ||
| + | {{Purge}} | ||
| + | |||
== Organization chart (clusters, roles) == | == Organization chart (clusters, roles) == | ||
Revision as of 16:27, 27 March 2020
Welcome!
This page is part of the organization of MCH2022. Feel free to look around and please note that information on pages such as the Main Page or Q&A is kept more up to date.
MCH2022 is a "DIY" hacker event, organized by volunteers and everyone who visits. If you want to help prepare the event, please join the orga by participating in a team. If you want to help at the event, please participate as an angel.
Teams are the backbone of MCH2022, which are made out of volunteers that have or want to gain expertise in a certain field. Their decisions power the event from location to management, from IT to ticket sales to the tap-water installation on the terrain.
It is possible, and you are welcomed, to join any of the team mailinglists and meetings. Please introduce yourself on the list or at meetings :)
To create a team, use the form: Form:Team
To create a project use the form: Form:Project
Team expectations
For a team to embed themselves in the orga, but also be reachable for new team members, please make sure the following is listed on the team page:
- Who is/are the first point of contact (not necessarily the team lead), make sure this person or persons have contact information shared.
- Add role information in your team description from the roles page.
- Plan _all_ meetings up to the event itself and share them on your page. This will save you massive amounts of time with agenda syncing, datumprikkers, planners every time. Would one meeting per month work? Make it clear how somebody can join that meeting.
- Make it clear for new people how to join the team. The orga and visitor wiki are now one, which should make it easier for new people to join your team.
- See how many team members your team _must_ have and for what, and how many would be nice to have (and for what).
- Speak to other, related teams (see orga picture) on a regular basis, so you know what is happening.
Teams
Teams
Projects
Organization chart (clusters, roles)
This is a view of the SHA organizations split into roles. We're trying to adopt this idea, it's new.
For the role description please visit the following: https://wiki.ifcat.org/Roles