►
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
Perfect
everyone
and
welcome
to
the
new
jstc
meeting
of
the
13th
of
july
2022..
So
let's
start
with
the
usual
agenda
and
are
there
any
announcements.
A
No
doesn't
seem
so
so,
let's,
let's
move
forward
with
the
the
first
item
of
the
on
the
repository,
the
first
on
node.js
node,
which
is
issue
four
three:
five:
two:
zero
move
stream
development
out
of
node
out
of
core:
oh
yeah,
yeah,
the
security
that
is
restart
reach.
Thank
you
announcements.
Yes,
security
release
were
out
last
week.
A
Were
released
last
week,
okay
and
put
them
on
the
agenda,
so
let's
see
at
least
that's
it's
there
right
now,
stop
learning
yeah!
If
you
could
reach
that
would
be
amazing
so
that
I
can
focus
on
right
like
this
cool
okay.
So
it's
first
issue
is
move
stream
development
out
of
core
issue.
Four,
three:
five:
two:
zero!
A
A
Next
issue
is
the
proposal
node.js
vendor
namespace
issue
43413
what
was
proposed
by
james
nell,
which
is
not
on
the
call,
and
it
was
added
by
james
at
the
to
the
tsc
to
the
tsc
meeting.
I
don't
know
exactly
what
is
the
question
here,
but
let's.
A
Maybe
it's
just
awareness,
so
I
don't
think
I
don't
see
any
specific
question.
Are
there
any
concerns
that
somebody
wants
to
state
about
this
topic.
B
The
only
thing
I'd
say
is
there:
there
have
been
things
raised
in
in
the
issue
and
been
discussed
an
issue
and
they've
been
acknowledged
as
yes,
we
should
consider
it
or
you
know
we.
We
should
have
a
high
bar
barrier
for
including
something,
but
until
that's
kind
of
I
guess,
crystallized
into
to
some
actual
real
real
examples
of
you
know
what
might
be
included.
What
might
not
be
included,
and
you
know
what
is
that
bar
other
than
saying
it's
high,
it's
a
little
bit
difficult
to,
because
I
I
think
there
has
been
a
lot.
B
Concern
yeah
value
concerns
expressed
about
you,
know,
putting
something
in
and
into
node
and
then
including
something
to
know
and
then
having
to
to
deal
with
either
maintaining
it
or
updating
it
or
you
know
all
sorts
of
things
that
happen
when
we
bundle
something
into
to
our
binaries
and
it's
all
theoretical
at
the
moment.
It's
just
an
idea,
and
it's
not
really
a
concrete
proposal
in
terms
of
you
know,
what's
actually
going
to
what
would
be
the
next
thing
that
happens
on
that
yeah
and.
A
To
be
honest,
I
I
don't
know,
what's
the
next
step,
I
don't
know
if,
like
from
my
point
of
view,
the
discussion
is
happening
on
github,
okay,.
A
A
It's
it's
on
github,
so
I
don't
think
it's
I
think
it's
fine,
like.
I
don't
see
a
big.
C
If
we
include
something
and
it's
an
esm
package,
then
does
it
become
available
to
comma.js
and
if
so,
how?
So
there
are
some
technical
questions
to
figure
out
too,
but
in
my
mind
it's
much
more
project
management,
and
I
assume
he
wants
some
signal
from
us
about
like
how
we
feel
about
those
questions.
But
maybe
we
could
do
that
over
here
at
home.
A
Then
bethany
also
was
saying
in
the
chat
that
there
were
like
questions
about
reporting
and
security
issues
and
that
the
most.
A
A
The
conversation
is
happening
here
in
utah.
D
Yeah,
I
don't
see
any
specific
question
that
needs
to
be
discussed
in
the
dsc
on
this
or,
if
the
ask
is
the
tse
assistance
to
shape
up
the
proposal.
Even
that
is
also
not
clear
in
there.
On
the
other
hand,
the
discussion
is
happening
in
the
github,
so
it's
better
left
at
the
moment.
A
Yeah,
I'm
yeah
remove
the
agenda,
we'll
talk
a
little
bit
again
after
the
fact
cool.
Okay,
this
one
is
is,
is
covered.
Okay,
now.
A
These
are
the
next
one
is
issue,
four,
three,
three
eight
two,
which
is
the
consider
explicit
string,
formatting
module,
which
it's
more
or
less
it's
partially
related
to
the
previous
one,
which
it's
it's
probably
a
more
hated
discussion,
and
I
added
the
dsc
agenda
issue
mostly
for
for
awareness.
A
C
A
I
would
say,
like
the
the
fundamental
question
here
is:
there
are
a
few
interesting
points
released
in
this
in
this
one
one
is
we
have
a
lot
of
string,
formatting
behavior
in
core,
in
that
it
probably
starts
to
become
a
a
little
bit
convoluted,
okay,
and
on
that
I
agree
with
with
with
ruben
but
yeah
the
the
other
questions
are
related
to
esm
and
other
tangential
discussion
of
that
are.
A
E
Yeah
there's
there
was
an
ass
from
benjamin.
There
was
around
considering
the
impact
on
module
owners
and
the
ecosystem
like
sponsorships,
and
things
like
that,
and
there
was
a
suggestion
that,
like
the
tsc
that
should
be
on
mine
for
the
jfc
and
I
think
that's
separate
from
the
like
technical
resolution
of
this
issue
itself.
Someone
has
asked
that
we
consider
the
you
know,
impact
of
sponsorship
and
things
on
these
decisions.
A
E
A
So
yeah,
it's
it's
not
easy
to
some
extent
is
not
easy.
I
would
say
that
it's
subsuming
some
functionality,
that's
present
in
the
ecosystem,
means
that
we
really
yeah.
We
don't
know
russia
yeah,
okay,
let's,
as
I
say,
let's
move
it
back
to
github.
I
don't
think
there
is
anything
that
we
need
to
talk
about
this
today.
A
So
it's
it's
still
moving.
So
I
don't
think
it's
still
good
at
the
discussion.
I'm
going
to
post
a
message
there.
A
And
do
we
and
we
bring
inside
community
separate
issue
and
in
the
original
topic.
A
A
A
A
Okay
and
perfect:
that's
it.
A
A
A
C
A
Putting
in
a
blocked
discussion,
okay,
that's
done!
Then
we
have
another
issue
on
the
node.jstsc,
which
is
the
openjs
cross
project
council
nomination
for
node.js.
A
There
is
a
proposal
to
reappoint
the
previous
year
members.
We
were
josephi
and
rich
trott
and
I
would
second
that
motion.
However,
we
don't
have
pardon
to
make
that
decision
today.
So
I,
however,
I
I
think,
there's
no
question
and
I'm
going
to
add
something
on
the
issue
that
reaches
open,
saying
that
we
are.
A
A
This
one
is
covered,
and
next
one
is
a
nodejs
internationalization
issue.
612
i18n,
that's
a
repo
okay,
and
this
is
one
that
every
single
time
periodically
this
gets.
This
has
been
around
for
all
tsc
meetings,
so
we
probably
want
to
come
to
a
little
bit
of
a
better
conclusion.
I
will
if
this
has
been
kicked
back,
because
we
don't
know
what
to
do.
A
A
A
So
the
this
is
kind
of
over.
For
today
we
have
a
big
a
little
bit
of
spot
for
strategic
initiatives.
I
don't
think
there
is.
Is
there
anybody
that
wants
to
that?
Has
animated
any
progress
on
any
of
the
certificate
initiatives
to
to
do
it?
A
Cool
and
know
that
it
is
nothing
please
remember
that
the
upcoming
meetings
are
available
in
the
nodejs
project
calendar
and
you
can
find
it
at
https
and
nodejs.org
calendar,
and
you
can
just
add
it
to
your
own
google
calendar
and
follow
up
on
our
meetings.
A
Having
said
that,
I
think
that
for
today,
if
you
all
can
stay
on
for
a
second,
there
is
a
little
bit
of
security
stuff
that
we
probably
need
to
talk
about.
So
please,
folks
and
if
bad
can.