SummitChanges
Differences between revisions 11 and 21 (spanning 10 versions)
|
Size: 4041
Comment:
|
← Revision 21 as of 2010-02-11 06:31:37 ⇥
Size: 4438
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| * '''Launchpad Entry''': UbuntuSpec:foo * '''Created''': <<Date(2005-10-25T15:45:54Z)>> * '''Contributors''': * '''Packages affected''': * '''See also''': SpecTemplate |
* '''Launchpad Entry''': N/A * '''Created''': <<Date(2010-02-10>> * '''Contributors''': Jono Bacon, Jorge Castro * '''Packages affected''': N/A |
| Line 9: | Line 8: |
| The "summit system" we use for the Ubuntu Developer Summit needs to be fixed. | The "summit system" is what we use for the Ubuntu Developer Summit. In the previous iteration of UDS we faced some problems with the system that need to be resolved. Summit is hosted at [[https://edge.launchpad.net/summit|lp:summit]] |
| Line 13: | Line 12: |
| 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. | 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. We would like to assign a developer to do some performance testing and add some small features for the next UDS. |
| Line 19: | Line 18: |
| * David has been good about scheduling his sessions but as the new needs pile up he "cheats" and adds the session right into the Django admin interface since that's much easier than adding a blueprint and waiting for the system to import it into the session view. As a result he can't take advantage of the conflict resolution bits. * Jono wants to ensure that people are mingling inbetween sessions, he wants assurances from the system that no 2 tracks are ever scheduled back to back in the same room. |
|
| Line 26: | Line 27: |
| A specification should be built with the following considerations: | In order of importance: |
| Line 28: | Line 29: |
| * 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. | ==== Performance Work ==== |
| Line 30: | Line 31: |
| * That the use cases covered in the specification should be practical situations, not contrived issues. | ''HIGH'' |
| Line 32: | Line 33: |
| * Limitations and issues discovered during the creation of a specification should be clearly pointed out so that they can be dealt with explicitly. | * Performance review - ISD added memcached support which improved the performance considerably. We need to perform a code review of the rendering and scheduling code to ensure it is working more efficiently. |
| Line 34: | Line 35: |
| * 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. | ==== Additional Data To Be Captured ==== |
| Line 36: | Line 37: |
| * 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. | ''HIGH'' |
| Line 38: | Line 39: |
| Specific issues related to particular sections are described further below. | * A field for "crew" and "videographer" * In the "Meeting" table there is a subtable that is called "Key People". * In addition to Drafter, Assignee, Approver, and Scribe, add a "Videographer1" and "Videographer2" field. * Use the system to schedule crew with the conflict resolution facility. * Ability to tag an attendees record as "Crew" and then designate a day that they will be assigned crew duties. In the day view there should be a field on the calendar that shows who is going to be crew for that day so attendees know who the person is. Each role is then integrated into the person's personal view so it's on their schedule. (The "Hide talks that aren't for me" feature) ==== Design Review ==== ''HIGH'' ''Requires Design Team Input''. * Bring summit.ubuntu.com up to speed with the branding and design of our other web properties. Mark has input on what he would like to see here. ==== Schedule Session Button ==== ''MEDIUM'' ''Requires Design Team Input''. * 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. [[attachment:summitbutton2.png|Mockup]] * 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. ==== In Session Display Time ==== ''LOW'' ''Requires Design Team Input''. * 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. 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 * Also useful for other calendaring facilities for attendees and for use in Lernid. ==== Admin Facilities ==== ''LOW'' * 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 46: | Line 90: |
| == Outstanding Issues == * 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. * [[attachment:summitbutton.png|Mockup]] * Clicking on the button will spawn a lightbox with 2 fields, title and description for the session and an ok/cancel button. [[attachment:summitbutton2.png|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 [[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. * 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. |
Currently assessing resourcing opportunities. |
Launchpad Entry: N/A
Created: <<Date(2010-02-10>>
Contributors: Jono Bacon, Jorge Castro
Packages affected: N/A
Summary
The "summit system" is what we use for the Ubuntu Developer Summit. In the previous iteration of UDS we faced some problems with the system that need to be resolved. Summit is hosted at lp:summit
Rationale
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. We would like to assign a developer to do some performance testing and add some small features for the next UDS.
Use Cases
- 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.
- David has been good about scheduling his sessions but as the new needs pile up he "cheats" and adds the session right into the Django admin interface since that's much easier than adding a blueprint and waiting for the system to import it into the session view. As a result he can't take advantage of the conflict resolution bits.
- Jono wants to ensure that people are mingling inbetween sessions, he wants assurances from the system that no 2 tracks are ever scheduled back to back in the same room.
Scope
These fixes are for UDS-M, anything after is out of scope.
Design
In order of importance:
Performance Work
HIGH
- Performance review - ISD added memcached support which improved the performance considerably. We need to perform a code review of the rendering and scheduling code to ensure it is working more efficiently.
Additional Data To Be Captured
HIGH
- A field for "crew" and "videographer"
- In the "Meeting" table there is a subtable that is called "Key People".
- In addition to Drafter, Assignee, Approver, and Scribe, add a "Videographer1" and "Videographer2" field.
- Use the system to schedule crew with the conflict resolution facility.
- Ability to tag an attendees record as "Crew" and then designate a day that they will be assigned crew duties. In the day view there should be a field on the calendar that shows who is going to be crew for that day so attendees know who the person is. Each role is then integrated into the person's personal view so it's on their schedule. (The "Hide talks that aren't for me" feature)
- In the "Meeting" table there is a subtable that is called "Key People".
Design Review
HIGH
Requires Design Team Input.
- Bring summit.ubuntu.com up to speed with the branding and design of our other web properties. Mark has input on what he would like to see here.
Schedule Session Button
MEDIUM
Requires Design Team Input.
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
- 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.
In Session Display Time
LOW
Requires Design Team Input.
- 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. 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
- Also useful for other calendaring facilities for attendees and for use in Lernid.
Admin Facilities
LOW
- 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.
Implementation Plan
TBD
Implementation
Currently assessing resourcing opportunities.
SummitChanges (last edited 2010-02-11 06:31:37 by c-67-164-44-209)