►
From YouTube: 2021-10-06 - CNB Core Team Sync
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).
B
C
All
right,
I'll
start
or
I'll
stop
sharing.
C
C
A
Awesome,
I
don't
know
what
that
means
or
how
we
want
to
deal
with
that.
I
guess
downstream,
but
I'll
take
it
for
this
core
team
sync
and
then
figure
it
out
afterwards.
A
Cool
just
don't
forget
to
sign
the
doc.
If
you
haven't
already
looks
like
I
see
more
than
three
people
in
this
meeting.
A
A
So
there's
new
draft
pr
on
distribution,
spec
emily
opened
up
this
release.
Md.
A
I
think
yeah
david
basie
has
responded
to
some
stuff,
that's
about
it.
I'm
probably
gonna
go
ahead
and
just
split
this
do
some
work
on
this
pr,
but
all
the
stuff
should
still
be
wrong.
I'm
just
gonna
basically
take
out
this
section
and
putting
it
in
kind
of
this
contributing
md
file
yeah.
I
would
love
any
other
feedback.
You'll
have
or
plus
one.
So
I
can
merge
it
in.
A
I
guess
on
the
note
from
last
week,
looking
at
stephen
and
ben
to
chime
in,
I
know
joe's
been
out
this
last
few
weeks,
but
I
will
also
shane
and
bug
him
separately.
A
We
have
stuff
for
basically
platform
08
and
bill
pack
07
coming
down
the
pipe
related
to
probably
the
stack
removal
stuff
is
the
I
guess
releases.
We
want
those
in.
A
For
the
stackmo
rc,
I
work
with
javier
just
to
get
the
merge
stuff
working
locally,
but
the
we're
going
to
merge
that
in-
and
I
think
those
are
some
of
the
biggest
changes
coming
down
the
pipe
is
that
something
we
want
in
basically,
platform
08
and
bill.
Paco7.
B
For
this
spec
releases,
I
I
lean
on
natalie,
for
I
don't
know
what
the
status
of
implementing
that
is.
I
know
the
rfc
made
it
through
and
I
think
some
people
are
going
to
pick
it
up.
Sorry
go
ahead.
D
So
I
I
was
going
to
bring
this
up
later,
but
for
thinking
about
some
of
the
other
features
that
we
have
sort
of
queued
up,
that
might
be
implemented
faster.
So,
for
example,
the
standardized
s-bomb
requires
a
bump
to
both
the
platform
and
the
build
pack
api.
D
If
we
want
to
get
that
out
and
not
have
it
blocked
on
sort
of
the
bigger
changes
which
are
you
know,
removing
stacks,
and
you
know
the
docker
files
work
like
you
might
want
to
place
them
in
different
apis.
A
It's
that
my
consideration.
We've
done
that
in
the
past
of
getting
stuff
out
that
was
already
in
progress
or
smaller,
I
guess
sans
emily
being
around.
What
are
you
thinking
about
for
the
next
platform
release?
A
Is
there
a
spec
change
related
to
the
s
bomb
stuff
for
life
cycle?
There
is.
C
So
if
I
remember
correctly
from
the
rfc,
the
build
packs
themselves
or
the
build
pack,
api
will
have
some
sort
of
key
change
backwards.
Compatibility
where
it'll
accept
the
deprecated
stack
structure
right
like
existing
stack
key.
C
I
don't
know
if
that's
been
necessarily
explicitly
defined
for
the
platform
api
as
well,
but
it
does
kind
of
make
me
think
if
the
build
pack
api
should
be
the
first
thing
to
get
changed
and
then
being
followed
by
the
platform
afterwards,
I
don't
know
if,
if
they
need
to
go
basically
together
or
if
they
could
go
separately,
if
the
build
pack
api
is
backwards,
compatible.
C
It's
the
removing
of
the
stacks
and
mix-ins
right.
D
D
It's
just
so
it's
a
larger
platform
to
deliver
and
we
would
wait
on
the
s1
work
if
we
want
to
do
that.
A
A
And
we
want
to
target
build
pack
of
seven
and
platform
away.
A
Is
there
anything
else
going
into
platform?
Oh
wait
or
build
hacker7.
B
B
A
B
A
Yeah,
this
is
ready.
No
wait
cool
is
that
it.
A
I'm
gonna
assume
yes,
cool.
That
sounds
good.
We
can
revisit
this
next
week
as
well.
If
there
are
more
things
you
want
to
add,
but
I'm
also
happier
with
smaller,
faster
releases
of
stuff
should
move
on
to
rfcs.
A
A
The
combined
organized
metadata
file
locations
across
lifecycle,
not
only
slash
just
me,
yeah.
B
I
haven't
updated
this,
I'm
kind
of
thinking
about
putting
placing
placing
this
on
pause.
Yeah,
I
really
just
haven't,
had
the
time
to
go
through
and
make
the
change
and
yeah,
I'm
not
sure,
unless
anyone
feels
really
strongly
that
we
should
be
pushing
this
because
of
another
rfc
right
now,
I
kind
of
feel
like
we
should
put
it
on
the
back.
B
I
don't
know
if
you
want
to
tag
like
a
bunch
of
rfcs,
but
like
1.0
or
something
like
things
we
want
to
do
before
the
buildback
api
becomes
so
the
platform
api
hits
1.2.
Don't.
B
A
Nope,
no,
not
nerve
ceilin.
It
may
be
worth
talking
about
revisiting
I'm
okay,
moving
it
to
draft.
For
now
we
can
revisit
that
conversation
at
a
later
point.
D
D
D
Maybe
we
could
do
some
sort
of
survey
or,
like
you
know,
try
to
collect
data
on
what
apis
are
most
in
use.
That
could
inform
that
decision.
A
A
B
A
Yeah,
do
you
mind
if
I
assign
you
to
this
natalie?
I
think
we
understand
it
because
emily
I
understand
emily
from
every
rc.
A
Room
stacks
mix-ins.
I
will
be
merging
this
in
I'm
just
like,
I
said,
before,
figuring
out
just
the
merge
rfc
script
stuff,
so
the
bot
things
actually
go
through
with
javier
support.
Docker
files,
steven.
B
I
think
does
this
have
enough
approvals.
Yet
I
thought
I
went
through
everything
got
some
yeah
jesse.
Can
you
do
we
have
everybody
we
need?
Is
there
anything
else.
A
Okay
yeah:
let
me
review
some
of
the
more
recent
changes,
but
I'm
also
happy
to.
A
B
So
I
don't
know
if
I
don't
know,
if
there's
a
big
rush,
no
one
was
holding
off
on
implementing
something.
I
think
right
now,
but
whenever
you
have
a
chance.
A
A
Okay,
simple
plexus
blocks
additional
explorable
layers.
A
Sam
steve-
and
I
just
met
right
before
this
meeting-
to
talk
about
some
alternative
ideas.
I
don't
know
how
you're
feeling
about
that
sam.
Is
that
a
alternative
proposal,
or
are
you
going
to
replace
this
proposal
or
you
want
to
have
both
proposals
on
the
table.
D
A
Cool
any
particular
thing
you
want
to
highlight
from
that.
D
I
had
one
question
about
inline
build
packs
because
we
said
that
the
translation
from
schema
to
schema
should
not
be
lossy
and
at
the
same
time
the
o1
schema
didn't
explicitly
have
anything
relating
to
inline
build
packs
in
it.
So
I
I
made
up
something
where
I
just
stuck
inline
build
packs
under
build
packs
in
the
01
schema,
but
I
don't
know
if
that's
like
completely
unexpected
by
platforms
and
that
will
break
everything
or
if
we
should
just
put
it
in
metadata
or
just
forget
about
it,
because
you
know
too
bad.
D
You
can't
use
inline
build
packs
if
you're
on
o1.
I
called
that
out
as
a
question
in
the
well-
maybe
not
very
obviously,
but
if
someone
who
has
an
opinion
can
jump
in
and
opine.
That
would
be
great.
Okay,.
A
Is
this
something
you
want
to
talk
about
more
tomorrow,
or
that's
the
only
thing
and
you'd
rather
do
that?
I
think.
D
Yeah
we
could
talk
about
it
tomorrow,
maybe
that
that
would
be
helpful
on
the
agenda.
A
C
Yeah,
I
definitely
wanted
to
bring
this
up
as
something
to
discuss
tomorrow,
just
from
a
practicality
standpoint
of
whether
or
not
we
want
to
proceed
with
this
route.
A
Cool
is
there
any
other
rc
or
things
that
we
want
to
put
on
the
agenda
for
tomorrow.
A
A
C
Yeah
yeah,
I
don't
think
we
need
to
discuss
that.
Okay,.
A
Cool
sounds
good.
I
will
try
remember
to
copy
that
over
anything
else.
Before
we
close,
we
are
four
minutes
past.
A
See
head
nod
her
head
shaking,
so
cool
sounds
good,
see
everyone
tomorrow,
I'm
just
gonna
make
it
to
work.