►
From YouTube: WG Component Standard 20191210
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
december
10th
working
group
component
standard
meeting.
This
will
be
our
last
meeting
of
the
year,
we'll
pick
back
up
in
january,
so
welcome
everyone.
We've
got
one
item
on
the
agenda
today,
which
is
from
alex,
which
is
what's
our
path
to
component
config
in
the
controller
manager.
A
Let
me
share
the
notes
here
and
then
alex
won't.
You
get
started.
B
Yeah
sure
so
I
think
mike
and
I
have
been
talking
during
some
previous
office
hours,
that
we
want
to
like
revive
the
effort
and
I
could
look
into
it.
So
I
was
just
trying
to
gather
up
all
the
points
which
have
been
made
recently,
so
I
linked
that
doc,
which
I
created.
I
think
it's
in
the
meeting
notes.
A
B
B
B
There
were
a
couple
of
discussion
lines
and
lucas
posted
this.
This
draft
proposal
for
an
alternative,
and
then
there
were
a
couple
discussion
points
and
I
kind
of
like
went
stale.
Nothing
really
happened.
I
reached
out
to
stuart
and
he
said
he's
quite
busy
with
another
project.
He
won't
be
able
to
work
on
this.
I
think,
but
he'll
be
able
to
like
if
we
have
any
questions
or
so
we
can
ping
back
to
him.
I
think
but
yeah.
B
So
my
idea
was
to
just
maybe
like
look
over
the
current
stage,
which
I
tried
to
like
summarize
here
and
just
discuss
on
how
we
can
move
this
forward.
So
I
think,
like
in
regards
of
where
we
are
right
now
is.
We
do
have
some
some
types
here.
B
B
Yeah,
I
I
saw
like
there's
one
discussion
point
from
stefan,
which
was
was
it
oh.
B
There's
one
here,
it's
kind
of
like
disclosed
pr
where
he
closed
this
one
and
said
it
might
be
attractive,
like
unpractical
to
have
like
50
differently
versioned
objects.
So
I
wasn't
quite
sure
if,
like
this
has
already
been
addressed
in
this
in
this
pr.
A
A
I
think
there
were.
There
were
a
few.
There
were
a
few
things
that
came
up.
One
was
like,
oh
my
god.
This
is
a
lot
of
boilerplate.
If
we
have
to
add
this
to
everything,
one
was
a
lot
of
controllers
like
need
the
same
config
for
the
same
thing
like
for
a
client
or
for
like
maybe
some
auth
stuff
or
something,
and
so
people
don't
want
to
have
to
retype
that
for
every
controller's
config.
A
Another
comment
that
I
saw
in
there
was
that,
like
apparently
it's
not
serializable
today,
but
I
I
wasn't
sure
exactly
what
folks
meant
by
that.
Maybe
there's
just
a
bunch
of
runtime
stuff
that
needs
to
get
better
separated
out,
but,
like
you
said
it
has
that
v1
alpha
one.
So
I'm
not
sure
exactly
you
know,
but
we
we
need
to
chase
that
down.
C
A
A
A
And
you
know
we
we
have
to
like
remember
our
main
goals
right
like
getting
onto
component
config
in
the
first
place,
is
a
huge
win,
and
so,
if
we
have
to
make
a
few
compromises
short
term,
get
there
and
say
hey
look.
These
will
be
bundled
in
one
big
api
group
for
controller
manager.
For
now,
and
maybe
in
the
future,
we
split
them
out.
If
that
resolves
a
discussion
that
could
be
like
a
months
long
bike
shed
and
gets
us
moving
forward.
It's
the
right
thing
to
do
at
this.
B
Point
so
what
would
be
like
what
would
be
a
good
like
actionable
point
here
in
regards
of
picking
this
up?
I
guess,
if,
like
stuart,
can't
spend
time
on
this,
should
we
like
carry
all
the
work
from
that
cap
and
extend
that
what
would
be
the
best
way
forward?
Yeah,
that's.
A
B
B
Maybe
we
can
spend
some
time
in
during
the
office
hours
to
maybe
look
at
the
code
a
little
bit
more
in
detail,
and
you
know
I
I.
I
still
have
some
questions
on
how
how
this
all
like
works
together
and
what
could
be
like
good,
good
points
to
address.
Yeah.
B
Then,
like
on
this,
so
like
there
are
a
couple
couple
places
right,
so
I
think
this
cap
is
it's
kind
of
like
isolated.
I
feel
they
have.
We
have
like
this.
Have
this
issue
here,
but
hasn't
hasn't
been
mentioned.
I
think
yeah.
A
B
Be
an
easier-
maybe
we
can
like
pick
up
this
issue
since
this
opener
system
discussion
on
it,
and
basically
maybe
I
have
a
summary
on
what
we
discussed
here-
that
we're
moving
this
forward
and
that
will
you
know,
work
on
a
cap
or
something.
B
Cool
yeah,
then,
let's
spend
some
time
during
the
office
hours
and
check
out
the
code
a
little
bit
more.
A
Sweet
all
right,
that
was
our
first
kind
of
agenda
item.
Does
anyone
have
anything
else
they
want
to
talk
about
today.
A
All
right
cool,
so
we'll
pick
up
our
next
meeting
on
january,
7th
same
time
still
tuesdays,
so
happy
holidays,
folks
enjoy
the
time
off
and,
and
you
know,
have
fun
relax
a
little
bit
one
more
one.
B
One
more
question
you
mentioned
in
slack
that
the
zoom
is
going
to
change.
A
Yeah,
so
we
have
right
now
we
have
two
separate
zooms.
One
is
the
one
we
are
using
for
this
meeting
and
one
is
the
one
we
used
for
the
office
hours
meeting
the
office
hours
made
me.
The
zoom
account
that's
actually
owned
by
the
chairs
of
the
working
group,
and
the
one
we're
currently
using
for
this
meeting
is
like
a
sequence
or
lifecycle,
one
that
conflicts
with
their
meetings.
A
So
I
want
to
since
sometimes
the
meeting
like
runs
way
over
the
30
minute
time,
and
then
people
start
joining
from
their
one
of
their
meetings
and
kicking
us
out.
I
want
to
switch
it
so
that
we
don't
have
that
conflict
anymore.