SummitChanges

Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2010-02-04 00:16:35
Size: 598
Editor: unassigned
Comment:
Revision 4 as of 2010-02-04 00:48:03
Size: 1416
Editor: unassigned
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
Development / Deployment: === Feature Requests ===
Line 15: Line 15:
 * ISD have limited capacity and limitations around release.  * A button in the sidebar, "Schedule a session" which will allow a scheduler to schedule a session on the fly without having to register a blueprint. [[attachment:summitbutton.png|Mockup]]
 * A field for "crew" and "videographer" so we can use the system to schedule crew with the conflict resolution.
 * Design review - Input from the design team as Mark has ideas on what he wants the schedule to look like design-wise
 * "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 [[http://people.csail.mit.edu/rahimi/marcus-bains-line/|Marcus Baines Line]] would be great.
Line 17: Line 20:
=== Benefits === === Bugs we need fixed ===

 * 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.

Summit System Assessment

Current System Assessment

Problems

Functionality:

  • Conflicts with multiple people scheduling - seven people scheduling can cause conflicts.
  • Blueprints should not be used to schedule sessions - blueprints are for specs not sessions, and don't apply to roundtables and private sessions.
  • BoFs can't have attendee subscribers - adding BoFs and roundtables cannot use the collision system for attendees.

Feature Requests

  • A button in the sidebar, "Schedule a session" which will allow a scheduler to schedule a session on the fly without having to register a blueprint. Mockup

  • A field for "crew" and "videographer" so we can use the system to schedule crew with the conflict resolution.
  • Design review - Input from the design team as Mark has ideas on what he wants the schedule to look like design-wise
  • "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.

Bugs we need fixed

  • 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.

Next Steps

SummitChanges (last edited 2010-02-11 06:31:37 by c-67-164-44-209)