►
From YouTube: 2022-07-06-Node.js Technical Steering Committee meeting
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
B
Seem
unable
to
promote,
but
friend
friend
renzi
needs
to
be
promoted.
Sorry.
A
B
Excellent,
does
somebody
want
to
make
an
announcement
about
what
the
latest
greatest
is
on
the
security
release?
Maybe
maybe
bethany
has
some
information
on
that
or
something
or
richard.
C
A
A
A
Okay,
board
meeting
and
cpc
minute
updates
on
the
cpc
front
by
rich.
Do
you
want
to
have
any
updates
on
that
front?.
B
I
attended
the
meeting
this
week,
so
you
think
I
would
but
of
course
I
didn't
think
about
it
until
right
now
so
board
meeting
cp.
So
so
there
are
some.
There
are
some
nominations
around
that
needs
to
be
made
or
some
things
that
need
to
be
considered
around.
Who
we
appoint
to
the
cpc
on
the
board.
B
I
have
to
look
to
check
how
many
folks
we
have,
but
but
like
last
year
there
was
like
tsc
appointed
one
person,
and
that's
me
I
think
you
know
it
was
originally
mary,
but
she
couldn't
keep
doing
it
so
I
took
over
so
now
it's
me
and
then
they
and
then
the
com
com
also
appointed
a
person
in
which
I
believe
is
just
josephialdo.
B
You
know,
I
know
michael
you're
on
the
cpc
as
well
and
a
few
other
people,
but
but
through
different
routes
and
with
comcom
no
longer
a
thing.
We
need
to
decide
how
we're
going
to
continue
to
appoint
those
seats.
I
I'm
I'm
proposing,
but
I
want
to
talk
to
joe
about
it
first,
as
one
of
the
appointees
and
as
the
chair
of
cpc.
B
A
B
I'll
take
a
look
I'll,
take
a
look
for
that,
but
if
anybody
knows
where
it
is
or
find
something,
please
point
me
to
it
and
save
me
that
hassle.
That
would
be
great.
A
A
B
A
Who
knows,
but
I'm
gonna
go
find
out.
We
have
two,
I'm
pretty
sure
we
get
two
two
cpc
representatives
as
an
impact
and,
of
course
anybody
who
wants
to
to
be
and
join
the
cpc
regular
members
can
join,
but
we
have
two
voting
members,
one
which
is
like
from
the
you
know
two
voting
members
and
I
think
what
we
discussed,
but
again,
don't
know
if
we
wrote
it
down
agreed
whatever
was
like
we'd
continue
to
have
one
pointed
from
the
tse
and
then
one
which
would
be
like
from
the
greater
community.
B
A
Soon
right,
so
what
I'm
writing
down
in
the
minutes
is
just
it's
time
for
the
elections,
appointments
for
the
impact
members
and
we
need
to
figure
out
how
we
confirm
who
we
want
to
put
forward
right.
That
sounds
perfect.
Thank
you,
michael
and
not
you
know
on
the
so
board.
Semi-Related
to
that
on,
the
board
is
like.
There
was
the
second
community
director
that
election
is
active.
I'm
not
re-running
this
year,
so
that's
open.
If
somebody
wants
to
run
and.
B
Okay
and
okay,
yeah-
let's
let's
get
some
nominees
for
that,
then,
okay,
thanks
michael,
I
don't
have
anything
I
want
to
add
to
that.
That's
just
the
main
thing
I
want
people
to
be
aware
of
is
that
the
nominations
and
elections
are
happening
and
there's
yeah
a
bunch
of
things
yeah.
Some
things
we'll
need
to
decide.
A
Yeah,
right,
okay
and
and-
and
there
are
some
other
things
like
there's
voting
members
elected
from
the
from
the
cpc
itself-
so
there's
basically
a
whole
bunch
of
the
elections.
I
think
everything
except
for
the
chair,
which
was
run
a
little
while
ago
and
the
first
director's
seat,
which
was
which
is
run.
You
know
six
months
off
the
second
one,
so,
okay,
we
might
as
well
move
on
then
to
the
issues.
The
first
one
is
move
stream
development
out
of
core.
So
this
is
number
43520.
A
A
So
I
know
we
had
some
discussion.
There
were
some
concerns.
It's
like,
I
think
it's,
it's
not
like.
People
are
like
no,
but
it's
not
like
people
are
just
an
instant,
yes
either.
So
maybe
maybe
I
don't
know
if
people
have
think
you
know
do
people
think
we
should
have
something
useful
to
discuss
today
or
we
should
just
sort
of
say,
issue
discussion,
continuing
an
issue.
Please
jump
in
there.
A
A
The
next
one
proposal
is
proposal,
node.js
vector
vendor
namespace
434133
again,
we
did
have
some
good
discussion
last
time,
there's
no
new
discussion
in
github
since
the
last
time,
but
I
think
there
are
a
number
of
sort
of
key
issues
we
need
to
work
through
in
terms
of
mechanics.
What
that
would
look
like,
and
I
think
back
to
the
what
you
know
is
often
mentioned.
We
we
want
to
capture
as
much
as
that
as
we
can
in
the
issue.
A
A
Okay,
I
don't
send
any
last
week,
so
I
don't
hear
any
objections
to
that.
So
I'll
just
note
that
in
minutes
consider
explicit
string,
40
module
formatting
module.
This
is
43382.
A
C
I
thought
the
discussion
last
time
split
into
there
were
two
separate
issues.
One
was
should
should
we
have
an
api,
exposing
coloring
text,
and
then
there
was
another
separate
question
about
vendoring
and
that's
as
much
as
I
remember
from
from
the
last
tlc
meeting
it
was.
It
was
kind
of
like
it
was
at
least.
C
At
least
two
different
sort
of
things
that
came
out
of
the
discussion
around
the
specific
pr
around
coloring
text.
A
I
don't
hear
any
objections,
so
I'll
move
on
to
the
next
one,
which
is
build.
Dev
container
configuration
48.25
and
you
know
tierney
had
asked
for
somebody
to
basically
work
with
him
on
that
it
turned
out
to
be
more.
He
just
wanted
somebody
to
be
in
the
loop
in
terms
of
the
configuration
and
what
was
set
up.
So
I
I
I
sought
with
him
and
he
showed
me
some
of
that.
A
We
basically
have
some
credentials
from
github
not
get
up
from
docker
hub
and
through
those
credentials
we
have
a
a
repo
which
we
already
agreed
to
through
the
admin
repo
where
we
build
a
container
that
includes
the
latest
nightly
node
tree,
checked
out
and
compiled
so
that,
if
you
want
to,
if
you
want
to
do
development,
you
can
basically
just
start
up
that
container
and
you've
got
like
a
pre
warmed
up
cache
of
node
to
do
a
compile
and
development,
which
I
think
that
actually
would
be
quite
useful.
A
I
was
going
to
take
it
off
the
agenda
because
I
think
it
was
you
know
he
got
out
what
he
wanted
from
adding
it
to
the
agenda,
and
it's
just
going
to
continue
to
move
forward
to
improve
it.
Okay,
rich.
B
I
just
put
a
link
in
the
chat,
if
you're
on
the
zoom
for
a
very,
very
similar
feature
that
can
live
side
by
side
and
can
eventually
be
removed
when
gippod
enables
the
ability
to
use
the
the
docker
image
that
pureney
has
set
up,
but
I'm
hoping
we
can
get
broad
consensus
that
something
like
getpod
is
worth
installing
and
at
least
letting
it
as
an
experiment
run
for
like
a
month
or
two
until
the
end
of
open
source
day,
which
is
the
grace
hopper
thing
we're
doing
this
year.
B
Hopefully
I
guess
we
hear
back
in
another
week
or
something
like
that,
and
but
yeah
both
of
these
things
will
go
a
long
way,
hopefully
towards
easing
developer
pain,
at
least
on
linux.
If
you
need
to
test
something
on
windows,
you
probably
still
have
to
compile
it
from
scratch,
but.
B
So
git
pod
disposable,
it's
very
much
like
code
spaces,
it's
disposable
development
environments.
So
you
just
point:
you
know
you
tell
you,
tell
git
pod
open
up
this
repository
in
in
visual
studio
code
in
my
browser,
so
I
can
make
changes
and
by
enabling
pre-builds
it
will
do
the
warmed
up,
cache
and
everything
so
that
someone
using
git
pod
to
develop
to
make
a
to
do
it.
B
A
A
B
Yeah
I
would
like,
since,
since
I
mean,
since
these
things
can
all
exist,
can
coexist
together,
I
wouldn't
mind
just
having
them
all
happen
and
we
can
sort
of
like
figure
out
which
one
we
actually
want
to
support
based
on.
You
know,
which
ones
don't
blow
up
with
great
frequency
or
require
a
ton
of
care
and
feeding
anyway,.
C
Is
there
anything
we
wanted
to
put
out
then
not
sort
of
officially,
but
just
some
sort
of
message
statement
about
that?
These
are
all
experimental
and
you
know
they
may
or
may
not
work,
because
you
know
I
don't
think
we're
in
a
position
where
we
can
sort
of
say
yes,
we've
added
it
we're
going
to
keep
it
working
until
we've
had
more
experience.
C
Because
that's
always
the
thing
with
adding
things
we
can
have
whatever
we
like,
but
it's
the
question
then
of
that
once
you
add
something
in
there's
an
expectation
that
somebody
involved,
the
project
is
supporting
it
right
and
then
that
would
be
my
only
concern
with
with
these
things.
B
So
my
intention
with
git
pod
and
probably
a
good
approach
for
all
of
these
things
is
step.
One
is
add
it
and
do
not
document
it.
You
have
to
know
about
it
to
use
it.
If,
if
the
three
people
who
are
using
it,
then
don't
discover
like
game
change,
you
know
like
deal
breaking
problems
then
put
out
some
kind
of
announcement
or
documentation.
That
says
this
is
experimental.
It
may
go
away,
but
please
help
us
and
try
it.
It's
probably
buggy
it's
an
alpha.
Please
do
it.
B
You
know
please
try
and
let
us
know
and
then
go
from
there
if
it.
If
you
know,
if
it
if
it
works,
then
you
can
promote
it
to
something
that
we
really
support
and
use,
and
if
it
doesn't,
then
we
can
just
take
it
away
or
just
leave
it
in
perpetual
buggy
alpha.
But
I
don't
particularly
love
that
option,
but
that's
my
thinking.
I
don't
know
if
that.
If
that
sounds
right
to
you,
I
know
that
some
people
might
not
be
crazy
about
not
might
not
be
enthusiastic
about
the
you
know.
B
Just
do
it
and
don't
tell
anybody
for
a
little
while
approach.
What
I
mean
I
had
to
I
had
to
work
in
my
repository.
I
had
to
work
for
a
while
to
figure
out
how
to
get
pre-built
store
and
had
to
like
talk
to
the
git
pod
people
for
a
little
bit
to
figure
out
how
to
get
pre-built
working
with
something.
As
you
know,
resource
intensive
as
an
as
a
node.js
build,
and
so.
C
B
Right
so
so
it
has.
I
have
to
do
like
this
funky
little
thing
where,
where,
if
it's,
I
know,
I
have
an
hour.
So
if
I'm
getting
to
50
minutes-
and
I
might
run
out
because
that
includes
the
time
to
do
the
checkout
and
create
the
the
other
thing.
So
if
I'm
getting,
if
I'm
bumping
up
against
that
hour,
instead
of
letting
it
time
out,
which
will
then
fail
and
then
the
user
doesn't
has
no
has
nothing
to
use.
B
Instead,
I
just
exit
with
a
success
code,
and
it
just
you
know
the
the
vm
goes
away,
but
the
workspace
has
all
of
the
compiled
artifacts
that
got
up
to
that
point,
and
so,
if
that,
if
that
happens,
and
hopefully
it
won't,
but
if
that
happens
then
a
make
should
take.
You
know
a
matter
of
minutes
rather
than
a
matter
of
an
hour
or
something
like
that.
So
it's
still
it's
there's
still
benefit,
but
I
want
to
see
how
often
that
happens.
C
B
B
B
Here's
a
link
to
a
commit,
we
know
is
good
and
just
have
a
github
action
that
updates
it
or
whatever,
but
I
don't
want
to
do
that
out
of
the
gate
out
of
the
gate
I
just
want
to
let
it
run
not
tell
people
and
experiment
it
with
like
me
and
experiment
with
it
with
me
and
a
handful
of
other
people
and
see
what
happens,
but
the
big
advantage
from
my
perspective
that
this
has
over
these
other
things
we've
been
talking
about,
is
that
this
is
ready
to
go
like
we.
B
We
could,
if
we
wanted
to
turn
this
on
like
right
now.
You
know
if
we
wanted
to,
whereas
all
these
other
things
still
have
work
that
need
to
happen,
and
so
to
me,
that's
a
big
advantage,
because
we
have
an
open
source
date
coming
up,
and
I
really
don't
want
to
have
to
explain
over
zoom
to
you
know
a
bunch
of
people
that
they
need
to
install
x.
You
know
download
xcode
and
I'm
going
to
wait
while
they
do
it
or
something
that
just
seems
like
a
terrible
experience
for.
A
I
everybody,
the
only
question
would
be
like
in
there
you
you
have
the
it
requires
installing
the
git
pod
up.
Do
you
know
what
privileges
it
requires
for
that?
I
forget
I'll.
Take
a
look
because
really
that
this
change
seems
like
nothing
right
other
than
on
its
own.
It's
just
adding
a
file
which,
if
it's
useful,
seems
like
a
good
thing
to
do.
A
B
The
beautiful
thing
about
the
dev
containers
thing
that
that
tyranny's
working
on
is
that
that's
a
standard
or
a
de
facto
stance.
Anyway,
that's
agreed
upon
by
multiple
vendors.
So
they
don't
all
support
it.
Yet,
but
in
theory
at
least
eventually
they
all
will
and
then
it'll
just
be
a
matter
of
having
that
and
we
can
like
only
have
that,
and
then
people
can
use
whatever
service
they
happen
to
like
if
they
want
to
use,
which
is
great
if
they
want
to
use
git
pod
great.
If
they
want
to
use
something
else.
A
A
Moving
on
to
the
next
issue,
add
jeffrey
booth
as
tse
members.
So
there
is
an
open
issue
where
I
think
effectively
rich,
that
we're
having
the
vote
right.
B
Yeah,
so
I
think
what
I'm
gonna
do
is
unless
anybody
objects,
maybe
after
this
meeting,
although
some
someone
please
beat
me
to
it,
if
I
fall
down
on
this,
which
I
probably
will
but
at
some
point
close
the
issue
open
a
pull
request,
adding
the
plus
ones
in
there,
as
you
know,
a
vote
dot
a
json
file
for
voting
tsc
records
and
on
board
jeffrey
probably
have
him
attend
the
next
meeting.
I
think
as
a
tsc
member.
B
A
A
Okay,
the
next
section
is
strategic
initiatives,
so
I'm
going
to
see
one
if
there's
any
updates
on
the
issue
itself,
because
I
often
forget
to
do
that.
So,
let's
start
there.
A
I
do
see
variate
currency,
so
targos
updated
there,
and
thank
you
for
that.
So
let
me
copy
that
one
first
in
as
an
update
there.
A
A
Mac
os
does
sound
like
there's
a
suggested
fix,
but
basically
says
be
prepared
for
other
problems.
After
the
compilation
is
fixed
and
the
test
hash
seed
has
started
to
fail
recently.
So
those
are
a
number
of
issues
which
we
we
you
know
sounds
like
there
could
be
use
some
help
in
terms
of
helping
to
get
the
next
version
of
v8
updated.
A
A
Next
10,
you
know,
I
I
think
the
we
had
a
meeting
today.
The
main
thing
at
this
point
is
sort
of
trying
to
so
after
the
last
collaborator
summit,
we're
actually
down
to
two
two
technical
priorities
where
we
haven't
done
deep
dives.
A
One
of
them
I
had
a
very
quick
email
with
with
targos,
is
around
keeping
up
to
date
with
ectoscript
features,
and
we
do
that
through
v8,
and
I
we
agreed,
we
don't
think,
there's
really
anything
that,
like
a
deep
dive,
would
make
sense.
A
The
other
one
is
on
better
support
for
threading
for
multi-threading
or
sorting
multi-threading
that
one
you
know,
we
think
we're
thinking
you
know
would
be
a
topic
that
we
could
schedule
the
best
the
earliest
time,
because
summertime's,
not
a
great
time,
is
to
do
that.
Actually
in
a
collaborator
summit
along
with
node
coffee
you
if
we
get
that
lined
up,
so
that's
the
current
thoughts
there.
A
Otherwise,
you
know
once
we
get
we
get
through,
that
we'll
be
at
the
end
of
sort
of
like
the
current
technical
priorities,
and
so
the
work
of
next
10
will
mostly
be
around
trying
to
see
if
we
can
sort
of
help
prioritize
or
support
work
to
get
the
things
that
we
identified
as
being
important
on
all
the
other
technical
priorities
going.
A
So,
for
example,
there's
actually
a
pretty
active
discussion
on
the
single
executable
application,
proof
of
concept
and
we've
actually
added
a
initiative
out
of
that
to
the
list
here.
So
the
discussion
there's
there's
a
list
of
issues
in
that,
and
this
is
discussion
ongoing.
So
I
think
that's
good
and,
and
the
idea
will
be
like.
Similarly
can
we
do?
We
need
to
have
a
strategic
initiative
to
support
any
of
the
other
things
we've
identified
or
even
like
feature
requests.
You
know
one
of
the
things
talked
about
for
esm.
A
Adoption
was,
you
know,
the
dm
model,
vm
module
supporting
esm,
which
it
doesn't
today,
but
that
affects
the
number
of
test
frameworks.
A
So
you
know
figuring
out
how
we
surface
some
of
those
priorities
and
sort
of
do
our
best
to
to
highlight
them
as
things
that
we
should
be
working
on
and
if
people
have
tight
cycles
that
they
know
that
that
would
be
important
to
work.
So
that's
next
ten-
and
I
think
that
takes
us
to
the
end
of
the
list
of
ones
that
we
have
people
here,
for
anybody
have
anything
else
to
add.
A
If
not,
that
takes
us
to
the
end
of
the
agenda
before
we
just
retire
for
a
short
private
section.
Is
there
anything
else
people
want
to
talk
talk
about
before
we
close
out
the
public
session
for
today.