►
From YouTube: Working Group: 2022-12-07
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
It
doesn't
look
like
you
are,
but
that's
what
I
do
here?
Okay
and
then
that
takes
us
immediately
to
the
roadmap
status,
update.
A
All
right,
I'm,
just
gonna,
go
through
the
items
here
and
we
can
briefly
discuss
what
the
status
of
them
might
be.
I
think
we've
got
a
couple
here
that
are
in
this
kind
of
needs.
Investigation,
state,
I
know
this.
A
One
came
up
again
this
week
in
a
thread
that
I
saw
I'm,
not
sure
if
Dan
kuza
will
be
able
to
join
us
today,
but
I
think
the
primary
issue
was
that
not
all
of
the
Java
build
packs
have
moved
over
to
Docker
Hub
as
their
primary
distribution
point,
and
so
there's
still
some
references
to
GCR
related
things
which
was
causing
some
confusion.
A
I
think
someone
went
to
go,
pull
a
build
pack
and
it
pulled
some
stuff
from
Docker,
Hub
and
some
other
stuff
from
GCR,
but
I
can
catch
up
with
Dan
and
see
about
what
the
status
of
this
might
be
and
see.
If
we
can
get
this
across
the
Finish
Line
before
the
end
of
the
year.
A
You
know
it's
been
outstanding
for
quite
a
long
time,
and
then
we've
got
this
other
one
here
about
reloadable
process
types.
A
I
think
the
only
thing
that's
left
here
is
this
Ruby
issue,
and
this
is
there's
nothing
blocking
this.
This
is
just
a
a
bandwidth
issue.
If
we
can
get
the
time
to
do
this,
we
will
we
just
haven't.
I
haven't
had
the
time
recently.
B
A
B
A
No
okay,
because
I
had
another
and
I
I
have
an
idea
for
us
redoing
the
way
we
do.net
core
reload,
but
that's
more
native
to
that
ecosystem,
but
yeah.
If
you're
not
interested
in
doing
it,
then
I'll
save
that
for
another
day
or
someone
who
maybe
is
is
interested
in
helping
us.
A
Okay,
so
then
moving
on
we'll
go
to
the
in
progress
ones.
I'll
start
here
from
the
bottom:
we've
got
Implement
dependency,
RFC
zero,
three
through
six
I
think
this
might
be
done
to
someone
on
the
call
want
to
give
us
a
status
update,
maybe
Victoria
or
Forest.
C
Yeah,
so
this
is,
for
all
intents
and
purposes
done,
the
Teeny
is
still
the
only
open
issue
and
I
have
an
open
RFC,
proposing
that
we
oh
I,
have
an
open
RFC,
proposing
that
we
move
teeny
to
using
a
pre-compiled
static,
binary
from
Upstream
and
an
open
implementation
ready
for
whatever
that
RFC
is
merged.
C
A
It'll
be
nice
to
see
this
finished
before
the
end
of
the
year.
I'll
leave
it
for
now
and
in
January.
When
we
look
at
this
item,
we'll
check
it
off,
then
all
right
reduce
build
complexity
of
dot
net
runtimes.
C
This
is
approaching
being
done
soon,
as
well
as
soon
as
we
sort
of
remove
the
backwards
compatibility
aspect
that
we
have
set
up
in
the
build
pack.
Then
that's
when
we
can
kind
of
close
this
out,
but
until
then
it's
open
until
yeah.
A
A
A
It
looks
like
PHP
is
done,
I,
don't
know
if
php's
been
added
to
the
Builder.
Yet
that's
probably
something
that's
going
to
happen
today.
A
Okay,
I'll
look
into
that.
Let's
see
what's
going
on
there,
it
should
be
pretty
straightforward,
just
adding
PHP
to
the
the
builders
order
grouping.
It
should
be
as
easy
as
that
and
then
I
think.
Maybe
there's
like
a
smoke
test
or
something
that
maybe
needs
to
get
added.
C
A
A
So
there's
a
whole
bunch
of
of
language
families
here
all
of
them
with
completely
different
debugging
support.
So
if
you're
interested
in
I
don't
know
implementing
node.js
remote
debugging
wink,
wink
Philip,
then
maybe
I
don't
know,
contribute
a
PR
for
that
particular
functionality
and
I
know.
The
team
would
appreciate
it.
B
A
We've
got
default
behavior
for
build
Pack
set
language
ecosystem
I,
know,
there's
just
some
I
think
they're
outlined
down
here,
there's
just
some
odds
and
ends
and
I
think
that
the
maintainers,
as
they
get
bandwidth
here
towards
the
end
of
the
year,
probably
can
just
take
a
look
through
this
and
make
a
determination
as
to
whether
or
not
changes
should
be
made
in
the
specific,
build
packs
for
the
things
that
are
mentioned.
A
I,
don't
think
it's
that
many
I
think
it's
a
handful
of
of
environment
variables
that
I
think
in
most
cases
it's
just
to
change
the
value
from
an
override
to
a
default.
So
it's
worth
it's
worth.
Looking
at
these
things,
it's
another
item
we
can
close
off
at
the
end
of
the
year
and
I.
Just
don't
think,
there's
that
much
work
involved.
A
A
We've
basically
done
everything,
that's
necessary
for
this
for
this
RFC
and
then
we
actually
have
testing
infrastructure
that
asserts
that
now
so
I
think
that
this
is
done
and
I
could
probably
go
ahead
and
close
this
out
as
implement
it.
After
this
meeting.
A
A
Oh
thanks,
Sophie,
okay,
cool
I
will
move
this
into
like
a
in
progress.
State
then
or
done
State
I
guess
and
we
can
or
I'll
put
it
in
progress
now
and
then
I'll
go
ahead
and
have
the
python
maintainers
close
the
actual
RSC
issue
that
should
move
it
over
to
done
and
we've
got
here.
This
Implement
potato
Community
HTTP
function
build
pack.
Those
are
my
long
list
of
stuff
to
do
as
a
steering
committee.
A
Member
I
need
to
change
the
kind
of
RFC
definitions
to
include
a
like,
will
not
Implement
state
or
something
along
those
lines,
so
that
we
can
just
say
that
this
isn't
going
to
happen,
at
least
not
not
in
the
way
that
it's
written.
A
It's
just
beating
up
space
on
the
roadmap
here
and
we
have
no
intention
of
actually
implementing
this
as
defined,
but
I'll
get
around
to
that.
Hopefully,
as
my
time
frees
up
towards
the
end
of
the
year.
A
And
then
we've
got
some
auto-generate
reference
documentation.
I
know
this
is
something
that
we've
wanted
to
do
for
a
long
time
with
the
Jammy
stuff
kind
of
ending
it.
Maybe
is
something
worth
considering
putting
relatively
high
on
the
roadmap
for
next
year,
but
yeah
we'd
love
to
hear
some
feedback
from
users
about
the
documentation,
especially
stuff.
Like
configuration
parameters,
things
we
could
be
doing
a
better
job
of
exposing
and
providing
information
about.
A
So
specifically,
I
think
this
is
mostly
talking
about
like
environment
variables.
We
have
some
documentation
that
exists
on
the
website,
but
it's
all
human
documented.
So
there
are
definitely
instances
where
the
environment
variables
Behavior
has
maybe
changed
in
a
subtle
way
and
then
that
documentation
menu
is
not
updated
or
we've
just
missed
an
entire
environment
variable
that
exists
in
the
build
pack
and
has
functionality,
but
it's
actually
not
documented
on
the
website.
The
idea
behind
this
would
just
be.
A
And
then,
lastly,
here
to
find
an
image
and
dependency
resolution
policy,
I
need
to
catch
up
with
Dan
and
kuza
about
this
one
I,
don't
think,
there's
anything,
that's
pressing
or
urgent,
because
the
timeline,
if
I'm
not
mistaken,
is
two
years.
A
But
it's
worth
us
looking
to
see
what
we
have
currently
in
our
Registries,
both
Docker
Hub
and
GCR,
to
see,
if
there's
anything,
that's
already
out
of
scope,
we're
coming
up
on
I
guess
it
will
be
the
third.
Is
it
the
third
or
is
it
the
second
time's
flying
this.
C
A
No
one
knows:
okay,
anyway,
there's
probably
images
on
there
that
maybe
are
reaching
the
end
of
this.
This
lifetime.
D
Probably
third
round
because
I've
heard
paqueto
being
mentioned
since
day,
one
of
my
time
here
and
that's
a
little
over
two
years
so.
A
Cool,
that's
what
I
thought
I
just
can't
remember.
It
feel
like
yeah
I've,
been
on
the
zoom
call
giving
this
update
for
a
while
yeah
and
time
is
flying
all
right,
so
that
covers
the
remainder
of
items
for
the
roadmap
for
2022,
and
this
seems
like
a
good
moment
for
me
to
call
out
another
item
here,
which
is
that
we
are
starting
to
solicit
feedback
for
the
2023
roadmap.
A
A
That's
odd,
okay,
I'm
gonna,
just
put
that
here.
This
is
the
2023
road
map
discussion.
A
Please
feel
free
to
leave
comments,
upvote
items.
Our
goal
is
that
at
some
point
in
January,
we'll
Lock,
This,
Thread
and
kind
of
synthesize
the
details
of
what
people
have
talked
about
and
requested
and
we'll
figure
out
what
the
themes
for
2023
look
like
I've
mentioned
here.
Both
the
link
there's
a
link
to
last
year's
discussion
thread
and
also
the
roadmap
blog
post.
A
That
folks
are
interested
in
trolling
both
of
those
for
ideas-
and
you
know
stuff
we
didn't
get
to,
but
that's
still
important
make
sure
you
bring
them
up
here
again,
foreign,
so
that
covers
that
and
I
think
we
then
move
on
to
the
outstanding
rfcs.
So
I've
got
outstanding
rfcs
here,
there's
only
a
couple.
A
The
first
one
here
is
this
RSE
to
remove
gme
or
remove
Ruby
from
the
Jamie
full
stack.
Is
this
another?
My
failure
to
merge
situation.
A
Guess
you
have
one,
but
I
should
take
another
look
and
make
sure
I'm
good,
sorry,
okay,
great,
no,
no
worries,
okay,
great
and
then
the
only
other
one
here
is
what
Forest
mentioned
the
this
new
RFC
for
teeny
Forest.
You
wanna,
walk
us
through
this.
C
Yeah,
it's
pretty
lightweight,
currently
teeny
is
being
built
and
hosted
on
paquetto
like
by
picetto.
C
However,
teeny
creates
a
static,
binary
release,
so
there
doesn't
appear
to
be
any
reason
for
us
to
need
to
build
that
and
we
could
just
pull
it
from
Upstream,
so
I'm
just
proposing
that
that's
what
we
do.
I
have
a
proof
concept
that
shows
that
the
static
binary
works
and
then
I
actually
have
a
full-blown
PR
of
the
implementation
of
this
RFC
of
pulling
from
upstream,
and
all
that
linked
in
a
comment
here
so
pretty
much
as
soon
as
this
gets
approved
that
can
be
merged,
and
this
will
be
done.
A
This
is
under
utility,
so
utilities
and
maintainers.
Please
take
a
look.
A
Okay
that
covers.
A
A
That
covers
the
outstanding
rfcs
I.
Think
the
next
agenda
item
here
is
CMB
updates
and
questions.
A
I,
don't
I,
don't
know
if
there
were
any
updates
this
week,
Can
anyone
anyone
on
the
team
want
to
mention
something
they
saw
or
thought
might
be
important.
A
Doesn't
sound
like
it,
okay
and
then
moving
on
we've
got
our
project
update.
The
only
item
here
is
the
2023
roadmap
discussion.
Let
me
move
this
link
down
here
then
any
other
project
updates
that
folks
wanted
to
mention.
A
That
doesn't
sound
like
it
all
right
then,
the
last
item
here
any
open
questions
or
discussion
topics.
A
Great
I
think
we've
reached
the
end
of
this
meeting.
Then
take
a
look
at
that
discussion.
Leave
us
some
feedback
and
we'll
see
you
here
next
week
or
wait
a
second
did
we
decide
that
we
were
going
to
cancel
the
remainder
of
meetings.
A
Sophie
is
saying
that
she
doesn't
think
so
all
right.
Well,
if
the
next
meeting
or
any
of
the
remainder
ones
are
canceled,
then
I'm
sure
David
will
post.
He
should
be
back
with
us
next
week.
So
we'll
see
how
that
goes,
but
yeah
we'll
play
it
by
ear,
maybe
see
you
next
week.
All
right
folks
have
a
good
day.