►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
so
wow
that
was
logistically
crazy,
but
it's
working
it's
working
this
time
and
I
think
we
I
have
to
replicate
this
formula
on
the
Mac
that
I
normally
used
I
get
different
results
every
time.
I
try
to
do
this
on
my
Mac,
the
audio
doesn't
work.
The
video
doesn't
come
out
right,
it's
real
choppy
and
then
the
very
next
time.
Everything
is
perfect
so
and
the
best
time
that
it
worked
where
it
just
worked
right
out
of
the
box.
A
A
Well,
let's
do
has
to
sort
of
intros
I'm
Jarek
winkworth
I
am
the
developer
advocate
for
enery
labs,
I
work
at
juniper,
Networks
and
I
am
one
of
the
hosts
co-hosts
of
this
show.
Matt
is
out
at
Interop
this
week
talking
to
augment
work,
automation,
nerds
in
las
vegas
I
I
wish
I
could
have
been
there,
but
I
wasn't
invited.
That's.
A
Yeah
I've
been
there
so
many
times
now.
For
these
events,
I,
don't
really
care
about
being
in
Las
Vegas.
You
can
get
good
beer
anywhere
and
I.
Don't
really
do
Las
Vegas
things,
I,
don't
gamble
and
stuff
like
that,
so
David
G
sometimes
comes
on
here
too,
but
he
he
wasn't
able
to
make
it.
But
we
do
have
another
regular
co-host
that
we'd
like
to
introduce
a
key
member
of
the
NRI
labs
team
are
her
name
is
Lisa
Cawood
she's,
also
at
Juniper,
Networks
Lisa?
Why
don't
you
tell
us
a
little
bit
about
yourself
sure.
B
So
Derek
and
Matt
and
David
and
I
go
way
back
many
many
years,
but
we've
all
been
kind
of
floating
around
open
source,
stuff
and
networking
stuff
for
quite
a
long
time.
I
very
recently
joined
juniper
and
thus
got
hooked
up
with
NRI
labs
about
my
last
gig
was
actually
with
the
Linux
Foundation
and
before
that,
I
was
working
on
open
daylight
at
one
of
the
open
daylight
member
companies.
B
A
A
We'll
do
we'll
have
other
fun
things
like
that.
Hopefully
we're
gonna,
do
it
from
a
live
event
soon
like
it
like
an
event
somewhere,
not
just
our
off
our
home
offices,
so
so
Matt,
nice,
oh
I'm,
the
developer
advocate
name
I'm.
You
know
I'm
slowly,
you
know
getting
into
that
role
and
I'm,
and
it's
sort
of
still
sort
of
technical
focus
in
working
with
people
who
want
to
contribute,
make
sure
the
tools
work
for
them,
that
you
know
that
kind
of
thing
that
they
get
recognized
for
their
contributions,
and
you
know
I
said
really.
A
So
one
thing
Matt
and
I
have
never
really
done
is
actually
start
an
actual
community.
We
have
lots
of
github
repositories
with
all
kinds
of
a
broken
abandoned,
or
you
know
less
than
less
than
functional
code
in
them,
but
that
does
not
a
community
make.
So
we,
yes,
so
Lisa
actually
has
some
background
in
this.
You
know,
as
as
a
director
and
in
marketing
at
the
Linux
Foundation
that
that
was
one
of
her
prior
roles.
B
Well,
I
mean
the
first
thing
is
I
mean
get
people
excited
about
the
project,
obviously,
but
I
think
the
thing
to
that
that
oftentimes
engineers
sort
of
overlooked
because
they're
really
excited
about
their
stuff,
is
you
have
to
make
it
easy
and
accessible
for
people
to
do
stuff?
So,
if
you
think
about
like
when
you're
learning
any
new
thing
right,
you're
you
you
you're
watching
somebody
else,
do
it
and
you
go.
Oh
that
looks
cool.
B
B
So,
let's
say
I'm
in
the
middle
of
like
making
a
cheese
and
somebody's
comes
along
and
says
well,
I'd
love
to
a
little
bit
make
cheese
and
I'm
like
great
here,
hold
the
colander
for
me,
while
I
scoop
the
curds
into
the
colander,
like
it's
a
very
specific
practical
thing
that
is
useful
and
helpful.
You're
you're,
like
in
the
mix
you're
watching
people,
do
stuff
you're,
not
in
a
place
where
you're
gonna
mess
stuff
up,
but
you
know
you're
getting
to
actually
participate
in
a
small
piece
and
oftentimes.
B
You
know
just
getting
that
that
that
specific,
practical,
tangible
thing
that
that
a
new
person
can
do
is
the
thing
that
kind
of
gets
them
over
the
hump
and
they
go
okay.
What
next
and
then
you
go
okay,
so
now
we're
going
to
strain
the
curds.
What
does
that
mean?
Why
are
we
doing
it
and
I'll
explain
it
as
I'm
going
along,
but
they're
said
they're
standing
there
holding
the
colander
for
me
while
I'm
straining
the
curds,
and
you
know
it's
just
it's.
B
It's
kind
of
that
that
you
know
giving
out
little
piece
parts
over
and
over
again
depending
on
and
you
as
you
get
to
know
people
you
get
some
other
interests
and,
and
you
know
one
person
might
be
really
excited
about
planning
events
and
you're,
like
oh
we've
got
this
event
coming
up.
Can
you
help
with
this
because
honestly
I
second
logistics,
but
this
other
person's
really
good
at
checklists,
can
I
put
them
in
charge
of
like
making
sure
we
have
whatever
we
need
to
have
for
in
place?
B
For
that
event
and
I'll
go
do
the
stuff
I
just
need
them
to.
Let
keep
track
of
it
all
for
me
or
it
might
be.
You
know
it
could
be.
You
know
any
number
of
other
things
depending
on
what
people
are
interested
in,
but
it's
it's
a
question
of
just
carving
off
little
pieces
of
things
that
match
people's
interests
and
skills
and
getting
them.
B
You
know
sort
of
involved
and
in
the
process
of
doing
those
little
things
they
get
to
know
other
people
in
the
community,
people
who
are
maybe
a
little
further
along
who
then
are
sort
of
other
points
of
connection
for
them,
and
you
know,
as
people
start
to
make
friends
and
kind
of
find
their
way
around
a
community,
then
they'll
go
they'll
starts
to
see
other
things
that
are
going
on
and
go.
Oh
I'd
love
to
get
involved
with
that.
B
A
A
So
you
know
we
Lisa
does
have
all
kinds
of
practical
advice
and
she
knows
how
to
do
things
up
when
it
so
one
of
the
things
I
do
now.
I
had
a
good
talk
with
her,
not
that
long
ago,
and
one
of
the
things
I
do
now.
I
know
this
is
silly,
but
as
engineers,
sometimes
we
get
wrapped
up
in
what
we're
doing
like
in
our
own
headspace
right
and
we're
doing
whatever
it
is,
we're
doing
in
our
headspace
for
banging
out
code
or
configuring
stuff
or
setting
things
up,
and
you
lose
track
of
time.
A
A
I
have
to
stop
and
have
to
check,
to
see
if
there's
messages
or
someone's
trying
to
get
ahold
of
me
and
and
that
kind
of
thing
so
I
bought
what
I
actually
excuse
me
I
was
describing
this
problem
to
Missy
and
some
of
the
things
that
Lisa
and
I
had
talked
about
and
she
went
out
and
got
this
thing.
It's
called
it's
a
time
timer.
This
is
really
cool.
A
A
B
A
A
Besides,
ignore
everyone
in
and
do
technical
stuff
and
what's
shocking,
is
that
I've
I've
turned
this
thing
on
and
it's
not
on
now,
because
you
know
we're
streaming,
but
when
I've
turned
this
thing
on
and
I've
started
doing
stuff
thinking,
okay,
I
have
an
hour
I'm
going
to
get
this
thing
done
and
and
then
it
seems
like
boom,
it's
beeping
and
there
is
no
way.
I've
only
been
doing
this
for
like
ten
minutes
and
no
it
was
like
an
hour.
B
A
B
I
mean
the
other
going
back
to
the
you
know,
finding
little
things
for
people
to
do.
It's
it's
the
other
piece
of
it.
I
think
is
helping
people,
you
know
sort
of
see,
see
the
you
know
how
their
little
thing
fits
into
the
bigger
hole
and
for
that
it
really
comes
down
to
being
really
consistent
and
articulate
about
what
it
is,
we're
actually
trying
to
achieve,
and
why
and
who
it's
for,
and
you
know,
having
a
clearly
articulated
and
documented
plan
for
getting
there.
B
B
Or
even
just
kind
of
you
know
from
a
sort
of
a
strategic
standpoint,
what
are
what
are
we
doing,
and
why
and
that's
actually
one
of
the
things
that
that
Matt's
out
doing
it
in
app
today
is
explaining
what
we're
doing
and
why
but
you're
just
from
a
technical
standpoint
right
we
have.
We
have
a
bunch
of
contributors
already
who
have
been
doing
things
and
it's
sort
of
you
know
it's
it's
sort
of
classic.
You
know
early
stage
formation
kinds
of
project
stuff
where
people
are
just
doing
stuff.
B
That
seems
like
it's
interesting
and
useful
and
I
think
that's
that's
absolutely
appropriate
when
a
project
is
first
starting
out,
because
it's
kind
of
that
that
sort
of
swirling
formation
process
is
how
the
project
finds
identity
and
what
it
wants
to
be
about
and
kind
of
the
form
it
wants
to
take.
But
at
a
certain
point
you
kind
of
have
to
switch
over
and
say:
okay,
you
know
we
have.
We
have
a
platform
in
place.
We
have
some
core
lessons
in
place.
B
You
know
what
do
we
actually
need
to
do
to
get
to
whatever
we
think
the
next
level
is,
and
so
you
know,
we've
we've
been
kind
of
talking
about
what
we
think
that
next
level
is-
and
you
know
clearly
I
mean
you
work
for
juniper
I
work
for
juniper
Matt
works
for
juniper,
but
none
of
us
want
this
to
be
a
Juniper
project.
We,
you
know,
we've
we've
open
sourced
the
code,
but
now
we
really
really
want
to
build
a
a
a
truly.
B
You
know
open
community
that
is
not
dependent
on
juniper
and
so
one
of
the
ways
that
we
do,
that
is
by
you
know,
being
really
crystal
clear
about.
You
know
all
of
the
different
platforms
that
are
being
supported
by
that
that
people
can
play
around
with
in
in
re
labs
and
and
kind
of
learn
how
to
do
automation
on
different
types
of
platforms.
So
one
of
the
things
that
we
really
want
to
do
is
start
building
lessons
for
other
platforms
from
other
vendors.
That's
number
one
number
two
is
kind
of
start
knocking
off.
B
You
know
kind
of
the
top
automation
tools.
I
mean
building
lessons
around
them.
We
have
a
lot
of
the
fundamentals
in
place,
but
we
kind
of
need
to
start
focusing
on
tools
that
people
might
actually
use
on
a
day
to
day
basis
in
their
automation,
practices
and
start
building
more
lessons
around
them.
So
you
know
those
are
kind
of
the
two
things
that
we
need
to
really
start
doing:
I
think
as
a
community
and
just
being
starting
to
be
prescriptive
about
how
we're
going
to
get
from
here
to
there.
B
A
So
we
have
a,
we
have
a
question
hold
on
one.
Second,
the
question:
yes,
maybe
I
missed
it,
but
is
there
a
plan
to
add
an
option
for
custom
network
topologies
to
practice,
automation
on
energy
labs,
and
the
answer
to
that
question
is
there
is
a
plan
actually
to
do
this?
That
where
you
can,
you
can
actually
specify?
What
do
you
want
that
topology
to
look
like
it
won't
be
now?
This
isn't
at
the
moment
meant
to
scale
massively
we're
talking
about.
A
You
know
like
maybe
six
No
or
something
like
that
I'm,
usually
when
people
are
trying
to
figure
something
out,
you
don't
need
a
huge
full
scale.
Topology
anyways
you,
you
build
those
for
scale,
testing
right,
you
you're,
usually
doing
that
just
to
test
functionality,
here's
three
nodes
or
four
nodes
or
whatever
it
is
to
to
get.
A
You
know
your
your
your
network,
configuration
in
place
with
you,
know,
configured
in
some
way,
that's
congruent
to
the
environment
that
your
automation
will
work
in
and
then
you
can
build
your
automation
against
that
smaller
scale,
version
of
of
your
production
network
and-
and
so
that
feature
is
coming.
That's
we
have.
We
I
think
next
week
or
the
week
after
we
have
a
plan
if
you're.
If
this
is
something
that's
really
interesting,
you
we're
gonna,
go
into
great
detail
about
how
we're
gonna
evolve.
A
Energy
labs
over
the
next
year
there's
a
lot
of
really
interesting
changes
that
are
happening
and
that's
definitely
one
of
them.
So
that's
a
good
question
by
the
way,
if
you
guys
do
have
questions,
justjust
put
them
in
the
chat.
They're
just
like
fun
has
been
putting
him
in
there
and
we'll
we'll
answer
mer
as
we
go
along
yeah,
so
that
that
is
a
good
idea
and
I'm
beyond
just
the
tools
right
he's.
A
A
A
And
it's
not
just
it's
not
just
the
this
is
crazy.
How
much
more
effort
there
isn't
I
mean
the
core
piece
of.
It
obviously
is
having
this
working
platform
and
having
something
where
people
can
go
learn,
but
you
know
we
have
to
support
that
with
all
kinds
of
like
content.
You
know
we
have
to
write
blogs
and
make
videos
we
do
the
stream.
This
was
just
ad
hoc,
the
stream.
We
decided
one
day
with
like
30
minutes
before
we
decided
to
do
it,
that
we
were
just
gonna.
Do
it
with
no
plan
and
when.
B
You
strike
out
it's
great
to
you,
know
just
throw
stuff
at
the
wall
and
see
what
sticks
that
said.
I
mean
yeah
you're
talking
about
all
those
sort
of
the
stuff
we
need
to
do,
and
I
I
keep
coming
back
to
something
that
a
Dave
Meyer
used
to
say
and
Dave
Meyer
was
the
the
founding
chair
of
the
open
daylight
project
and
he
liked
to
say
I'm
and
I'm.
This
isn't
an
exact
quote:
I'm
paraphrasing,
but
he
liked
to
say
that
the
code
is
the
artifact
of
the
process
and
what
he
meant
by.
A
Yeah,
it
is
because,
without
that,
without
the
how
the
the
what
goes
nowhere
rain,
we
have
to
get
other,
we
have
to
get
people
in
gate.
I
mean
it's,
it's
crazy,
because
you
think
it's
about
the
tech
and
you're
just
gonna
make
this
awesome
thing
and
then
people
will
find
it
and
then
those
just
use
it
right.
They.
A
B
You
know
III
was
having
this
rather
interesting
conversation
on
Twitter
over
the
weekend
with
a
guy
who
runs
a
living
history
group
he
had
based
in
the
UK,
and
he
focuses
on
Saudi
ins.
Now
Saudi
ins
were
an
Iranian
people
who
were
sort
of
merchants
and
traders
back
in
the
6th
and
7th
centuries
kind
of
sinful
around.
What's
now
whose
back
has
done
so
bukata
and
and
some
archons
and
so
he's
off.
B
And
you
know
at
various
times
he's
talked
about
you
know
wanting
to
you
know,
be
be
sort
of
the
the
counterpart
to
the
sort
of
the
the
mainstream
in
the
West
narrative
about
you
know.
The
Persians
are
always
the
bad
guys
against.
You
know
the
Greeks
or
whoever
happens
to
be
in
happening
and
Amanda
Julia
and
at
other
times
he
used
to
talked
about
different.
You
know
wanting
to
do
it
for
different
kinds
of
reasons,
and
you
know
it
really
came
back
to
well.
B
Are
you
trying
to
do
events,
or
are
you
trying
to
build
a
community?
You
know
what
fundamentally
is
your
goal?
Because
that
really
dictates
you
know
how
you
approach
things
and
I
think
you
know
for
us
for
NRI
lamps.
You
know
we
were
I,
think
all
of
us.
You
know
sort
of
kind
of
at
the
core
of
it,
or
are
really
really
clear
that
we
really
want
this
to
be
about
the
people
and
about
the
the
you
know:
building
skills
for
working.
B
A
Yeah,
that's
that
is
important,
I,
think,
building
the
community
and-
and
you
don't
make
being
make
sure
you're
communicating
all
the
time
with
them
right
to
all
of
the
various
channels.
We
have
a
discourse
forum
now,
it's
community
network
reliability
that
engineering,
if
you're,
not
signed
up
on
that
for
Lauren
Jett,
please,
please
go
do
so,
there's
already
quite
a
few
people
on
there
interacting
with
us,
and
you
know,
reporting
bugs
and
talking
about
the
work
they're
doing
so.
Please
please
do
that,
but
we
you
know
we
have
to
pay
attention
right.
A
We
have
to
you
have
to
make
sure
that
we're
we're
engaged
on
all
these
channels
and
that
you
know
we're
encouraging
people.
In
fact,
oh
wait
hold
on.
We
have
another
comment.
Let
me
express
gratitude
that
for
someone
like
me
who
wasn't
working
on
automation
but
wants
to
get
into
it,
options
like
and
energy
labs
are
a
blessing
can't.
Thank
you
guys
enough.
Oh
sweet.
A
A
Can't
do
that
I'll
get
in
trouble,
I
have
so
much
stuff.
I
have
to
do
right
now,
but
that
is
that
is
the
actual.
You
know.
That's
that's
the
core
of
what
we're
trying
to
do
here.
It's
not
automation
is
you
know
we
got
to
make
it
easy
for
people
to
get
into
it
and
and
to
learn
it
like
on
a
bite
by
bite
basis
right
and
then
not
turn
it
into
this.
A
You
know
grand
thing
like
studying
for
the
Jay
&
cie
or
the
CCIE,
or
something
like
that,
which
is
you
know
six
months
of
intensive
effort.
You
should
be
able
to
learn
little
things
at
a
time
that
are
useful
and
take
that
back
into
your
everyday
work
and
and
and
try
to
try
to
have
it
benefit
you
right
and
it
shouldn't
be
that
hard
to
get
in
it
shouldn't
the
barrier
should
not
be
that
great
doing
that
yeah.
So
so,
thank
you
for
the
comment.
A
A
You
know
what
that
reminds
me:
I
got
a
I'm,
gonna
say
this
before
I
forget
our
our
first
public
bounty
was
announced
two
Fridays
ago
and
I
just
want
to
make
sure
everyone
on
the
on
the
on
the
stream.
Here
is
aware
of
it
if
you
haven't
seen
it
on
the
discourse
forum
or
if
you
haven't
seen
it
on
on
Twitter.
A
Basically,
you
know
how
our
lessons
are
organized.
We
have
different
categories
of
lessons
and
then
each
lesson
is
divided
into
stages
and
those
stages
cover
different
sort
of
topics
within
the
overall
theme
of
the
lesson.
So
we
have
a
like
a
little
stage
about
Yama
lists
under
the
yama
lesson,
and
then
we
have
another
stage
under
the
Yemma
lesson
about
yeah
mel
dictionaries.
Well,
anybody
anybody
well
at
least
first
few
people
that
dad
add
to
stages
right.
A
A
A
There
I
guess
in
video
games
now
loot
box,
everyone,
I
I,
don't
understand
video
games.
I
played
a
lot
of
you
games.
Younger
people
get
excited
about
these
loot
boxes
because
they
like
to
customize
their
characters.
They
don't
get
like
new
abilities
or
like
more
powerful
or
anything.
They
could
cause
medic
items
like
hats
and
shirts,
and
sometimes
it's
funny
and
goofy,
and
sometimes
it's
more
serious,
looking
like
ensembles
and
they
they
like
to
customize
and
get
rare
like
anyways.
A
They
call
them
loot,
boxes
and-
and
this
has
bled
over
into
real
life,
and
you
can
actually
subscribe
to
all
different
kinds
of
loot
boxes.
Now,
like
you
can
like,
like
different
like
we
we'd
subscribe
to
this
nerd
box
for
a
television
show,
that's
been,
has
been
cancelled
now
for
almost
a
decade
called
Firefly
and
they're
still
sending
out
loot
boxes
and
they
send
you
collectibles
for
Firefly
in
this
loop
box,
and
it's
when
you
open
it.
It's
super
fun.
A
Every
single
time,
anyways
we're
gonna,
do
a
physical
loop
box
and
mail
it
to
whoever
does
these
stages
in
our
public,
bounty
and
it'll
include
a
sticker
and
a
shirt.
If
you
want
a
shirt,
so
please
please
contribute
and
and
possibly
get
a
loop
box
with
some
cool
stuff
in
it
yeah
I'm.
I
can't
wait
to
figure
out
what
else
is
gonna
go?
Actually
we
need
to
talk
about
that
I,
don't
know
if
I
don't
know.
B
A
A
Content,
and
then
we
talked
about
above
and
beyond-
writing
code,
you
have
to
build
a
community
and
that's
obviously,
community
content
goes
into
that
right.
The
streams
and
the
videos
absolutely,
and-
and
it's
not
just
us,
creating
those
things
we
have
to
come
up
with
a
way
to
encourage
others
and
to
make
sure
that
you
know
when
they
take
the
time
to
create
that
content
that
we
share
and
we
actually
had
a
couple
of
community
members
write.
A
Some
really
great
blogs,
make
some
interesting
contributions
over
the
last
couple
weeks
and
and
we'll
talk
about
that
and
before
the
end
of
the
podcast
here
in
a
few
minutes,
but
yeah
stick
around
for
that.
There's
some
cool
things
that
people
did
for
us
in
this
in
in
the
community
of
which
look
some,
what
of
anyways
stick
around
for
that?
A
So
what
are
some
some
of
the
other
things
like
we
have
to
you
know
we
have
to
be
at
events
and
stuff
like
that,
and
it's
not
always
obvious
to
us
what
events
we
have
to
be
yet
there's
a
lot
of
different
events
and
Matt
right
now
is
that
Interop
and
there's
like
there's,
there's
like
a
thousand
different
events
every
year
yeah
and
we
have
to
do
some.
You.
B
Can
you
can
you
can
spend
all
your
time
and
energy
and
money
going
to
events
I'm,
not
personally?
A
big
fan
of
events
I
think
that
the
return
on
investment
is
pretty
low.
I
think
you
need
to
be
really
selective
about
about
which
events
you
go
to
if
you're
going
to
go
to
events,
it's
a
really
a
question
of:
where
are
you
going
to
meet
the
people
who
are
most
going
to
benefit
from
your
stuff?
A
Use
it
so
I.
Usually
what
happens
is
whenever
my
kids
love
Chinese
food,
and
so
whenever
we
decide
to
order
it-
and
we
just
did
the
other
day,
I'm,
usually
working
when
that
decision
is
made
and
then
they'll
come
in
here
and
start
writing
the
order
on
the
board,
because
they
all
expect
me
to
make
the
phone
call
and
go
get
it.
So
that's
and
then
these
have.
A
Make
sure
when
you're
done
you
order
this
and
go
get
it
yeah
they've
written
actually
one
time
I
got
up
here,
and
there
was
something
highly
inappropriate
up
there
that
my
teenager
wrote
and
I
didn't
realize
until
about
halfway
through
it.
Wasn't
this
podcast
there's
another
one,
and
then
somebody
mentioned
somebody
sent
me
a
DM
was
like
you
might
want
to
erase
your
whiteboard.
I
was
like
oh,
my
goodness.
I'm
gonna
have
to
have
a
talk
with
them.
A
So
we
have
even
above
and
beyond
so
we
have
contents
and
events,
and
we
have
you
know
just
day-to-day
thinking
more
strategically,
rather
than
tactically.
We
have
these
things
like
like
Community
Guidelines,
like
governance,
Docs,
and
that
kind
of
thing
can
you
explain
like
a
little
bit?
What
exactly
is
the
purpose
of
a
governance
TOC
for
an
open-source
community
yeah.
B
It
basically
describes
the
the
rights
and
responsibilities
of
all
the
members
of
the
community
and
members
members
is
actually
something
that
gets
has
different
meanings
in
different
contexts,
and
so
we
should.
We
should
maybe
talk
about
about
that
right
in
itself
a
little
bit.
So
you
know
when
I
was
working
for
the
Linux
Foundation.
B
You
know
in
in.
In
our
case,
you
know
right
now
the
the
the
costs
are
not
particularly
high.
You
know,
juniper
is
paying
our
salaries,
but
you
know
so
it's
that
beyond
that
there
aren't
there
aren't
a
lot
of
costs.
Are
the
needs
of
the
project
are
really
much
more
centered
around
you
know
developing
the
lessons
and
and
and
building
and
fleshing
out
the
platform
and,
and
things
like
that.
B
Who
gets
to
be
a
member
who
gets
to
be
a
committer
who
gets
to
be
a
contributor
how
those
decisions
are
made
and
just
being
really
crystal
clear
about
all
those
things
and
very,
very
transparent
about
all
those
things
so
that
everybody
knows
coming
in
kind
of
how
things
work
and
there
aren't
any
surprises,
and
if
you're
coming
in
as
a
contributor,
you
want
to
know
how
you
could
how
to
work
with
with
committers.
You
know
what
are
the
criteria
for
getting
your
stuff
accepted?
B
How
can
you
become
a
contributor,
as
you
go
along
and
kind
of
builds,
build
a
body
of
work
and
a
you
know
some
stature
and
standing
in
the
community
like
what
are
the?
What
are
the
parameters
for
that?
And
so
you
know,
almost
every
open
source
project
out
there
originates
in
every
major
open
source
project
has
originated
in
some
sort
of
organ
another
that
you
know
that
typically
incubates
the
person
doing
the
work
and
so
forth,
and
so
on,
and
that's
perfectly
normal.
B
What
you
want
to
see
over
time
is
is
that
that
the
originating
organization
you
know,
let's
go
and
is-
is
completely
open
to
other
people
from
other
parts
of
the
universe,
taking
control
and
taking
positions
of
leadership
and
so
forth,
and
establishing
a
good,
strong
governance
model
is
really
key
to
that
and
being
and
then
also.
Of
course,
you
know
living
by
the
principles
that
are
that
are
set
out
in
the
governance
model,
some
some
communities
honestly
do
that
better
than
others.
B
So
you
know
they're
out
there.
Obviously,
in
any
system
in
the
world
there
are
ways
to
get
in
the
system.
So
so
you
know
the
question:
is
you
know
what
does
the
governance
model
look
like
on
paper,
and
then
you
know
in
practice
you
know
over
two
or
three
years.
How
does
it
actually
play
out
in
terms
of
you
know
how
people
wind
up
in
leadership,
roles
and
and
and
things
like
that,
so
you
know
how
how
open
is
the
community
on
paper
and
how
open
is
it
in
reality?
B
Those
are
those
are
both
things
that
are
worth
looking
at
and
evaluating
as
you're
thinking
about
how
you
you
engage,
are
there
as
a
contributor
to
an
open
source
project
or
as
a
user,
to
an
open
source
project,
also
understanding
that
these
are
things
that,
especially
when
a
project
is
first
starting
out,
you
know
everything's
in
flux
and
everything's
up
for
grabs.
You
know
right
now,
just
because
we're
kind
of
you
know
starting
to
emerge
from
the
formation
stage.
B
A
B
A
governess
talk,
it's
more
a
a
statement
of
scope
and
of
intent,
and
that's
actually
it's
it's
not
really
obvious.
Weird,
it's
actually
under
the
the
antidote
portion
of
our
of
our
github
site,
but
it
is
it.
Is
there
it's
it's
a
it's!
A
good
I
think
it's
a
reasonably
good
statement
of
intent
and
mission
scope,
and
things
like
that.
It's
of
course,
still
sort
of
you
know
open
for
other
people
to
comment
on,
and
you
know
that
that
can
always
be
an
evolving
document
too.
B
It's
not
set
in
stone,
but
you
know
again
it's
not
something
that
we
want
to
change
lightly
either.
We
want
to
be
intentional
about
it,
especially
for
something
as
foundational
as
a
code
of
practice,
because
again
the
artifacts
are
the
outcome
of
the
process,
and
so
we
want
to
be
very
thoughtful
about
when
we
put
together
a
code
of
practice.
A
A
Oh,
when
you
go
to
that
repository,
just
click
on
pull
requests,
and
then
there
is
a
there
is
a
single
open,
pull
requests
that
are
now
called
called
Dakota
practice
and
you
can,
you
can
read
it
and
if
you
have
any
feedback
you
can
leave
in
a
github
or
you
can
leave
it
on
our
forums
or
you
know
any
on
discord.
Whatever
is
easiest
for
you
and
we'll.
You
know
it's
a
discussion.
So
please
discuss
I.
A
A
A
A
So
please
go
check
that
out
actually
also
walks
through
how
to
how
to
get
it
set
up
with
KVM
if
you're
not
a
VirtualBox
fan,
which
is
which
is
the
default
setup
for
for
development,
vibrant,
it's
trivial
to
change
that
and
if
it
works
better
for
you,
then
definitely
you
know
his
blog
walks.
You
through
that
those
product
that
process
also
there's
an
ongoing
discussion.
100
over
Jaques
OBE
are
gix.
A
One
of
our
community
members
went.
Did
some
hackery
and
managed
to
get
VNC
to
work
and
know,
and
if
you're
familiar
with
our
lesson
layout,
you
know
we
have
the
lesson
text
on
the
left
side.
It
would
be
my
left
side,
I,
don't
know
if
left
or
right,
anyways
on
the
right
side,
there's
a
bunch
of
tabs
and
normally
it's
all
SSH
s
engine
you
can
tap
through
those
to
you
know
the
network
nodes
or
the
like
a
Linux
box
or
whatever,
but
these
managed
to
get
it
so
that
you
can
actually
embed
VNC
session.
A
So
you
get
a
desktop
from
a
container
inside
of
those
tabs.
Of
course
it's
not
committed.
Yet
it's
not
a
feature
that
you
he
just
sort
of
went.
He
just
did
some
hackery
to
see
if
it
would
work.
There's
some
some
other
significant
changes
that
we
have
to
make
in
order
to
support
that,
but
that
is
coming
now.
It's
it's
now
officially
on
the
roadmap
and
hopefully
we'll
have
that
in
the
next
couple
of
months.
A
That
would
be
a
great
addition
to
to
our
you
know:
it's
another
capability
for
people,
building
lessons
where
it
makes
sense,
some
some
tools
that
people
use
our
in
fact
desktop
tools,
they're,
not
command-line
tools,
so
it
we
need
to
have
that
so
I
wanted.
So
thank
you
over
Jicks
for
that
and
thank
you,
Brian
Linklater,
for
that,
for
that
blog
right,
up,
I
think
I.
Think
I
think
we'll
just
end
it
here
and
please
come
back
next
Monday
I
think
Matt
will
be
back
and
we'll
we
have
even
more
things
to
discuss.
A
A
We
should
go
over
that
because
that
is
kind
of
the
Network
automation
event.
That's
whatever
reason:
everyone
who's
really
in
the
network,
Automation
blogs
about
a
lot
works
for
companies.
You
know
that
dual
Network
automation
etc-
or
you
know
orgs
or
you
know
whatever
for
some
reason
Interop
is-
is
now
the
de-facto
home
of
where
they
all
congregate.
Every
year
and
Matt
went
this
year
to
represent
our
community
and
to
talk
to
people,
and
we
should
be
good
to
hear
a
status
on
what
cool
things
he
saw
and
stuff
like
that.
A
That's
something
we
want
to
cover
more
actually
on
the
stream
is
not
just
any
labs
but
taking
some
time
out
to
look
at
some
of
the
cool
projects
that
are
out
there.
Things
like
nor
near
and
netbox
and-
and
you
know
stuff
like
that,
because
there's
so
much
work
going
on
it's
you
know
it's
it's
worth
talking
about
right,
I
mean
we're
seeing
something
really
awesome
happening
in
the
network.
A
Engineering
space
people
are
starting
to
embrace
being
able
to
say,
hey,
you
know
what
I'm
just
gonna
make
the
tool
that
makes
sense
for
network
engineers
and
then
whatever
it
does,
that
that
tool.
That
does
the
thing
that
the
network
engineers
need,
they
they
put
it
on
github
and
they
they
start
building
a
community
around
it
and
there's
some
cool
things
that
people
have
done.
So
we
should.
We
should
be
I'm
sharing
that
especially
things
that
are
gonna,
be
we're
good.
There's
gonna
be
lessons
about,
instead
of
any
real
apps
yep.
B
A
So
so
we're
gonna
sign
off
I'll
give
the
standard
goodbye,
Lisa
Jim,
anything
you
want
to
say
no.
B
A
C
you
can,
you
can
follow
me
on
Twitter,
I'm,
Claude,
toad
and,
of
course,
follow
n
re
labs
at
and
re
labs
and
please
take
the
time
again
join
this
course.
Forum
join
our
discord,
chat
server
and
please
follow
us
on
Twitter
you're
watching
right
now.
So
in
that
YouTube,
that's
where
we
publish
our
recorded
videos.