uos-track-leads team mailing list archive

[Michael Hall <mhall119@xxxxxxxxxx>]

Hello everyone,

First of all I would like to thank you all for volunteering to be a
track lead for the upcoming UOS.  These summits are an important part of
our community development process, and your help with the organization
of it has a huge benefit to the community and project as a whole.

As this is only our second Online Summit, and some of you are first-time
track leads, I want to go over the difference between UOS and UDS. Where
UDS was very focused on planning work for the next Ubuntu release, UOS
combines that development planning with presentations, workshops, and
other content geared towards consumption by both users and developers.
Sessions can be exclusively one or the other, or a combination where a
presentation is followed on by future planning. Since have had a growing
percentage of the audience who is there to learn and follow Ubuntu
development, rather than actively contribute to that development, please
try and recruit a good mix of both types of sessions.

As track leads, your primary responsibility will be recruiting these
sessions from both Canonical and Community contributors. Usually you can
simply ask people to come up with topic ideas on their own, but you may
also want to think of topics that you know might interest viewers of
your track and then ask people if they can host that session. Session
hosts should be prepared to start an On Air Hangout on Google for their
sessions, but we ask that track leads be available to step in and run
the hangout if the intended host is not able.

Once you have a session topic and somebody to host it, the next step is
to get it into Summit. There are two ways you can do this, the first is
to register a Blueprint in Launchpad[1], which is best for sessions
where any kind of planning will take place, as the Blueprints can be
used to document work items and have them show up on
status.ububuntu.com. As a UOS track lead you will be able to approve or
reject Blueprints for the Launchpad sprint[2]. Once approved, these
Blueprints will be automatically imported into Summit as meeting
sessions, and will be available to add to the schedule.

For non-planning sessions it's simpler to propose them directly in
Summit[3]. For these you will need to review them in Summit[4] rather
than Launchpad, where you will again be able to approve or reject them.
Once approved they will be immediately available for you to schedule.

Once you have approved meetings, your next responsibility will be adding
them to the Summit schedule[5]. We don't automatically schedule meetings
for UOS (like we did with UDS in the past) so you will need to manually
add each session to a room and slot for your track. If your hosts have
specific day or time restrictions, it's up to you to try and work them
into the schedule as best as you can. If you find that you need need
more sessions in a given slot than you have rooms for, you can either
borrow another track's room or ask me to add an additional one to your
track.

Each track has two rooms (IRC channels) available, and 13 slots
available for sessions. That means you can have up to 26 sessions on
your track. You don't have to fill them all, but that is the target
number. If you have more than 26 we can always open a third room, and if
you have fewer than 14 we can close a room.

Finally, If you have any questions about what to do or how to do it,
please don't hesitate to contact me via email or IRC (mhall119) at any
time, and I will get back to you as soon as I possibly can. If you are a
first-time track lead, you can also ask your fellow leads who have been
through this process before for help.  And once again, than you all for
volunteering.

[1] https://wiki.ubuntu.com/UDS/Create
[2] https://blueprints.launchpad.net/sprints/uos-1411
[3] http://summit.ubuntu.com/uos-1411/propose_meeting/
[4] http://summit.ubuntu.com/uos-1411/review/
[5] https://wiki.ubuntu.com/UDS/Scheduling

-- 
Michael Hall
mhall119@xxxxxxxxxx