►
From YouTube: [SIG ContribEx] Weekly Meeting 20210818
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
august
18th
installment
of
the
kubernetes
sid
contributor
experience
meeting
I'll,
be
your
host
allison,
just
some
general
house
keeping
before
we
get
right
into
the
deeper
things
we
all
abide
by
a
code
of
conduct
here.
So
in
short,
that
just
means
be
excellent
to
each
other,
so
yeah
and
if
you
could
add
yourself
to
the
attendees
under
meeting
notes,
that'll
be
awesome.
A
I
see
a
lot
of.
I
see
a
lot
of
new
faces
on
the
line,
so
I
think
it'll
be
kind
of
good
to
do
like
a
round
of
introductions
so
I'll
I'll
go.
First,
I'm
alison,
I'm
elsa
downey,
I'm
a
co-chair
of
kubernetes
sig,
contributor
experience
and
based
out
in
london
and
yeah
I'll
pass
the
baton
on
to
dawn.
B
C
Hi,
I'm
josh
burkus
been
involved
with
contributor
experience
for
a
long
time.
I
work
on
mentoring
and
a
few
other
things.
I
also
work
at
red
hat
and
I'll
pass
it
off
to
mottov.
D
Hi,
my
name
is
madoff.
I
I
do
small
things
in
the
community,
but
I've
been
involved
with
contrabex
for
about
three
months
now.
This
is
my
third
meeting
here
with
you
and
I
recently
started
working
with
vmware
and
like
full,
full
time
on
upstream
kubernetes.
So,
hopefully
I'll
get
to
see
more
of
you
often
that's
awesome
I'll,
pass
it
off
to
kim.
First,
okay,.
E
Hi,
I'm
kim
I'm
a
developer
advocate
at
digitalocean
and
like
mother,
I'm
sort
of
new
to
coming
to
these
meetings.
I
think
this
is
my
third
one,
but
hoping
to
get
more
involved
in
contributing
to
kubernetes
and
just
knowing
the
community
so
matthew.
Have
you
gone
already?
I
I
came
in
late.
I.
F
Didn't
go
yet:
okay,
all
right!
So
I'm
marty,
I'm
new
to
the
kubernetes
community
and
contributor
experience.
I
this
is
my
first
meeting
and
I'm
interested
in.
I
guess
learning
more
about
contribute,
experience
and
starting
somewhere.
So
I
think
this
is
a
good
place
to
start
before
I
try
working
on
upstream
prs
later
this
year.
Let's
see
I
work
at
vmware
and
I'm
based
out
of
seattle.
G
G
I
think
sedev
is
the
last
next
person
to
go
on.
H
I
work
at
ibm
in
north
carolina
and
I'm
an
existing
contributor
to
kubernetes
working
on
it
for
for
four
years
now
contributing
to
various
parts
on
cloud
provider
side
and
I'm
also
one
of
the
maintainer
for
fcd
project.
H
A
Oh
and
I
believe
the
last
person
on
the
line
to
introduce
themselves
have
we
had
wait.
We've
got
two
people
left,
I
think
anad
and
sir
anna
next.
I
guess
yes,.
J
Hey
hi
hamano,
I'm
based
in
france.
I've
been
in
the
community
for
three
years
now,
I'm
the
co-chair
of
koi
ketan
for
working
group.
I'm
a
release
manager
associate
I'm
also
in
country
bus
as
registration
lead.
K
Hi,
my
name
is
nigel.
I
haven't
been
to
one
of
these
meetings
before
I
saw
the
github
issue
looking
for
folks
to
help
out
a
coupon
with
the
contributor
or
the
contributor
summit,
and
that's
how
I
got
found
out
about
this
place.
I'm
a
community
manager
over
at
vmware-
and
I
very
recently
found
out
about
this
meeting
which
I'm
in
the
car
currently
so
yeah
hello,.
D
I
think
deba
is
left
yeah
yeah
hi,
I'm
deva
I'm
from
india.
So
basically
I
just
recently
started
to
contributing
to
contributes
and
presently
working
with
paris
and
regarding
the
annual
contributors
meeting
doc
and
we
are
working
on
releasing
some
of
the
tweets.
So
I'm
regarding
that
document,
some
doubts
and
I
want
some
reviews
of
new
guys
so
yeah
this.
A
Cool
so
yeah
it's
a
pretty
packed
call
today.
Thank
you,
everyone
for
coming
along,
so
with
all
that,
let's
get
right
onto
the
agenda,
so
we've
got
first,
we've
got
events
office
hours-
I
don't
see
pop
or
raw
code
on
the
line,
but
does
anyone
have
any
updates
about
office?
Hours
have
heard
anything
about
that.
A
It's
like
that
has
no.
Next,
we
have
the
community
meeting.
I
think
it's
still
in
the
same
from
last
time
same
state
as
last
time
we
discussed
it.
A
So
august,
being
the
release
retro,
I
don't
see
laura
on
the
line,
but
does
anyone
have
any
updates
around
the
community
meeting.
A
All
right,
contributor
summits-
I
wasn't
at
the
last
summit
staff
meeting,
but
so
if
anyone
here
on
the
line
was
at
that
meeting
could
fill
us
in.
That
would
be
awesome.
L
I
was
there
gotta
remember
what
happened,
though
you
bring
up
the
notes.
A
Awesome
so
also,
I
I
noticed
a
bunch
of
people
on
the
line
earlier
were
saying
they
want
to
get
involved
with
contributor
summit
and
all
that
there
is
a
separate
meeting
that
goes
on
at
mondays.
A
At
11
a.m,
pacific
time
so,
and
that
that
that
meeting's,
more
focused
around
contributor
summit
I'll
put
a
link
to
the
notes
for
that
meeting,
which
has
all
the
the
invite
and
the
meeting
info
there.
I
believe
so
I'll
post,
that
is
there
still
space
for
folks
to
help
out
on
site.
I
believe
this
there
should
be
space.
It's
just
a
case
of
like
what
we're
still
planning
out
what
we're
doing
a
lot
so.
A
Oh
beans,
we've
got
mentoring,
meet
our
contributors.
We
haven't
had
one
of
these
in
a
while
needs
to
get
rescheduled
onto
that
calendar.
There's
the
g
suite
migration
stuff
that
I'm
a
bit.
I
need
to
catch
up
on,
what's
happening
with
that,
so
that
we
can
get
the
calendar
invites
out.
So
there's
that
does
anyone
have
any
information
around
meet
our
contributors?
Any
updates.
L
There
was
some
great
discussion
about
meet
our
contributors
in
the
marketing
team
meeting.
Last
week
we
had
some
folks
who
had
started
an
effort
to
do
an
apac
focused
meet
our
contributors
thing
it
sounded
like.
Maybe
they
were
going
to
target
a
blog
post
style
for
that
for
the
apac
focused
meet
our
contributors,
but
they
had
started
this
effort
in
january
of
2020
and
then
it
kind
of
got
left
alone
for
a
while
and
they
were
coming
back
to
it.
L
So
it's
I,
I
told
them
that
they
should
probably
connect
with
paris,
and
there
was
some
conversation
going
on
on
slack
about
what
they
were
going
to
do
next
for
that
effort,
so
exciting.
A
Yeah
that
that
sounds
that
sounds
exciting
yeah.
Definitely
if
they
need
help
with
that
with
the
media
contributor
stuff.
I
think
definitely
like
raising
a
message
like
a
call
for
volunteers
out
onto
the
mailing
list
for
just
more
stories
and
things
and
getting
it
in
terms
of
a
blog
post
thing
into
the
contributor
site.
As
a
blog
post,
I
think
it
shouldn't
be
too
difficult.
Yeah
yeah,
we
said.
L
L
L
We
said
we'd
be
happy
to
help
them
through
that
so
they're
trying
to
work
out
within
their
own
group,
who's
gonna
do
what
and
what
they
want
it
to
look
like,
and
then
they
were
gonna
come
back
to
us
with
more
information.
D
We
have
an
organized
effort
now,
like
we
are
trying
to
reach
out
to
specific
contributors
or
related
to
specific
countries.
We
have
made
an
async
google
form,
actually
that
form
was
made
last
year
by
number
one
and
we're
using
that,
and
also
we
have
a
lot
of
information
that
was
already
collected,
and
we
are
just
you
know
like
moving
forward
on
basis
of
that,
and
we
will
be.
D
You
know
we
are
dividing
it
on
the
basis
of
two,
like
a
part
of
a
group
of
people
will
be
working
on
collecting
the
inputs
from
the
contributors
and
another
group
will
be
working
on
documenting
the
whole
thing.
We
now
plan
to
release
blogs
according
to
country
like
the
countries
that
come
under
apac
also,
the
most
difficulty
that
now
we
are
dealing
with
is
on
the
base
of
language,
because
you
know
some
countries
are
not.
D
The
contributors
are
not
native
english
speakers,
so
we
also
need
to
get
that
kind
of
speaking
group
coming
up
and
helping
us,
so
we
will
be
reaching
out
people
soon
and
now
we
are
just
organizing
thing
and
today
only
I
think
got
back
on
the
questions
we
had
and
even
like
in
the
github
that
is
getting
active.
Now
people
coming
up
a
lot
of
people
have
no
come
up
to
help
us
so
yeah.
That
part
is
going
on.
A
Awesome
thanks
for
the
update,
so
that
sounds
like
it's
all
coming
along,
really
well,
look
looking
forward
to
see
the
blog
posts
and
stuff
come
along
next.
Next
we
have.
We
have
playground,
google
summer
of
code
outreachy
all
that
cyano
stuff
ehor
any
updates
around
there,
lfx
and
stuff,
like
that.
M
Yeah,
a
quick
update
about
google's
room
of
code
first
world,
so
we
are
at
the
final
stage
and
we're
actually
at
the
stage
where
students
are
required
to
to
provide
their
feedback
and
to
fill
out.
The
final
revelation
forms
in
a
next
week
or
so
we'll
also
receive
the
similar,
the
final
revelations
from
mentors
as
well.
So
by
the
end
of
the
month,
we
will
have
the
final
results
about
google
summer
call
2021
lfx.
M
So
the
summer
cycle
is
ongoing
and
by
the
end
of
september,
we'll
have
the
final
results
about
it
and
on
lfx
fall
cycle
with
which
we
are
currently
kicking
off.
We
are
actively
accepting
mentorship
candidates
to
participate
in.
So
if
anybody
on
this
call
wants
to
participate
in
lfx
mentoring
as
a
mentee
or
if
you
know
any
people
who
are
willing
to
you,
have
any
friends
or
so
so
it's
right
time
to
share
this
across
across
these
groups.
So
we
are
accepting
accepting
applications
until
the
end
of
the
current
week.
M
We
have
a
few,
I
believe
we
have
three
projects
proposed
by
kubernetes
and
we
also
have
other
opportunities
with
other
cncf
projects.
Some
of
them
are
also
related
to
kubernetes
directly.
M
C
Yeah,
as
for
outreachy,
we
haven't
decided
whether
we're
doing
outreach
yet
next
term.
We
don't
currently
have
any
projects
set
up
for
outreachy,
partly
because
this
cycle,
outreachy,
lfx
and
gsoc,
tend
to
are
kind
of
coinciding
so
likely.
What
we'll
end
up
doing
is
skipping
the
cycle,
because
you
know
we
as
a
project
only
going
to
mentor
so
many
people
at
one
time.
A
Oh,
which
brings
us
to
our
next
item
contributor
workshop,
no
updates
from
me
on
this
front,
so
yeah.
A
L
Sorry,
it
takes
me
a
minute
to
find
mute.
Sometimes,
as
I
mentioned,
we
had
a
lot
of
fun
in
the
marketing
meeting.
Last
week
we
had
a
discussion,
of
course
about
the
meet
our
contributors
stuff.
It
was
exciting
to
see
everyone
there
and
let
me
bring
up
the
notes
to
remember
what
else
we
talked
about
in
that
meeting.
L
L
And
we
have
a
couple
of
sig
profile,
blog
posts
which
are
on
their
way
to
the
blog
one
of
them,
I
think,
is
in
a
pr
now,
which
I
need
to
check
back
in
on
for
sig
node
and
then
there's
another
one.
L
A
Oh,
thank
you
very
much
caslin
for
the
update.
Next
we
have
next
items
on
the
agenda
contributor
documentation.
I
don't
think
we've
got
any
updates
around
this
so
far
and
then,
after
that
github
management
does
anyone
have
any
updates
around
github
management.
D
Actually,
I
had
an
update
for
contributor
documentation,
so
I
think
around
a
few
months,
back
or
a
month
back,
there
was
someone
who
came
up
in
sick
architecture
and
like
pointed
out
that
our
definitions
of
a
few
api
terminologies,
like
science
resources,
they
were
differing
in
the
official
docks
and
things
like
developer
documentation
under
cig
architecture
in
gay
community.
D
So
then
tim
came
forward
and
suggested
that
we
document
this
under
kubernetes.dev
as
like
a
main
source
of
truth
and
like
this
is
sort
of
develop
a
documentation
and
then
reference
this
or
give
a
summary
of
this
in
the
official
docs.
D
But
so
I
was
trying
to
drive
that
for
a
while,
but
I
kind
of
lost
track
and
I
wanted
to
take
that
up
back
up
back
up
again.
So
I
wanted
to
ask
what
repository
would
should
I
like
create
an
issue
and
to
like
maybe
help
track
this
so
under
a
community
or
is
there
something
else
that
I
could
additionally
do.
A
A
For
the
best
kind
of
place,
I
think
this
word
issue
would
fall
under
would
be
under
the
community
site,
the
kdev
site
and
I'll
just
see.
If
I
can
pull
that
repo
out.
D
Yeah,
so
I
think
the
discussion
was
around
like
creating
a
new
like
a
page
under
the
document
like
the
developer
contributor
documentation
section
to
help
document
this
as
like
a
source
of
truth
across
like
the
different
sources
so
like
the
official
docs
is
at
a
higher
level,
but
sig
architecture,
developer.
Documentation
is
at
a
more
technical
level
and
the
skew
is
significant
enough
for
it
to
seem
different
in
both
places
for
someone
who's
just
coming
in
so
I
was
hoping,
like
maybe
a
new
page
under.
D
So
by
docs
I
mean
under
devil's
slash
architecture
under
in
community,
so
contributors.
Let
me
just
pull
that
up.
Just
a
second.
C
Yeah
I
mean,
I
think
it
would
make
sense
to
make
it
clear
that
the
two
things
are
distinct,
because
that's
what
you're
asking
the.
D
Not
just
yeah,
so
not
just
that,
it's
that
when
people
come
in
and
like
try
to
look
at
so
they
first
look
at
the
visual
docs
and
if
that's
not
clear
enough,
they
try
to
look
at
something.
That's
more
deep,
like
talks
about
it
in
more
detail.
D
But
the
skew
appears
to
be
significant
enough
for
them
to
like
not
be
convinced
with
either
of
them.
So
try
to
sort
of
provide
like
a
middle
ground
which
act
which
is
highly
high
level
enough,
but
also
goes
into
enough
detail
about
some
of
these
topics
so
that
both
sides
of
the
things
become
clear.
So,
like
the
cigars
side
of
things
also,
they
can
dive
into
after
this
and
also
try
to
understand
what
the
high
level
thing
in
I
mean.
C
All
that
sounds
good.
Is
there
anything
stopping
stopping
you
from
doing
it.
D
Oh
no,
so
I
just
wanted
to
ask
if
yeah
this
would
be
the
right
avenue
for
it
and
like
if
there
is
anything
else
or
like
just
creating
a
readme
under
developer
documentation
in
gay
community.
C
C
The
no
they
clean
the
the
contributor
kubernetes
computer
website
so.
D
I
was
hoping
that
it
that
might
be
the
right
place
for
it,
but
in
case,
if
folks
think
that
just
like
documenting
it
somewhere
inside
the
repository
is
a
better
option
than
publishing
it
onto
khs.dev.
No.
C
No,
we
want
all
the
stuff
to
be
on
cadet,
okay,
but
it's
just
a
question
of
whether
or
not
it's
already
been
activated
there.
C
And
in
some
cases
we
may
want
to
move
it
physically
in
order
to
make
it
easier
to
publish
yeah.
Almost
none
of
this
stuff
is
there
right
now.
D
Okay,
so
I'll
create
an
issue
on
a
community
and
I'll
talk
to
tim
about
it,
and
hopefully
we
can
bring
this
up.
C
Yeah,
so
I
mean
there's
two
things:
one
is
updating
the
content
and
making
it
clear
what
the
structure
is,
and
the
second
thing
is
setting
it
up
so
that
it
starts
getting
published
to
kubernetes
dev.
A
D
For
github
management,
I
had
a
question
so
I
think
day
before
yesterday
or
like
somewhere
this
week,
there
was
a
pr
fixing
a
few
links
in
gay
community
in
sega
and
sig
api
machinery.
But
since,
like
it,
didn't
get
a
lot
of
traction
initially.
So
I
pinged
one
of
the
reviewers
and
they
said
that
we
do
like.
D
D
A
I
don't
really
have
an
answer
to
that
question.
Sorry
yeah,
but
yeah,
probably
suck
up
an
issue
to
discuss
just
discuss
that.
A
All
right
next
up,
we
have
slack
infrared
any
updates
on
sly
comfort,.
A
All
right,
which
leads
us
to
open
mic
and
discussion
so
if
you've
got
something
you'd
like
to
share
with
the
group
that
didn't
make
its
way
into
the
gender,
this
is
the
best
place
to
chat
about
it.
If
you've
got
like
a
lingering
question
or
a
thought
or
yeah,
you
want
some
help
with
something
yep.
This
is
the
place.
C
Steering
committee
elections,
the
next
step
is,
we
have
an
elections
committee
next
step
is
proposing
that
getting
it
confirmed
to
the
steering
committee,
followed
by
the
elections
committee
by
the
way
consisting
of
me
allison
and.
E
C
With
arnaud,
acting
as
our
leads
on
to
kubernetes
infra,
because
this
is
going
to
be
the
first
one
run
on
self-hosted
electo,
so
there's
some
infrastructure
setup
involved,
speaking
of
which,
after
we
get
that
up
and
running
electa,
will
then
become
available
for
any
kind
of
elections
within
the
community.
C
C
Following
that,
we
have
to
set
an
election
calendar
and
and
and
then
get
things
going.
That's
where
we
are
with
the
steering
committee
elections.
A
Yeah
I
had
some
questions
around
the
steering
election
things
because
I
was
just
going
through
the
the
process
and
all
the
documentation
and
all
that-
and
there
is
the
it's
written
here
that
they're
at
least
so
we're
proposing
people
forward
to
be
election
officers,
and
it's
saying
two
election
officers
could
have
served
before
and
there's
they've
got
there's
a
list
of
history
here.
So
I
see
josh
on
the
line.
A
Sir,
was
in
the
election
officer
on
the
beforehand,
but
from
the
committee
that
we
proposed
in
the
slack
meeting
last
time
as
I'm
not
sure
we
have
two
people,
but
I
don't
know
if
we
can
kind
of
let
that
slide.
We.
A
C
Should
note
that
in
the
proposal
yeah
the
for
that
matter,
I'm
kind
of
wondering
if,
if
two
people
who
served
before
should
be
the
requirement,
because
I
have
a
feeling
that
that's
that's
going
to
be
the
exception
more
than
the
rule.
C
A
Yeah,
so
I
I
just
need
to
write
the
email
and
fire
that
off
to
steering
saying
these
are,
who
we
have.
This
is
who's
going
to
be
responsible
for
what
and
probably
should
add
that
somewhere
in
the
process,
because
this
process
is
pretty
well
documented
but
like
the
fire
fire
off
an
email
to
inform
the
steering
committee?
This
is
this:
is
this
the
election
committee
but
yeah.
A
It
seems
pretty
straightforward
like
what
needs
to
be
done
and
yeah.
That's
that's
my
kind
of
question
stuff.
D
D
You
can
check
the
links
we
have
given
the
particular
issue,
so
the
problem
is,
we
want
to
put
this
feature
to
it
in
the
contributor
to
its
that
has
recently
been
active,
so
I
wanted
to
connect
with
the
maintainers
or
the
developers
of
this
particular
contributor
to
it
its
us
to
know
if
we
could
put
tweets
in
threads
or
not
in
this
particular
github
actions
or
like
only
single
to
it,
can
be
possible
at
one
particular
point
of
time
or
with
one
issue.
L
I
think
if
you're
creating
a
tweet
to
be
tweeted,
I
think
it
can
only
do
a
single
tweet
at
a
time
usually
for
anything
like
retweets
or
threads.
We'll
have
to
go
in
and
do
that
manually,
which
I
can
help
with.
I
did
not
write
the
automation
there,
but
I
create
a
lot
of
the
tweets
and
and
help
manage
the
the
tweet
flow.
L
But
if
you'd
like
to
talk
to
rajoula
and
kartikayan,
you
could
at
contributor
comms
in
slack
or
join
us
on
our
friday
meetings
at
8
am
and
ask
there.
Does
that
help.
L
Cool
and
happy
to
help
any
more
questions
that
pop
up,
and
if
you
want
to
tell
us
more
about
that
happy
to
hear
it
either
in
slack
or
in
our
meeting.
A
Cool,
so
anyone
any
other
things
you
folks
would
like
to
discuss
on
the
open
mic
today.
D
While
we
are
on
the
subject,
so
the
migration
of
kind
design
to
kind
feature
on
kk,
I
think
that
needs
some
like
discussion
further
to
happen
and
to
decide
what
to
do
next,
because
from
the
current
github
management
and
like
the
automation
that
already
exists,
the
reviews
that
were
provided
by
aaron,
some
of
them,
like
you,
can't
achieve
some
of
them
with
the
existing
functionality
in
labelsync.
D
So
either
label
sync
has
to
be
extended
or
a
manual
process
might
need
to
be
put
into
place
to
like
address
some
of
those
review
points.
D
So
if
folks
can
like
go
to
the
issue,
I
will
which
I
will
put
in
the
chat
right
now
and
like
take
a
look
and
comment
if
any
thoughts
that
be
great
so
that
we
can
move
that
forward.
A
Cool
so.
A
Pay
the
issues
in
chat
I'll
make
sure
that
gets
posted
across
to
the
meeting
notes.
Now
anything
else
would
like
to
chat
about
or
discuss,
got
a
bit
of
time
left
on
the
line.