►
From YouTube: Kubernetes SIG Contributor Experience 20190403
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
D
E
E
A
A
A
Right
so,
let's
launch
into
our
recurring
meeting
items
so
first
office
hours,
George.
F
F
So
CNC
at
marketing
can
help
us
out
so
that
doesn't
change
people
could
subscribe
instead
of
just
like
the
main
YouTube,
you
know,
YouTube
channels
going
live
and
then-
and
they
also
set
lets
us,
set
the
descriptions
and
all
that
stuff
ahead
of
time
which
the
way
it's
set
up
now
when
you
go
live,
you
have
to
like
do
the
setting
and
stuff
so
I
think
that
that
will
help
some
I
started
to
work
moving
office
hours.
That
way
and
Paris's
asking
me
questions
about
being
our
contributors,
so
I
think
that's
going.
Ok,.
E
Had
our
April
edition
today,
and
then
we
have
another
one
at
one
o'clock
today,
everything's
going
well
so
well.
Actually
that
I
have
we
have
like
Cove
a
stores
lined
up
for
at
least
every
session
for
the
next
five
months,
which
is
nice.
We
definitely
have
content,
and
today
we
had
it
being
75
total
viewers
and
like
20,
that
stayed
with
us
forever,
meaning
like
the
whole
time,
which
is
really
super
cool
and
bad
Valerie
and
Bob
and
George
on.
E
So
we
had
like
a
small
group,
but
we
still
got
it
done,
but
everything
is
going.
Super
awesome
for
me
they're
contributors
and
if
anybody
here
would
like
to
come
on,
definitely
welcome
it
we're
full
for
this
afternoon,
but
we
do
have
a
slot
available
for
the
7:30
a.m.
Pacific
on
May
1st
pre
cube
con
edition.
What's
the
update.
F
Next
community
meeting
George,
how
are
we
looking
for?
We
are
all
scheduled
for
host
until
after
Barcelona,
so
good
job.
Everyone
like
volunteering,
it's
everything
is
set
for
this
week.
I
think
that
Val
who
I
seed
has
joined
the
call
foot
is
gonna
host
her
first
one
this
week.
I
did
make
a
mistake
that
I
am
going
to
note
down
in
the
document
is
when
we
scheduled
the
retro
I
forgot
to
move
the
demo
to
not
be
on
the
retro,
so
they
showed
up
and
we're
p.m.
when.
Is
it
our
turn?
F
So
since
it's
the
beginning
of
the
release
cycle,
I'm
gonna
sneak
in
two
demos
this
this
Thursday,
so
that
because
they
were
on
Indian
time
and
it
was
like
11:00
p.m.
and
I
was
like,
oh
god,
what
have
I
done
to
you,
so
we're
gonna
slot
them
in
since
early
I'm,
expecting
the
release
status
to
be
really
short.
This
early
in
the
cycle,
so
we're
gonna
have
two
demos
for
this
Thursday
and
then
everything
should
be
set.
F
Chris
and
I
are
working
with
vow
to
make
sure
that
she
has
everything
she
needs
to
be
successful.
On
Thursday
yeah.
E
Parasurama
anybody
yes
mean
some
tips.
Anybody
have
any
tips
for
those
that
don't
know
what
I'm
talking
about
or
what
we're
talking
about.
Every
so
often
we
send
the
chairs
and
the
tech
leads
it's
over
75
people
between
4
&
5
tips
that
they
need
to
share
with
our
maker
communities
all
at
once,
and
then
they
can
get
that
word
out.
Of
course,
this
week,
we'll
also
have
the
contributor
summit
information
it'll.
Have
it
until
we're
done
pretty
much,
so
you
can
talk
on
that.
E
Diver
yeah
I
can
definitely
remind
them
to
tighten
that
up
too.
I
did
see
that
the
the
maintained
nerve
track
on
the
cube
con
schedule
is
a
little
messy
because
you
can't
tell
which
project
it
is
based
on
the
inch
and
deep
dive.
So
I
was
gonna,
also
reach
out
to
CN
CF
to
see,
if,
like
that,
could
be
more
clear,
but
I
think
that
also
could
just
be
the
chairs
and
tiel's
changing
their
titles.
So
I'll
do
that
as
well
thanks
for
reminding
me
of
that.
H
Right,
I'll
start
so
for
Barcelona
we
had
our
meeting
on
Monday
Gwen
walked
through
kind
of
the
agenda,
for
the
entire
day
walked
through
the
101
and
the
201
levels,
they're
looking
really
good.
We
talked
about
code
based
tours
earlier
here
on
the
call
and
that's
actually
something
that
Wayne
would
like
to
have
in
the
201
session
there,
Gwen
I,
don't
know
if
you're,
yes,
you
are
on.
We
want
to
talk
about
that.
Hey.
I
Yeah,
so
one
thing
that
we
haven't
been
doing
for
the
new
contributor
workshop
is
a
code
base
walkthrough,
and
it's
been
something
that
people
have
been
asking
for
and
I
think
it
would
be
really
helpful
to
have
for
201
contributors,
because
while
they
have
the
ideas
that
they've
contributed
to
open-source
before
we
have
a
pretty
giant
monolith
and
kind
of
just
pointing
people
at
the
six
yeah,
no
and
patting
them
on
the
shoulder
and
saying
good
look,
it
might
be
nice
if
we
could
really
just
have
a
live.
I
Okay,
sorry
that
you
just
filled
my
screen
and
I
was
like
oh
it's
anyway,
yeah,
so
I
I
would
love
to
be
able
to
give
the
walkthrough
or
have
someone
give
the
walkthrough?
If
no
one
is
available,
I
am
more
than
happy
to
just
you
know.
Maybe
somebody
would
be
willing
to
give
me
the
walk
free,
so
I
can
pass
on
that
knowledge.
I
I
struggle
just
the
same
as
other
contributors,
so
I
see
a
plus-one
from
Valerie
can.
E
I
give
you
the
link
to
the
clip
that
we
have
for
the
codebase
tour
kubernetes,
the
kubernetes
from
meter
contributors
and
then
let
me
know
what
you
think
is
missing
from
that
and
then
also
Stefan,
who
did
that
code
based
tour
could
probably
do
it
again.
Some
kind
of
like
longer
version
yeah,
I'm
gonna,
get
the
link
for
that
right
now
and
then
tell
me
what
needs
to
be
modified
or
edited
or
go
into
more
deaths,
etc.
Sure.
F
C
E
C
I
Yeah
I
mean
and
again
there's
no
reason
that
shouldn't
be
me
I,
just
I
would
like
to
delegate
if
possible
and
also
I
am
not
that
familiar
with
the
code
bases.
Other
folks,
who've
spent
more
time
on
KK.
It's
just
a
reality.
I
F
I
Yeah
or
if
somebody
can
give
the
give
the
walkthrough
and
is
there
and
available
in
Monday,
so
you
know
either
one
of
those
is
fine,
I'm
happy
to
do
it.
It
might
be
cool
to
have
someone
else.
Do
it
either
when
I'm
flexible,
I'm,
not
trying
to
be
wishy-washy,
I'm
just
trying
to
be
flexible.
Apologies
if
that's
confusing
so.
E
A
H
Great
thinking
so
other
than
that,
we
also
talked
about
volunteers
for
Barcelona's
contributor
summit,
because,
of
course
this
is
all
bar
all
run
by
us
volunteers.
We
now
have
five
volunteers
who
are
workshop
assistants.
Thank
you
so
much
to
to
everyone
who
signed
up
there,
we
have
two
room
facilitators.
We
definitely
need
more.
H
So
a
room
facilitator:
this
is
going
to
be
for
the
cig
face-to-face
rooms.
We
have
six
different
rooms
for
six
to
be
in.
We
most
likely
will
divide
them
up
in
a
morning
and
an
afternoon
session,
depending
on
how
many
six
we
actually
get
to
sign
up.
I
know,
Paris
and
others
are
doing
a
phenomenal
job
in
actually
talking
to
the
stakes
there
so
for
a
facilitator,
you're,
essentially
making
sure
that
no
stakes
are
too
noisy,
making
making
sure
that
the
room,
sound
level
is
proper,
making
sure
that
everyone
knows
where
to
go
when
so.
H
If
you're
looking
for
sig
UI,
you
need
to
be
in
that
room
at
this
time,
so
people
don't
get
lost.
So
it's
going
to
be
pretty
simple,
making
sure
that
those
things
have
what
they
need
as
well.
If
they
need
anything
specific,
maybe
we
can
get
it
yeah.
So
pretty
simple,
hang
out
with
with
a
bunch
of
cool
people
from
six.
A
All
right,
let's
jump
into
the
project
board,
then.
E
J
C
E
E
Never
did
respond
to
anybody
who
left
an
email,
with
the
exception
of
the
fact
that
they
got
a
swag
item.
I
did
give
them
the
schwag
I,
but
the
problem
was
people
responded
with
emails
because
they
may
have
either
asked
a
question
or
something
so
I
don't
know
if
he
lot
of
cycles
to
like
respond
to
other
people
is
sort
of
as
Q&A,
but
that
would
be
super
helpful,
but
yet
I
think
the
large,
the
largest
thing
that
we're
hanging
on
is
the
blog
posts.
A
E
E
Let's
see
yeah
we
so
we've
got
the
PR
in
flight
for
a
new
contributor
ambassador
PR
inflate
from
nikita
for
triage
captain
and
PR
Wranglers
retrospective
leads
will
most
likely
go
to
sick
p.m.
now.
Bloggers,
social
media,
other
marketing
stuff,
is
PR
in
flight.
The
one
thing
that
we
have
not
done
is
a
a
packer
EU
contra
backs
the
liaison
team.
That
would
help
with
mirroring
programs
and
also
help
us
stand
up
more
hours
of
our
programs
in
those
locations.
E
D
F
E
E
E
It's
all
about
ownership
and
the
top
line
owners
file.
So
it's
like
about
directory
access,
so
I
think
all
the
docs
that
pertain
to
YouTube
and
YouTube
streaming
should
live
in
the
YouTube
guide
in
the
same
places,
the
YouTube
guidelines
right,
the
people
that
are
treating
the
guidelines
are
also
the
people
maintaining
the
thing.
Okay,
so.
F
K
Sure
and
Josh
has
his
hand
up.
Yeah
I
have
a
couple
of
really
short
things
just
wanted
to
inform
the
congruence.
These
are
going
on
so
I
have
a
draft
of
a
registration
form
for
Shanghai
op
like
Barcelona,
we're
using
a
separate
registration
on
the
no-shows,
the
it's
currently
being
reviewed
by
everybody
involved
with
the
high
and
would
go
out
for
translation
today
and
then
at
that
point,
CN
CF
will
run
it
as
soon
as
they
can
put
it
up.
K
K
It'll
be
before
the
end
of
the
previous
movies.
The
one
thing
in
relation
to
that
was
that
we
moved
the
registration
form
from
SurveyMonkey
to
a
Google
Doc,
because
the
problem
with
Survey
Monkey
is
its
CN.
Cf
s--
account
it's
restricted
access.
It
means
that
we
can't
share
the
applications
with
the
whole
release
team
I.
L
C
Not
you
can't
actually
do
collaboration
with
with
Survey
Monkey
through
that
way.
It's
essentially
a
shared
account
that
a
few
people
know
the
credits
to
to
log
into
the
one
way
that
you
can
pass
like
a
survey
over
is
you
can
create
the
survey
like
you
have
access
to
all
the
options
as
a
normal
user,
and
then
you
can
share
that
with
the
official
account
and
then
it
can
send
out
and
manage
the
results
actually.
K
C
L
K
Don't
honestly
think
that
using
Google
Forms
is
seriously
a
problem.
The
Chinese
folks
we've
had
who've
been
willing.
Who've
been
interested
in
shadowing
the
release.
Team
seem
to
be
able
to
get
enough
access
to
Google
Docs
to
fill
out
a
form,
and
otherwise
we
say
you
know
if
you
don't
have
any
access
to
Google
Docs
email,
us.
K
E
B
F
F
So
I've
been
thinking
a
lot
about
the
last
six
months
of
what
we
do
been
doing
mean.
Could
try
max
and
I
would
like
to
propose
some
changes
to
the
Charter.
However,
they
are
very
rather
extreme
is
a
good
way
to
put
it
so
I
kind
of
bluntly,
just
butchered
the
thing
and
figured
let's
talk
about
it
or
whatever.
F
So
what
I
kind
of
wanted
to
do
like
I
feel,
especially
with
all
the
slack
stuff,
that's
been
happening
lately
that
we're
turning
into
sick
pager
duty
and
what
I
want
to
do
is
explicitly
list
out
more
in
our
Charter.
What
we're
responsible
for,
responsible
for
and
not
responsible
for,
and
then
go
to,
steering
and
say:
hey
these
things
are
important.
They're
great.
The
project
needs
for
them
to
happen,
but
it's
not.
We
don't
want
this
to
be
part
of
contributor
experience.
F
We
could
just
hand
that
over
to
somebody
else,
so
that
we
can
do
contributor
experience
style
things
as
opposed
to
you
know,
trying
to
find
moderators
and
doing
all
that
sort
of
yeah
or
whatever
it
ends
up
being
the
reason
I
did
it
as
a
PR
is
because
it
kind
of
forces
us
to
deal
with
the
issue
and
then,
if
we
put
it
on
on
steering's
like
card
project
thing,
then
they
have
to
talk
about
it
because
steering's
deal
is
like
they're
kind
of
role
is
to
ensure
that
each
thing
that
the
community
needs
is
staffed.
F
It
has
a
group
and
I
think
if
we
were
to
say
you
know,
we
would
like
to
refocus
on
the
things
that
matter
for
us.
Keep
us
being
contributes
about,
contributes
all
the
stuff
is
important.
I'm,
not
saying
it's
not
important.
We
just
need
to
be
more
explicit
and
split
it,
so
it's
more
manageable
and
scales
easier.
F
So
that's
why
I
kind
of
like
I
want
to
get
it
that
card
and
steering
in,
like
you
know
so,
however,
I've
been
butchering
it
as
I
going
along,
so
the
diff
in
the
review
is
kind
of
worthless,
so
I
just
had
the
full
document
here,
but
the
big,
the
big
thing
is
things
like
slack
for
moderation,
I
just
say:
CN,
CF
and
Chris,
so
I
saw
it
to
Chris
and
a
check
and
kind
of
you
know.
Let
Dan
know
that
I
was
kind
of
proposing
this
really
dull
butter
knife.
F
You
know
they
don't
do
moderation,
that's
not
their
jam.
So
I
did
find
out
after
getting
inspired
by
Hamilton,
that
there
is
precedence
to
this.
So
back
in
the
day
when
Docs
was
kind
of
like
they
didn't
have
enough
volunteers
and
things
like
that,
CN
CF,
you
know,
didn't,
go
out
and
just
hire
a
bunch
of
technical
writers
to
fix
Docs.
F
They
kind
of
contractors
Zac
to
kind
of
build
a
scalable
program,
and
then
they
approached
CNC
a
member
companies
and
said
the
project
needs
this
stuff
done
either
staff
it
or
you're
gonna
pay,
CN
CF,
and
we
will
get
a
contractor
and
that's
how's
that
kind
of
started,
and
then
he
built
up
this
whole
scalable
program.
So
I'm
thinking
the
approach
might
be
two-headed
where
it's
like.
F
F
D
F
E
E
F
So
I
agree
with
that.
It's
not
like
I'm
gonna
go
and
turn
off
slack.
However,
a
lot
of
these
things
that
you
have
been
discussing
has
been
meetings
with
them
that
we've
had
over
the
years
and
things
like
that
I
say
the
last
three
months
or
yeah
and
the
well
yeah.
Okay,
what
I'm
trying
to
say
is
approaching
steering
and
kind
of
like
writing
those
out
and
like
force
it
as
an
issue
and
then
ask
him
to
time
box
it.
F
Just
be
like.
We
are
at
a
breaking
point,
I
feel
like
we.
We
have
our
fingers
in
holes,
especially
things
like
slack
like
I
get
the
feeling
that
people
think
slack
is
fixed.
Slack
isn't
fixed
the
people
that
were
helping
before
just
started
to
donate
time
and
there's
still
very
large
institutions
and
organizations
out
there
that
are
still
not
chipping
in
so
what
I
kind
of
want
to
do
is
be
like.
Okay,
no
one
else
is
gonna
chip
in
Dan
Chris.
Can
you
raise
the
taxes
kind
of
thing,
I.
E
F
Like
I
think
when
I
was
chopping
up,
all
the
bits
like
the
one
bullet
I
saw
and
I
didn't
write.
It
I
think
this
was
you
Paris,
like
the
number
one
thing
help
on
board
new
and
current
contributors
into
the
culture,
workflow
and
CI
of
our
contributor
experience
here.
The
contributor
guide,
other
related
documentation,
contributor
summits
and
programs
tailored
to
onboarding
mentoring.
F
You
know,
and
all
that
stuff
like
I,
feel
like
it
fits
not
related
to
that,
like
I
feel
like
we
should
say,
steering
it
it's
kind
of
your
job
to
ensure
that
whether
the
project
needs
is
fully
staffed.
We
recommend
a
new
say.
You
know
we
I
mean
the
time
box
it
like
I'm,
not
saying
we're
just
gonna
hard
cut
off,
because
we
have
to
do
this.
F
We
can't
abandon
slack,
that's
not
what
that
what
I
want
to
do,
but
what
I
want
to
say
is
like
there's
an
opportunity
there,
and
if
we
can't
get
staffing,
we
would
like
to
approach
CN
CF
on
what
it
would
take
to
have
a
full
time
community
manager
to
help
do
this
beyond
what
a
is
doing
like
the
rest
of
us.
He
also
can't
we're
all
kind
of
maxed
out.
Is
the
pitch
I
kind
of
want
to
do?
You
know
I,
don't.
D
F
And
propose
other
SIG's,
it's
it's
steering's
responsibility
to
ensure
that
there
are
organizations
within
kubernetes
that
we
need
like
it's,
not
our
job,
to
ensure
sake,
user,
a
contributor
or
user
experience
or
whatever
and
launches
properly.
I.
Think
our
job
is
to
denilla
eight,
what
we're
responsible
for
and
what
we're
not
responsible
for
and
a
steering
our.
D
E
E
F
E
D
D
A
A
So
it
sounds
like
we're
wanting
to
put
this
proposal
back
in
front
of
the
CNCs
in
a
way
that
reinforcement
that
we
are
very
serious
about
this,
leaving
our
set
of
responsibilities
and
but
also
proposing
a
path
forward
as
well,
not
just
saying
not
us
and
letting
the
chips
fall
as
they
may
so.
Paris
is
envisioning
a
proposal
for
new
sig.
If
I
heard
George
correctly,
he
was
proposing
talking
to
the
CNCs
about
steering
sorry
steering
about
hey
like
if
we
don't
have
the.
A
A
So
it
sounds
like
we
kind
of
have
two
different
proposals
for
like
steps
forward.
So
maybe
we
should
take
this
to
the
mailing
list
and
see
who,
if
there's
more
traction
behind
either
creating
a
new
cig
or
letting
are
going
to
steering
and
proposing,
steering
talk
to
the
scenes
yeah
about
building
out
a
new
program
and
soliciting
members
for
aid,
because
I'm
looking
at
their.
D
F
I
guess
yes
is
so
if
I
look
at
steering's
Charter,
it
says
through
the
chartering
review
process,
which
I
guess
that's
what
I'm
asking
for
a
Charter
Review.
We
our
review,
yeah,
delegate
ownership
of
responsibility
for
an
authority
over
areas
of
the
project
to
specific
entities
right.
What
I
want
to
say
is
we
feel
or
what
I
want
to
propose?
Is
we
feel
like
these
things
aren't
working
out
for
us?
We
would
like
to
delegate
ownership
of
these
sections
to
another
group.
F
A
F
Sara
comes
back
and
says
you
know
what
this
is
your
responsibility
deal
with
it.
That's
fine
like
then,
then,
we'll
know
for
sure,
and
then
I
will
know
that
you
know
I'll
have
to
be
a
slack
admin.
You
know
but
like
I
feel
like
we
need
to
tell
steering
that
this
like
this
is
like
a
huge
sort
of
press
and
burn
out
for
a
lot
of
people
and
I
know
I'm,
not
alone.
F
D
D
A
So
maybe,
instead
of
saying
you
know,
here's
our
problem,
here's
some
possible
solutions.
What
do
you
think?
Maybe
resent
it
as
a
you
could
have
this
or
you
can
have
this,
but
maybe
we
don't
leave
it
as
open-ended
I.
Think
I
made
that
suggestion
and
chat
and
I
thought.
That
was
like
a
super
good
idea
that
we
we
present
them
with
a
limited
set
of
options,
and
then
we
tell
them
to
choose
from
those.
F
F
L
L
The
official
way
like
the
appropriate
and
all
the
other,
all
the
cnc
of
projects
I'm
doing
this-
is
that
people
who
are
mentioned
in
official
series
of
maintenance
ways
able
to
submit
the
service
desk
teachers.
To
be
honest,
and
after
that
conversation
with
service
desk
or
so
hinder,
like
some
specific
questions,
so
we
with
kubernetes
project,
we
have
two
big
entities
of
people
who
are
able
to
do
it.
L
It's
the
steering
committee
and
it's
the
group
of
people
who
are
listed
in
the
owners
file
of
communities,
community
recon,
that
are
those
people
who
are
defect:
communities,
community
men,
communities,
community
ventures.
Most
of
these
people
are
present
at
the
car,
so
you
also
evoked
some
proposed
is
to
see
and
surf
Westeros
disk.
It
is
same
time
as
well.
Larry
mentioned
its
it's.
The
really
good
idea
to
write
down
what
the
communities
community
again
do
here.
What
who
are
there
other
people
who
can
do
it
besides?