GTFO Core: Difference between revisions
Jump to navigation
Jump to search
Filled in from lead role description form |
→Schedule: more from form |
||
| Line 15: | Line 15: | ||
=== Schedule === | === Schedule === | ||
Prior to event: ad-hoc meetings with cluster leads, reach out to volunteers to assess. | |||
Closer to event: approve early access hill access requests and print parking passes. | |||
During event: show up for Extra-Early Arrival, and perform traffic control onsite. Then same for exodus traffic. | |||
=== Experience === | === Experience === | ||
Latest revision as of 18:52, 16 February 2026
GTFO Lead Responsibilities
- Prior to early arrival, approve vehicles (based on ground clearance) for early arrival.
- Print out vehicle access passes. We have templates and mail merge processes for this, it just needs do-ing, and can be delegated.
- Onsite, perform the role of "Air Traffic Controller" during early arrival and exodus - basically, communicating with each of our loading zones to assess inbound and outbound traffic, and release them in an orderly fashion so as not to cause traffic jams.
- Resolve traffic issues.
This seems difficult and tedious but it's really not! If you enjoy the idea of controlling a massive multiplayer game involving actual vehicles, real danger, and logistics like optimizing traffic flow, it's a good bit of fun and you can really make a difference helping the event run smoothly.
Who makes a good GTFO Lead?
Location
Schedule
Prior to event: ad-hoc meetings with cluster leads, reach out to volunteers to assess.
Closer to event: approve early access hill access requests and print parking passes.
During event: show up for Extra-Early Arrival, and perform traffic control onsite. Then same for exodus traffic.
Experience
Should be familiar with the land.