Merge lp:~summit-hackers/summit/user-manual into lp:summit

[Chris Johnston]

Begins adding docs on using summit

[Michael Hall (mhall119)]

I'm not really concerned with code reviews for documentation, if you want to just land this kind of thing yourself that'd be okay by me.

review: Approve

=== modified file 'docs/index.rst'
--- docs/index.rst	2012-01-23 01:18:55 +0000
+++ docs/index.rst	2012-02-29 13:38:17 +0000
@@ -11,6 +11,10 @@
 .. toctree::
    :numbered:
    
+   using
+   scheduling
+   lead
+   scheduler
    installing
    credits
 

=== added file 'docs/lead.rst'
--- docs/lead.rst	1970-01-01 00:00:00 +0000
+++ docs/lead.rst	2012-02-29 13:38:17 +0000
@@ -0,0 +1,18 @@
+==================
+Track Lead Permissions
+==================
+
+**Managing Meeting Proposals**
+
+The track leads are responsible for accepting or rejecting proposals. As a track lead, you need to visit the list of blueprints for the upcoming summit to approve or decline blueprints that have been proposed to meetings.
+
+You should see a sentence before the footer like:
+
+You can show topics that have been declined and since you are a driver of Linaro Connect Q4.11 you can also accept meetings or topics that have been proposed.
+All the track leads should have this authority. If you don't, you'll need to speak to the correct person in your organization.
+
+The accept/reject interface is self-explanatory.
+
+**Tips**
+
+If you like a proposal but want some updates to it, don't reject it. Its easier to tell the person to make the updates and then check back and accept it.

=== added file 'docs/scheduler.rst'
--- docs/scheduler.rst	1970-01-01 00:00:00 +0000
+++ docs/scheduler.rst	2012-02-29 13:38:17 +0000
@@ -0,0 +1,5 @@
+==================
+Scheduler Permissions
+==================
+
+Coming Soon!

=== added file 'docs/scheduling.rst'
--- docs/scheduling.rst	1970-01-01 00:00:00 +0000
+++ docs/scheduling.rst	2012-02-29 13:38:17 +0000
@@ -0,0 +1,101 @@
+==================
+Scheduling a Meeting
+==================
+
+You have two options to schedule a meeting. If you've already defined a blueprint that needs discussing you can register it. You can also create one from scratch.
+
+Using an Existing Engineering Blueprint
+---------------
+
+If your blueprint can fit into a single session, this is the route to choose. After creating your blueprint you may select the "Propose for sprint" option when viewing the blueprint in Launchpad.
+
+
+Creating a "Scheduling Blueprint"
+---------------
+
+If your engineering blueprint is too big for a single session, you can break it up by using multiple "scheduling blueprints".
+
+To create a scheduling blueprint, you need to visit the sprint page in Launchpad. You will find a link to this page on the main page for the Summit you are attending.
+
+Prior to creating a blueprint, first view the blueprints proposed to see if one matches the topic you want to discuss.
+
+If none of the existing blueprints match your topic, you may register a new Blueprint by selecting the "Register a blueprint." 
+
+When creating a blueprint, please use the naming convention below. Keep in mind that the name of a blueprint is very important as it affects how your meeting will appear in the scheduling tool at UDS. 
+
+The format is either:
+
+* ubuntu-<cycle>-<track>-<topic>
+* linaro-<track>-<cycle>-<topic>
+
+Further information on this topic can be found at:
+
+https://lists.ubuntu.com/archives/ubuntu-devel/2011-March/032813.html
+http://ubuntudevelopers.blip.tv/file/3539348/
+The video is old so ignore the beginning about the wiki and just pay attention to the part where Jorge talks about Launchpad.
+
+Filling Out the Blueprint Fields
+--------------
+
+The following are fields on the "Register a blueprint" page.
+
+**For**
+
+When registering a blueprint for UDS, the project will be "ubuntu."
+
+**Name**
+
+The name is important as it determines how your meeting will appear in the scheduling tool at UDS, here are the track names:
+
+consumer community design desktop foundations hardware security serverandcloud ubuntu-arm
+
+You need to name your blueprint after the track name, and the title, and then the animal letter so that we can track it for this cycle:
+
+hardware-p-kernel-decision serverandcloud-p-openstack-integration design-p-wallpapers foundations-p-python-transition
+
+... and so on.
+
+**Title**
+
+This should be a human readable form of the name. Remember that your title will be displayed on the monitors, and need to be short and upfront, so make it easy to understand and put the information up front so that when the scheduler truncates your long title it makes sense.
+
+**Specification**
+
+Optional, but it can be a link to a page in this Wiki, but it's becoming popular to put your meeting notes from etherpad here, so:
+
+http://pad.ubuntu.com/serverandcloud-p-openstack-integration
+
+Don't worry, the system will autocreate your etherpad during UDS.
+
+What Happens Next
+==============
+
+After you submit the blueprint, it will wait for approval by a track lead. Once it has been approved it will show up on the summit schedule:
+
+* http://summit.ubuntu.com/
+* http://summit.linaro.org/
+
+If your blueprint is not on the schedule during the week before the summit, please ask your track lead to approve it. If they don't have it then it means you didn't submit it to the correct sprint (see the video). Track leads will be approving specs on a regular basis, so if you don't see your meetings on the schedule it's up to YOU to bother the track lead.
+
+Jono Bacon and Michael Hall keep an eye on the incoming specs for UDS, so if a track lead is particularly swamped we help keep the submissions going smoothly, but it helps tremendously when you check.
+
+If anyone has any questions please contact Michael Hall.
+
+Tips
+---------
+
+**Meeting Title**
+
+The title of the blueprint is important. We have screens setup at our events displaying the meetings for the day at various locations. For example:
+
+http://summit.linaro.org/uds-o/2011-05-11/
+
+A long title will be cut off on the display, however in your browser, you can hover and get the full title. This is not possible on the hallway screens and you will only be able to see the truncated text on the screens. Therefore, it becomes important to make sure the most important words show up near the beginning of your title.
+
+**Whiteboard**
+
+The etherpad document will most likely get used to collect notes for a meeting. This creates a small dilemma when you need to put work items in and make it a real "engineering blueprint". The recommended approach to dealing with this is to copy the contents of the notes from etherpad and paste them into the whiteboard.
+
+**Before Creating a Blueprint**
+
+Its a good idea to talk to the track lead before drafting a proposal and see if they like the idea.

