Scheduling

Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2011-09-27 15:12:11
Size: 6951
Editor: jorge
Comment:
Revision 12 as of 2013-10-23 17:08:22
Size: 815
Editor: cjohnston
Comment: Update for 13.11
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from AndyDoan/Sandbox/Blueprints/SchedulingBlueprint
{{https://blueprints.launchpad.net/@@/meeting-logo|UDS Meeting Logo|align="right"}}
= Scheduling a Blueprint for Linaro Connect =
When Linaro Connects are co-located with Ubuntu Developer Summits (UDS), we use
their "summit" tool for scheduling sessions. This software requires us to create
Launchpad Blueprints using a specific format. This page walks you through the steps
required to get a session scheduled.
<<Include(UDS/Header)>>
Line 9: Line 3:
<<TableOfContents>> = Scheduling Meetings =
Line 11: Line 5:
== Scheduling a Session ==
You have two options to schedule a session. If you've already defined a blueprint that
needs discussing you can register it. You can also create one from scratch.
If you are a scheduler, you will need to be listed as a [[http://summit.ubuntu.com/uds-1311/tracks|Track Lead]] in Summit, and be
logged in. Then, from the [[http://summit.ubuntu.com/uds-1311/|uds-1311 page]], you will have an "Actions" box
on the side of the screen with a "Schedule Meetings" link.
Line 15: Line 9:
=== 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.
{{attachment:Actions_schedule-meetings.png}}
Line 20: Line 11:
  {{attachment:propose-for-sprint.png | Proposing a blueprint for a session}} Clicking that will bring you to the manual scheduling
interface, where you will be able to schedule the meetings for your
track (and only your track) by dragging the meeting block from the
Unscheduled side-bar to an open room and time slot.
Line 22: Line 16:
=== 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".
{{attachment:Scheduling.png|alt Scheduling|width=600}}
Line 26: Line 18:
To create a scheduling blueprint, first view the blueprints scheduled for
a Connect event under a link like:
  https://blueprints.launchpad.net/sprints/<sprint>
For example, Linaro Connect Q4.11 is located at: https://blueprints.launchpad.net/sprints/lcq4.11

You may register a new Blueprint by selecting the "Register a blueprint" link
as shown here. Use the normal [[../NamingConventions | naming conventions]],
but append a "-1", "-2", etc for each session that you'll need scheduled.

  {{attachment:register.png | Session Registration Link}}

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 ==

=== For ===
Pick the Linaro project in Launchpad this is related to. You can use the search option
to help find the proper project. Examples include:
 * linaro-image-tools
 * linaro-graphics-wg
 * linaro-android

If a project does not exist, you can use the "Linaro" project.

=== Name ===
The name is important as it determines how your session will appear in the
scheduling tool at UDS. The [[../NamingConventions| Naming Conventions]] guide
explains this.

If you have a question on the naming, contact the [[Resources/ContactUs|Engineering Resources]]
team.

=== Title ===
This should be a human readable form of the name.

=== Specification ===
Optional, but it can be a link to a page in this Wiki usually based on the
[[Process/SpecTemplate| Specification Template]].

== 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/uds-p/
 * http://summit.linaro.org/uds-p/

If it's been a few days and it's not on the schedule then ask your track lead
to approve it. If they don't have it then it means you didn't submit it to UDS
(see the video). Track leads will be approving specs on a regular basis, so if
you don't see your sessions on the schedule it's up to YOU to bother the track lead.

Jono Bacon (Canonical) and Jorge keep an eye on the incoming specs 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 [[JoeyStanford|Joey]] or
[[https://launchpad.net/~jorge|Jorge]]. Jorge is jcastro on freenode.

== Traceability ==

'''TODO''' ''document how this references the work defined from the roadmap.''

== Tips ==
=== Session Title ===
The title of the blueprint is important. We have screens setup at our events displaying the sessions for the day at various
locations. For example:
 http://summit.linaro.org/uds-o/2011-05-11/

A long title gets truncated. In your browser, you can hover and get the full title. However, you can
only the see the truncated text on the screens at the event. Therefore, it becomes important to make sure the most important
words show up near the beginning of your title.

In the example link above we had a session titled ''"Refining the blueprint page and associated content"''. This
was specific to Linaro, but we had a few people show up to the session because they didn't notice the Linaro icon
and thought the session was about changing blueprints in general. Another example of sessions were for Android.
Some of these had titles that ended with " for Android". This text was truncated, so people walking by could mistakenly
think the session was about all of Linaro.

=== Whiteboard ===
The whiteboard will most likely get used to collect notes for a session. 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 the whiteboard and paste them into the blueprints specification
in the Wiki.

= Managing Proposals (for Track Leads) =

The track leads are responsible for accepting or rejecting proposals.
When you go to a page like:

  https://blueprints.launchpad.net/sprints/lcq4.11

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 sessions or topics that have been proposed.''

All the track leads should have this authority. If you don't, you'll
need to request membership to:

  https://launchpad.net/~linaro-connect-organizers

The accept/reject interface is self-explanatory. A few tips to think about are:

 * Its a good idea to talk to the track lead before drafting a proposal and see if they like the idea.
 * 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.

= Managing the Summit Scheduler =

Track leads can manage the scheduling of time slots from the summit site. For example:

 http://summit.ubuntu.com/uds-o/2011-10-31/

Key Points:

 * once logged in, track leads should be able to manually drag-and-drop sessions to different time slots.

 * once a session has been manually updated, the scheduler will no longer handle it when doing automatic rescheduling work.

 * once UDS/Connect starts, only Arwen/Marianna have the ability to make updates. This is to prevent people from making concurrent changes that were tripping up the scheduler. So go to the event desk and ask them for help.


----
CategoryHowTo CategoryProcess
If your scheduling causes a scheduling conflict, it will notify you
which person has the conflict.

Scheduling Meetings

If you are a scheduler, you will need to be listed as a Track Lead in Summit, and be logged in. Then, from the uds-1311 page, you will have an "Actions" box on the side of the screen with a "Schedule Meetings" link.

Actions_schedule-meetings.png

Clicking that will bring you to the manual scheduling interface, where you will be able to schedule the meetings for your track (and only your track) by dragging the meeting block from the Unscheduled side-bar to an open room and time slot.

alt Scheduling

If your scheduling causes a scheduling conflict, it will notify you which person has the conflict.

UDS/Scheduling (last edited 2015-10-12 07:54:43 by dholbach)