►
From YouTube: Working Group: July 19th 2023
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
Any
new
faces,
I
don't
see
any
new
faces,
it
looks
kind
of
like
the
same
old,
so
let's
hop
right
into
open
portal.
Quest
first
up
we
have
decoupled
dependencies.
A
I
haven't
had
time
to
work
on
this,
I
have
been
busy
doing
other
work,
unfortunately,
and
it
is
a
bit
of
a
Puzzler,
because
I
have
to
figure
out
how
to
condensed
this
RFC
and
generalize
it
in
hopefully
a
way
that
will
make
it
so
that
we
can
actually
Define
a
solid
contract
to
interface
with
so
I
haven't
had
any
time
to
sit
down
and
get
to
writing.
A
I
have
been
thinking
about
this
off
and
on
when
I
have
the
time,
and
hopefully,
I
will
soon
be
able
to
write
some
stuff
down.
A
A
I
think
he
said
that
he
was
going
to
reach
out
to
the
group
that
he
had
been
talking
to
on
slack
in
the
potato.
Slack
I
don't
know
if
he
did
that
or
had
the
time
to
do
that.
A
Yeah
I
I
discussed
a
little
bit
with
him
around
the
idea
of
like
what
it
would
mean
to
like
add
the
Manifest
to
the
builders
as
well.
So
you
know
or
like
what
kind
of
things
it
would
look
like
to
add
this
capability
to
builders.
He
said
that
he
had
quite
honestly
not
thought
about
it,
because
it
wasn't
in
his
sort
of
purview.
He
was
sort
of
more
sort
of
more
worried
about
the
stacks
and
the
build
packs,
which
was
fair
enough.
A
So
if
that's
something
that's
interesting
to
you,
I
think
that
reaching
out
to
him
makes
sense,
I
think
he's
looking
for
right.
Feedback
on
that.
A
Great
next
up,
CNP
updates,
potentially
relevant,
update,
not
really
update,
just
something
that
I
noticed
in
the
CNB
slack.
The
other
day
was
a
discussion
about
cutting
a
release
of
life
cycle
0.17.0.
A
This
is
relevant
as
far
as
I
can
tell
for
people
who
are
working
on
the
Ubi
track,
because
I
think
currently,
the
only
way
to
get
the
extensions
to
work
is
to
use
a
17,
pre-release,
so
I
think
that
they
are
looking
to
cut
it
soon.
I
think
that
they
are
waiting
for
Natalie
to
get
back
from
vacation.
A
I
think
it's
because
that's
the
version
of
the
life
cycle
that
begins
to
support
extensions,
if
I
recall
correctly
so
like
and
that's
how
we
are
approaching.
The
Ubi
workflow
is
using.
C
Sort
of
related
to
that
at
some
point,
the
CMV
team
is
going
to
start
deprecating
support
for
old
platform
and
build
pack
apis
in
the
life
cycle.
I,
don't
think,
excuse
me
I,
don't
think
that's
going
to
happen
like
imminently,
but
it's
something
that's
been
like
bubbling
for
a
long
time
and
I
think
they.
It
is
likely
that
in
the
next
like
six
months
or
so,
they
will
start
like
more
aggressively
dropping
support
for
old
Bill
pack
and
platform.
Apis
I.
C
Don't
think
it's
going
to
impact
us
for
a
while
on
the
potato
side,
because
we're
using
fairly
modern,
build
pack
apis
like
around
the
six
seven
eight
kind
of
area,
they're
going
to
start
dropping
support
for
like
three
and
four.
You
know
in
the
coming
couple
of
life
cycle
releases
if
I
can
find
a
document
for
this
I
will
share
it,
but
I
saw
one
but
I
can't
find
the
link
for
it
just
yet.
A
No
all
right
does
anyone
have
any
project
updates
that
they
would
like
to
give.
B
I'm
curious
I,
don't
have
an
update,
but
I
do
have
a
question
for
Ozzy
on
Ubi
and
how
that's
going
and
yeah
I
guess
we're.
What?
Where
are
you
at
with
it
and
is
there?
Are
there
there
been
any
challenges.
D
There
have
been
many
challenges,
but
mostly
related
to
updating,
tooling,
to
handle
extensions
that
I'm
still
working
through
with
help
from
Daniel
and
Anthony
and
stuff,
because
the
Ubi
stuff
at
the
moment
I'm
we
kind
of
split
up.
There's
Michael
and
Costa's
been
working
on
the
Node
side
of
it
because
they're
not
using
octo
to
generate
their
pipelines,
so
the
node
side
of
it
is
getting
further
ahead.
I
think
they've
still
got
a
couple
of
PRS
that
need
looking
at
from
their
side.
If
I
remember
rightly
lost
a
chat
with
Michael.
D
He
said
that
they've
hit
a
problem
there,
where
the
Builder
image,
when
it's
published
then
runs
a
pipeline
that
updates
itself
to
the
last
released
life
cycle,
which
isn't
the
one
that
has
all
the
changes
we
need
in.
So
you
know
it's
fighting
itself
at
the
moment
because
we're
running
ahead
of
where
the
current
released
life
cycle
is.
Hopefully
this
should
resolve
itself
next
week
when
Natalie
gets
back
from
vacation
and
that
gets
published.
D
So
then
we
should
start
seeing
life
cycle
releases
that
will
get
drawn
in
and
then
we
won't
be
fighting
the
update
pipeline
trying
to
do
what
it
thinks
is
the
right
thing,
but
isn't
for
for
the
actual
Builder
image.
So
until
then,
we've
got
the
build
pack
list,
Builder
being
published.
We
can't
publish
the
actual
one
with
the
node.js
extension
in
yet.
For
that
reason
we
can't
publish
the
Ubi
Java
extension
into
it,
because
that
needs
an
updated
version
of
octo
which
needed
updated,
lib
pack
and
lip
CNB.
D
We've
worked
through
all
of
that
lot.
We're
just
getting
to
the
point
this
morning
where
we
might
be
able
to
actually
say
that
we've
got
a
version
of
pipeline
Builder,
that's
viable.
So
where
are
we
at
close?
How
long
more
is
it
going
to
take?
That's
the
question
everybody
wants
to
know:
I
mean
if
everything
merges
and
goes
well,
we
could
be
done
and
had
stuff
out
there
within
a
week
or
two
and
I
suspect
after
that.
D
We're
probably
then,
looking
at
a
couple
of
weeks
worth
of
tweaking
and
releasing
additional
stuff,
because
I
know
that
for
the
Java
side,
I'm
gonna
have
to
write
another
build
pack
to
be
a
companion
to
the
extension
and
I
haven't
even
started
that
yet
because
I've
got
the
extension
published
yet
so
once
everything
comes
together,
you
know.
Let
me
see.
Where
are
we
at
now
tail
end
of
July,
so
I'm
guessing
mid-august
at
this
stage
now
and
probably
tail
end
of
August
to
be
sure.
D
That
I've
hit
anywhere
along
the
way
so
far,
I
mean
for
the
stuff
that
we're
doing
for
node
and
Java
we're
literally
just
running
the
one
Docker
file
that
modifies
the
Builder
image
so
yeah
the
Builder
image.
While
it's
running
you're
not
really
worried
about
that
from
a
layer
perspective
and
then
from
a
run
image,
we
will
have
the
same
or
fewer
number
of
layers
that
exist
today.
In
poquito.
A
The
this
these
are
also
fresh
Builders
as
well,
so
the
only
two,
the
only
two
things
that
they
actually
have
running
on
them
are
well
I
mean
there
is
no
Builder
that
is
published
with
anything,
but
the
the
bill
pack
list.
One
will
only
run
you
know
with
like
node
and
Java
once
it
once
it
is
live.
So
we
have
a
little
while
to
contemplate
layer
issues.
As
we
add
language
families
as
necessary,
got.
B
A
All
right
are
there
any
other
question
or
are
there
any
other
project
updates?
I
should
move
on
to
questions.
A
D
D
A
We
can
I
can
reach
out
to
well
I
guess
if
Michael's
already
doing
it,
then
I
probably
don't
need
to
also
harass
the
node
maintainer.
So
I
will.
D
It
was
just
things
taking
a
while,
so
we'll
see
where
we
get
to.
A
All
right
anything
else,
right,
okay!
Well,
thank
you
all
for
this
short
meeting
awesome.
Let
me
see
you
take.