=== added file 'docs/using.rst'
--- docs/using.rst	1970-01-01 00:00:00 +0000
+++ docs/using.rst	2012-02-29 13:38:17 +0000
@@ -0,0 +1,56 @@
+==================
+Using The Summit Scheduler
+==================
+
+The Summit Scheduler is a web tool utilized at Ubuntu Developer Summit and Linaro Connect.
+
+Registering to Attend a Summit
+==========
+In order to use Summit for your personal schedule, you will need to register in Launchpad as attending the summit. To do this, click the "Register in Launchpad" link on the main page for the summit.
+
+*Note*: Once you register, it may take up to 20 minutes for you to be able to use Summit.
+
+
+Signing up to Attend a Meeting
+==========
+After you have registered yourself as attending a Summit, you have the ability to "attend meetings." Signing yourself up to attend meetings will create your own personal schedule.
+
+To sign up to attend a meeting you have 2 options:
+
+**Subscribe to the blueprint**
+
+If a meeting has a blueprint, you can subscribe yourself to the blueprint which will mark you as attending the meeting. Subscribing to a blueprint will also notify you each time that the blueprint is changed. Sign up this way if you are interested in following the progress of the topic after the summit is over.
+
+When subscribing to the blueprint there is the ability to mark yourself as "Participation essential." By doing this, the Summit Scheduler will attempt to make the meeting at a time in which you are available. 
+
+*Note: Please only subscribe to a blueprint as Participation essential if your participation truely is essential.*
+
+**Subscribe to the meeting in Summit**
+
+If you do not want to follow the progress of the topic after the summit is over, or if the meeting does not have a blueprint,ou will want to subscribe to the meeting in Summit. Signing up this way will still add the meeting to your personal calendar, however you will not get emails after the summit when the blueprint changes.
+
+To subscribe to a meeting in Summit, click on the meeting name and you will be sent to the meeting page. In the navigation near the top, you will see a link called ""Attend this meeting." Shortly after clicking this link, the meeting will show up in your personal schedule.
+
+Agenda View
+==========
+
+When you are logged into Summit, the agenda view will show your personal schedule. All of the meetings have a star infront of the name of the meeting. If this star is grey you are not subscribed to the meeting. If the star is gold, you are subscribed.
+
+If you mouseover the meeting name, you will see the details about the meeting. This includes the meeting description, participants, and tracks. Any participants with a red star next to their name are "Participation essential."
+
+Wide Screen View
+==========
+
+The Wide Screen View is the traditional schedule view. This view is no longer recommended for use on personal computers.
+
+The Wide Screen View is the primary view for the monitors around the halls of the summit for reference when moving between meetings.
+
+Track View
+==========
+
+The Track View will show you all of the meetings for a particular track.
+
+Room View
+==========
+
+The Room View will show you all of the meetings for a particular room.