►
From YouTube: Working Group: April 4, 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
All
right,
let's
go
ahead
and
get
started.
Could
I
get
a
designated
Note
Taker
for
today.
A
A
So
we
can
hop
into
it.
It
is
the
first
meeting
of
the
month,
I
believe
so
we
should
be
doing
a
quick
little
road
map
update.
Let
me
share
my
screen.
A
A
C
A
A
D
A
Love
a
shiny
badge
all
right,
so
in
that
case,
then,
how
do
we
actually
drive
out
action
to
do
this
other
than
somebody
just
taking
it
upon
themselves
and
doing
this.
A
A
I
think
that
it's
probably
fair
for
us
to
ping
just
language,
family,
maintainers
in
general
and
say
hey,
go
to
your
go
to
your
readme's
and
check,
probably
go
your
readme's
and
make
sure
that
they're
all
accurate.
You
should
probably
just
give
them
a
read
but
go
your
readme
is
and
make
sure
that
they
are
pointing
at
Docker
images
and
then
to
do
the
same
with
the
website.
So
I
can
start
harassing
people.
Let
me
find
my
notebook.
A
Next
up
we
have
node.js,
Yarns
supports
yarnberry,
I,
think
Tim
who's
been
driving.
Most
of
this
out
is
unfortunately
out
sick.
Today,.
D
I
think
it's
mostly
like
the
barrier.
There
is
there's
just
a
lot
of
there's
a
lot
of
Ruby
start
command,
build
packs,
and
so
it's
just
like
a
bunch
of
work
and
we
haven't
heard
resounding
affirmation
from
the
Ruby
Community.
This
is
like
a
feature
that
they
desperately
need.
So
we
just
haven't
had
a
high
on
our
priority
list
to
get
to.
C
A
D
A
That's
I
think
that's
the
only
update
the
only
other
thing
would
be
I
guess
this
spring
boot
Dev
tool,
integration
and
I
have
no
idea
what
the
status
of
that
is.
We
should
reach
out
to
Dan
makuza.
A
And
then
this
next
one
is
default.
Behavior
for
Bill
Pack
set
language
ecosystem
environment
variables.
That's
quite
a
mouthful.
A
I
think
that
we
went
through
here
a
while
ago,
and
was
it
was
out
of
Investigation
I,
think
that
a
couple
of
things
have
been
sewn
up,
at
least
in
the
net
case,
so
I
need
to
go
in
and
check
that
and
then
I
need
I.
Think
I
still
need
feedback
from
npm
and
yarn
install
get
some
more
feedback
from
maintainers
on
this,
but
I
think
that
it's
like
effectively
almost
wrapped
up.
A
A
A
All
right,
then,
I
think
that
we
can
keep
it
in
planned
and
it
will
probably
stay
in
plan
for
a
while
as
these
sort
of
like
the
need
and
want
for
these
slowly
Shuffle
in
I.
Think,
although
thinking
about
this
web
servers
might
be
something
interesting
to
investigate,
I
think
I
feel
like
we
added
some
thing
for
maybe
nginx
in
terms
of
how
we
were
compiling
nginx
to
allow
for
some
form
of
remote
debugging.
But
I
would
have
to
investigate
that
further.
D
A
All
right
that
makes
sense,
I
think
it's
fair
to
keep
this
here.
Then
I
think
this
is
also
probably
fair
to
keep
this
here.
I,
don't
know
that
anyone
has
made
any
progress
on
this.
A
I
think
this
is
still
waiting
on
some
work
from
Dan,
isn't
it
we
may
want
to
at
him
in
this
issue
at
some
point
soon,
with
a
is
there
anything
like
I,
don't
know
specifically
what
we're
still
waiting
for
on
Dan.
So
Ryan.
If
you
know
specifically
what,
if
you
could
add
Dan
and
say,
hey
we're
still
waiting
for
X,
Y
or
Z.
That
would
be
appreciated.
A
Awesome
all
right.
Finally,
we
have
two,
no
statuses,
so
two
new
stuff.
We
have
create
language,
family
builders,
I
think
this
one
is
in
the
name.
There's
there's
a
proposal
to
create
builders
for
specific
language.
Families
I
believe
that
the
main
driving
of
this
was
for
Java.
Has
any
work
started
on
that
or
is?
Could
this
be
moved
into
just
planned.
A
F
And
so
yeah,
if
you,
you,
obviously
have
not
been
like
read
out
the
whole
of
this
issue,
but
if
you'd
like
to
get
into
it,
like
I,
did
a
little
bit
of
exploration
into
like
using
the
go,
build
pack
on
the
static
stack
and
it
doesn't
just
work
in
the
way
that
I
expected
it
to,
which
is
to
say
that
it
doesn't
just
make
a
statically
linked
like
static
compiled
binary
that
works
on
the
static
stack.
The
stack
is
probably
doing
the
right
thing.
It's
like
probably
has
everything
it
needs.
F
The
book
I
probably
needs
to
change,
but
I
haven't
received.
All
the
gold
maintainers
haven't
received
any
feedback
that
this
is
a
feature
that
we
want
to
make
in
the
global
ecosystem,
so
that
buildback
hasn't
changed
rather
than
the
exploration
and
there's
not
really
a
lot
of
other
build
packs
that
we
kind
of
expect
to
run
in
a
static
stack
environment
anyway.
F
Yeah
we
could,
we
could
do
that.
That
would
be
like
the
simplest
possible
Builder
that
would
exist.
I
guess
the
question
is
sort
of
like
is
there?
Is
there
value
in
creating
and
maintaining
such
a
thing
right?
So
maybe
I'm
just
in
a
certain
way.
The
intention
we
ever
received
was
to
make
a
stack.
We
made
the
stack
it
does
what
we
wanted
it
to
do.
We
put
a
line
in
that
says,
we
should
make
a
build
pack.
F
I'm
sorry,
build
that
and
then
so
the
RFC
said
like
we
should
make
a
bill
there,
as
well
as
a
stack
and
then
so.
This
story
is
like
we
trained
them
in
the
RFC.
We
have
to
make
a
bill
there,
but
I.
Don't
think
what
you
need
a
builder,
so
I'm
not
sure
what
to
do
with
this
like
influence
story
right,
like
maybe
maybe
the
way
of
saying
like.
Actually,
we
want
to
scratch
this
aspect
out
of
the
RFC
until
unless
and
until
we
get
further
feedback.
G
F
G
G
Because
that
was
like
in
in
the
discussions
about
like
I
mean
that
was
triggered
by
our
RFC
I
think
to
add
some
packages
to
the
tiny
stack
and
there
was
an
argument
that
there
are
actually
people
interested
that
would
be
liking.
Such
a
smaller
footprint
stack.
G
D
Yeah
I
know
that
we
have
like
within
VM,
where
is
like
commercial
product,
an
interest
in
this
like
static
stack,
I,
don't
know
whether
or
not
basically
like
I've
been
pinged
in
some
slack
channels
internally,
asking
about
it
and
whether
or
not
it
functions
in
the
way
we'd
expect
it
to
function.
I
haven't
had
any
feedback
positively
or
otherwise
about
any
sort
of
success,
using
it
in
any
sort
of
way.
Maybe.
G
A
So
it
sounds
like
this
is
potentially
in
limbo,
for
a
little
while
do
I
maybe
want
to
put
it
in
needs.
Investigation.
F
F
Not
planned
that
it's
100
not
in
progress
so
like
maybe
it
needs
investigation,
and
maybe
we
can
try
and
reach
out
to
some
of
those
internal
BMI
folks
and
see
if
there's
any
feedback
that
can
be
shared
in
the
paquelo
community
and
that
will
either
drive
out
doing
this
RFC
or
we'll
learn.
Maybe
that
this
was
like
the
wrong
direction
and
we'll
create
a
process
to
rescinder.
A
D
H
Yeah,
it
asked
for
a
few
last
minute
changes
to
make
sure
that
the
image
names
have
put
the
community
in
it
rather
I've
already
committed
all
of
those
and
then
I
re-requested
a
review
from
him
yesterday
on
it.
But
I
don't
know
if
he
hasn't
seen
it
yet,
but
yeah
I
think
it,
but
hopefully
I've
just
accepted
the
changes
that
he
is
proposing.
So
he
should
be
good
with
them.
E
So
this
one
was
blocked
for
a
long
time
because
we
didn't
have
a
mechanism
to
deliver
it,
but
now
that's
the
language.
Family
RFC
is
approved
and
merged.
We
can
open
this
one
back
up
for
discussion.
A
Awesome
I
assume
that
this
is
probably
here
you're
having
discussions
about
this
in,
like
Java
working
group
meetings
as
well.
A
Not
this
fair
enough!
Is
there
anything
that
you'd
like
to
bring
up
to
this
other
than
the
fact
that
it's
now
unblocked,
yeah.
E
D
We
decided
to
not
progress
on
this,
mostly
because
we
didn't
know
how
to
do
things
like
cattle
categorize
need
on
particular
clouds
versus
others
right.
It
became
this
whole
conversation
of
like.
Where
do
we
draw
the
line?
Like
is
Alibaba
cloud
someplace?
We
should
be
pushing
images
like
you
know.
It's
like
what
thing
qualifies
as
like
a
cloud.
That's
important
enough
for
us
to
have
images
located
on
it.
D
The
main
goal
for
this
one
was
mostly
to
support.
There's
a
product
on
Amazon,
that's
called
app
Runner
and
there's
some
conversation
in
there
for
them
to
become
a
build,
a
CND,
build
packs
platform
and
to
be
able
to
like
natively
support.
Build
pack
builds
for
applications
using
that
product,
but
they
kind
of
wanted
us
to
provide
Builder
images
somewhere.
D
That
was
like
closer
to
where
they're
running
this
thing
and
I
think
we
kind
of
decided
at
the
end
of
the
day
that
if
they
wanted
those
things,
it's
perfectly
reasonable
for
them
to
pull
them
themselves
from
where,
like
the
canonical
location,
we
have
but
yeah
it
with
that
kind
of
left.
In
this,
like
undecided
State,
we
chose
to
just
not
press
forward
with
this
RFC,
so
no
there's
no
advocate
for
it.
Emily
is
basically
not
working
on
the
project.
Anymore.
D
I'll
have
a
note
about
that.
When
we
get
to
the
open
questions
or
open
discussions
section
so
yeah
I,
don't
know,
I
would
say,
like
this
point,
close
go
ahead
and
close.
This
pull
request.
A
Great
and
I
think
that
gets
us
to
the
bottom
of
our
outstanding
RCs.
Do
we
have
any
CMB
updates.
A
The
open
mic
questions.
First,
one
anyone
attend
anyone
planning
on
attending
Cloud,
Foundry
Day
in
Heidelberg,
Germany.
G
It's
like
I
just
entered
that
this
was
published
on
the
I.
Think
on
the
cloud
Foundry
slack
I
mentioned
it
briefly
in
the
potato.
I'd
be
interested
because
I'm,
just
like
I
live
like
30
kilometers
from
there,
so
I
I
would
be
around
the
corner.
If
anyone
is
there,
we
could
just
easily
arrange
some
something,
and
maybe
even
some
some
colleagues
might
be
there.
That's
why
I'm
just
asking
somebody
ask
us
like,
besides
corifi
as
the
how
to
run
CF
workloads
on
kubernetes.
That's
the
other
big
topic
that
the
cff
is
actually
putting.
A
A
Of
anybody
going
yeah.
D
Yeah
I
just
wanted
to
mention
about
this
is
a
I
guess,
a
temporary
change.
The
steering
committee
is
going
to
be
meeting
a
little
bit
later
today
to
talk
about
the
steering
committee
composition
in
the
interim
between
now
and
when
the
actual
election
takes
place
and
we're
going
to
be
making
a
couple
of
changes.
The
first
one
is
that
we're
going
to
vote
to
have
Emily
Casey
retired
from
the
committee.
D
She
basically
has
like
stepped
away
from
the
project
and
has
had
like
continuingly
less
and
less
involvement
over
it
as
like
she's,
you
know,
moved
on
to
another
kind
of
phase
in
her
life
and
found
another
job
and
is
no
longer
involved
that
much
in
container
build
stuff,
and
so
we,
it
doesn't
make
sense
for
us
to
just
have
this
kind
of
like
extra
student,
Committee
Member
that
counts
in
our
our
Quorum
counts
and
isn't
really
actually
there
to
vote
on
anything.
D
So
we'll
have
her
move
to
the
kind
of
Emeritus
status.
The
other
one
is
that
I'm
going
to
be
leaving
on
Parental
leave
from
VMware,
so
because
of
that
I'm,
basically
going
to
be
Mia
for
a
number
of
months,
including
the
months
that
cover
the
elections
and
so
for
the
update.
The
update
on
the
elections
is
that
the
cff
would
like
us
to
hold
the
paqueto
elections
in
tandem
with
the
cff
talk,
elections
which
happen
kind
of
the
middle
of
May
to
the
middle
of
June.
D
D
D
D
So
this
is
not
a
permanent
position
that
is
just
filling
the
interim
time
period
so
that
we
don't
end
up
in
a
situation
with
the
only
person
able
to
approve
anything
is
Dan
bakuza,
so
just
making
sure
we
have
at
least
two
people
showing
up
for
the
steering
committee,
so
yeah
we're
I'm
gonna
meeting
with
Dan
later
today.
D
All
this
has
already
been
like
kind
of
pre-decided,
but
we
will
like
formally
meet
and
have
a
vote
to
have
this
take
place
and
we'll
record
it
in
the
meeting
notes
just
wanting
to
make
sure
that
that's
happening
transparently.
D
So
it
doesn't
seems
like
some
sort
of
backdoor
backroom
deal.
That's
taking
place.
D
Anyway,
that's
all
I
have
to
say
about
that
steering
committee
stuff
look
forward
to
seeing
the
results
of
the
election
when
they
happen
coming
up.
That
should
be
an
exciting
time.
B
D
Packs
node.js,
as
the
slack
handle
or
you
know,
open
issues
against
any
of
the
node
repositories.
D
Those
people
are
Timothy
hitchner
and
Victoria
Campbell.
Okay,
thanks
yeah.
A
Great.
Thank
you
so
much
for
coming
to
the
meeting
see.