What will tracks be like?
Tracks are a good way for conference attendees to plan their sessions, by choosing which topics they most relate to, and also to invite people to submit their talks related to others with a similar topic.
At the time when talks are being submitted, some people expect tracks to be pre-defined, and available for categorizing their submissions. On the other hand, some people think of tracks as sub-conferences, where a person (the track coordinator) is in charge of a series of adjacent timeslots, and takes care of getting talks to fill the time they have, prepare the schedule of the track itself, and even rank the proposals and do talk selection in case they get more proposals than time.
Tracks can either take a half day (3 or 4 timeslots), or a full day (7 timeslots), in a single lecture room.
We prefer to let attendees self-organize tracks (see below on how to propose a track), but the content team might also create tracks as they organically appear amongst accepted talks; feel free to volunteer as the coordinator for an orphan track!
 Tracks for DC18
|Cloud and containers
|Packaging, policy and infrastructure
|Systems administration, automation and orchestation
 Proposing a track
- Track proposals are done by adding your track and your name(s) as coordinator to the table above
- Send a mail to firstname.lastname@example.org to ensure we pay attention to your track as early as possible!
- Track coordinators are expected to
- coordinate the track during the conference itself: be a moderators, help flow from session to session, join as talkmeisters...
- help select talks during the submission process; the content team will still review, rank and approve individual talks, regardless of tracks (and might not initially attach selected talks to tracks), but you can/should tell us what your ideal lineup would be, as you are probably an expert on the track's topic
- suggest us already submitted talks to add to your track