►
From YouTube: Kubernetes SIG ContribEx 20181121 Weekly Update
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
A
This
is
also
my
first
time
hosting
a
meeting
ever
so.
Let
me
know
if
I
missed
something
so
first
things.
First,
we
do
have
a
code
of
conduct,
so
please
keep
that
in
mind
and
be
excellent
to
each
other,
I
think
Erin
or
someone
else
posted
the
meeting
notes
link
in
the
chat.
So
please
add
your
names
to
the
attendees
list
will
also
need
a
note-taker
at
this
meeting.
Who
wants
to
volunteer
for
that
awesome?
Thank
you.
Bob,
let's
see
Oh,
so
we
do
this
every
meeting.
B
B
A
A
A
C
A
D
A
And
about
meter
contributors
I
have
an
update
from
Paris,
so
we
are
looking
for
more
volunteers
for
the
December
5th
edition
and
the
January
2nd
edition.
If
you
have
a
few
our
regular
contributor
to
kubernetes-
and
you
want
to
mentor
someone,
but
you
don't
have
the
time.
This
is
an
excellent
opportunity
for
you
to
do
so.
Please
please,
please,
please
sign
up,
and
one
wonderful
I
mean
I
would
always
want
to
add
it
from
like
myself
is.
If
you
could
do
a
code
based
work.
A
That
would
be
seriously
amazing,
and
if
you
are
a
new
contributor
you
can
you
can
come
on
the
call.
We
would
love
to
have
your
insight
about
how
you
want
to
get
the
contributing
or
how
you
are,
or
even
what
problems
you're
facing
to
contribute.
I'm
pretty
sure,
like
other
new
contributors,
are
also
facing
such
similar
problems,
and
if
you
have,
if
you
have
suggestions
of
code
bases
that
you
would
like
to
see
a
tour
of
please
reach
out
to
Paris
or
me
and
we'll
try
to
make
that
happen.
A
E
I
think
it
actually
I'm
new
to
condo,
kubernetes
and
contributing
from
last
two
or
two
months
yeah.
Actually,
when
I
go
to
the
API
side,
I
mean
in
core
I'm
working
on
pod
and
conformance
testing
side:
ok,
I'm,
ok,
fine,
when
it's
reaching
the
a
pipe
I
mean
before
they
pay
when
it's
getting
called
on
part
creating
before
it
goes
to
the
core.
F
G
I
I
think
like
I
know,
Stephen
did
like
a
brief
tour
of
some
of
the
code
base
in
kubernetes,
but
I'm
not
I
personally,
haven't
seen
anything
that
does
a
real
deep
dive
and
to
end
of
like
ok,
I'm
gonna
stand
up
an
API
server
and
then
here's
how
the
end
points
get
wired
up
and
then,
when
an
end
point
gets
hit.
Here's
how
the
end
point
actually
calls
the
logic
that
does
the
thing
you
know.
H
G
My
impression
is,
if
you
spent
a
chunk
of
time
in
the
registry
codebase
the
registry
package
in
KK,
that
could
be
a
useful
thing.
There's
not
something
I,
necessarily
volunteering
to
do,
because
I
may
already
be
locked
up
tight
for
release,
1:13
stuff
and
the
steering
edition
of
meet
our
contributors.
But
that
would
be
my
suggestion.
G
A
I
K
J
That's
kind
of
tangential
to
this,
but
as
you're
going
along
this
journey
think
about
how
we
might
improve
our
developer
guide.
We
need
more
of
this
type
of
descriptive
stuff
and
tell
people
orient
to
doing
kubernetes
internals
development,
and
we
have
a
large
open
tasks
from
contribute
experience
to
work
on
improving
that.
So
contributions
welcome.
A
A
A
Can
you
all
see
my
screen?
Okay,
before
we
move
on
to
the
block
column?
I
actually
want
to
talk
about
completed
column
so
that
we
can
celebrate
some
small
wins.
First,
we
saw
Christoph
did
this,
he
removed
direct,
read
access
from
many
folks
2kk,
which
is
kind
of
a
huge
deal,
because
it's
super
important
for
github
organization,
my
dreams
so
yay
and.
A
A
L
A
G
A
J
Guess
I
can
just
mention
that
planning
is
underway,
we're
getting
into
the
final
stretches
there,
but
also
things
have
been
split
between
Cuba
and
China
and
cucum
North
America
and
with
China
done.
Those
of
us
who've
been
contributing
that
are
now
also
focusing
again
on
North
America.
So
hopefully,
in
the
next
week
or
two
we've
got
everything
nailed
away.
J
A
A
A
A
A
The
next
thing
we
have
is
I
have
some
updates
from
Paris.
So
the
first
thing
is
that
the
project
manager
will
vent,
live
on
the
world
board
and
discussed
at
Cabrini
start
IO
and
on
the
mailing
list,
and
she
said
a
or
someone
else
will
be
tackling
that
and
will
be
updating
us
in
the
next
meeting.
Is
that
correct
you.
C
Are
it's
great
yeah,
so
we
we
have
briefly
discussed.
Discretion
was
Paris,
so
it's
likely
for
us
to
have
not
a
single
person
will
handle
this,
but
at
least
a
group
of
two
or
even
more
people,
so
I'm
going
I'm
going
to
work
on
this.
At
the
same
time,
there
are
any
other
people
who
would
like
to
focus
on
this
role
and
spend
just
a
few
hours
of
their
time
during
the
week.
Working
in
our
backlog
and
and
the
project
budget
would
be
great
so
feel.
A
C
A
So
that
looks
like
it's
going
on
well,
the
next
update
is
that
we
have
selected
and
appreciate
in
turn,
so
anywhere
will
be
joining
us
I.
Think
on
December
5th,
we
will
introduce
him
on
the
mailing
list
next
week
and
on
the
next
meeting
and
he
will
be
working
on
the
developer
guide
so
like
it
was
discussed
like
a
few
minutes
ago.
A
I
think
it
will
be
super
cool
to
include
all
of
this
in
the
developer
guide,
and
the
idea
is
that
all
the
firm's
to
contribute
experience
will
be
working
with
him
and
helping
him
and
mentoring
him.
So
we
will
probably
most
of
you
will
probably
be
there
on
the
calls
that
we
will
have
with
him,
and
that
looks
like
we've
completed
all
the
items
on
our
agenda.
Does
anyone
have
anything
else
they'd
like
to
talk
about
this
is
like
the
shortest
contra
vex
meeting
in
the
history
of
central
banks.
G
Since
Christophe
is
here,
I
will
sync
up
with
Christophe
afterwards
to
talk
about
our
automation,
talk
for
the
contributor
summit.
If
anybody
here
has
any
crazy
awesome
suggestions,
they'd
like
to
throw
our
way
you're
welcome
to
ping
us
in
slack
and
the
contributor
experience
channel.
Maybe
we
can
make
a
thread,
but
I
have
an
idea,
we're
roughly
gonna
since
it's
supposedly
to
an
audience
of
current
contributors
who
all
know
how
our
automation
works.
G
I'm,
sure
we
don't
have
to
educate
them
on
all
the
stuff
that
goes
on,
but
we'll
probably
at
least
do
like
I
want
to
leave
some
room
for
like
an
AMA,
basically
I'm,
not
I,
don't
necessarily
want
to
open
us
up
to
a
great
hate
and
have
everybody
asked
us
to
fix
everything?
Please,
but
I
do
think
it's
gonna
be
a
more
useful
session
if
there's
back-and-forth,
so
any
seating
questions
y'all
have
would
be
helpful,
most
likely,
khloe's
I
think
that's
all
I
have
and.
A
G
H
G
G
H
G
H
G
N
G
N
G
The
sake
release
me
yesterday
for
the
shadow.
If
anybody
here
is
interested,
but
my
thing
was
like
I
will
be
the
release
lead
for
114,
but
I
only
want
to
do
it.
If
I
have
a
solid
shadow,
because
history
has
taught
me,
I
tend
to
get
yanked
around
in
different
places
and
I
feel
like
it
would
be
a
disservice
to
the
community
if
I
flew
this
solo.
So
if
you
or
know
anybody-
or
you
yourself
are
interested,
you
know
come
come
chat
with
me
and
we'll
see.
If
we
can
figure
it
out.
G
G
H
N
N
H
D
M
H
A
Okay,
I
had
I
want
to
discuss.
One
thing
we
did
talk
about
this
on
the
country
backs
channel
a
lot
about
trivial
fears.
I
am
NOT
talking
about
a
solution
per
se,
but
some
people
reached
out
to
me
on
DM
asking
if
they
should
hold
years,
which
have
like
one
or
two
typos
I
just
want
to
get
understanding
whether
we
agree
on
holding
or
not.
G
G
What
am
I
trying
to
say
here,
like
I'm,
really
really
in
favor,
of
letting
typos
in
and
letting
people
contribute
typos,
it's
the
easiest
lowest
friction
way
to
get
in
but
like
at
some
point.
We
start
to
notice
that
somebody's
making
nothing
but
typo
fixes
and
it's
if
it
starts
to
like
eat
up
review
or
bandwidth,
that's
kind
of
when
it's
a
problem
for
us.
But
it's
unclear
to
me
how
we
can
quantify
like
how
much
pain
it
is
actually
inflicting
on
us
or
if
it's
just
an
inconvenience
that
we're
noticing
more
of.
G
G
The
problem
is
there
sometimes
really
critical
fixes
that
involve
changing
one
character
and
they're,
often
a
lot
of
bug
fixes
that
are
like
one
line,
so
we
do
label
PRS
to
size
extra
small,
but
that
doesn't
necessarily
quantify
the
importance
or
value
of
the
PR
and
I
really
would.
Rather,
we
avoid
the
idea
of
attributing
value
to
contributions.
That's
begins
to
be
a
very
slippery
slope.
To
me
it's
more
about,
if
there's
pain
being
inflicted
on
people
here,
to
find
a
way
to
mitigate
that
I.
Think.
J
The
best
way
that
we
could
do
this
now
granted
this
requires
somebody
to
step
up
and
do
it.
But
if
we
had
I,
don't
want
to
call
it
a
feature
branch
but
a
branch,
a
particular
owner
that
handled
typos
and
if
we
documented
and
people
knew
hey
those
fixes
they
go
to
this
person.
There's
a
person
there
that
reviews
them
and
periodically
batches
that
up
in
a
combined
PR
into
whichever
appropriate
repositories
that
could
mitigate
some
of
the
review
overhead
I'm
thinking.
J
If
everybody
in
the
communities
bumping
into
all
of
these
things
coming
in,
but
also
still
facilitates
the
newcomer
getting
through
that,
because
it's
friction
on
them
as
well
to
just
get
that
first
contribution
end
and
then
it
would
be
a
place
where
somebody
would
maybe
notice
and
be
able
to
highlight
if
there
was
the
abuse
or
whatever
we
want
to
call
it
gaming.
Those
statistics.
H
O
H
About
the
typos
I
to
have
sent
people
to
do
typos
as
their
first
full
request.
I
have
backed
up
from
that,
because
I
have
noticed
a
little
bit
of
backlash
in
the
community.
However,
I'm
I
think
it
matters.
Two
things
map
two
things
I
want
to
know
one
if
it's
someone's
first
contribution,
I
think
it
is
100
percent,
fine,
I,
just
don't
it's
it's
hard
enough
to
make
a
contribution.
My
first
contribution
was
a
type
of
fix
and
somehow
it
wound
up
being
removing
all
the
munch
munch
lines
later
from
all
the
Ducks.
H
It
was
great
anyway,
but
it
started
out
as
a
type
of
fix.
Okay.
If
I
hadn't
started
out,
then
we
would
still
have
like
Munder
lines
sitting
around
and
all
the
community
Docs
and
then
to
I
want
to
know
what
the
actual
numbers
on
this
are.
It
sounds
like
something
where
people
are
just
like:
oh
it's,
a
typo
and
I.
Don't
know
what
the
actual
do
we
know
what
the
actual
impact
of
this
is
do
we
do.
We
have
any
kind
of
projection
on
how
bothersome
this
is.
H
How
many
of
these
type
of
fixes
do.
We
see
our
people
are
people
like
annoyed
with
them.
You
know.
Are
there
certain
reviewers
that
see
nothing
but
typo
fixes
and
it
stops
them
from
doing
work?
So
that's
that's
just
kind
of
that's
just
my
two
cents,
I'm
like
I,
want
to
know
what
the
actual
annoyance
here
is.
It's
it's
easy
to
see,
people
being
annoyed.
That's
that's!
That's
one
point.
There's
one
data
point,
but
what's
the
actual,
like
you
know,
volume
of
annoyance.
C
Just
just
a
note
so
from
a
personal
perspective,
it's
more
about
so
the
negative
impact
of
the
type
of
fixing
is
not
it's
not
about.
There
are
the
time
over
viewers,
but
more
about
the
batplane
and
playing
with
statistics.
So
this
is
do
like
like
for
my
personal
perspective.
Is
this
is
the
major
downside
furnace
so,
as
someone
mentioned
in
our
one
of
the
treads
and
slack
yeah,
it's
gaming,
destard
so
or
gaming,
sticky,
latex
or
any
other
tool
that
measures
the
contributions.
C
B
That's
in
the
code
of
conduct,
or
is
it
something
that
could
be
put
in
the
code
of
conduct,
because
what
what
they're
doing
is
something
that's
detrimental
to
the
project
and
a
code
of
conduct
violation.
It
might
be
a
better
way
to
deal
with
this
because
then
you
can
roll
their
commits
out,
and
then
they
don't
get
to
commit
any
more
or
I.
Don't
know
exact
I
I
should
go,
read
the
code
of
conduct
and
see
exactly
exactly
what's
in
it.
I
glanced
through
it.
N
H
B
H
What
we
can
do
is
when
we
talk
about
first
contributions
and
type
of
fixes.
We
can
remind
people
to
you
know
do
that
in
the
spirit
of
improving
the
community
and
the
project
that
would
kind
of
fall
in
line
with
like
if
it's
your
first
contribution
by
all
means
have
it
be
a
type
of
fix.
Maybe
if
it's
your
second
contribution,
try
and
make
the
whole
paragraph
more
readable,
I.
G
Don't
care
if
anybody
games
them
stats?
Speaking
as
a
member
of
the
steering
committee,
who
did
a
dev
stats
based
selection
thing,
do
you
really
think
we're
gonna
use
the
exact
same
criteria
now
that
everybody
knows
how
to
game
it
like
if
somebody
wants
to
like
go
off
and
boost
their
contribution,
stats
based
on
whatever
project
they're
gonna
find
a
way
to
do
it?
G
I,
don't
really
feel
the
need
to
have
to
defend
against
that
I
do
care
if
it's
wasting
your
time
and
I
do
care
if
it's
impeding
the
velocity
of
the
project
but
I
feel
like
I
haven't
found
I,
don't
know
that
we're
really
being
we
haven't
quantified
that
yet
and
I,
and
back
to
like
echoing
go
at
Gwyn,
said
I
really
want
to
understand
how
much
of
a
problem
this
is
and
measure
the
impact.
That's
the
problem,
I
see
Christophe
has
raised
his
hand.
O
So
then
we
can
figure
out
the
best
way
to
tackle
it,
because
right
now
it's
it's
there's
a
whole
bunch
of
anecdotes
and
I've
heard
a
bunch
of
anecdotes
and
everybody's
heard
a
bunch
of
anecdotes
here,
but
it's
it's
getting
getting
that
hard
data
so
that
we
at
least
know
because
if
we
have
a
particular
statistic
or
metric
or
way
of
measuring
it,
then
if
we
go
and
change
something
we
also
have
a
way
of
measuring.
Did
that
change
have
the
impact
that
we
wanted
it
to
have.
L
L
So
in
the
bug,
I
kind
of
said,
is
there
a
way
to
rate
limit
this,
like
you
know,
if
you've
done
three
extra
small
commits
and
you're
not
part
of
the
org
pr's
in
the
last
day
or
whatever
the
numbers
are
right,
like
it's
Stack
Overflow,
if
you're
a
new
user,
it
doesn't
let
you
do
things
until
you
earn
enough
reputation
to
do
stuff.
So
I
was
wondering
is
like
if
you
see
a
whole
bunch
of
really
small
little
ones
coming
in
a
short
amount
of
time.
L
It
gets
flagged
put
in
a
queue
somewhere,
and
it's
like
hi
welcome
to
kubernetes
is
really
great
and
stuff,
but
by
the
way,
here's
a
trivial
policy.
You
know
no
key,
no
remember
I,
think
you
talk
someone
through
hey
here's,
how
you
level
up
to
kind
of
make
it
look
like
hey.
Look
it's
great
that
you're
doing
this,
but
maybe
it's
you're
smarter
than
this.
You
can.
L
Maybe
you
know
and
that'll
help
weed
out
the
people
who
aren't
like
really
serious
about
it
and
then
that
way,
like
I
kind
of
feel,
like
especially
if
they're
doing
it
in
kubernetes
kubernetes
that,
like
it's
like
hey,
if
you're
serious
about
this
I,
would
rather
you
do
this
in
the
communtiy
repo
and
bother
me.
You
know,
then
like
doing
it
in
KK
itself,
so
my
idea
was
kind
of
just
like
maybe
there's
a
way
to
kind
of
figure
out
which
ones
are
exactly
spamming,
and
you
know
if
they
are
indeed
spamming.
A
Yeah
I
think
yeah
I
think,
like
we
all
agreed
that
we
need
data
and
metrics
before
deciding
anything.
So
I
created
an
issue
a
few
days
ago.
So
I'll
just
add
a
comment
on
that
that
we
need
data.
I
might
not
go
finding
data
for
it
right
away,
but
I
will
add
a
comment
that
the
next
step
should
be
to
find
data
about
it.
P
Yeah
in
in
the
sense
of
collecting
data,
it's
going
to
be
important
to
think
about
sorry,
I'm,
still,
calm,
crud,
it's
going
to
be
important
to
keep
in
mind
all
the
gear.
Switching
that
goes
along
with
this,
because
I
think
that's
going
to
be
one
of
the
biggest
problems,
not
necessarily
the
time
that's
spent
reviewing
and
even
necessarily
saying
well
reviewing
a
typo
takes
X
number
of
seconds
or
minutes,
but
the
whole
we're
knocking
people
out
of
their
train
of
thought
and
that's
probably
going
to
be
a
bigger
impact
than
the
actual
reviewing
themselves.
A
Yeah
I
think
I
think
that
makes
sense.
I'll
just
I'll
just
add
a
comment
on
the
issue
with
everything
we
just
talked
about
and
maybe
link
to
the
meeting
notes,
and
then
we
can
bike
shared
on
the
issue.
What
we
want
to
do
so
there's
also
a
record
of
what
we're
discussing
looks
like
we
reached
the
end
of
her
agenda.
Does
anyone
else
have
anything
to
add.