The "summit system" we use for the Ubuntu Developer Summit needs to be fixed.
The summit system is showing it's age, as we increase the number of sessions, tracks, and people who schedule things it gets slower and more cumbersome to use.
- Matt is a track lead and runs into Joe in the hallway. Joe wants a session to be added to the schedule but doesn't need a blueprint. This is impossible to schedule.
- Amber has been tagged as a volunteer videographer for UDS but doesn't know how it matches her schedule. The summit system automatically tags and shows her which sessions she needs to videotape.
These fixes are for UDS-M, anything after is out of scope.
A specification should be built with the following considerations:
- The person implementing it may not be the person writing it. It should be clear enough for someone to be able to read it and have a clear path towards implementing it. If it doesn't, it needs more detail.
- That the use cases covered in the specification should be practical situations, not contrived issues.
- Limitations and issues discovered during the creation of a specification should be clearly pointed out so that they can be dealt with explicitly.
- If you don't know enough to be able to competently write a spec, you should either get help or research the problem further. Avoid spending time making up a solution: base yourself on your peers' opinions and prior work.
- Specifications should be written in clear, concise and correct English. If you're not a native speaker, co-editing the spec with somebody who is might be a good idea.
Specific issues related to particular sections are described further below.
- Schedule session button:
Allow a scheduler to schedule a session on the fly without having to register a blueprint so people can schedule BoFs quickly.
Clicking on the button will spawn a lightbox with 2 fields, title and description for the session and an ok/cancel button. Mockup 2
- Clicking on ok will accept the session and then add it to the sidebar, where the scheduler can schedule it.
- Clicking cancel will take the user back to the normal view.
- When the session is on the sidebar it can be dragged into a time slot.
- A field for "crew" and "videographer"
- So we can use the system to schedule crew with the conflict resolution.
- The role is then integrated into the person's personal view so it's on their schedule.
- Design review
- Input from the design team as Mark has ideas on what he wants the schedule to look like design-wise
- Needs to look as professional as our main website, since partners and upstreams come to UDS.
- "Big screen friendly"
When on display at UDS we need to have a clock on the schedule that won't scroll off so people can see where we are in the schedule. A Marcus Baines Line would be great.
- Ensure the page elements show up even on scroll, list of rooms, time slots, etc.
- iCal Support
- Needed so we can have the IRC bot announce sessions in the channel
- So people can use their phones for the schedule.
- Auto-generate the time slots.
- We run a SQL query to generate blank slots to drop sessions in, this is annoying, and making them by hand is time consuming.
- Performance review - ISD added memcached support which improved the performance considerably. We need to find a way to generate the schedule without hammering launchpad over and over.
- Archive old UDS schedules.