You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in the group: emailconfirmed.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

Team Info[edit]

First line contact(s):
	'This field uses autocomplete.'
Description: Our first task is to get the village registration up and running. However, many conditions are still to be clarified (e.g. rules about cooking within a village, etc.). All necessary info relevant for villages must be gathered, and provided to villages in advance, making sure villages will be able to comply with potential rules. Shortly before the event, villages will have to be placed on the map, depending on their needs, and camp requirements. On the event itself, the arriving villages must be coordinated. The same applies to teardown.
Is an exclusive team:
	Team members in an exclusive team only have responsibilities to this team, and cannot be involved in other teams.
Contact:
	The mailing list of the team (like "Villages@lists.MCH2022.org")
IRC:
	The IRC channel the team uses ("MCH2022-Villages" becomes #MCH2022-Villages)
This team is required for the event: Meaning: without the deliverables of this team the event can not continue. For example: team:power is a requirement for lectures, recording, sanitation and so on. Counter example: a badge is a great add on to the event, but even if it fails, the event can continue safely. Crucial teams contribute to safety, essential services, hygiene, health.
Status: Team has contact information: Meaning: a new volunteer or the existing network of volunteers can easily contact this team and ask questions or status information.
Status: Team has informative wiki page: Meaning: the wiki page of the team details a bit of their plans, how they do it and what they provide to others. It contains who the team members are. This is a treasure trove for next events, as well as a way to streamline information to other teams.
Status: Team has meetings are planned until the event: Meaning: the team is in control and regular meetings / gatherings to check progress, todo's, questions and whatever is relevant to the team. Meetings do not always need to be formal or documented in order to set this checkmark of course.
Status: Team has enough orga-volunteers to function: Meaning: there are enough dedicated people on the team that everyone on the team can enjoy at least two days at the camp without doing anything for this team. The stress level is relatively low because work is shared among team members. Angels are excluded in this metric: note that angels often need training, which also takes time which must be allocated. Examples of what this being unchecked can mean: people are not exclusive to this team and thus cannot guarantee time before and during the event, there are tons of plans but no actual work is planned, performed or managed, people are out of reach, there is no backup for crucial team roles, there is no time allocated to instruct and guide angels. There is no tracking of progress.
Status: Team has drafted a budget: Meaning: there is a table of expected expenses and projected income. This consists of listing of items, with their price. This does not need to be public, but team:finance must know. If there is no budget, the finance team / board will try to determine one: better to be in control yourself, so allocate, estimate and write it down.
Status: Team has informed team:volunteers: Meaning: if there are any angel requirements, or orga-volunteers needed, team:volunteers is aware of their numbers and needed capabilities. Yes you can search yourself, and you can also get more searching capacity if these numbers and skills are shared.
Contact at projectleiding:
Backup Contact at projectleiding:

Team Members[edit]

Add another Member

Free text[edit]

!! Important for Villages !! FAQ and most recent information: [[Villages-FAQ]]. = Roles = From the [[Roles]] page: {{:Role:Villages}} =ToDo lists= This is our ToDo list in which you can track the actions and their status. {| class="wikitable" |+ Team Villages ToDo list |- ! Action !! Description !! Status |- | Define Angels / shifts || Bike angels needed to guide people for build-up on the terrain. Detailed description as in mail. || Confirmation to be received (W) - Mail sent. Update expected early june. |- | Define Food || Angels work better when they are not hungry. The number of meals depends on the number of assigned Angels. || Confirmation to be received (W) - Mail sent. Update expected early june. |- | Order bikes || Bike Angels will ride to hell and back but do need bikes for the build-up and tear down as they lead the way on the terrain and we also need bikes for the team to coordinate. || Confirmation to be received (W) - Mail sent. Update expected early june. |- | Order walky-talky || Instead of shouting up and down the field at the top of our lungs all day, walkie-talkies would be more than welcome. || Confirmed, spreadsheet up to date. |- | Order phones || POC: done, team DECT call is via VILL (8455) || Confirmed, 2 DECT phones ordered |- | Finish planning || Straighten the timelines on the wiki, and fine-tune and finalize the pages. || Done. Timelines and pages on the wiki are fine-tuned and straightened. |- | Finish role description || Finalize the page Roles and it's linked role page for villages || Done. Role:Village : ok; Role:Village rental services belongs to Team:Moebelhaus (K) |- | Check clusters in Wiki || Cluster function in wiki is not working as aspected || Done (W) - Repaired! See: https://wiki.mch2022.org/Clusters |- | Write blog post || Show what is going on. || Done (K) https://pad.hackalot.nl/villages-ad |} =Open Questions= Much to do, we still have. * Interfaces: ** Traffic control/gatekeeping: responsibility? Night shifts covered? : awaiting feedback orga / team:terrain ** "on-site logistic" of people + stuff from parking - responsibility? ** Dish washers - responsibility? ** Distribution of rented stuff - whom to contact? * Organizational questions ** Amount of vehicles allowed onsite per area: awaiting feedback orga / team:terrain ** Materials needed for marking areas on the field, routes, etc. * Clarfied: ** Noisy area will be on Lamarr field =Timeline= === Planning activities === This is our Timeline in which you can track the actions and their status. {| class="wikitable" |+ Team Villages Timeline |- ! Action !! Status !! Description |- | Village registration || CLOSED || Villages can register - new registrations are not considered after 4.07.2022. Please contact us via mail, if you have not registerd in time. |- | Review registrations and special needs || Done. || We can run reports and contact villages if there is reason to do so. |- | Set "preferred location" on village page - deadline 30.6. || CLOSED || No guarantee that the village will be placed at this spot, but we will do our best. |- | 1st of July: place villages || Done. || The ease and quality of arranging the villages strongly depend on the quality and completeness of the information from the village registration form as provided by the villages. |- | Finalize handout, passing permits (print) || Done || Color coding |- | day -2: check field, routes, etc. for village guidance || Done || make sure all village places are accessible |- | Buildup / teardown timeline || Done, some points to be clarified. || See below. |} === Capacity Planning === This is our Capacity Planning in which you can track the planned capacity as of Q2 2022 and communicated to Team:Volunteers. {| class="wikitable" |+ Team Villages Capacity Planning |- ! Day !! Date !! Weekday !! Crew !! (Bike) Angels !! Food (Crew) !! Food (Angels) !! Radios (Crew only) !! DECT |- | -7 || 14-07-2022 || Thu || 0 || 0 || 0 || 0 || 0 || 0 |- | -6 || 15-07-2022 || Fri || 0 || 0 || 0 || 0 || 0 || 0 |- | -5 || 16-07-2022 || Sat || 0 || 0 || 0 || 0 || 0 || 0 |- | -4 || 17-07-2022 || Sun || 0 || 0 || 0 || 0 || 0 || 0 |- | -3 || 18-07-2022 || Mon || 3 to 5 || 0 || 3 to 5 || 0 || 5 || 2 |- | -2 || 19-07-2022 || Tue || 3 to 5 || 0 || 3 to 5 || 0 || 5 || 2 |- | -1 || 20-07-2022 || Wed || 3 to 5 || 8 to 12 angels per shift (ca. 5 shifts à 2 hours) || 3 to 5 || 8 to 12 angels per shift || 5 || 2 |- | 0 || 21-07-2022 || Thu || 3 to 5 || 8 to 12 angels per shift (ca. 8 shifts à 2 hours) || 3 to 5 || 8 to 12 angels per shift || 5 || 2 |- | 1 || 22-07-2022 || Fri || 3 to 5 || 0 || 3 to 5 || 0 || 5 || 2 |- | 2 || 23-07-2022 || Sat || 3 to 5 || 0 || 3 to 5 || 0 || 0 || 2 |- | 3 || 24-07-2022 || Sun || 3 to 5 || 0 || 3 to 5 || 0 || 0 || 2 |- | 4 || 25-07-2022 || Mon || 3 to 5 || 0 || 3 to 5 || 0 || 0 || 2 |- | 5 || 26-07-2022 || Tue || 3 to 5 || 8 to 12 angels per shift (ca. 2 shifts à 2 hours) || 3 to 5 || 8 to 12 angels per shift || 5 || 2 |- | 6 || 27-07-2022 || Wed || 3 to 5 || 8 to 12 angels per shift (ca. 4 shifts à 2 hours) || 3 to 5 || 8 to 12 angels per shift || 5 || 2 |- | 7 || 28-07-2022 || Thu || 3 to 5 || 0 || 3 to 5 || 0 || 5 || 2 |- | 8 || 29-07-2022 || Fri || 0 || 0 || 0 || 0 || 0 || 0 |}

Summary:

This is a minor edit

Watch this page

Cancel

Edit Team: Team:Villages

Team Info[edit]

Team Members[edit]

Free text[edit]

Navigation menu

Search