►
From YouTube: WG Component Standard 20190618
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
Okay,
welcome
everyone
to
the
tuesday
june
18th
working
group
component
standard
meeting.
We've
got
a
couple
items
on
the
agenda
today
and
I
think
lucas
also
has
an
announcement
to
make
so
I'll
I'll
wait
for
him
to
join
to
make
that
announcement,
and
we
can
just
start
in
on
the
rest
of
the
agenda
here.
B
This
patch
has
been
up
for
quite
a
while.
What
we've
found
definitely
is
that,
through
the
process
of
making
the
necessary
changes
to
api
machinery,
there's
some
bottlenecks
with
just
getting
reviews
and
feedback,
and
I
think
that
I
know
I
personally
can
put
more
effort
into
creating
some
relationships
there.
I
know
lucas
worked
with
stefan
out
in
kubecon
to
kind
of
chat
about
how
we
can
help
out
there,
but
this
patch
is,
I
think,
pretty
done.
B
There's
like
maybe
one
thing,
which
is
make
some
better
doc
strings,
but
it's
got
tests
now
that
exercise
the
paths
have
changed.
So
if
anybody
wants
to
come
in
and
also
we
don't
have
anybody
new
to
the
group
here,
I
guess
we
did
have
a
new
contributor
looking
to
help
out,
but
yeah
I
mean
reviewing
these
code
bits
I
don't
know,
might
be
helpful
for
somebody
but
yeah
the
this
should
be
good
to
go.
So
we
can
get
this
in
once
the
is
116
open.
C
B
A
A
A
Yeah,
okay,
I'm
glad
that
she
looked
at
that.
I
asked
her
to
take
a
look
at
that
also,
so
I
will
I
will
try
and
get
to
that
this
week.
D
Yes,
it
has
only
minor
changes
compared
to
the
dock.
Basically,
I
changed
the
like
the
terminology,
a
bit:
it's
like
now
now
it's
using
local
and
shared
config,
as
opposed
to
node
and
cluster
config,
and
it's
made
to
resemble
a
little
bit
more
recap.
B
I
will
add
the
link
to
the
notes.
I
just
oh
great,
thank
you
for
being
that
way.
A
Yeah,
so
I
guess
lucas
still
isn't
here
so,
let's
still
move
forward,
so
lucas
has
kind
of
announced
that
he
doesn't
have
time
to
chair
this
working
group
anymore
and
so
he's
going
to
be
stepping
away
unfortunately,
and
he's
proposed
that
lay
takes
his
place.
A
So
I'm
not
exactly
sure
what
the
official
process
is
for
making
that
proposal
and
like
getting
the
plus
ones
in
like
we've
kind
of
already
seen
that
in
slack
but
it.
What
I
think
would
probably
make
sense
is
for
lucas
to
send
an
email
to
our
mailing
list
kind
of
outlining
all
of
that
and
making
the
proposal,
and
then
we
can
get
the
plus
ones
recorded
there.
B
Thanks
for
that,
mike
yeah
yeah,
it
does
make
me
you
know
a
little
a
little
sad,
because
lucas
has
just
been
a
big
mentor
for
me,
and
I
wish
I
would
have
had
more
time
to
kind
of
bounce
things
off
him
for
this
project.
But
the
the
work
of
this
working
group
is
quite
important,
for
I
think
everyone's
best
interest
in
kubernetes.
A
Yes,
I
agree
with
that,
and
it
also
sounds
like
he's
not
going
to
be
he'll
be
available
to
talk
to
you
still
just
he
doesn't
have
time
to
work
directly
on
things
anymore.
A
B
As
far
as
like
helping
people
get
on
board
to
this
project,
like
the
work
of
the
working
group,
is
very
heavily
rooted
in
design
stuff
right
now,
how
can
we
help
people
who
want
to
get
involved,
because
I
know
tim
has
been
making
an
effort
to
get
the
word
out
to
new
contributors,
that
this
is
the
space
that
we
need
help
in.
A
Yeah,
it's
a
really
good
question
that
I
I
don't
have
a
good
answer
for
yet,
and
part
of
it
is,
is
just
like
a
lot
of
this
there's
so
much
historical
context
and
state
in
like
we're.
Basically,
this
is
like
a
refactoring
working
group
right.
So
there's
all
this
like
sort
of
understanding
that
we're
trying
to
bring
to
existing
situations
so
like
how
to
build
that
quickly
and
a
new
contributor
is
the
main
question
for
me
and
we
obviously
need
more
people
to
help
us.
A
So
we
kind
of
need
to
figure
out
how
to
get
them
up
to
speed
on
how
to
think
about
these
designs,
and
maybe
that's
just
a
process
of
encouraging
them
to
make
suggestions
so
that
we
can
review
and
getting
more
people
coming
in,
because
I
don't.
I
really
don't
know
how
to
build
that
expertise,
like
other
than
you
know,
taking
the
chance
of
trying
something
and
then
getting
feedback
from
other
people.
A
You
know,
like
you,
guys,
have
all
sent
prs
and
caps
and
other
things
with
suggestions
for
this
working
group
and
then
those
have
been
pretty
heavily
reviewed
and
that's
built
your
expertise
up.
So
we
kind
of
need
more
people
to
do
that,
and-
and
I'm
wondering
if
there's
ways
we
can
be
encouraging
like
along
that
route
for
someone,
because
it
can
be
pretty
discouraging
to
just
get
like
all
this
massive
amounts
of
feedback
and
design
tweaks
and
stuff
for
months.
While
you
try
to
get
a
design
resolved.
D
So
we
can
basically
point
these
tracking
issues,
new
contributors
and,
like
tell
them
hey,
there
is
a
certain
thing
that
needs
to
be
done
in
order
for
this
gap
to
be
implemented.
D
A
A
F
Right
we
we
should
do
or
we
could,
let's
start
with
just
just
to
say
that
yeah
I'm
going
to
you,
might
know
that
I'm
going
to
university
and
I'm
a
bit
disappointed
that
first
I
had
to
be
in
military
service
and
now
going
to
university,
and
now
I
just
realized-
I
don't
have
enough
time
here
in
between
to
to
actually
give
give
the
attention
that
this
work
group
needs
as
a
lead.
So
then
it's
better
to
free
up
the
place
to
someone
else.
For
example.
F
Yes,
as
mentioned
there,
but
yeah
right
so
so
dancer,
that's
a
context
and
I'm
sorry
to
just
see
that
be
that
way.
But
well
stuff
life
happens
right.
So
what
we
could
do
is
the
same
as
we
did
in
a
cluster
lifecycle.
So
we
have
one
dedicated
meeting
sometime
to
just
just
for
new
contributor
onboarding,
so
basically
walk
through
all
the
code.
That
is
relevant.
F
Talk
through
different
concepts
give
background
that
you
know
you
know
like
one
or
two
hours,
even
whatever,
whatever
fits,
and
that
will
help
all
those
who
are
interested
in
contributing
can
should
I
should
join,
and
then
I
I
can
be
there
and
and
everybody
else
that
is
relevant
once
we
find
such
a
time
and
we
can
well
as
it's
recorded.
We
can
just
point
to
that.
That's
what
we
do
as
a
class
lifecycle
point
to
that.
Every
time
somebody
says
I
don't
know
how
to
start
with
cubadem.
A
That's
a
great
idea:
we
should
definitely
do
that
yeah,
let's,
let's,
let's
think
about
putting
some
plans
together
for
that
kind
of
meeting
and
then
advertising
it
so
that
people
can
come.
A
I
mean
yeah,
we're
sorry
to
see
you
go,
but
we
understand,
like
life,
happens,
yeah.
So.
F
Yeah,
well
I
mean,
and
the
the
good
thing
about
it
is
that,
although
not
being
a
lead,
doesn't
stop
me
from
from
doing
actual
work.
If
that
would
be
the
case
that
I
have
say
that
never
happens,
but
I
say
I
would
have
two
days
free
to
do
whatever
I
want
and
then
I
decide
that
now
component
standards
should
get
some
some
previews
or
something
then
I'll
I'll.
Do
it,
but
but
it's
more
yeah
as
a
lead.
A
You
know,
and
you
have
to
manage
your
focus,
so
we
understand
that
I
think
you
know
I
agree
with
lee's
nomination
and
I
think
a
lot
of
other
people
do
as
well.
So
I
I'm
not
exactly
sure
what
the
official
process
for
this
is,
but
I
would
ask
that
you
sort
of
send
an
email
to
the
working
group,
mailing
list
kind
of
announcing
your
transition
and
making
that
proposal
for
leave.
So
we
can
just
get
the
plus
ones.
A
B
B
G
George,
I've
been
yeah.
I've
been
trying
to
I've
been
here
for
the
last
couple
of
videos
just
to
just
to
figure
out
like
what
things
you
are
all
working
on
to
see
a
word
best
to
help,
and
I
guess
actually,
while
you
what
you
were
talking
about,
how
to
get
new
contributors,
and
I
guess
and
the
things
that
you
need
done,
are
camp
reviews
or-
and
I
see
a
couple
of
pr's
open
in
the
from
the
project
from
the
github
project.
B
No
yeah,
thank
you.
So
much
for
joining
george
yeah
feel
free
to
to
speak
up.
We
would
love
to
help
you
identify
places
where
you
can
start
to
grow
and
apply
your
existing
skill
sets
and
perspectives.
Are
you
using?
Have
you
been
using
kubernetes
for
a
while?
Do
you
have
pain
points?
What
what
has
your
interest
in
the
project.
G
Overall,
I
just
love
the
community
but
yeah
long
term,
a
long
time
user
trying
to
see
where
I
can
help.
B
Cool
yeah
we
we
definitely
have
some
things
that
can
be
reviewed
if
you're,
if
you're
looking
for
something,
maybe
more
esoteric,
the
first
link
in
the
agenda,
it's
a
patch
that
I
put
together
that
makes
some
changes
to
api
machinery
and
it's
it's
a
little
bit
of
a
fun
spelunk.
B
Also
yeah,
the
the
coop
controller
manager.
Kep
is
an
interesting
problem
because
it's
a
controller
manager.
It
has
a
collection
of
other
component
configs
and
then
the
coupe
proxy
kept
that
russ
just
put
up.
I
need
to
look
at
that,
but
that
one's
moving
from
an
alpha
to
beta
api.
So
it's
a
little
bit
less
less
crazy.
A
A
And
then,
in
addition
to
that,
we
also
have
all
the
legacy
flag
stuff,
that
library
merged
the
first
version
of
it
merged
a
few
weeks
ago,
and
we
need
to
prototype
actual
examples
against
like
q,
proxy
or
cubelet
with
that
library,
which
I've
been
meaning
to
do
at
some
point,
but
haven't
had
time
yet.
E
A
We're
all
available
on
slack,
you
know,
feel
free
to
ping
us
with
questions
or
express
your
interests
and
we'll
do
our
best
to
help
out.
G
F
Right
thanks,
I
I
could
just
add
that
I'm
I'm
willing
to
mentor
like
or
do
one-on-ones
or
or
stuff
like
that
as
part
of
the
the
transition
in
the
coming
weeks,
but
to
help
other
people
get
get
up
to
speed.
So
so,
if
you're
interested
in
that,
just
just
picking.
A
Me
you,
okay,
everyone
have
a
nice
day.