►
From YouTube: Kubernetes Contributor Experience SIG 20180516
Description
Join us every Wednesday at 9am PT!
A
If
I
can
record
nope
did
somebody
else
have
the
recording
permissions
yep
go
ahead?
Are
we
recording
sweetie,
okay,
happy
Wednesday?
Everyone
welcome
to
the
may
16th
edition
of
the
contributor
experience
community
off.
If
you
have
not
done
so
already,
please
add
your
name
to
the
attendees
section
of
the
agenda.
The
agenda
can
be
found
in
the
calendar
invite
for
the
meeting,
so
we're
going
to
start
out
by
hitting
our
recurring
business
first.
So
are
there
any
new
contributors
on
the
on
the
line?
New
people
to
this
call.
A
A
B
C
D
E
B
Lukas,
anytime,
you
want
to
anytime,
you
want
to
talk
about.
Dev
stats
to
during
the
community
meeting
feel
free.
You
have
a
slot
like
we
have
reserved
a
slot
every
meeting
now
for
a
graph.
So
if
you
have
something
to
say
that
pertains
to
dev
stats
feel
free
to
use
that
time,
okay
I
mean
it
doesn't
sound
like
just
this
is
necessary,
but
just
wanted
to
throw
that
out.
There
yeah.
E
F
A
A
A
C
Of
give
a
lead-in
so
Aaron
Kroger,
Burger
King
me
last
week,
cuz,
he
you
know,
I
had
a
little
bit
of
experience
in
this
particular
space,
and
he
mentioned
that.
Brian
grant
had
mentioned
that.
There's
this
ticket
out
there
and
he
thought
it
was
something
could
Trebek
should
run
with
and
he
he
he
said
it
in
a
way
that
he
that
Aaron
took
the
impression
that
he
thought
we
were
running
with
it
and
Aaron
kind
of
thought.
C
Oh
I'm,
not
sure
so,
I'm
gonna
poke
a
few
people
and
make
sure
that
this
doesn't
just
on
the
table
as
Aaron
is
stepping
back
for
a
bit.
So
the
on
the
issue
is
linked
there
in
the
in
the
minutes
and
the
the
basic
idea
is
that
when,
when
go,
vendored
code
gets
pulled
in
for
an
update
or
even
during
weather
weather
for
a
new
bit
of
enduring
or
an
update
of
existing
vendor.
C
It's
important
to
comprehend
the
licenses
of
those
components
to
make
sure
that
they're
compatible
with
the
overall
licensing
of
the
project
and,
ideally
on
a
project.
You
do
that
with
automation,
so
whether
it's
a
pre-commit
hook
or
CI
testing
to
ensure
that
things
are
okay,
there's
a
need
here
for
some
tooling
and
then
the
linked
off
of
that
issue
was
a
PR
just
recently
and
some
kind
of
homegrown
tooling
to
try
and
do
some
license
validation.
But
this
is
a
particular
space
where
there's
a
ton
of
existing
software
out
there.
C
That
does
similar
and
it
seems
like
a
maybe
a
bad
place
to
reinvent
the
wheel,
and
this
is
a
wheel
that
I
think
is
really
often
reinvented.
So
if
we
could
figure
out
a
way
to
go
with
something
that's
established,
then
we
we
get
the
benefits
of
open
source
scale,
we're
on
leveraging
the
kind
of
a
collective
hive
mind
of
the
open
source
ecosystem
there.
C
So
in
the
PR,
that's
linked
off
of
the
issue,
the
the
conversation
kind
of
revived
there
and
one
of
the
questions
I
had
was
like
well,
okay,
so
CN,
CF,
maybe
or
somewhere
from
a
governance
perspective.
We
need
to
understand
what
is
the
project
overall
license
and
what
incoming
licenses
would
be
understood
to
be
compatible
with
that
and
I.
C
Don't
think
that's
been
answered
yet,
but
then
the
the
idea
of
CN
CF
having
licenses
to
use
fossa
came
up
and
I
think
that's
where
I'd
kind
of
hand
off
to
Christophe
to
us
to
talk,
because
he
was
gonna.
Look
at
that
and
then
I
see
that
matt
has
his
hand
up.
So
maybe
Christophe.
If
you
want
to
discuss
fossa
just
for
a
moment,
then
we
can
kind
of
open
it
up
for
broader
discussion.
C
G
G
So
the
steering
committee
kind
of
got
poked
at
it
again
and
yeah
so
Matt
had
raised
fossa
I've
looked
into
it
and
the
biggest
kind
of
an
initial
issue
was
cost
and
how
they
would
bill.
Could
they
typically
bill
on
developers,
but
it
appears
the
CNC
F
has
negotiated
a
free
plan
for
the
MCF
projects,
so
yeah
in
the
in
that
meantime,
between
where
we
had
highlighted
Foss
as
an
option,
but
there's
a
potential
cost
issue.
H
So
I
was
talking
with
it
was
either
Dan
or
Chris
over
at
the
CMC
F
earlier
this
week,
and
they
have
I
think
it's
non
falsi
tooling
to
go,
evaluate
this
stuff,
I'm,
forgetting
the
name
of
a
tool,
but
there
is
an
open-source
tool
that
a
bunch
of
companies
even
use
to
evaluate
their
own
stuff
that
we
could
go
off
and
use
I
think
the
Linux
Foundation
uses
it.
So
if
we
reach
out
to
probably
Dan
or
Chris,
they
can
probably
point
us
in
the
right
direction.
H
I
was
chatting
with
them
about
this
topic
today,
because
we're
looking
at
stuff
around
home
and
we
were
funding
that
I'll
get
some
the
other
stuff
done,
but
they're
like
we
can
jump
all
over
this.
So
don't
know
what
licenses
are
acceptable
and
they
have
tooling
to
build
us
more
projects
with
that
today
we
just
have
to
go
figure
out
what
it
is.
Do.
G
H
That's
the
direction
they
want
to
go
now.
There
was
another
tool:
I
looked
at
it
and
I
went
that's
ugly.
The
first
few
times
I
looked
at
it
and
I
liked
a
service
to
do
it
so
I
like
falsi.
So
if
we've
got
something
in
that
direction,
but
because
it's
legal
licensing,
if
they've
got
a
recommended
way
and
they
know
which
licenses
and
how
to
handle
it-
I
love
twenty
eight
to
that
yeah.
C
One
of
the
concerns
so
I
definitely
I,
like
I
kind
of
part
of
me,
agrees
with
Matt
like
I,
want
service
and
as
much
as
somebody
is
maintaining
the
scanning
logic,
because
finding
a
license
within
a
file
is
actually
extremely
complex
and
then
mapping
all
of
the
variations
of
white
space
and
and
spotting
that
somebody
made
a
slight
wording.
Change
like
it
is
the
tools
that
do
this
well
end
up,
really
quite
complex
and
and
there's
a
mess
of
licenses
out
there
and
go
library
package
code.
C
G
So
I
put
this
in
the
minutes
that
I
just
dropped
it
in
contrived
acts
as
well.
So
that's
container
deep,
that's
their
boss,
a
dashboard,
so
it
hooks
in,
like
you
know,
Travis
or
you
know
other
other
CI
systems,
Ian
it's
more
like
with
github
web
books
and
tracks
license
data.
So
it
would.
It
would
do
a
status
context
in
the
PR.
Just
like
the
CNCs,
like
the
CLA
check
or.
H
G
Of
Prowse
checks,
so
it
kind
of
has
that
integration,
I
I,
want
to
verify
verify
how
it
works
as
well
as
make
sure
that
it
doesn't
do
anything
weird
as
far
as
setting
the
PR
statuses,
so
it
doesn't
trip
up
any
of
our
tooling
around
prowl
and
tide.
That
would
be
to
me
that
would
be
a
deal-breaker
if
it
if
it
did
any
of
that.
G
But
you
know
on
the
surface,
it
looks
like
it's
something
that
again
that
we
could
just
kind
of
punt
and
let
somebody
else
take
care
of
because
as
well
as
policy,
if
we're
on
the
CNCs
account,
if
they're,
if
they
have
like
policies
around
which
licenses
they
deem
acceptable.
That
you
know,
may
deviate
like
there's
other
people
that
can
go
in
as
far
as
the
legal
check
boxes.
So
it's
not
either
us
taking
that
on,
or
the
steering
committee
clicks
Trish.
Traditionally,
it's
been
like
Brian
and
Tim,
who
who've
handled
that
that
coverage.
H
Yeah
yeah
and
the
CNC
F
is
the
legal
entity
responsible
for
this,
and
so,
if
they
have
a
recommended
way
that
they
want
us
to
handle
this,
it's
probably
in
our
best
interest
that
the
people
who
are
the
the
throat
to
choke
for
I
can
be
of
a
better
term
right
now
on
it
to
go
with
their
path
on
it
because
of
the
for
the
day,
we're
not
the
ones
who
end
up
being
legally
responsible
for
this.
They
are
right.
H
I'm
probably
got
to
quick
other
things
on
SPD
acts
lets
you
kind
of
shorthand
write
licenses
into
stuff
it'll.
Let
you
do
that
in
like
package.json
and
stuff
like
that,
but
when
people
of
lut,
so
it
basically
gives
it
a
quicker
path.
But
the
other
project
that
I
was
thinking
of
is
called
false,
ology
here
with
it,
and
that's
the
one
that
a
lot
of
folks
will
also
end
up
using
I'm
gonna
put
those
in
the
notes.
Matt.
G
H
I
do
have
one
maybe
miles
objection
when
we
get
into
the
whole
idea
of
who
can
do
it
better
right,
I
think
only
if
maybe
our
requirements
aren't
met,
we
try
to
do
it
not
so
much
if
it's
better,
because
we
are
very
much
run
thin
with
a
million
things
to
do.
It
can
be
easier
to
say
you
know
what
I
can
write
this
about
the
way
and
just
to
be
careful
that
it's
not
around
our
definition
of
better
but
maybe
more
around.
H
It
doesn't
meet
some
requirement
that
we
legally
have
from
the
CNC
yeah
that
we
can
articulate.
So,
therefore,
we
need
a
gap
to
fill
in
that
we
have
to
go
do
rather
than
our
definition
of
matter.
Is
it's
so
easy
to
give
ourselves
kind
of
lunch
to
go
recreate
the
wheel?
That's
just
a
constant
nervousness
of
life.
I'd.
C
Even
go
further
and
say
like
if
we
find
the
gap
like
that
first
step
is
to
talk
to
them
and
assuming
we've
gone
with
them
and
say:
okay,
this
this
is
a
gap
and
are
you
interested
in
and
filling
it
because
it
makes
them
better
as
well
and
yeah.
The
that
my
biggest
thing
here
is
that
we're
not
reinventing
stuff,
because
that's
a
huge
cost
and
this
idea
of
better
is
highly
highly
subjective.
Yes,
good.
H
Now,
good
enough
model
of
open
source
development,
you
know
antenna
be
honest,
fossil
achieves,
but
a
lot
of
big
enterprises
use
or
their
legal
people
all
over
it.
So
if
the
way
of
going
is
to
use
the
service-
and
it
doesn't
work,
then
we
should
probably
talk
to
the
scene
to
Yap
about
the
fallback
is
because
they're,
the
ones
who
are
legally
responsible.
This
is
gonna
fall
back
in
other
projects.
This
is
a
bigger
question
that
justice
is
trooper,
that
he's
right.
We
there
might
be
other
things
like
pathology.
F
Oh
I
forgot
where
I
brought
this
up
was
that
at
the
last
community
meeting
or
this
last
meeting
is
if
you're
looking
github
and
PRS
there's
a
lot
of
caps
incoming
and
a
lot
of
them
are
major
things
and
I
was
wondering
about
perhaps
having
a
section
in
the
off
weeks
from
the
from
the
church
or
whatever.
That
would
be
like
hey,
so
you
know,
so-and-so
has
submitted
a
cap
he's
you
know
he
or
she's
looking
for
feedback.
You
know
maybe
things
that
kind
of
like.
F
Put
put
the
fact
that
these
are
out
there
and
their
proposals
out
to
the
wider
audience
so
that
they
can
comment
on
it,
especially
now
we
seem
to
be
really
getting
through
the
community
meetings
a
lot
faster
and
we
should
probably,
if
there's
important
stuff
to
talk
about
so
I,
don't
know
it
should
I.
Add
a
template
should
I,
maybe
like
how
should
I
approach
this
should
I,
say
hey?
Who
wants
to
go
first
tomorrow,
like
how
do
you
like?
Do
we
want
to
do
this?.
I
F
A
little
about,
let's
say,
someone's
doing
a
Capon,
it's
like
hey,
you
know
this.
This
touches,
you
know
three
SIG's
or
whatever
and
and
here's
my
proposal,
and
this
is
the
P,
are
you
know,
I'm
closing
comments
in
like
two
weeks
that
sort
of
thing
like
it
doesn't
need
to
be.
Unless
you
know
it
brings
up
a
bunch
of
stuff
that
needs
to
be
discussed
by
a
bunch
of
people,
then
you
know
it
could
be
as
easy
as
okay.
I
I
F
I
also
noticed
that
there's
naming
collisions
now
with
caps
like
so
the
way
they
did
it
in
the
caps
folder.
There's
one
there's
one
number
that
says
next
cap,
but
if
you're
kept,
does
it
get
merged
like
I,
think
mike
epps
gonna
end
up
not
being
kept
seven
depending
on
who
gets
merged
first
and
I
have
a
lot
of
questions
about
that.
I,
don't
know
if
why
do
we
just
make
it
the
5-minute
caleb
show
or.
D
F
I
don't
know
I'm
anyway.
The
only
concern
that
so
Joe
brought
this
up
to
me.
He
was
like
there's
a
lot
of
stuff
happening
in
caps
and
if
you're
not
paying
attention
and
github,
you
might
miss
it.
And
since
you
finished
a
meeting
in
27
minutes,
which
is
my
fault
apparently
he's
like,
maybe
we
could
use
that
time
to
kind
of
give
visibility
to
caps.
You
know
again
again
get
people
looking
in
the
right
place.
F
So
Matt
seems
to
+1
Josh,
would
you
say
okay
and
then
maybe
we
can
we
can
chase.
Maybe
I
can
talk,
I
should
actually
just
talk
to
Caleb
and
then
maybe
put
an
explicit
thing.
You
know
we're
here
to
give
visibility
to
caps,
not
plus
plus
or
minus,
either
way
right.
It's
more
of
a
visibility
announcement
thing
than
it
is
a
this.
Does
that
does
that
work
for
you
I
think.
I
That's
good
yeah,
just
as
get
people
knowing
that
they
exist
and
that
there's
a
place
that
they
can
centrally
review
them
if
they're
interesting,
I,
just
the
body,
and
so
we
have
for
the
community
meeting,
is
so
wildly
varied
that
it
doesn't
rest.
It
doesn't
necessarily
represent
a
strong
cross-section
of
any
particular
strata
of
leadership
or
community
input.
So
sure
yeah
I,
think,
starting
with
the
weirdness,
is
good.
Yeah.
F
Yeah,
so
I
was
thinking
of
also
making
the
sig
update
template.
So
right
now
we
say
you
have
ten
minutes
ago
and
I
was
thinking
making
it
a
little
bit
more
like
we
did
a
cube
con.
That's
kind
of
like
concentrate
on
things
that
are
external
to
your
sig,
but
I
can
like
propose
that
and
then
do
it
through
the
list.
So
I'm
not
taking
it
too
much
time
here,
I.
B
All
right,
your
turn,
dr.
Khan
I,
wanted
to
get
a
final
call
to
who
was
going
I
know.
Josh
was
going.
I
know
that
Tim
Hawken
is
keynoting.
He's
going
and
Assad
from
storage
is
going
reason.
Why
I'm
asking
is
we
have
a
three-hour
kubernetes
contributor
office
hours,
office,
hours
being
no
structure,
so
it's
not
like
the
workshop
docker
contributors
and
the
like
will
be
coming
by
to
I
guess,
asked
questions
I'm
sure
it's
going
to
be
something
along
the
lines
of.
B
What's
sake
should
I
join,
but
if
anybody
is
there
and
would
like
to
help
you
know,
so
we
have
a
cnc
of
Goutham.
No,
it's
not
a
CNC
F
booth,
it's
a
an
actual
3-hour
slot,
that's
in
their
Community
Day
and
other
projects
will
be
there
too,
like
other
CN
CF
projects,
but
it's
not
a
CNC
F
booth.
Okay,.
B
Cool
all
right!
Well,
if
anybody's
interested,
that's
why
I'm
just
putting
out
the
last
call
I
might
add
like
a
couple
I'm
not
going
to
like
add
slide
slides
but
like
I,
might
put
a
slide
up.
That
has
like
the
new
contributor
workshop
like
bit
ly
links
and
some
other
hot
links.
People
might
be
interested
in
while
they
fly
by,
but
not
structured,.
B
K
Sure
I
have
a
PR
out
for
that,
and
you
know
it
is
going
to
allow
us
to
say
the
this
is
you
know
forgiven.
Org
here
are
the
members
that
we
want,
and
here
are
the
admins
here.
Are
the
teams
and
here's
who's?
An
exceedance
lived
in
sin
PRS,
that's
gathering
with
people
too
there
and
you
have
to
hopefully
make
it
a
little
bit
more
obvious
live
when
we're
at.
You
know
sure
that
the
actual
org
member
list
is
what
we
want
and
there's
no
extra
we're.
K
K
C
K
But
I'm,
you
know,
there's
other
orgs
outside
of
kubernetes.
I
know
that
are
interested
in
this,
so
I
want
to
design
it
to
be
sort
of
the
base
thing
to
be
generally
applicable
to
any.
You
know
large
org,
that
wants
to
manage
themselves.
This
way,
I
think
we
might
want
to
have
on
some
additional
layers
that
maybe
help
make
it
easier
for
kubernetes
to
like
the
specific
you
know,
dialect
of
kubernetes.
We
would
think
we
want
to
do.
K
We
could
sort
of
take
a
maybe
secondary
configuration
that
generates
this
first
one
like
how
we
have
multiple.
We
have
both
you
know
kubernetes
and
kubernetes
SIG's.
Maybe
we
want
the
members
of
that
to
be
exactly
the
same
or
something,
but
to
start
out
with
I
wanted
to
sort
of
have
a
basic,
dumb
thing,
which
is
mostly
concerned
with
here's
the
you
know:
here's
the
membership
list
that
I
want
and
then
reconcile
that
with
the
actual
membership
list
in
github.
B
F
Alright
I'll
be
fast.
Let
me
just
share
my
screen.
Real
quick,
everyone's
favorite
thing
in
the
world
numbers
can
y'all
see
that
so
part
of
my
kep
was
to
share
weekly,
how
the
discuss
kubernetes
prototype
is
doing
traffic
wise
and
then
over.
The
course
of
the
prototype
will
decide
if
it's
a
success
or
not
so
basically
kind
of
soften
my
new
camera.
Sorry,
so,
basically,
the
way
it
works
is
we
kind
of
soft
launched.
Last
week
after
I
got
the
domain
set
and
everything
with
Tim
and
I
started
to
let
the
the
numbers
generate.
F
Everything
earlier
here
is
like
when
it
was
like
me
and
Josh,
like
posting
and
stuff,
like
that,
so
I'm,
mostly
concentrating
on
this
part
of
the
graph
we
have
about
265
users
signed
up
and
14,000
views
in
the
in
the
last
few
days.
Now
we
were
kind
of
limping
along,
and
then
Joe
mentioned
us
on
TGI
K,
which
really
helped,
though
that
brought
us
a
set
of
flux
of
new
users,
and
the
amount
of
new
users
coming
in
is
good.
F
The
amount
of
posting
is
not
as
awesome
as
I'd
like
so
what
I'm
doing
is
I'm
grabbing
people
who
typically
don't
have
a
place
to
post
things.
So
we
had
a
few
people
in
slack
that
wanted
to
announce
projects
that
they
were
working
on,
and
maybe
they
were
spamming
somebody,
so
we
encouraged
them
to
post
there.
Instead,
that
kind
of
thing
a
more
ecosystem
to
me,
things
where
people
would
feel
uncomfortable
posting
that
to
the
developer
list
and
I'm
also
running
a
giveaway
for
new
users
to
like
win
a
kubernetes
t-shirt.
F
That
sort
of
thing
one
interesting
thing
is:
we
used
a
live
thread
this
morning
during
office
hours
for
people
to
post
questions
and
paste
notes
and
stuff
back
to
each
other
and
I
felt
I
felt
that
went
pretty
well,
that's
why
it's
probably
the
number
one
topic
right
now.
The
only
thing
I
could
really
use
help
with
is
posting
content,
so
we're
getting
people
signing
up
and
reading
and
looking,
but
getting
people
to
interact
has
been
a
little
bit
harder
than
then
I
would
have
liked.
F
So
if
you
have
something
interesting
to
post,
even
if
it's
an
announcement,
you've
already
posted
it,
do
me
a
favor
and
post
it
in
the
announcement
section
and
I'm
doing
things
like
every
week,
I'll
be
posting.
The
community
meeting
notes
in
a
separate
thread
that
sort
of
kind
of
thing
to
kind
of
give
people
content
to
consume
and
things
like
that.
But
any
questions
or
comments.
B
Lc
and
I
are
going
to
go
in,
hopefully
the
next
month
at
some
point
start
attempting
to
use
github
projects
so
that
we
can
keep
our
head
on
straight
better
and
start
to
better
manage
umbr.ella
issues
and
things
like
that.
But
we'll
talk
about
that
in
greater
detail
as
we
get
there,
but
better
project
management
is
on
the
way.
D
B
Talked
to
him
on
Monday
yeah
yeah,
he
was
on
the
retro
call
and
I
told
Vanessa
that
we
should
just
go
ahead
and
reserve.
What
did
I
say,
I
think
I
said
seven
to
nine
rooms,
yes
Seattle
and
then
I
also
did
ask
for
a
walkthrough
I
said:
I
would
fly
to
Seattle
personally
for
a
walk-through
and
see
if
we
can
get
a
better
situation
there
and
George
also
offered
and
quite
a
few
other
people
offered
as
well
so
yeah.
F
D
B
B
L
B
F
F
D
F
J
B
B
D
D
You'll
have
a
massive
current
computer
tract
going
on
so,
and
you
know
and
it'll
take
us
a
couple
of
cycles
to
kind
of
nail
down
what
the
roles
should
be,
but
like
I
mean,
for
example,
for
Seattle
I
think
you
should
have
a
volunteer
to
be
a
communications
role.
Know
somebody
who
specifically
is
focused
on
just
getting
the
news
out
about
the
contributors
summit.
Instead
of
me
necessarily
arranging
the
content
right.
C
B
L
D
F
So
people
can
see
it
yeah,
you
know
what
we
knew.
We
know
when
it's
gonna
be
so
just
slap
it
in
slash
events,
slash
2018
and
then,
when
we,
so
we
have
the
meetings
on
the
Mondays
with
with
the
CN
CF
and
then
we'll
just
say:
hey
we'll
start
with
the
github
source
of
truth
will
link
the
spreadsheets
in
there
and
then
we'll
just
iterate
every
week.
Is
that
that's
all
what
you
want
your.
F
B
B
F
L
G
L
G
Thing
that
we
might
need
a
separate
repo
for
is
if
we
want
to
have
a
continuous,
like
contributor
playground
that
has
bought
set
up,
but
is
not
going
to
alarm
and
send
out
notifications
to
anybody
who's
watching
the
community
repo.
If
we
wanted
to
get
it
run
more
of
those
like
new
contributor
workshops,
I'm
having
like
a
a
bot
playground
at
testing
repo
would
not
be
a
bad
idea.
I.
L
D
L
Just
a
final
question
from
me:
probably
if
I've
discussed
it
recently
because
I'm
adjourned
so
late.
So
what
have
we
defined
for
our
plan
for
our
recent
meetings
on
Mondays
with
C
and
C
F
events
team?
So
before
for
Copenhagen,
we
had
a
single,
weekly
or
bi-weekly
meeting
discussing
both
existing
contributors
and
new
contributors
summits.
This
time
we
have
Shanghai
and
Seattle,
and
we
also
have
to
two
major
Sabu
lands
like
for
the
new
contributors
and
for
the
existing
contributors
in
Seattle.