Akademy/Structure

The following is a proposal for a structure of the Akademy team that can produce a world-class event. This structure is informed by years of experience in organizing large conferences, including experiences from past Akademy events that we want to learn from.

In general, the goals driving this are:

We come off as "professional"; attendees (who often aren't yet full community members) see that we have our shit together and want to make the next step into contributing to KDE
Defined areas of responsibility to prevent a situation where volunteers are running around trying to figure out who knows what (who can help with the network? who can announce program changes to attendees? what happens to the cash from t-shirts?)
If we promise something (eg, hybrid BoFs, good quality streams, showing slides in the streams, working network, t-shirts) we can actually deliver.

Roles and Groups

Event Producer - "The Buck Stops Here". The producer of Akademy generally has the final say in decisions about the event.
Track Captains
- Track 1 Captain
  - Session Chair
- Track 2 Captain
  - Session Chair
Program Committee
Volunteer Coordinator
Sponsor Liason
Facilities Support