The idea is to select broad topic areas early, and then let microconf owners determine actual content when we're much closer to the conference date. This gives organizers enough info to request paper submissions and potential attendees to determine if they want to come, but still will let the miniconf be about current issues in September, not our guesses in January.
We're relying on getting a person from each topic area – the microconf owner – to determine the actual course of discussion, so it's also very important that we find the right 10 people for that role.
| Microconf Topic | Runner |
|---|---|
| The future of Linux storage | Matthew Wilcox |
| Video input infrastructure and V4L2 | Mauro Carvalho Chehab |
| Power management and tools for efficient resource usage | Matthew Garrett |
| Future displays and input devices | Keith Packard |
| Desktop Integration | David Zeuthen |
| Linux server management | Darrick Wong |
| Boot and init | Dave Jones |
| Moving to modern APIs 2: Audio | Lennart Poettering |
| Moving to modern APIs 3: Kernel/userspace interfaces | Greg Kroah-Hartman |
| Debugging, tuning, tracing, and profiling | Steven Rostedt |
What are significant problems that need work in Linux today?
Already solved?