Scheduling a Blueprint for Linaro Connect
Linaro Connect is using the same scheduling tool that is used at Ubuntu Developer Summits (UDS). We are using their "Summit Scheduler" 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.
- Scheduling a Blueprint for Linaro Connect
- Managing Proposals (for Track Leads)
- Managing the Summit Scheduler
Scheduling a Session
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, first view the blueprints scheduled for a Connect event under a link like:
For example, Linaro Connect Q1.12 is located at: https://blueprints.launchpad.net/sprints/lcq1-12
You may register a new Blueprint by selecting the "Register a blueprint" link as shown here. Use the normal naming conventions, but append a "-1", "-2", etc for each session that you'll need scheduled.
Further information on this topic can be found at:
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
Pick the Linaro project in Launchpad this is related to. You can use the search option to help find the proper project. Examples include:
If a project does not exist, you can use the "Linaro" project.
NOTE: There seems to be a bug in Launchpad that won't let you use a project group say 'linaro-graphics-wg' so you have to use an actual project. For example, "linaro-graphics-misc".
The name is important as it determines how your session will appear in the scheduling tool at Connect. The Naming Conventions guide explains this.
If you have a question on the naming, contact the Engineering Resources team.
This should be a human readable form of the name.
Optional, but it can be a link to a page in this Wiki usually based on the Specification Template.
The definition must be either 'New,' 'Discussion,' or 'Drafting' to be picked up by the scheduler.
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:
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 Connect (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.
If anyone has any questions please contact Joey.
TODO document how this references the work defined from the roadmap.
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:
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.
The whiteboard should contain a reference to a roadmap card, so it is clear why this session is held. This is done with a Meta tag similar to this:
Meta: Roadmap id: ANDROID2011-FDT-LEB
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:
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:
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
Scheduling of Linaro Connect is done automatically by a script built into Summit. The scheduler takes into account who is required to be at a meeting, and attempts to not schedule someone to be required at two meetings at the same time.
The only thing that the script will not schedule is private meetings. Private meetings must be scheduled by Arwen.
How to Create Private Meetings
Private meetings can be created by Track Leads and Managers by clicking the "Create Private Meeting" link on http://summit.linaro.org
- When creating a private meeting, please add the required participants.
- After creating the private meeting, please contact Arwen to get it scheduled.
internal/archive/Process/Blueprints/SchedulingBlueprint (last modified 2013-08-27 23:05:07)