Current Sprint Information » History » Version 178
Eric Helms, 07/02/2015 09:04 AM
1 | 165 | Eric Helms | h1. Latest Demo Information |
---|---|---|---|
2 | 1 | Anonymous | |
3 | 165 | Eric Helms | h2. URLs: |
4 | 1 | Anonymous | |
5 | 165 | Eric Helms | ** read-only event stream: https://plus.google.com/events/cj864hk5cs53guesl28hu2erors |
6 | ** read-only YouTube stream: http://www.youtube.com/watch?v=CTfIPD2w8sY |
||
7 | 178 | Eric Helms | ** *presenters only*: https://plus.google.com/hangouts/_/hoaevent/AP36tYcrm5fhPDm0DyIj5KTrvvK-RDGs5hYf2JZBE3Uo9hp-amkqdw?authuser=0&hl=en |
8 | 1 | Anonymous | |
9 | 165 | Eric Helms | h2. Demo Checklist |
10 | |||
11 | h3. Presenters |
||
12 | |||
13 | * If demoing a terminal |
||
14 | - ensure the font is large (typically 2 shift-ctrl-+) |
||
15 | - ensure your color and font are readable from arms length to the keyboard as a heuristic |
||
16 | * If demoing a browser |
||
17 | - when on a widescreen monitor, shrink the browser width to 1300-1400 pixels |
||
18 | - increase browser zoom if possible (ensure it doesn't break styling) |
||
19 | * If demoing a presentation |
||
20 | - ensure you hide or remove action bars or do a full screen presentation |
||
21 | * Include initial background on the topic. For example, if demoing an update to the Content Views UI, remind the audience what a content view is and how to get to the starting point of the UI. |
||
22 | * Remember that you are trying to inform users why the change is important for them to know and how they can make use of it. |
||
23 | |||
24 | h3. Moderator |
||
25 | |||
26 | * Turn on Q&A application on Hangout page before starting hangout |
||
27 | * Start by introducing what the general theme of the Demo is, and the overall flow, include: |
||
28 | - What the demo is for |
||
29 | - When and how questions can be taken (e.g. at the end, after each presenter, using the Q&A app, whether the moderator will read the questions or the presenters) |
||
30 | - If there is a time limit, mention at the start for the presenters that you will be timing and enforcing |
||
31 | |||
32 | h2. Agenda |
||
33 | |||
34 | 163 | Eric Helms | * Description of feature to demo (Your Name, X minutes) |
35 | 160 | Eric Helms | ** Any 10+ minute presentation should be done as a deep dive instead. Keep to <= 5 minutes per feature if you can. |
36 | 164 | Shimon Shtein | |
37 | 166 | Marek Hulán | * Partition Tables new features (Marek Hulán, 5 minutes) |
38 | 172 | Lukas Zapletal | * Small things (lzap, 4 minutes) |
39 | 173 | Lukas Zapletal | - foreman-debug no longer uploads by default (use -u option) |
40 | - VNC/SPICE websockify port is randomly selected from the whole pool instead of incremental approach (update your firewalls) |
||
41 | 169 | Stephen Benjamin | * Salt automatic state importing (stephen) |
42 | 171 | Daniel Lobato Garcia | * GCE support fixed and allows to add disks |
43 | 175 | Ivan Necas | * Dynflow 0.8.1: multiple executors, concurrent-ruby at backend, socket-less (inecas 4 minutes) |
44 | 174 | Ivan Necas | * Remote Execution: Dynflow and basics for SSH provider on smart proxy (inecas 4 minutes) |
45 | 176 | Marek Hulán | * Remote Execution: Job templates (Marek, 5 minutes) |