►
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
Hello,
everyone
and
welcome
to
the
new
contributor
workshop
development
meeting
today
is
august,
the
third
2020.
A
just
this
general
guideline,
these
meetings
or
all
the
meetings
follow
the
cncf
code
of
conduct,
which,
in
general
just
means
be
excellent
to
each
other
yeah.
So
we've
got
quite
a
bit
of
items
on
the
agenda
today,
but
before
we
get
in,
is
there
anyone
who
anyone
here
who
hasn't
been
to
one
of
these
meetings
before
and
would
like
to
introduce
themselves.
B
I
can
introduce
myself,
I
am
kendall
nelson.
I
spend
most
of
my
time
working
in
the
openstack
community
doing
roughly
the
same
thing
that
you
guys
are
doing
here.
I
know
some
of
the
faces
in
here.
I
like
more
recently
have
gotten
involved
in
kubernetes
as
well
and
kind
of
trying
to
like
help
our
communities
bridge
between
one
another
and
like
learn
from
each
other.
So
I
figured
it
would
be
good
to
start
attending
some
of
these
meetings.
C
Cool
kendall
isn't
mentioning
it,
but
she's
probably
responsible
for
what
is
it
called
upstream
institute.
C
B
Yes,
openstack
upstream
institute
and
our
contributor
guide
and
on
a
couple
occasions,
I've
like
met
up
with
paris
and
one
of
our
like
mentoring
programs,
helped
inspire
your
like
contributor
ladder
thing
and
so
there's
kind
of
been
connection
and
back
and
forth.
Collaboration
already.
But.
A
Awesome
well,
it's
good
to
have
you
here.
Okay,
now,
let's
get
right
into
the
agenda
now.
The
first
item
we
have
is
tips
for
recording
video,
recording
or
questions
yeah.
C
So
that's
me
so
I
took
on
writing
a
video
recording
guide.
I
have
a
bunch
of
content
from
cncf,
I'm
just
waiting
to
use
that
from
their
guide
for
coupon
recordings,
I'm
just
waiting
for
permission
to
actually
copy
that
into
a
document.
That's
going
to
go
into
our
repo,
and
that
covers
most
things.
There
are
some
things
that
it
doesn't
cover
and
the
end
I
just
wanted
to
put
that
in
there
to
request
people
putting
things
in
there.
C
C
D
So,
especially
with
accents,
the
auto
subtitles
tend
to
not
work
well,
just
from
personal
experience.
The
other
thing
that
I
want
to
bring
up
is
accessibility
for
hard
of
hearing.
Folks,
like
is
there
a
way
we
can
like
get
a
sign
language.
You
know
box
if
we're
making
like
legit
instruction
videos
that
should
be
part
of
it.
D
E
It
would
also,
if
you
do,
asl
and
just
to
keep
us
internationally
focused
you're,
focusing
on
americans
and
anyone
who's.
Looking
at
it
as
josh
was
noting
they're
gonna
be
able
to
read
the
subtitles.
D
C
Okay,
that
was
my
only
question
other
other
than
you
know,
soliciting
people
to
work
on
this,
although
hold
back
a
little
bit,
because
I
expect
to
get
permission
to
paste
in
the
stuff
from
the
cncf
tomorrow
and
I
and
then
we'll
mark
it
up.
I
mean
something's
going
to
be
bigger
to
us
like
where
you
upload
and
paste
everything.
C
That
is
the
advantage
that
it's
going
into
a
website
that
already
has
a
translation
framework.
So
if
people
do
the
translation,
then
we'll
have
translations
for
that
by
the
way.
If
anybody
wasn't
clear
in
this,
what
we're
talking
about
is
the
basically
the
documentation
version
of
the
segments,
so
you
know
for
each
video
segment.
C
We
also
want
a
written
documentation
version
of
that
for
people
who
prefer
reading
things
to
hearing
them
and
the
and
and
that's
where
it's
going
to
go,
which
means
people
just
need
to
write
it
and
mark
down.
C
The
paris
was
asking
about
linking
to
the
documentation
we
already
have
when
that
documentation
covers
the
same
topics.
Yes,
but
we
really
want
this
oriented
around
the
specific
lessons
of
the
you
know
for
new
contributors
and
there's
we're
gonna
need
a
lot
of
additional
material
for
that.
C
F
Messy
okay,
at
least
for
the
the
long-term
goal
with
a
lot
of
the
contributor
guide
stuff,
will
probably
eventually
be
to
shift
it
over
to
the
contributor
site.
But
that
is
you
know,
maybe
sometime
next
year,
where
we
can
support
all
the
localization
stuff
easily
till
then
we
have
at
least
the
localized
versions
of
the
cheat
sheet
as
a
I
guess:
sort
of
stop
gap.
C
Yeah
the
yeah,
but
if
we
do
this
new
material
all
directly
in
the
contributor
site
repo,
then
we're
not
creating
additional
problems
for
ourselves
down
the
road.
The.
C
So
yeah,
so
one
of
my
questions
there
also
is
the
existing
segment
assignment.
Stuff
does
not
include
any
mention
of
writing
up
the
documentation
portion,
and
so
I
was
going
to
ask
do
we
want
to
add
that
to
the
existing
segment
issues,
or
do
we
want
to
create
a
separate
sort
of
mirror
set
of
issues
of
right
documentation
for
x.
C
C
Can
you
turn
this
into?
You
know
a
doc
page
version
and
get
additional
volunteers
that
way,
particularly
people
who
don't
feel
comfortable,
recording
video
or
aren't
set
up
for
it.
G
C
C
C
A
All
righty,
so
we've
got
the
the
segment
assignments,
but
next.
C
A
F
I
don't
think
too
many.
Yes,
too
many
people
have
taken
them.
I
know
jason
said
he
would
help
out,
but
hasn't
selected,
a
specific
one.
It
will
probably
be
at
least
two
weeks
before
he'd
be
ready
to
record
something
just
because
he's
also
going
through
a
job
change.
H
H
A
I
A
A
A
A
This
is
this:
this
is
the
trouble
like
five
different
people.
Okay,
excuse
my
rambling
and
stumbling,
but
this
is
the
draft
of
the
thing
we're
going
to
send
out
to
kaidev.
Well,
not
the
draft.
This
is
the
thing
we're
going
to
send
out
to.
A
C
Oh,
you
know
what
where's
the
oh
right,
yeah
you've
got
the
issue
link
in
there.
Yes,
that
is
correct.
C
D
So
I'm
going
through
some
of
those
issues
and
I'm
not
entirely
so
having
not
looked
at
them
before.
I
see
that
local
building
tests
have
like
four
separate
issues,
and
everything
else
is
pretty
great.
I
just
I
just
kind
of
want
to
know
what
the
difference
in
focus
is
between
the
four
those
four
issues,
in
particular.
G
C
Sure
the
I
we
allison
and
I
created
those
sort
of
segments
based
on
what
was
in
the
program
for
amsterdam
yeah,
and
we
chopped
it
in
to
left
it
chopped
into
four
segments
out
of
the
idea
that
hey,
we
don't
really
want
to
ask
anybody
to
do
two
and
a
half
hours
of
content
by
themselves.
C
The
number
four
is
the
build
and
test
that
would
have
gone
with
the
intermediate
track.
If
you
follow
me,
so
it's
like
a
more
advanced
hackery
session.
D
Sure
I
just
I
just
want
I
just
want
like
I
just
want
clear,
like
what
is
done.
Look
like
for
this,
like
what
is
the
end
goal?
The
other
thing
is,
is
I
don't
know
that
a
video
presentation
needs
to
be
two
and
a
half
hours
right,
because
it'll
it'll
look
a
little
bit
more
like
here's,
the
run
book
for
the
slides,
and
you
can
pause
the
video
and
go
with
your
own
content
at
your
own
pace,
yeah
right
so.
E
D
It'll
be
less
like,
oh
let's,
let's
take
it,
let's
tell
a
couple
jokes:
while
everyone
is
like
getting
their
stuff
together
or
or
hey,
let's,
you
know
it's
more
like
if
you're,
if
you're
having
trouble
with
this
pop
a
question
into
either
k
dev
in
the
chat,
I
mean
the
yeah,
the
developer
community
or
something
you
know
what
I
mean
like
it'll,
be
less
like:
let's
wait
until
everyone
has
pulled
the
images
and,
like
all
that
stuff,
it's
more
like,
we
should
have
frequently
asked
questions
selection
right
because
everyone's
doing
this
async,
so
we
should
have
a
frequently
asked
questions
for
this
kind
for
this
for
the
content
and
maybe
even
like
our
own,
I
don't
know
stack
overflow
page,
you
know
what
I
mean
like
the
contributor
workshop,
specific
stack,
overflow
or
or
or
on
slack
channel.
D
This
is,
this
is
actually
less
related
to
local,
build
and
test
and
more
like
in
general.
If
we're
making
this
async,
there
should
be
an
faq
and
there
should
be
instruction
frequent
instructions
on
where
to
go.
If
you
need
help
as
part
of
your
videos,
keep
that
in
mind,
and-
and
we
should
keep
in
mind
too-
that
it
doesn't
have
to
be
a
live
recording
of
watching
a
build.
A
You
can
just
go
from
the
start
to
the
finish
like
this
is
what
it
looks
like
before
you
hit
the
buttons,
and
this
is
what
it
looks
like
after
you've-
hit
the
buttons
and
waiting.
If
anything
doesn't
look
right
to,
you
feel
free
to
poison.
It
pause
now
and
just
have
a
re-look
over
your
work
kind
of
thing
and
then
at
the
start
and
the
end,
we
have
a
intro
kind
of
clip
like
welcome
back
to
new
contributor
workshop,
you
know
the
virtual
box
set.
This
is
where
the
faq
is.
A
C
D
C
Oh
damn
it
and
I
stopped
taking
notes
considered
everyone
else,
but
also,
I
would
like
to
see
you
create
an
issue
of
this
additional
material
that
needs
to
go
into
the
print
version
of
the
new
contributing
workshop,
because
you
mentioned
several
things
that
we
need
to
remember
to
put
in
the
print
version
that
are
not
going
to
be
videos.
E
We've
been
spending
a
bit
of
time
at
ii,
following
along
with
other
people's
presentations
and
videos,
creating
shared
pair
terminals
that
we
share
with
sometimes
everybody
in
the
meeting,
sometimes
just
a
few,
where
we
capture
org
files,
that
are
the
topics
of
discussion
and
the
code
examples
and
as
we're
going
through
when
we
say,
execute
this
code
block.
For
you
know,
cuddle
apply
or
whatever.
We
actually
capture
the
output
and
have
some
keystrokes
to
turn
that
into
markdown.
E
And
we've
we've
been
working
with
it
for
about
two
years
now.
So
it's
getting
more
and
more
solid
to
the
point
where
you
can
just
bring
up
a
kubernetes
cluster
and
helm,
helm,
install
right
and
then
just
attach
and
export.
The
markdown.
E
I
know
that
I'd
be
willing
to
allocate
some
of
my
team
towards
that
effort,
but
it
would
be
useful
if
there
were
other
community
members
that
were
willing
to
kind
of
pick
up
that
tool
as
well
and
look
at
just
doing
some
pipelining
around
those.
E
So
my
direct
output
like
right
now
seems
under
contributor
side,
content,
english
and
then
the
breaking
out
these
segments
into
the
doc
follow
through
based
on
what
we're
seeing
on
the
screen
for
this
first.
You
know
this
first
session
and
then
maybe
next
contributor
summit
having
those
org
files
be
the
basis
for
the
people
doing,
because
we
don't
want
to
change
a
whole
lot
here.
E
We
just
want
to
capture
things
in
a
way,
that's
consistent
when
we
spend
time
together
with
those
pair
sessions,
and
I
think
when
people
go
back
through
and
have
these
org
files
available,
bang
the
content
for
new
contributor
workshop,
we'll
have
more
people
being
able
to
follow
in
these
step-by-step
guides,
but
I
think
it
for
right
now
it's
a
wait
till
we
have
recordings,
go
through
those
recordings
and
generate
documentation.
E
E
I
guess
what
it
would
be
good
is
just
to
at
least
take
a
few
of,
and
maybe
in
particular,
the
the
build
and
local
ones,
those
one
through
four,
as
a
as
a
as
a
takeaway
is
walking
through
those
in
a
step
by
step
to
create
the
markdown
side
contributions
for
those
and
if
we
we
like
those
and
other
people
are
interested,
can
expand
it
beyond
those
four.
But
I
don't
mind
volunteering,
my
crew,
to
show
up
and
do
it
for
those
four
segments.
C
C
D
So
I
wrote
up
a
bunch
of
content
for
the
new
contributor
workshop
in
k
community
like
a
few
months
ago
under
events
I
think
or
maybe
mentoring.
I
think
the
whole
folder
got
moved.
D
Anyway,
I
can
look
at
the
local,
build
and
test
and
just
kind
of
break
it
out.
Look
at
the
slides,
because
I
have
more
context
here
right.
It's
like
it
just
says,
look
at
these
slides
and
it's
just
like
well,
what
am
I
signing
on
for
here,
so
I
can
do.
D
C
A
Yeah,
I'm
kind
of
like
we'll
send
the
letter
out
to
kadev
and
then
just
see
what
doesn't
end
up
getting
claimed
and
help
peop
help
guide
faults
through
the
through
the
process
of
making
these
videos,
because
I
I
know
I
I
don't
think
I'm
gonna
be
able
to
pick
up
heaps
of
stuff
because
I'm
I'm
planning
to
move
in
like
a
couple
weeks
so
yeah.
I
know
I'm
crazy,
crazy.
A
A
The
face
of
shock
I'll
try
pick
a
safe
district.
A
Well,
thank
you.
Everyone
for
coming
along
and
we'll
see
you
the
same
place
same
time,
two
weeks
from
now.