►
From YouTube: 2022-1-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
So
welcome
to
the
node.js
technical
steering
committee
meeting
for
january
6
2022
we'll
follow
the
agenda
that
was
tagged
in
issue
number
1145
in
the
repo
and
before
we
get
started,
does
anybody
have
any
announcements
that
they'd
like
to
share.
A
I
guess
otherwise
I'll
just
say
happy
new
year
to
everybody
and
looking
forward
to
working
with
everybody
in
this
new
year.
The
next
section
is
the
cpc
and
board
meeting
updates.
I
don't
think,
there's
anything
to
report
from
the
the
cpc
or
board
meeting.
I
guess
the
one
thing
that's
maybe
potentially
interesting
is
you
know
the
the
planning
for
opengs
is
continuing,
including
a
collaborator
summit,
so
I
think
planning
and
scheduling
for
that
should
be
being
discussed
soon,
so
anybody
who's
interested
in
the
collaborator
submit
and
wants
to
get
involved.
A
You
know
be
on
the
lookout
for
that
and
I
think
it's
on
thursdays
there's
a
program
committee
meeting
and
so
that's
a
good
place
to
get
involved
if
you
want,
if
you
want
to
help
the
plan
and
make
that
happen,
but
I
think
we'll
bring
more
specific
details
around
the
collaborator
summit
than
what
we
might
plan
for
node
to
hear
into
other
places
in
the
project.
A
Actually
we
discussed
that
last
time
and
I
took
the
action
to
write
up
a
proposal
for
how
we
manage
pr
to
like
propose
some
text
around
how
we
manage
feature
requests.
I
haven't
done
that
yet,
so
I
don't
think
there's
anything
to
discuss
this
week.
A
A
I
think
it
was
mateo
who
added
to
the
the
agenda,
and
we
have
had
some
discussions
back
and
forth
on
it
in
previous
meetings.
A
A
A
Okay,
the
next
one
is
renamed
default
branch
from
master
to
main
that
one
I
don't
know
of
any
updates.
I
know
there's
a
few.
You
know
we're
down
to
like
five
or
six
repos
that
we
need
to
finish
off
before
doing
the
main
repos
they're,
starting
to
be
some
of
the
like
the
trickier
ones
so
taking
a
little
bit
longer.
A
Okay,
well
then,
the
next
one
is
number
1141
which
is
nominating
darshan
to
the
tse
and
and
welcome
darshan
for
coming
to
the
first
meeting,
I'm
just
opening
that
you
know,
I
think
we
have
lots
of
plus
ones
there
I'll
just
have
to
go
check
back
on
our
our
governance
and
on
how
we
close
on
that.
But
you
know
look
forward
to
having
you
join
darshan
and
collaborate
with
all
the
rest
of
tsc
members.
Here,
thanks.
A
A
The
invite
the
next
one
is
invite
cc
members
in
the
google
calendar
from
for
meetings.
That's
one
one,
three
three,
I
know
mary
opened
that
one
and
was
gonna,
take
a
look
at
it.
So
I'll
just
take
a
look
to
see
if
there's
any
updates,
since
we
yeah,
I
don't
see
any
update
on
that
one.
So
I
think
we'll
have
to
wait
until
we
have
married
to
see
if
there's
any
updates
there.
A
A
I
don't
know
if
anybody
else
has
any
updates
or
discussion
that
they
want
to
add
to
that.
I
know
antoine
if
you
you've
been
pretty
active
there.
If
you
had
any
anything
in
terms
of
what
next
are
we
still
just
waiting
to
figure
out
what
the
the
questions
will
be
or
something
else.
C
Yeah,
I
think
that's
yes,
that's
about
it.
C
Yeah,
I
guess
it's
waiting
on
someone
to
make
the
vert
happen.
Maybe.
C
A
C
Sorry
I've
suggested
something
yeah
yeah,
I
don't
know
if
it's
the
consensus
to
follow
my
suggestions.
C
A
Okay,
the
next
one
was
that
security
triage
to
core
repo
governance,
md
and
or
charter.
I
think
that
one
is
is
kind
of
you
know.
Rich
has
been
working
on
ramping
up
the
triage
team,
and
this
was
just
on
the
the
agenda
as
a
reminder,
but
I
don't
know
that
there's
anything
specific
to
discuss
this
week
on
that
one.
A
B
A
Then
the
last
one
adding
jessnell
to
security
triage.
I
think
this
is
just
on
the
agenda
because,
as
we've
written
up
our
our
governance,
you
know
we
need
it's
part
of
what
we
need
to
do
in
terms
of
like
having
a
heads
up.
A
A
We
have,
I
mean
we
have
different
approaches,
so
in
some
cases
the
governance
is
very
specific
that
it
actually
needs
to
be
a
vote
in
a
lot
of
cases,
it's
more
consensus
seeking.
So
it's
like
as
long
as
people
aren't
objecting-
and
you
know
some
tfc
members
are
approving-
then
that's
good
enough,
so
I
it's
one
of
those
those
cases
where
like
if
I'm
proposing
something
I
always
like
as
many
positive
confirmations
as
possible,
but
technically
by
the
governance
likely.
You
know
it's
good
enough
already.
B
A
Yeah
like
it's
on
the
you
know,
we
if
there's
an
issue
in
the
repo,
that's
discoverable,
you
know.
If
we
have
it
on
the
agenda,
then
you
know
people
had
a
chance
to
know
about
it
and
you
know
so.
It's
kind
of
like
the
no
objections
part
makes
you
want
to
say
like
okay,
have
we
done
enough
to
to
reasonably
say
yeah
anybody
who
would
have
had
an
objection
could
have
had
it
right,
yeah,
so
yeah.
I
think
you
know
the
ask
is
if
you
can-
and
I
think,
though,
likely
it's
just
going
to
proceed.
A
Okay,
that
takes
us
to
the
end
of
the
list
of
things
that
were
on
the
agenda.
At
this
point,
I
will
flip
over
to
the
strategic
initiatives
and
take
a
quick
look
where
we
are
there.
A
Okay,
so
just
looking
at
the
lists,
I
think
the
only
one
that
we
have
one
of
the
champions
here
for
is
our
promise
api.
So
I
don't
know
if
there's
any
update
and
antoine
on
that
one,
no.
B
A
A
I
guess,
if
not,
if
people
can
stick
around
for
a
short
private
session,
that
would
be
great
and
thanks
for
everybody,
who's
taking
the
time
to
watch
on
the
youtube
stream.