►
From YouTube: Config Working Group 9/5/2019
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
All
right
so
they're
recording
yeah,
so
this
plan
is
based
on
some
of
the
work
that's
already
in
flight,
so
one
four
is
going
to
be
a
short-term
release
cycle.
We
have
roughly
five
weeks
of
at
that
time
to
get
this
landed
and
the
overall
team
is
most
likely
gonna,
be
usable,
t,
reliable,
t,
stability
and
simplicity.
Right
so
will
be
that's
the
TLC
rejection
guidance
that
we
expect
to
be,
and
we
have
a
few
items
in
the
list
and
I
think
some
of
this
stuff
may
change
in
in
terms
of
priority.
A
So
the
first
thing
we
have
is
the
multi
object
analysis,
so
the
work
has
been
going
on
in
this
space
for
a
while.
So
we
are
trying
to
align
between
key
any
spirit
on
this
one.
There
are
some
discussions
going
on
and
I'm
hoping
that
we
will
actually
reach
a
consensus
on
this
one
soon.
The
outcome
of
that
will
be
a
building
model
to
be
established,
and
then
we
can
start
unifying
rule
sets
and
essentially
ruling
so
there's
also
existing
functionality.
Mr.
A
huttle
hoarding
validation
that
should
be
subsumed
into
this
work
and
then
one
thing
I
added
here
is
to
actually
add
online
documentation
that
we
can
refer
to
right.
So
the
idea
here
is
to
we
can
incorporate
error
codes
that
are
easy
to
search,
and
then
we
should
have
online
documentation
describing
what
the
problem
is,
so
that
user
kind
of
users
can
easily
go
out
find
them.
So
we
also
want
to
actually
expose
this
semantic
analysis
through
the
CID
is
status
fields.
So
there
is
a
prototype
for
this
already
in
place.
A
It's
about
land
and
it
may
be
in
a
couple
weeks,
but
it
is
not
production
ready.
So
41.4
is
a
p2.
We
should
get
it
and
make
it.
You
know
productionize,
but
still
have
it
protected
by
a
flag
of
by
default,
and
that
has
me
son
asks
coming
in
about
creating
an
API
head
from
galleys,
so
that
yelling
can
actually
expose.
The
whole
error
sets
from
a
single
point
instead
of
like
having
these
dispersed
across
multiple
series
text
fields.
A
A
A
A
We
should
have
JSON
schema
definitions
embedded
in
our
series
and
then,
if
we
can
replace
our
hand-rolled
validation
code
with
cubase
rules,
that
would
be
great
I
think
so
that
actually
allows
us
to
move
a
lot
of
the
manual
well
vision
into
just
some
simple
declarative
form
that
can
be
co-located
with
the
protoss,
which
is
also
the
another
nice
aspect
of
this
and
I
think
the
biggest
cost.
So
this
one
is
going
to
be
just
like
kind
of
having
this
publicized.
You
know
among
the
es2
folks.
B
A
D
A
There's
a
bunch
of
getting
promised
here
so
the
next
thing
is
all
of
these
pieces
are
already
implemented.
It's
just
that
their
flag
protected
today
and
they're
off
by
default.
So
we
need
to
enable
likely
do
something,
a
bit
more
testing
and
enable
that
and
on
by
default
for
one
point
first,
so
this
is
actually
mostly
test.
Cost
is
mostly
on
the
test
side.
There's
also
a
little
bit
of
functionality
that
I
want
to
actually
move
from
point
of
together,
so
that
we
can
make
pilots
communities
agnostic.
A
A
So
very
linked
is
this
is
essentially
creating
a
version
conversion
of
a
book
for
multiple
API
versions
and
actually
is
asking
you
to
escalate
this
prior
to
eyes.
So
you
know
I
Jason,
we
discussed
about
like
you,
may
be
tackling
this
work
yeah.
So
if
this
goes
higher
priority,
you
think
you'll
be
able
to.
D
Yeah
I
think
I
can
so
are
we
targeting
just
one
for
us
yeah
again:
okay,
yeah.
Let's
talk
about
this
in
more
detail
because
I
I
don't
have
very
big
technology
in
the
web
hook.
Yet
so,
let's
talk
about
and
about
the
timeline,
I
think
kind
of
what?
When
do?
We
want
to
end
this
kind
of
what
it
marks
or
something?
Okay,
yeah.
A
C
A
D
A
And
the
final
thing
is,
we
start
looking
at
some
API
model
improvements,
so
right
now,
I'm
working
on
a
document
for
establishing
the
principles
I'm,
hoping
that
by
the
next
meeting
it
should
be
available
early
for
review
broadly
and
essentially
for
41.4.
We
want
to
have
those
principles
established
and
accepted
and
then
starts
on
proposals
on
how
we
modify
existing
resources
or
introduce
new
ones
and
I
think
that
those
will
come
in
later
workgroup
meetings.
B
A
Miss
Cheerilee
I
mean
it's
usually,
so
there
are
dependencies
that
we
need
to
break
some
Eliquis
work
needs
to
be
done,
like
the
validation
work
is
the
primary
thing
before.
Even
we
can
attack
that
and
then
given.
This
is
like
an
already
busy
schedule.
It
five-five,
depending
on
the
priorities
right
so.