►
From YouTube: 2020-11-11-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'm
just
hearing
myself
from
the
youtube
stream.
Okay,
so
there
we
go.
It
is
in
issue
949
in
the
tse
repo.
B
A
A
Okay,
if
not,
let's
move
on
to
the
cpc
and
board
meeting
updates.
I
don't
have
anything
new
to
report
on
the
board
front
on
the
cpc
front,
a
few
things
that
are
being
worked
that
I
know
of
since
mary
isn't
here
include
the
the
basically
the
the
yearly
review
process
for
projects
and
the
focus
really
today
is
on
growth
stage
projects
and
putting
in
place
templates
for
growth
plans
getting
a
few
of
them
in
place
and
and
basically
fleshing
out
that
part
of
the
the
overall
process.
A
A
I
think
those
are
kind
of
the
main,
the
main
things
to
to
report
at
this
point
and
the
board
meeting,
I
think,
is
well,
it's
the
the
I
believe
the
last
friday
of
this
month.
So
if
anybody
has
anything
that
needs
to
be
taken
to
the
board
or
you
think
I
should
bring
up
there-
just
let
me
know
okay.
So,
let's
moving
on
to
the
issues
that
were
tagged
for
the
agenda,
the
first
one
is
35
788,
which
is
backporting
util
types,
pathposix
and
pathwind32
to
v15
proposal.
A
A
Okay,
the
next
one
is
rename
default
branch
from
master
domain
or
something
similar,
that's
sort
of
a
long
ongoing
issue.
I
know
we
were
trying
it
out
on
a
few
of
the
different
branches
or
served
up
branches,
the
projects
within
the
organization
we
don't
have
miles
today
for
an
update.
I
don't
know
if
anybody
else
has
any
updates
or
comments
on
that.
A
A
Okay,
if
not
we'll
move
on
to
the
next
one,
which
is
audit,
google
account
access
again,
that's
basically
waiting
on
some
help
from
the
foundation
and
there's
no
update
this
week.
So
we'll
move
on
to
the
next
one
potential
stagnation
of
open
issues
on
h1
bounty
program,
654.,
I
think
rich.
You
were
going
to
jump
in
here
to
to
give
us
an
update.
B
Yeah,
so
we've
turned
off
the
ability
to
submit
more
entries
to
the
program,
and
so
the
accumulating
untriaged
reports
will
will
at
least
not
grow
and
we're
talking
with
the
security
working
group
about
what
to
move
forward
with
this,
a
couple
of
ideas
being
kicked
around
and
more
information
soon
and
if
anybody
is
interested,
anybody
in
the
tsc
is
interested
in
more
details.
Just
ask
michael
or
me
and
we'll
either
give
you
the
information
or
plug
you
into
the
conversation.
A
Sounds
good
thanks
for
that
update
any
questions
before
we
move
on
to
the
next
issue.
A
A
Still,
probably
I'm
just
we're
still
not
where
we
want
to
be,
but
we
haven't
had
any
sort
of
critical
issues
or
anything
like
that.
You
know
and
we're
still
still
on
the
the
board's
radar,
but
this
year
is
a
special
year.
So
I'm
not
sure
if
we're
gonna
see
something
like
in
terms
of
paid
resources
or
anything
like
that
too
soon,
but
I'm
still
on
still
on
the
radar.
A
A
Okay,
if
not
that
closes
out
our
agenda
for
today,
so
that
was
actually
a
fairly
quick
agenda.
If
people
can
stick
around
for
the
private
section,
I
will
stop
the
stream.
Thanks
for
everybody
who
joined
the
stream
today
and
we'll
see
you
in
github.