Summit development plans from UDS-O

Registered by Chris Johnston on 2011-07-14

Discussion and planning for Summit during the O cycle

Whiteboard

Work items:
[jorge] Talk to track leads about experience with summit website: DONE
[jorge] Make sure access to the admin is restricted as much as is practical: DONE
[chrisjohnston] Etherpad timeslider link: DONE
[chrisjohnston] Create official LP Bug tags for uds-p and linaro: DONE
[nigelbabu] Talk to IS to list about linking to recordings of sessions: POSTPONED
[nigelbabu] Pull blueprint data using the LP API, not screen scraping: DONE
[nigelbabu] Talk to Jorge and Jono about removing brainstorm: DONE
[summit-hackers] figure out a way to import data locally for testing: POSTPONED
[summit-hackers] Clean up render.py: POSTPONED
[summit-hackers] JSON export of data to be used for local testing: DONE
[summit-hackers] Add more content/direct links on the front page: POSTPONED
[summit-hackers] Create a mutable item to where meetings in the past are muted: POSTPONED
[summit-hackers] Making user roles for different users providing different levels of access: POSTPONED
[summit-hackers] Fix scheduling conflict resolution and notification: DONE
[jorge] Restrict scheduling permissions to admins only after the summit start date: DONE
[summit-hackers] Allow people to define their own Busy times, check them for scheduling conflicts: POSTPONED
[summit-hackers] on blueprints set the session summary page as the wiki page: POSTPONED
[mhall119] Create new series and production branches: DONE

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.