►
From YouTube: Node.js Community Committee Meeting 2021-06-24
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
I
don't
know
why
that
sounded
wrong
joining
us
for
another
community
committee
meeting.
This
is
for
june
24th
2021.
We
don't
have
agenda.
A
So
this
is
going
to
be
a
pretty
short
one.
We
are
going
to
have
a
private
session
discussing
some
stuff
yeah.
We
can
get
off
into
the
agenda
updates.
Anyone
want
to
provide
updates.
C
Hey
guys,
I'm
here,
to
give
on
behalf
of
the
membership
initiative,
so,
okay.
So
over
the
past
couple
of
weeks,
we
completed
the
round
of
applications
to
add
a
new
mentee
to
the
mentorship
initiative.
C
So
currently
we
are
sort
of
iterating
through
our
process
and
having
a
process
review
to
sort
of
tackle
some
of
the
inefficiencies
we
we
experienced
in
the
last
surrounds
and
make
our
process
more
efficient,
efficient
and
seamless.
C
When
I
think
of
we've
also
been
reaching
out
to
initiatives
that
we've
helped
get
mentors
on
board
to
find
out
how
great
is
doing
and
if
they
need
anything
else
and
currently,
we
are
also
available
to
help
teams
and
initiatives
that
are
looking
to
get
meteor
or
need
help
one
way
or
another.
So
if
any
of
you
guys
are
available,
you
can
talk
and
we
can.
We
are
basically
available
to
help
from
initiatives
that
we
will
be
needing
mentees
to
sort
of
help
them
out
in
their
work.
B
I
I
might
just
add
that
did
recently
add
another
mentee
for
the
node
api
team.
You
know
we'd
got
a
number
of
good
applicants
that
had
gone
through
the
process
and
so
having
onboarded
the
the
first
mentee.
B
E
Yeah
for
internationalization
we
are
some
things
are
definitely
underway,
we're
meeting
regularly,
which
is
good,
so
there's
some
picked
up
steam.
Again.
We've
got
more
of
the
process
of
adding
people
regularly
who
are
requesting
access
to
translate
continuing
to
audit
that,
because
it's
kind
of
an
ongoing
process,
we've
synced
up
with
the
web
redesign
working
group
and
we've
been
able
to
connect
with
them
and
kind
of
see
where
the
footprint
is
that
we're
going
to
move
forward
with,
translating
and
providing
what
we
can
provide
for
them.
E
So
that
was
great
ben
halverson
came
over
and
gave
us
a
a
walk
through
a
couple
weeks
ago
on.
You
know
what
we
can
do
for
that.
So
that's
awesome
and
then
what
was
the
other
thing?
Oh
just
internet,
interesting
crossovers
between
this
working
group
and
what's
going
on
in
the
open,
js
standards
working
group,
there's
somebody
named
mike
samuel,
who
I
don't
know
very
well,
but
I'd
like
to
get
to
hang
out
with
him
and
he's
going
to.
E
He
wants
to
meet
with
me
and
steven
and
zeke
sometime
soon
to
talk
about
translation
of
apis
in
an
ide
which
might
be
interesting
and
primarily
to
assist
pre
fluent
english
speakers
and
people
who
need
a
little
bit
of
help
there
so
interesting
conversation.
I
don't
have
a
ton
of
context
for
it,
but
I
know
he
did
present
in
a
standards
meeting
and
he'd
like
to
meet
with
us
soon.
So.
B
A
B
A
Language
server
is
well,
wait,
no
wait!
The
you
mean
translations
for
like
javascript
right
and
not.
A
E
Don't
have
the
full
context
for
it.
I
know.
Okay,
all
I
know
is
that
he
like
what
he
said
was
interested
in
chatting
about
presenting
translated
apis
in
an
ide
to
assist
pre-fluent
english
speakers,
so
he
did.
He
did
have
a
presentation
on
it,
so
I
know
that
there's
a
footprint
there,
if
you
want
to
take
a
deeper
look
at
it
and-
and
I
will
too
I
just
haven't-
had
time
to
to
look
at
it
yet,
but
it
sounded
interesting.
A
For
that
and
yeah,
so
it
has
to
do
with
the
language
server
protocol
stuff,
I
think,
and
language
is
not
like
internationalization
language.
It's
like
programming
language.
It's
a
thing!
That's
in
vs
code
that
other
things
are
picking
up
right.
E
E
I
think
that's
very
like
to
for
this
group,
so
I
think
that's
why
it
would
be
good
to
have
stephen
and
and
myself
and
zeke,
and
whoever
else
is
interested
in
that
there
also
continuing
on
that
note
continuing
to
cross
over
with
you
know,
steven
invited
me
to
go
to
cldr
meetings,
so
I'm
trying
to
get
in
the
swing
of
that
and
bringing
all
these
groups
together
within
the
context
of
standards.
D
Nice
right
on,
I
will
add,
as
well
in
terms
of
website
redesign
work,
that
there
has
been
some
progress
there
on.
You
know
kind
of
the
basic
page
work
that
needs
to
happen,
and
so
that's
good,
some
some
movement
there
for
sure
I
wasn't
able
to
attend
the
meeting
yesterday,
but
from
what
I
saw
last
week
and
the
work
that's
been
going
on,
there's
there's
been
some
progress
and
and
like
layouts
of
like
basically
the
the
about
us
section
on
the
the
current
website
you
know
I
had.
D
So
I
think
that
that
is
largely
done
and
yeah
just
trying
to
help
keep
the
team
on
track.
There.
E
That's
it,
and
I
can.
I
can
back
that
up
having
gone
to
a
couple
meetings
saying
that
the
ben
halverson
and
a
few
other
people
jatil
people
are
pretty
those
those
folks
are
pretty
active
and
there's
definitely
progress
there
and
they're
pretty
focused
on
it.
So
it's
been
exciting
to
see
them
pushing
these
things
along
and
just
help.
You
know
joining
joe
and
them
periodically
to
to
help
out
as
much
as
I
can.
D
D
Soon
kind
of
show
where
things
are
and
what
the
I
I
was
trying
to
just
just
to
kind
of
summarize
a
little
bit
trying
to
help
the
team
to
focus
on
the
low-hanging
fruit.
You
know
those
those
kind
of
basic
pages
get
those
done.
My
my
direction
for
them
is
always
like
look
at
node.js.org
and
look
at
the
designs.
I
know
the
designs
are
lacking
in
a
lot
of
ways,
but
you
know
try
to
try
to
use
the
current
site
as
a
a
guide.
D
You
know
and,
like
I
said,
get
the
low
hanging
fruit
done.
We've
got
some,
I
think,
bigger
effort,
things
that
we
need
to
work
on,
but
I
wanted
to
get
those
other
things
done.
First,
so
bigger
effort,
things
being
like
you
know,
docs
is
one
of
them
internationalization
localization.
I
guess
I
should
say
localization
making
sure
that
the
pages
the
links
are
the
same,
which
you
know,
I
think
we're
largely
there.
We've
got
to
go
back
and
do
an
audit
of
that.
D
The
only
kind
of
asterisk
on
that
comment
is
the
localization
part
of
it.
So
you
know
there
are
some
some
bigger
chunks
of
work
that
we
need
to
focus
on,
but
the
the
the
low-hanging
fruit
is
coming
along
nicely.
So
we'll
see.
A
Cool,
I
think
the
only
thing
I
could
update
on
is
examples.
Basically,
I'm
gonna
stalemate
with
examples
right
now.
Github
actions
is
broken
in
a
way
that
we
have.
We
can't
run
the
examples
repo
as
it's
built.
We
specifically
mateo
came
up
with
a
solution.
A
I
initially
structured
it
with
with
the
intent
of
having
everything
used
just
for
tests,
and
people
were
rightfully
against
that
for
basically
jess
doesn't
necessarily
work
for
every
kind
of
application
that
could
go
in
there.
So
mateo
came
up
with
a
solution
that
basically
uses
a
feature
of
github
actions
and
having
basically
a
mono
repost
structure
is
that
you
will
have
a
github
action
for
every
single
project.
A
That's
in
it
and
the
way,
the
way
you
do,
that
is
with
the
paths
property
in
there
seems
like
the
paths
property
just
doesn't
work
like
it
doesn't
actually
do
what
it's
supposed
to
do.
I've
had
github
people
tell
me
this
should
work,
and
it
doesn't
so.
I've
also,
you
know
I
months
ago,
created
an
issue
in
their
github
community
forum,
no
response,
so
I
I
don't
know
I
basically
have
to
go
through
and
completely
reevaluate
how
we
structured
it
and
part
of
that.
A
I
was
waiting
for,
like
mpm
workspaces
to
be
stable.
I
think
this
when
I
was
initially
doing
this
work.
This
was
pre
workspaces
existing.
So
I
I
think
at
some
point
here
I
have
to
go
and
do
a
complete
refactor
of
it.
Luckily,
there's
not
a
ton
in
there
already,
but
like
right
now,
every
single
ci
for
each
project
runs
on
every
single
pr,
which
is
not
what
we
want
and
that's
a
lot
of
compute.
That's
just
completely
unnecessary.
A
So
I
have
to
to
find
the
time
to
basically
go
and
completely
restructure
that
project,
which
is
fine
I
can.
I
can
do
that.
I
have
other
every
time
I
want
to
go.
Do
that
I
I
feel
like
I
should
prioritize
com
com
work
and
then
I
inter
stalemate
in
my
brain,
where
I
don't
do
that
and
then
I
don't
do
anything
so
yeah.
That's
kind
of
the
status
of
that
is
basically
examples.
A
Can't
can't
work
as
it's
structured
right
now
because
of
this
feature
that
should
work,
what
doesn't
in
github
actions
and
then
on
top
of
that
you
know,
I
I
think
I
had
been
planning
to
do
a
restructure
of
it
anyway
with
workspaces.
So
you
know
I
just
need
to
get
around
to
doing
that.
Basically,
but
yeah.
I
I
like
it's
basically
impossible
right
now
to
to
add
things
without
exponentially
increasing
the
the
load
on
that
repo,
which
I'd
prefer
not
to
do.
A
I
mean,
like
I
will
accept
pr's
and
stuff,
but
I'm
not
gonna
go
and
add
my
own,
like
add
new
examples
without
doing
that
work
first,
so
that's
the
status
of
that.
I
don't
think
I
have
anything
else.
I
have
been
doing
some
kind
of
just
planning
work
for
comcom,
but
we
can
talk
about
that
in
the
private
session.
A
So
I
do
we
have
anything
else
that
we
want
to
talk
about
or
need
to
talk
about.
A
Cool,
I
think
with
that
then
we'll
end
the
public
session
thanks
for
joining
us
and
we
will,
we
will
see
you
next
time-
com,
com,
members,
please.