►
From YouTube: CNB Team Leads 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).
C
Yeah
so,
let's
see
for
on
the
platform
side
really
there's
been
a
primary
focus
on
Pac
we
have
the
Google
summer
of
code,
mentorship
still
happening
for
the
cash
flag
implementation.
So
we've
got
a
good
majority
of
that
work
done
and
working
to
finalize
some
of
that
from
there
we'll
create
a
sort
of
like
blog,
post
or
whatnot,
to
try
to
promote
that
aspect
of
things.
C
Other
than
that
we
resolved
a
couple
of
CI
issues.
It's
been
a
while
now,
but
we
did
move
one
of
our
custom
Runners
to
GitHub
Runner
Natalie.
Thank
you
for
that
and
let's
see
working
on
improving
acceptance
tests.
That
seems
to
still
be
one
of
the
major
hindrances
to
you
know,
contributors
that
are
coming
on
board
to
the
project
so
trying
to
see
what
we
can
do
there
to
simplify
some
of
that
stuff.
E
For
implement
education,
we
have
this
long-running
open
track
of
work
for
Shell
removal
and
overrideable
arguments
that
Mikey
was
driving
for
the
like
pick
that
up
and
put
up
a
PR
for
it,
but
as
I
was
reading
over
it
going
back
and
looking
at
the
spec
and
then
going
back
and
looking
at
the
life
cycle
to
see
what
we're
actually
delivering
here.
E
So
I
opened
a
slack
Thread
about
that.
You
know
so
just
bringing
that
up
on
the
docker
files
side
of
things.
I
know
last
working
group,
I
kind
of
surfaced,
the
issue
that
registry
creds
are
readable
by
Docker
files
when
you
use
kaniko,
because
there's
no
trout
and
we
kind
of
talked
about
different
things
that
are
happening
on
the
conical
side.
E
There's
an
open
PR
that
would
Implement
a
trout
like
capability,
but
with
more
minor
tweaks
to
your
permission,
settings
than
like
actual
truth,
I
did
ask
Stephen
about
that,
and
his
kind
of
opinion
was.
You
should
do
whatever
you
can
to
avoid
messing
with
the
you
know
like
container
settings
at
all
right
and
I
had
this
idea
for
a
very
complicated
workaround.
That
would
basically
not
require
registry
credits,
because
all
of
the
images
would
be
placed
on
the
file
system.
E
You
know
beforehand
by
the
platform,
so
I'm
working
through
things,
I
have
a
couple
of
options.
Build
image.
Extension
is
easier,
so
we
can,
you
know,
probably
shift
that
first
more
to
come
here
and
then
also
around
darker
files
and
extensions
open
questions
about
how
rebase
will
work.
E
I
know
we
had
some
discussion
a
couple
working
groups
ago,
and
we
talked
about
it
briefly
yesterday
at
the
Capac
working
group,
I
have
some
questions
but,
like
my
fundamental
question
is
whether
we
can
actually
go
ahead
and
merge
the
RFC,
given
that
there's
this
outstanding
uncertainty
and
there
will
be
more
uncertainty
like
the
further
we
go
in
the
implementation.
There
will
be
more
questions,
I'm
sure,
but
we're
now
in
like
this
chicken
and
egg
situation,
where
we
can't
like.
E
E
We
can
add:
well,
we
could
add
them
to
the
agenda
or
to
the
working
group.
I
actually
can't
make
the
working
group
tomorrow
so
I,
interestingly,
I'm
doing
a
live
stream
like
hoe
with
Whitney
Lee,
who's,
VMware,
employee
and
also
the
creator
of
content.
You
know
describing
various
open
source
projects
and
I
agreed
to
talk
to
her
about
build
pack
so
I'm
doing
that
tomorrow
and
therefore
I
can't
make
the
working
group,
but.
A
E
Yeah
it's
one
of
those
things
where
I'm
actually
like
I.
She
assures
me
it
will
be
fine,
but
it's
like
it's
like
giving
a
talk,
but
you
don't
prepare
anything
beforehand
and
you
just
go
and
she's
like
tell
me
about
Phil
packs
and
she
kind
of
like
draws
it
out
as
we
go
to
so
she's
like
don't
worry,
it'll
be
fine.
Okay,.
E
F
A
The
I
think
the
general
implementation
of
profilable
package
done
in
most.
One
of
the
things
that
came
up
was
the
profile.
Script
is
now
being
run
twice
because
lifecycle
obviously
runs
it
and
the
buildback
is
now
trying
to
run
it.
So
we
are
just
waiting
for
World
pack
online
and
we
will
set
that
as
the
minimum
value,
because
we're
assuming
that
once
life
cycle
supports
build
back
online,
it
will
remove
the
support
for
sourcing
the
profile
script
and
the
application
directory.
At
that
point,
it
will
just
run
it
once.
A
F
F
A
Yeah,
so
that's
that's
again,
something
we
should
talk
about,
but
I
think
there's
like
the
profile
day.
Removal
and
there
are
other
changes.
We
also
made
as
part
of
that
to
get
to
change
how
input
arguments
are
interpreted.
It's
not
got
nothing
to
do
with
profile
day.
Just
how
input
arguments
to
the
process
are
interpreted.
I
think
it's
valid
to
ship.
Those
launches
changes
so
like
if
you're
running
and
build
back
process
contributed
by
a
new
buildback
API
version,
which
is
used
the
new
process
type
to
interpret
the
arguments
the
new
way.
A
Only
if
you're
doing
launcher
hyphen
knife,
you
know
like
running
or
direct
launcher
process.
That's
that's
where
the
breakage
happens.
Breakage
doesn't
happen
on
the
build
pack
API
side
of
things
like
if
you're,
using
the
launcher
through
a
build
pack
provided
process,
then
it's
up
to
the
buildback
to
control
and
interpret
the
arguments.
However,
it
wants
to
the
double
hyphens
were
never
part
of
the
build
pack
process
contract.
A
Yeah
but
then
it's
a
new
build
pack
version
right,
like
you,
whoever
has
done
like
Whoever
has
bumped
up
the
buildback
API
version
would
have
knowingly
said:
I
am
bumping,
this
build
pack
version,
and
this
is
the
new
Behavior
that
the
process
contributed
by
this
build
pack
as
whereas
switching
the
launcher
is
not
something
the
build
pack
author
can
control.
It's
not
like
it's
potentially,
not
even
something
that
the
Builder
Creator
can
control.
It's
like,
whatever
the
version
of
the
life
cycle
that
is
being
used
by
the
platform
during
the
invocation
controls.
A
A
E
A
A
But
that
you
can
communicate
as
the
build
pack
owner
rate
like
whoever
is
the
end
user
is
using
a
set
of
build
packs
from
someone
or
a
builder
from
someone
and
like
the
the
point
is
that
it
shouldn't
depend
on
which
version
of
pack
or
life
cycle
they
have
locally.
It
should
depend
on
the
build
packs
and
Builder
that
they're
using
so
I
as
the
Builder
owner
or
the
build
pack
owner
can
control
what
Behavior
would
be,
rather
than
whatever
platform
you're
running
it.
On.
E
A
It
can
I
can
explain
like
the
motivation
on
why
that
launcher
change
was
a
breaking
change
versus
why
this
buildback
change
will
still
be
fine.
Maybe
in
the
working
group
we
can,
but
we
can.
The
buildback
API
release
will
definitely
be
useful
like
and
I
can
explain,
but
it's
not
to
call
my
work.
Okay,
thank
you.
A
A
So
there's
this
Library
called
Venom,
which
is
also
used
by
Arkham
in
the
ghetto,
but
I
took
a
slightly
different
approach
to
that.
Just
wanted
to
share
it.
If
someone
is
looking
into
it
works
with
any
language,
declario
yaml
file
and
write
integration
test
for
your
buildbacks.
G
From
the
learning
team
site
we
had
three
new
documents:
one
overview,
buildback
phrases
on
the
buildbacks.io
talks,
another
one
that
does
have
a
bit
of
a
bug
in
it
on
caching
strategies,
but
I'll
fix
that
before
next
week
and
then
I
don't
know
if
I
said
it
last
week,
but
we
landed
the
videos
on
dotpacs.io,
so
yeah,
that's
pretty
cool.
G
D
So
an
old
old
colleague
of
mine
who
works
at
Docker
now
reached
out
to
me
the
other
day
and
they
want
to
restart
conversations
about
getting
build
packs
into
the
docker
CLI
or
you
know
what
we
had
started
before
so
I
told
them
I'm
traveling
this
week
and
I
was
going
to
try
and
set
up
something
next
week,
so
I'm
wondering
if
y'all
I
told
him
I
should
bring
some
like
team
leads
and
stuff
like
that.
So
I
was
wondering
what
what
time
works
like.
D
D
C
You
I'm
curious
as
to
what
sort
of
integration
Point
we're
thinking
about
or
they're
thinking
about
and
maybe
like
yeah.
D
He
didn't
give
me
he
didn't
give
me
any
details
so
I'm,
but
I
from
that
I
gather
that
they're
like
pretty
open
to
what
we're,
what
what
we're
thinking,
which
might
be
nothing
but
yeah
I
mean
to
me.
The
big
thing
is
like:
how
do
you
know
you
want
build,
packs
and
I
think
it
like
it
kind
of
circles
back
to
like
pack,
Tamil
or
project
Tamil,
or
something
like
that.
D
So
I
we
but
I,
don't
know
I
think
we
had
some
good
ideas
in
the
past,
so
maybe
there's
something
we
can
dig
up.
C
Yeah
because
I
think
and
the
two
that
come
to
my
mind,
real
quick
are
the
Docker
CLI
specific,
like
extensions
or
plugins,
like
that's
one
route,
but
that's
like
a
just
a
separate
binary
that
people
would
install
or
come
out
of
the
box
whatever
right,
then
there's
the
front
end
for
the
build
kit,
Docker
files,
which
is
a
more
integrated
method,
but
I
think
we
still
have
some
technical
challenges
that
we
haven't
really
solved.
For
that
there's.
A
A
Yeah
there's
a
Docker
desktop
extensions
thing.
That's
recently
come
out,
which
is
like
a
GUI
thing
that
shows
up
in
Docker
desktop,
and
you
can
add,
essentially
a
web
app
there,
that
you
can
use
to
add
enhancements
to
Docker
so
that
you
can
have
something
that
says,
like
browse
a
folder
and
then
show
the
build
process.
So.
A
C
I'm
gonna
go
ahead
and
just
in
the
document
that
we
have
list
out
the
three
options
that
we
have
for
anybody,
that's
curious
and
then
we
kind
of
take
it
from
there
as
well.
B
I'll
ask
him,
because
if
he
doesn't
want
it
recorded,
then
I
would
potentially
not
recommend
doing
it.
Maybe
during
this
man,
unless
we're
just
killing.
B
G
I,
don't
expect
a
learning
team
meeting
next
week
as
I'm
away,
so
you
can
use
that
time
slot
either
yeah.
B
A
F
F
D
I
kind
of
picture
you
as
that:
what's
the
narcos
guy
or
he's
like
standing
in
the
pool
and
he's
looking
all
somber.