SummitChanges

Differences between revisions 4 and 5
Revision 4 as of 2010-02-04 00:48:03
Size: 1416
Editor: unassigned
Comment:
Revision 5 as of 2010-02-04 00:55:43
Size: 2077
Editor: unassigned
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * 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.
 * Schedule session button:
   * Allow a scheduler to schedule a session on the fly without having to register a blueprint so people can schedule on-the-fly BoFs.
   * [[attachment:summitbutton.png|Mockup]]
 * 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 [[http://people.csail.mit.edu/rahimi/marcus-bains-line/|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.
Line 23: Line 36:
 * Archive old UDS schedules.

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

  • Schedule session button:
    • Allow a scheduler to schedule a session on the fly without having to register a blueprint so people can schedule on-the-fly BoFs.

    • Mockup

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

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.
  • Archive old UDS schedules.

Next Steps

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