►
From YouTube: [SIG ContribEx] Weekly Meeting for 20201007
Description
[SIG ContribEx] Weekly Meeting for 20201007
A
And
we're
now
recording
hello
everyone.
My
name
is
bob
killen.
I
am
one
of
the
chairs
for
sick
contributor
experience
and
this
is
our
weekly
meeting.
A
These
meetings
are
recorded
and
we
all
abide
by
the
cncf
code
of
conduct,
which
can
essentially
boil
down
to
please
be
excellent
to
each
other.
A
Before
we
get
into
our
recurring
business,
let's
go
ahead
and
do
a
couple
intros
feel
free
to
jump
in
if
you're
near
new
here
allison,
why
don't
you
kick
it
off.
B
Hello,
everyone
I'm
alison,
I
am
I
help
out
with
the
new
contributor
workshop
and
yeah,
a
member
of
the
contributes.
C
Sure,
hey
everyone,
I'm
nikitha,
I'm
one
of
the
technical
leads
for
sikkim
tripx,
and
I
know
this
is
software.
I
work
in
india
and
also
part
of
the
github
management
team.
So
if
you
have
questions
about
github
management
check
stuff
reach
out
to
me,.
E
I'm
actually
an
air
force
officer,
I'm
working
at
vmware
for
about
10
months.
I
don't
know
if
anyone's
probably
seen
me
in
a
meeting
or
two,
so
I'm
actually
working
with
george
and
amanda
on.
You
know
the
upstream
kubernetes
team
to
kind
of
learn
more
about
upstream
kubernetes
and
how
you
guys
contribute
through
the
cncf
so
literally
here
to
just
absorb
information,
I'm
a
program
manager,
and
so
you
know
trying
to
take
on
that
management
role
for
kubernetes
and
very
excited
to
be
here.
E
D
A
The
the
doc
should
be
shared
with
kubernetes
dev
and
the
contrabex
mailing
lists.
I
think
this
might
actually
be
a
artifact
of
the
doc
is
still
technically
owned
by
a
googler
and
some
permission.
A
Changes
were
made
recently
because
we
it
used
to
be
open
to
at
least
be
view
view
for
anyone
with
a
link
we
sort
of
knew
this
was
coming,
but
I
I
guess
that
the
change
has
has
now
gone
into
effect,
so
george
and
I
will
need
to
make
a
new
instance
of
the
notes,
probably
in
for
the
next
meeting.
A
Oh
welcome
aboard
happy
to
have
you
would
anyone
else
like
to
introduce
themselves?
Otherwise
we
can
get
right
into
the
up
and
other
fun
stuff.
B
Oh
I'll
go
hi,
I'm
ellen!
May
I'm
a
product
manager
on
project
pacific
at
vmware
and
I'm
just
interested
in
getting
to
know
my
way
around
the
kubernetes
community
and
eventually
get
on
board
with
some
projects.
But
I'm
not
sure
where
to
start
so
I'd
like
to
kind
of
get
my
feet
wet
just
by
getting
to
know
you
all
and
what's
going
on.
A
Awesome
well
again
welcome
to
have
you
something
you
might
be
interested
in
after
this
we
can
follow
up.
Is
the
enhancement
sub
project
under
sig
arch,
which
sort
of
wrangles
all
the
features
that
are
being
developed
in
kubernetes
with
with
each
release.
A
A
Okay,
does
anyone
else
want
to
introduce
themselves.
A
Okay,
we'll
get
right
into
our
recurring
business
with
events
office
hours.
A
A
Okay,
I
guess
he
dropped.
I
thought
you
popped
back
in
here,
so
that
and
the
same
for
community
meeting
will
punt
right
over
to
the
contributor
summits.
We
have
a
poll
that
was
sent
out
to
the
leads
man
list.
We
are
still
waiting
for
some
feedback
on
it,
whether
we're
going
to
have
one
sometime
in
the
remainder
of
this
cycle.
A
C
If
we
do
social
only,
what
are
we
planning
to
do?
Do
we
have
ideas.
A
A
The
other
idea
is
like
you
know,
either
use
something
like
discord
where
people
can
sort
of
join
in
and
play
like
a
bunch
of
different
games
with
each
other
or
do
something
like
some
of
the
web
only
game.
So
you
don't
you,
don't
necessarily
have
to
have
like
steam
or
one
of
the
other
things
installed
and
kind
of
kind
of
tossing
around
several
ideas.
A
G
Pretty
much
some
of
it
there's
a
few
creative
apps
now
out
there,
like
I'm,
trying
to
remember,
there's
one
where
you
like,
wander
around
an
8-bit
video
game
and
when
you
run
into
people
it
becomes
a
conference
call.
A
So
that
was
actually
developed
by
someone
that
I
both
george
and
I
actually
game
with.
A
And
I
will
I
will
pump
that
for
now,
for
the
sake
of
time
and
getting
through
all
our
milestone
options
and
things
like
that.
Any
other
quick
comments
before
we
move
on
to
the
next
thing.
A
Okay,
election.
G
Would
be
me,
I'm
sorry.
A
G
G
So
you
could
do
it.
Josh
yep,
the
yeah,
it's
just
you
know
having
this
long
interval
doesn't
help
for
anything
and
and
means
that
I've
got
this
weird
thing
where
it's
like
for
the
non-running
sc
members
I'm
like.
Well,
we
have
the
results,
but
I'm
not
going
to
tell
you
until
friday.
G
So
yeah,
it's
it's.
It's
done.
We
know
who
our
new
sc
members
well.
Three
of
us
know
who
our
new
sc
members
are
going
to
be,
and
everyone
else
will
find
out
on
monday
at
the
public
clc
the
public
steering
meeting.
G
Yeah,
but
also
we
had,
we
had
less
people
eligible
to
vote
because
we
restricted
it
to
org
numbers.
However,
looking
at
the
voting
pattern,
I
don't
think
restricting
it
to
org
members
had
much
of
an
effect.
I
think
we
had
maybe
a
total
of
well.
Actually,
we
didn't
have
anybody
ask
for
exceptions
because
they
met
the
contribution
threshold
but
weren't
nord
member
yeah.
G
A
The
main
reason
why
we
we
had
the
requirement
for
like
being
an
org
member
was
to
make
sure
people
were
on
the
k,
dev
mailing
list
and
people
were
actually
paying
attention,
because
last
year,
when
we
were
trying
to
hunt
people
down,
you
know
we
were
even
going
like
linkedin
and
things
like
that
to
try
and
get
their
contact
information
and
most
these
people
had
like
had
no
idea
that
what
was
involved-
or
you
know
what
was
going
on
with
it
sort
of
the
point-
was
to
try
and
make
sure
that
the
voting
body
was
at
least
informed
by
being
on
the
mailing
list.
G
Well
so
I'll
say,
basically
only
org
members
tried
to
vote
the
so
that
wasn't
really
a
thing
the
and
I
will
say
that
there
are
apparently
a
number
of
org
members
who
aren't
are
no
longer
on
k,
dev
or
at
least
are
not
reading.
It.
A
G
A
A
G
A
G
Based
on
the
number
of
people
who
contacted
me
asking
for
a
voting
exception
yesterday,.
A
But
like
kdev
is
the
one
thing
we
can
enforce.
That
is
a
thing
that
they
should
be
reading,
even
if
they
are
not
right,
there's
not
much.
We
can
do
about
that
one,
but
we.
A
A
A
H
Sorry,
I'm
late,
my
zoom
was
stuck
in
a
crash.
Loop
office
hours
is
in
a
weird
situation,
where
it's
actually
going
after
the
community
meeting,
because
the
first
of
the
month
was
on
a
thursday
and
we
always
do
third
thursday
of
the
month.
So
no
no
updates
this
week
for
that
the
community
meeting
the
host
is
going
to
be
dan
papa.
I
don't
actually
remember
his
last
name
dan
pop.
H
I
think
everyone
knows
I'm
a
cube
from
kubecon
he's
at
weaveworks
and
he'll
be
hosting
this
month's
community
meeting,
which
is
next
thursday.
All
the
things
have
responded.
The
notes
are
basically
done,
he's
doing
a
really
great
job
there
and
that's
all
I
have
unless
people
have
questions-
and
I
take
it,
you
all
met
adam
yep.
H
A
Okay,
so
that
will
take
us
to
mentoring.
Do
we
have
any
mentoring
updates
at
this
time.
G
Yeah
yeah
we
had
to
go
off
the
normal
community
bridge
schedule
because
our
community
bridge
application
was
actually
not
working
before
they
closed
the
normal
applications,
but
once
I
complained
they
restarted,
it
were
kind
of
on
our
own
project.
Schedule
will
be
picking
a
mentee
on
monday,
which
is
actually
going
to
be
really
difficult.
I'm
glad
I
pushed
for
them
to
redo
it
and
reopen
it,
because
we
got
some
extremely
qualified
candidates
down
to
the
point
where,
like
I
wish,
I
had
a
second
project
so.
A
A
Okay,
any
other
questions
or
comments
on
that.
A
Okay,
community
management-
I
don't
think
there's
anything
at
this
time
that
goes
into
the
need
to
know,
email
and
looks
like
there
is
no
updates
from
the
apac
coordinator.
So
with
that,
we
will
go
right.
H
I'm
sorry
there's
one
thing:
I'm
going
to
add
to
the
email
and
I'm
just
going
to
let
everyone
know,
because
I
know
the
rest
of
you
participate
in
cigs.
I
had
a
sick
chair.
Come
ask
me
about
swag
and
t-shirts
for
new
contributors
and
just
feel
free
to
tell
people.
We
got
plenty
of
codes
from
the
cncf
if
you're
in
a
sig
and
there's
a
new
person
and
they're
rocking
it
and
you're
a
chair
tl.
When
I
get
him
a
t-shirt,
ping
me
and
we'll
just
get
him
a
t-shirt.
H
I
know
attendance
and
meetings
have
been
like
rough
lately
and
stuff
and
if
a
new
person
showing
and
rocking
it,
let's
just
give
him
a
t-shirt.
H
F
A
Have
we
have
the
the
guide
for
chairs
and
tls
that's
fairly
light
on
content
at
the
moment,
so
that
would
be
a
good
item
to
put
in
there.
A
Okay
actually
toss
it
quick.
A
Okay,
that
will
take
us
over
to
dev
stats.
I
don't
see
laurie
on
the
line.
A
J
A
J
A
Oh,
that's
awesome.
I
actually
started
like
looking
at
the
the
weekly
progress
report.
I
think
it
was.
I
think
it
was
last
week
I
missed
it
when
I
was
going
on.
The
original
discussion
was
gone
in
slack
but
like
I'm,
I'm
all
gung-ho
for
that
sort
of
thing.
It
looks
good.
Thank
you.
I
So
when
we
last
looked
when
I
left,
I
looked
at
the
draft
on
thursday,
it
was
around
three
pages.
Have
you
ever
been
able
to
cut
that
down
at
all,
because
it's
a
real
long
talk
for
these
folks
to
look
at?
As
you
know,
you
were.
I
J
I
Would
shoot
for
one
yeah
like
you
could
always
give
them
more
information?
I
think
it's
that
teaser
just
getting
the
conversation
going
like.
What
are
you
what's
the
offer?
You
know
what
are
the
metrics
that
you're
providing
in
this
report
and
then,
if
they
say
oh
I'd
like
to
know
more
than
you
have
in
your
back
pocket
so
I'll.
I
can
help
you
with
that
too,
like
I'll
push
for
one
page,
just
let
me
know,
but
it
seems
like
you've
been
handling
this
pretty
well,
but
I
will
reach.
I
Laura
from
to
to
talk
about
small
companies
ospn's
a
small
company,
so
she
just
got
back
to
me
today
and.
A
Awesome:
okay,
and
that
will
kick
us
over
to
marketing.
Is
there
anyone
from
the
marketing
team
that
would
like
to
give
an
update.
A
Okay,
they
seem
to
be
like
chugging,
along
with
stuff
contributor
docs.
For
the
most
part,
this
has
sort
of
just
been
not
too
much
new
stuff
on
going
on
over
here.
We're
in
our
season
of
docs
mentee
is
still
going
through
and
applying
the
style
guide
to
the
contributor
guide.
A
A
Site,
okay,
it'll,
take
us
to
github
management.
Biggest
thing
is:
incubator
is
finally
retired.
The
the
thing
that's
taken
like
two
and
a
half
I
think
three
year,
almost
three
years
now
to
to
do.
A
Okay,
so
the
other
thing
we've
been
talking
about
this
in
the
github
management
slack
channel,
but
get
github
asked
if
we
wanted
to
participate
in
the
beta
to
try
and
enable
like
some
methods
of
recognition
through
github,
and
so
what
we
can
do
is
we
can
do
like
in
a
they've
added
a
command
and
it
can
be
tailored
to
the
org
for
us,
it'll
be
shout
out,
and
then
you
can
do
like
you
know
like
slash
shout
out
nikita
for
that
awesome
pr
review
and
that
will
show
up
in
their
hover
card.
A
So
if
you
like
hover
over
their
profile
will
say
like
you
know,
they
got
a
shout
out
for
this
and
right
now,
it's
like
repo
specific
and
it
will
also
be
viewable
from
like
if
you
go
browse
the
the
root
of
the
repo
you'll
be
able
to
see
it
there.
The
long
term
goal
is
to
be
able
to
aggregate
this
up
to
both
the
org
level
and
have
it
be
presentable
on
the
person's
like
github
profile
page.
A
When
that
happens,
they
will
have
a
whole
slew
of
like
different
moderation,
stuff,
that's
rolled
out
to
prevent,
like
spamming,
but
for
our
go
live
next
week.
There
will
just
be
a
limited
subset
of
those
capabilities.
A
Excuse
me,
one
nice
thing
is:
is
that
like
github
has
historically
like
when
you
go,
look
at
someone's
profile,
page
like
they
just
have
all
the
green
bars
of
or
green
blocks
of,
essentially
commits.
A
So
this
gives
people
the
way
to
get
like
recognized
a
little
thing
on
their
profile
for
things
that
weren't
necessarily
prs.
H
H
A
Know
I
don't
think
so
for
the
actual
beta
okay,
but
more
of
that
will
be
in
there
like
this.
This
will
eventually
be
a
great
stat
to
dump
to
devstats.
A
H
Actually,
a
quick
slack
update,
we've
made
explicit
some
certain
things
about
what
we
expect
of
channels
in
our
slack
that
we
had
not
written
down
before,
like
we're,
expecting
you
to
be
an
open
source
project
and
things
that
were
kind
of
unwritten
rules
that
the
moderators
were
doing
back
and
forth
so
check
the
slack
page
in
the
github
repo.
I
basically
took
everything
that
jay
said
and
turned
it
into
a
pr
there's
fyi
on
that.
One
I'll
add
that
to
the
notes.
A
Okay,
with
that,
we
are
through
our
regularly
scheduled
program.
I
will
now
switch
over
to
my
other
system.
A
A
A
So
last
we
left
off,
we
went
through
and
the
1.19
milestone
and
either
closed
out
the
remaining
items
or
bumped
those
off
to
the
next
milestone
or
dumped
them
into
milestone.
Next,
so
before
we
start
going
through
any
potential
items
that
haven't
been
tagged
with
a
milestone,
I
just
want
to
go
through
milestone
next
to
see.
If
there
is
anything
we
actually
want
to
work
on.
A
So
kubernetes
alpha
feature
posts.
This,
I
believe,
is
this-
would
actually
be
good
to
bring
up
with
enhancements.
We
talked
about
this
briefly
as
a
means
of
getting
more
users
to
see
alpha
features
and
test
alpha
features,
but
we
we
sort
of
put
it
on
hold
because
we
didn't
want
to
potentially
trigger
dog
piling.
A
Oh,
it's
all
good.
Essentially,
this
is
trying
to
get
some
marketing
and
early
feedback
on
enhancements
when
they
go
to
alpha
on
like
discuss
in
some
other
areas.
Oh.
I
Yeah,
I
guess
I
would
have
to
look
at
that
issue
and
then
provide
some
feedback
there.
I
know
I
would
I
would
be
looking
for.
How
could
we
recalibrate
towards
you
know
the
process
that
we'd
like
to
see
like
I've,
heard
things
about
what
happens
with
alpha
and
beta
that
you
know
we
might
wanna.
A
I
A
A
Okay,
I
will
just
assign
it
to
you
feel
free
to
unassign.
This
is
just
so
you
can,
you
can
see
and
get
eyes
on
it.
I
A
A
A
Process
for
summit
team
shadows,
honestly,
I'm
thinking
we
still
leave
this
one
in
next.
For
now
it's
talking
about
how
we
get,
how
we
solicit
shadows
for
our
various
events
and
because
events
are
kind
of
somewhat
on
hold
right
now,.
C
No
paris
is
running
a
group
mentoring
cohort
for
sig
node
with
temps.
So
I
think
group
mentors
group
mentoring-
is
going
to
be
a
priority,
at
least
for
120.
A
A
Honestly,
like
we
might
be
able
to
oh,
no,
this
isn't
the
sick
profiling.
This
is
talking
about
some
of
our
other
other
stuff,
but
it's
a
broad
issue
of
topics.
It's
not
actually.
This
should
probably
go
to
the
marketing
team
for
review
it's
on
their
boards.
A
Okay,
does
anyone
have
a
problem
with
me,
leaving
that
on
milestone?
Next,
for
now,.
A
A
H
I
feel
that
there's
some
that
are
being
overlapped
there,
where
it
might
make
sense
for
us
to
close
it
now
that
we
know
that
wg
naming
has
an
open
issue
for
it.
A
Yep,
what
I
can
do
is.
A
H
A
Yeah
we
do
have
one
for
in
k,
org
for
at
least
the
branch.
A
A
Okay,
honestly,
I
have
a
feeling
that
most
these
items
in
next
are
going
to
remain
in
next,
but
it's
good
to
just
go
through
them
anyway.
Yeah
responsive,
sig
chairs
needs
improvement.
This
is
a
long
term.
Multi.
H
I
also
feel
like
when
we
did
this
things
like
the
sig
chairs,
tl
newsletter,
mailing
list,
slack
channel
all
did
not
exist.
A
C
Probably
we
could
label
this
as
a
steering
issue.
I
think
it
was
leaving
the
steering
issue
before
I
don't
remember
why
it
removed.
C
Yeah,
I
think
we
could
just
label
it
as
steering
and
I'll
make
sure
that
we
tried
it.
C
A
There
isn't
a
good
solution
for
this
really
yet,
as
long
as
we
continue
to
track
some
of
the
sub
project
owner's
files
in
in
this
repo
separately,
I
do
plan
on
actually
revisiting
some
of
this
soon.
For
other
reasons,
so
I
can
at
least
assign
myself
to
take
care
and
audit.
C
A
A
Create
a
url
shortener,
this
has
come
up
like
there's
been
some
stuff
in
the
kids.io
repo
about
this.
It's
a
great
idea.
I
don't
know
how
much
traction
is
ever
going
to
be.
A
Well,
it
was
going
to
auto
close,
but
stp
michael
opened
it
back
up
again,
so
I'm
just
gonna
ping
in
there
like
it's
a
good
idea,
it's
just
kind
of
low
on
the
priority
list.
A
A
A
A
A
A
A
And
then
this
was
actually
eric.
One
of
our
tech
writers
had
updated
some
of
this
well,
I
think
that
was
the
cube
test.
2
documentation.
A
Now
this
is
another
one:
that's
just
been
open
forever.
The
mentoring
program
enhancements,
one-on-one
improvements,
group,
mentoring,
improvements,
mentoring,.
A
And
this
issue
is
directly
related
to
the
other
one
that
we
were
just
talking
about,
where
the
owner's
files
references
in
6.6,
that
yaml
will
will
be
out
of
date.
C
A
A
A
G
A
A
A
A
A
So
I
would
really
like
to
actually
get
like
eric's
thoughts
on
this
as
well,
because
they
were
open
to
the
idea
of
revisiting
the
entire
developer
guide
from
an
information
architecture.
A
This
one
markdown
linter
for
all
of
kate's.
I
think
we
all
collectively
agreed
that
we
didn't
want
to
do
this.
A
It
came
up
in
one
of
the
meetings
you
hear
my
comments
on
it,
like
the
only
thing
we
really
potentially
want
to
do
is
some
very,
very
basic
ones
like
and
this
one
here
where
you
need
to
have
blank
lines
around
a
list
lists,
but
I'm
still
sort
of
in
favor
of
just
closing
this
one
does
anyone
else
have
any
other
thoughts.
C
A
Oh,
it's
like
we're,
essentially
just
going
through
our
issue
like
milestone.
It's
essentially
like
issue
triage.
K
I
wanted
to
opt
in
the
cubectl
repo
into
the
new
needs.
Triage
label
and
I
didn't
know
if
there
was
an
easy
way
to
do
that.
C
I
can
get
a
beer
out
for
that
in
30.
It.
A
Okay,
so
it
would
just
be
for
issues
well
if
pr's
aren't
being
open,
it
doesn't
matter,
never
mind.
F
A
So
next,
finding
seconds
all
turns
less
active,
reviewers
approvers
same
thing
like
updating
owner's
files,
a
lot
of
there's
a
couple,
other
owners
ones.
I
believe
in
here-
and
a
lot
of
this
just
boils
down
to
consolidating
the
issues
down
to
one
overview
of
the
issues
with
the
owners
in
the
the
current
form.
A
A
A
A
So
I
don't
think
any
traction
has
been
made
on
this
issue.
Marky
looks
like
he
was
looking
into
it.
I
will
leave
it,
as
is
in
the
current
milestone
and
milestone.
A
H
H
C
A
C
A
I'm
actually
going
to
assign
all
three
of
us
just
because,
like
on
some
of
the
other
items,
we
were
also
talking
about
like
listing
in
the
chairs
and
tls
directory.
The
different
means
that
people
can
use
to
like
different
reward
mechanisms,
like
you
know,
getting
the
promo
codes
and
all
that.
So
I
do
think
that
we
can
at
least.
C
A
Good
process
for
requesting
community.
A
Surveys,
I
think
I
outline
yeah.
I
outlined
the
various
issues
with
it.
I
think
this
mostly
just
needs
someone
to
document
it.
Someplace.
A
E
A
Hey,
does
anyone
actually
want
to
do
this
themselves
or,
if.
G
G
G
A
A
Okay,
and
do
you
think
you
can
tackle
that
this
this
cycle,
or
should
I
oh.
G
G
A
My
what
my
current
plan
is-
and
I
do
actually
plan
on
creating
an
issue
for
this-
is
on
the
contributor
site
web
page
going
to
have
a
list
of
services.
The
list
of
services
are
going
to
be
all
the
various
things
like
you
know,
you
need
your
custom
repo.
You
go
here,
slack
channel,
you
go
here
and
then
I'll
link
out
to
the
various
different
documentation
sources.
So
that
way
there
will
be
sort
of
a
one
stop
shop
for
all
these
various
things.
A
I
also
just
realized
that
we
are
now
almost
out
of
time.
I
don't
want
to
hold
up
people,
do.
H
You
adam,
and
I
were
just
talking
in
the
background:
do
you
have
any
good
first
issue
or
something
that
maybe
he
can
tackle,
and
I
can
I
can
mentor
him
on
that.
A
Yes,
so.
A
I
A
F
I
H
I
A
I
actually
I
do
have
one
of
an
issue
that
I
created
earlier
today
or
it
might
have
been
yesterday.
A
Replacing
the
built-in
search
engine
and
the
contributor
site
with
google
search,
I
linked
the
instructions
there.
Let's
do
it
yep.
E
Let
me,
let's
see,
which
name
is
real
quick.
A
So
we
didn't
quite
get
through
our
backlog.
Here
we
have,
we
have
been
doing
the
stand
up
each
time
then
going
this
usually
like
the
last
half
hour.
A
J
H
A
E
A
Work
on
for
the
remainder,
we
can
probably
get
it
all
through
the
remainder
of
the
month.
If
we
do
it
that
way,.
H
A
A
So
by
the
end
of
october,
getting
milestone-
or
we
do
like
a
one-off
session
on
finishing
everything
out.
H
Yeah
we
could
just
extend
next
week's
meeting
and
just
finish
it
as
well.
A
Okay,
I
will
stop
sharing.
A
Okay,
cool
well!
Thank
you.
Everyone
for
coming
really
appreciate
it.
Thanks
for
staying
the
two
minutes
over,
we
will
call
that
there.