►
From YouTube: 2021-11-04-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
A
I
guess
there's
no
announcements
this
week,
so,
let's
move
on
to
the
issues,
the
first
one,
that's
tagged
under
node.js
node
is
doc
ad
initial
list
of
technical
priorities,
40235
that
one
was
on
the
agenda
for
awareness
to
you
know
it's
the
you
know,
agreement
on
the
technical
priorities
for
the
project.
A
A
If
not,
okay,
the
next
one
is
rename
default
branch
from
master
domain.
33
864.-
I
don't
have
anything
to
report
on
that.
There's
still
a
few
repos
left
that
we
need
to
do
some
work
on
unless
anybody
has
something
else
to
add
on
progress
on
that
we
can
move
on
to
the
next
one.
A
A
B
It
says
on
the
issue.
Voting
starts
in
two
weeks
from
now,
so
that
was
two
weeks
ago.
So
ryan
is
close,
but
yeah,
probably
not
gonna.
Do
it.
A
Yeah,
I
think
yeah
it's
voting
is
close.
That
makes
sense.
Okay,
thanks
thanks
for
writing
that
the
no
tsc
updated
security
team
to
reflect
the
status
quo.
Now
that
one,
I
think.
A
B
A
A
Okay,
so
that
I
think
just
reminded
me
of
that
one,
but
I'm
not
sure
it's
directly
related.
A
Right
so
this
is
I'm
just
looking
at
the
conversation
should
see,
I
guess
richard.
You
said
it
should
match
the
team.
C
I
understand
the
rationale
behind
clearing
the
list
up,
but
I
mean
the
list
is
supposed
to
reflect
the
github
team.
So
there's
not
enough
to
just
remove
people
in
the
list.
C
A
A
A
C
A
C
A
Okay,
that
sounds
good
thanks
for
doing
that.
The
next
one
is
eleven
one:
one:
zero,
zero,
add
security
triaging
to
core
repo
governance,
md
and
or
charter.
A
A
That
he
would
do
three
days
ago,
so
I
think
that's
that's
good
as
the
next
step
in
there
and
then
the
last
issue
on
the
agenda
was
I'd,
put
on
the
mini
summit
for
the
next
ten
effort,
which
is
from
november
on
november
18th.
A
It's
it's
10
to
2
eastern
and
I
have
it
on
the
agenda
for
awareness
hope
to
see
as
many
tse
members
as
we.
We
can
get
there
to
talk
about
two
issue,
two
particular
deep
dives
one
which
is
suitable
types
for
end
users.
This
is
discussion
on
like
where
the
current
state
is
for
people
using
types
with
node.
Are
we
in
a
great
place
and
we
don't
have
to
do
anything
or
is
there
something?
A
We
should
be
thinking
about,
doing
or
changing,
to
sort
of
dive
into
that
and
and
discuss
and
come
to
hopefully
some
conclusions
and
then
the
other
one
is
to
look
at
the
story
for
building
single
executable
applications
with
node.js
again
like.
Are
there
some
good
options
which
we
could
document
so
that
it's
easy
for
people
to
find
how
you
would
do
that?
Are
those
options
functional
and
you
know
again
it's
sort
of
down
to
do.
A
B
B
A
If
not
all
thank
everybody
for
who
came
today,
we
did
have
a
bit
of
a
light
agenda
and
light
attendance,
so
you
know
it's
good
to
quickly
go
through
things,
but
we'll
give
everybody
back
the
time
and
talk
to
everybody
next
time,
thanks,
bye,
bye,.