►
From YouTube: 2021-04-29-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
april
29th
2021.
we'll
follow
the
agenda,
which
was
in
issue
1020
in
the
tse
repo.
Before
we
start
on
that,
does
anybody
have
any
announcements
that
they'd
like
to
share.
A
A
On
the
cpc
front,
I
guess
worth
mentioning
is
that
there
is
currently
the
elections
for
some
of
the
voting
members
for
the
voting
members
for
non-impact
projects
and
reps
for
cpc
are
underway.
A
Those
aren't
necessarily
our
direct
representatives
as
a
project,
but
if
you
have
any
input
or
whatever
you
know
now
would
be
a
good
time
to
give
mary
or
joe,
who
are
our
cpp
cpc
representatives,
some
feedback
because
they
may
be
voting
in
those
otherwise
there's
some.
You
know
working
sessions
on
javascript
landy
have
taken
place
on
sort
of
the
project
landscape.
You
know
what
our
strategy
for
what
other
projects
might
be
in
in
the
in
the
you
know,
makes
sense
in
the
foundation.
A
A
We
won't
land
yarn,
but
the
consensus
was
that
we
should
explore
moving
in
the
direction
of
core
pack
and
getting
that
to
be
part,
as
we've
discussed
before
it's
not
a
you
know
an
approval
to
land
the
pr
as
is,
but
a
approval
for
that's
the
direction
that
we
think
is
the
right
way
to
go
so
we'll
work
in
that
context
going
forward.
Is
there
any
other
discussion
views
people
want
to
add
on
that.
A
A
Okay,
well,
that's
good!
So
we
can,
I
think,
close,
that
one
out
I'll
take
the
action
to
add
a
comment
on
that
specific
issue
which
was
blocking
and
then
I
think
the
pr
can
can
be
closed.
As
you
know,
we're
not
gonna,
not
gonna
land,
that
moving
on
to
the
next
one
tls
improved
compliance
with
shutdown,
standard
move,
hacks
number
three,
six
one
one
one!
A
I
looked
at
the
minutes
and
we
agreed
that
we
could
remove
that
from
the
agenda
last
week.
I
seem
to
have
forgotten
to
remove
it
from
the
agenda.
So
that's
why
it's
still
here,
so
I
don't
think
there's
anything
to
discuss
so
moving
on
to
the
next
one,
which
is
remain
default,
branch
from
master
domain
or
something
similar,
so
33
864.
A
that
one
is
sort
of
a
long,
ongoing
effort
to
to
move
our
projects
over,
I'm
not
sure
there.
I
don't
think
there's
been
any
more
progress
this
week
to
report
unless
there's
something
that
somebody
wants
to
mention.
A
B
A
B
A
Depends
on
the
repository
right,
so
you
know
in
some
repositories
master
sorry,
not
master
node.
We
know
that
there's
like
automation
and
tools
that
may
depend
on
the
branch
that's
being
used.
So
those
ones
you
know,
there's
more
intricacies,
other
ones.
There
really
won't
be
anything
and
for
some
of
those
it
depends
like.
If
I've
been
involved
in
them-
and
I
know
the
people
in
the
team,
I
can
feel
more
comfortable.
A
Just
saying
hey
like
we
may,
you
know
we're
going
to
go
ahead
and
do
this
because
I'm
part
of
that
community
that's
using
the
repo
in
other
ones.
It
probably
would
be
just
saying
opening
an
issue
saying
hey.
You
know.
I
know
I'm
not
active
in,
say
this
translation
group,
but
you
know
I
don't
think,
there's
any
issues.
A
C
The
the
two
main
sources
of
friction
are
are
are
automation
like
say,
like
a
github
action
that
specifies
master
rather
than
head,
or
something
like
that
or
other
tooling.
That
does
that
and
then
the
other
source
of
friction
is.
Is
you
know
the
the
developers
who
already
have
branch
who
already
have
forks
will
need
to
rename
or
do
some
work
around
if
they,
when
they're,
you
know
to
rebase
from
from
from
the
original
repository
and
github,
provides
those
instructions
but
getting
them
out
to
like
the
hundreds
of
people
who
are
doing
the
website.
A
C
A
Right,
so
so
that's
not
where
I
but
my
concern
is
that
we
make
sure
it's
not
a
surprise
right
like
if
we
just
go
and
change
it
on
them.
That's
not
nice,
but
if
we
at
least
give
them
the
the
the
heads
up
that
it's
coming,
they
could
have
an
opportunity
to
you
know
say:
oh
wait,
a
sec.
This
is
going
to
cause
me
grief.
A
Then,
when
it
happens,
they'll
probably
just
be
fine
right.
So
it's
more
about
you
know.
If
we're
not,
if
one
of
us
isn't
involved
just
making
that
issue
that
says
hey.
Do
you
mind
if
I
do
this,
because
I
you
know,
I
doubt
that
in
most
cases
it's
going
to
be
an
issue
for
anybody,
michael,
if
you
want
I'll
take
minutes,
so
you
don't
have
to
okay
sure.
Thank
you
very
much.
A
So
any
any
other
questions
like
it
sounds
like
that.
You're
just
wondering
you
know
what
what
might
make
you
what
you
should
do
in
doing
those
does
that
answer
the
question.
A
Thank
you,
okay.
So
then
we
can
move
on
to
the
next
issue,
which
was
3697,
which
is
migration
of
core
modules,
to
primordials
that
one
I'm.
A
D
D
Yeah,
so
I'm
still
working
on
a
documentation
to
document
what's
safe
to
do
with
pro
modules
and
what's
not,
but
no
no
progress
to
report
so
far.
C
I
think
there's
broad
agreement
that
generally
well-
maybe
I'm
mistaken
about
this,
but
generally
we
we
would
like
to
ideally
continue
moving
to
primordials,
but
do
it
in
a
more
careful
fashion
and
benchmark
hot
pads
and
so
on
and
so
forth.
And
if
that's,
if
that's
the
case,
I
wonder
if
this
can
be
removed
from
the
agenda
just
suggesting
anyway.
A
A
Yeah,
okay,
the
next
one
is
moderation:
team
certification,
one
zero
one
fourteen
I
know
rich.
You
had
a
plan
for
that.
C
My
plan
was
to
wait
for
the
chair
election
to
be
over.
Are
you?
Are
you
officially
our
chair
for
the
next
year.
C
C
C
Great
yeah,
so
so
hopefully
this
will
be
resolved
next
week,
but
I
I
do
wanna.
I
do
wanna
suggest
that
if
anybody
has
anyone,
they
want
to
nominate
some,
you
know
or
want
to
self-nominate
to
join
the
moderation
team.
Let
me
know
because
now's
now
is
the
ideal
time
to
do
it,
so
we're
just
certifying
everybody
in
one
single
boat
and
yeah.
A
That's
all
I
got.
I
think
it's
also
a
good
time
to
thank
the
people.
Who've
been
involved
in
and
doing
that
moderation
work.
It's
sort
of
a
an
important
unsung
hero,
kind
of
thing
that
that
goes
on.
I
know
there's
a
lot
of
work
that
happens
there
and
then
just
good
time
as
we
re-certify
people
to
say.
Also
thanks
for
continuing
to
do
that.
C
It's
a
nice
little
interesting
group
of
people
very
actively
engaged
in
node,
but
otherwise
largely
I
mean
not.
This
isn't
true
of
everybody.
C
C
Like
not
otherwise
deeply
involved
in
core,
I
don't
know
in
in
the
in
the
core
repo,
but
maybe
involved
in
you,
know,
community
community
and
other
another
repo.
It's
a
nice
little
cross
reference.
You
know
and
and
some
people
really
aren't
involved
in
core
in
in
node.js.
C
You
know
project
repos
at
all.
Really
so
it's
it's!
It's
it's
a
really
interesting
group
and,
and
I'm
really
grateful
for
the
work
they
do.
A
Yeah
and
thanks
okay,
so
the
next
one
is
revisit
the
meeting
times.
One
zero
zero.
Four,
so
I
know
chalker
you
were
going
to
take
another
look
at
the
numbers.
After
some
additional
people
had
completed.
I
think
the
goal
is:
let's
get
it
updated
for
next
week.
Do
you
have
the
the
the
data
on
that.
A
A
Whatever
that
says,
you
know,
I
propose
we
just
change
the
next
meetings
to
that
and
and
work
with
it.
A
A
Okay,
so
we'll
move
on
to
the
next
one,
which
is
potential
stagnation
of
the
openings,
h1
bounty
program,
654
and
I'm
going
to
say
we
are
inching
towards
resolution.
I've
been
working
on.
You
know
a
blog
post
and
approach
to
that
did
send
a
tsc,
an
email
to
the
tse
a
few
hours
ago.
Just
with
the
proposal
for
that
and
I'm
asking
that
we
just
stick
around
for
the
the
private
section
where
you
know
we
can
just.
A
I
just
want
to
give
people
an
opportunity
to
have
any
any
thoughts
on
that
if
there
are
any
but
yeah
so
we're
hopefully
within
you
know,
I'd
say
weeks
now
of
getting
that
closed
out.
A
A
A
So,
just
looking
at
the
initiatives
and
who
we
have
here
to
talk
to
them,
so
v8
currency,
nothing
new.
I
see,
okay,
thanks
for
filling
that
in
I
don't
have
anything
on
build
resources,
and
I
think
that
is
the
only
two.
Actually
I'm
going
to
go
and
promote
bethany
there.
C
On
we
really
got
to
get
back
to
I'll,
try
to
make
it
a
point
to
prompting
people
to
put
these
in
the
issue
before
the
meetings,
rather
than
doing
them
at
the
meetings,
because
it
just
works
better.
A
That
does
help
yeah.
No
that's
good.
So
that's
everything
that
we
had
on
the
agenda.
I
don't
know,
is
there
anything
else
that
people
would
like
to
discuss
or
things
we
should
talk
about.
A
I
guess,
if
not,
if
everybody
could
just
stick
around
for
a
few
more
minutes,
I
will
stop.