-
Notifications
You must be signed in to change notification settings - Fork 0
/
abstract.html
102 lines (88 loc) · 2.91 KB
/
abstract.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" type="text/css" href="style.css">
<link rel="SHORTCUT ICON" HREF="/favicon.png">
<title>OVS Orbit - How to Propose an Episode</title>
</head>
<body>
<div id="head">
<h1>OVS Orbit - How to Propose an Episode</h1>
</div>
<div id="main">
<div class="logo"><img src="orbit_144x144.png" class="logo"></div>
<p>
OVS Orbit is always seeking new content. To propose an
episode, please email <a href="mailto:blp@ovn.org">Ben
Pfaff</a> with a little bit about yourself and the proposed
topic and perhaps a few aspects of it that are worth
exploring.
</p>
<p>
OVS Orbit interviews aim to be between 30 and 45 minutes long,
but some end up being shorter or longer.
</p>
<p>
Recording episodes in person maximizes audio quality, but it
is also possible to record phone calls, etc.
</p>
<h1>Episode Outline</h1>
<p>
There are many possible interview formats, but in practice
most OVS Orbit episodes follow the general outline below.
<ol>
<li>
<p>Host introduction: Host announces the program and names and
briefly introduces the guests.</p>
</li>
<li>
<p>Guest introduction: Guests add some details about themselves.</p>
</li>
<li>
<p>Topic introduction: Guest or host introduces the high-level
topic and adds enough background that people can follow if
they don't already know anything about the topic, but do
have a basic background in networking in SDN.</p>
</li>
<li>
<p>Topic followup: What are the use cases for the topic, where
did it come from, how did you get involved with it, what's
the motivation for it, what keeps you interested in this
area, how does the business model work?</p>
</li>
<li>
<p>
Zeroing in on a subtopic: Host and guests discuss some
aspect of the overall topic that they (ideally) identified
in advance, and go into depth about it. It's nice to
identify multiple potential topics just in case the
discussion on one turns out to be short. If the subtopic
isn't directly related to Open vSwitch or software
switching, this segment tries to draw out some
relationship.
</p>
<p>
This is usually the longest part of the podcast.
</p>
</li>
<li>
<p>Future: What's happening next, in the subtopic or larger
topic? What are issues for concern? What questions need to
be answered?</p>
</li>
<li>
<p>Other: Is there anything else the interviewee wants to talk
about that we missed?</p>
</li>
<li>
<p>Finding out more: Where should listeners go to find out
more, such as a project website. Sometimes, contact
information for the speakers, such as a personal website or
Twitter or other social media handle.</p>
</li>
</ol>
</div>
</body>
</html>