►
From YouTube: 2022-01-20-Package Maintenance Team 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
package
maintenance
team
meeting
for
january
20th
2022.
before
we
get
started
on
the
issues
that
were
tagged
in
the
agenda.
Are
there
any
announcements
that
people
would
like
to
make.
B
Yes,
I
just
wanted
to
mention
the
parse
args
package
that
we're
all
working
on
in
the
package.js
org
is
in
an
attempt
to
make
it
easy
to
be
a
drop
in
contribution
to
node
core.
It's
following
the
same
primordials
pattern
that
node
uses
it
currently
did
that
by
copy
pasting,
a
file
and
modifying
it
slightly
from
node
core
I'm
in
the
process,
I've
claimed
the
package
name
primordials
and
I'm
in
the
process
of
building
a
package
that
can
be
used
for
that
use
case.
B
That
will
be
also
robust
in
like
in
outside
of
node
core.
In
a
way,
the
current
one
isn't
and
also
will
work
in.
You
know
older
engines
for
those
that
want
to
maintain
distant
backwards
compatibility,
so
yeah
I'll
make
a
pr
once
the
package
is
available.
B
Was
one
of
the
things
we
could
discuss?
I've
initially
created
it
under
my
username.
It's
still
a
private
repo
because
I'll
make
it
public
when
it's
ready,
but
I'd
be
happy
to
bounce
it
into
the
package.js
or
give
that
which
would
probably
make
sense
since
theoretically,
someone
should
only
use
this
package
if
they're
intending
their
the
consumer
to
be
migrated
to
node
core
there's
much
better
approaches,
if
you're
not
actually
aiming
for
that.
B
B
My
kind
of
what
I'm
envisioning
happening
is
that
the
parse
arcs
package
will
be
available
and
yargs
and
commander,
and
maybe
npm
and
so
on,
can
build
off
of
it
and
then
at
some
point,
node
will
ship
that
with
node
and
then
the
path
the
package
itself
can
defer
to
the
native
implementation
when,
when
present
and
have
the
in
the
javascript
one,
when
not-
and
at
that
you
know
in
that
way,
you'd
be
able
to
build
something
that
could
support
every
node
version
you
wanted,
but
in
all
the
modern
node
versions
would
use
the
native
parse
arcs
right.
A
If
not,
okay,
the
next
one
that
was
tagged
is
number
503,
which
is
updated
requirements
for
landing
prs.
I
think
I
opened
that
I
might
have
put
it.
Did
I
put
it
on
the
agenda.
A
A
this
one.
We
did
open
a
while
back
and.
A
I
think
at
this
point
yeah,
so
we
basically
said:
okay
yeah,
so
we
did
open
an
issue
right
so
499
we
opened,
which
was
the
please
respond
that
was
open
28
days,
so
we
said
we'd
give
everybody
30
days
to
respond
at
this
point,
there's
been
a
number
of
responses,
so
I
think
you
know,
maybe
by
the
next
meeting
we
can
action
the
the
audit
there
anything
else.
We
should
talk
about
that.
One.
A
Okay,
if
not
status,
an
update
for
the
next
steps
on
pkgs
create,
I
don't
think
I've
seen
any
updates
on
that.
I
don't
know
if
anybody
else
has.
C
Any
I
I
was
gonna,
try
and
stop
being
caught
up
with
some
other
stuff.
That's
my
next
thing
to
do.
I
think
I've
updated
the
docs
on
webby
landed
some
prs
in
there
and
I'll
be
turning
my
attention
to
that.
Like
you,
we
are
very
stretched
and
you
certainly
have
time
for
open
source.
A
A
And
then
the
last
one,
which
is
like
the
support
list
of
modules
to
get
support
info.
I
don't
think
there's
any
update
on
that
and
that
takes
us
to
the
end
of
our
agenda.
Actually
pretty
light
agenda
this
week.
Are
there
any
things
that
people
want
to
discuss
and
bring
up
before
we
close
out.
A
Yeah,
okay,
so
let's
see
we
can
talk
about
that
one.
Do
you
want
to
just
sort
of
lead
us
through
that
you
want
to
share
your
screen
or
how
do
you
think
the
best
way
to
do
that.
D
A
D
I
suggest
three
items:
firstly,
create
article
with
such
content
as
five
five
or
six
main
parts
goals
of
our
team,
current
status
tools
and
documents.
I
mean
existed
and
in
progress.
One
open
questions
and
next
steps.
Steps
and
last
item
call
to
action
to
invite
new
members
and.
D
To
promote
review
our
solutions
and
new
contributions,
then
I
think
that
we
can
do
some
status
talk.
I
mean
something
like
k
naught
on
the
round
table
with
the
same
content.
D
With
the
article,
maybe
with
slides,
maybe
with
extra
examples
or
some
media
content
and
then
roundtable,
I
think
that
it
can
be
a
online
event
with
lead
questions
from
community
and
also,
I
think
that
participants
can
be
a
few
members.
One
of
you,
members
from
our
team.
D
Guys
from
supported
packages
and
also
open
source
leaders,
I
think
that
five
six
participants
will
be
good
enough
for
the
first
time
for
dynamic
and
interesting
discussion.
A
Yeah,
I
think,
for
that,
like
for
the
round
table,
I'm
thinking
like
that
is
potentially
a
good
way
to
hear
from
more
package
maintainers
like
what
they're
struggling
with
what
their
problems
are
and
so
like.
If
we
could
get
if
by
having
like
a
you,
know
a
round
table
that
this
group
led.
That
might
be
a
way
to
to
get
some
of
that.
If
people
are
interested
in
showing
up
to
it,.
A
B
In
general
terms,
I
would
say
yes,
it
you
know
remains
unclear
whether
things
will
be
settled
down
enough
for
enough
people
like,
like
that's
a
general
thing,
for
any
in-person
adventure
scheduled
in
june,
but
like
for
a
smaller
subset
of
people
that
may
be
interested
in
such
a
roundtable.
It
might
be
even
more
tenuous
but
yeah
if
enough
people
could
show
up.
I
think
there's
definitely
enough
people
out
there
who'd
be
interested.
A
C
C
A
I'd
still
lean
towards
like
this
round
table
where
you
know
we
try
and
invite
three
or
four
maintainers,
and
one
of
us
or
two
of
us
moderates
sort
of
a
hey.
Let's
chat
at
the
you
know
the
state
of
the
events
what's
going
on.
You
know
what
are
our
biggest
challenges
that
that
would
be
interesting
to
me
like
it's
not
so
much
like,
even
if
nobody
watched
it.
I'd
still
be
interested
to
hear
and
be
in
in
that
discussion.
If
you
know
what
I
mean
yep.
C
Yep
yep,
that's
very
true.
There
are
some
pretty
big
things
coming
down
the
pipeline.
I
mean
I've
just
off
top
my
head.
One
of
my
things
is
es
modules
and
the
changes
required
for
testing
and
mocking,
and
all
that
sort
of
stuff
that
it's
eventually
going
to
come.
Where
everyone
is
has
this
little
blink
of
you
know,
I'm
not
using
them
just
yet?
C
Oh,
I
have
to
use
them
it's
coming,
and
that
is
quite
a
big
one
and
that
will
require
quite
a
lot
of
changes
by
people
if
they
wish
to
change
to
move
forwards,
and
it's
just
one
of
one
of
the
things
that
strikes
me,
as
is
quite
a
big
drive
of
change
and
maintenance
requirements.
A
It
actually
made
me
think
of
like
in
terms
of
these
round
tables
like
there's
different
audiences,
too
right,
like
there's
the
maintainers
and
then
there's
like.
I
think
what
you
were
reflecting
a
little
bit
is,
is
also
like
corporate
use
or
like
like
more
not
the,
not
people,
building
modules,
but
the
people
consuming
the
modules
and
there's
you
know.
A
roundtable
focused
on
those
people
might
also
make
sense
right,
absolutely
yeah.
It's
both
yeah,
it
is,
it
is
plus
and
like
so
doing,
one
of
those
a
quarter.
A
A
B
Move
to
es
modules
right
now,
it's
simply
not
tenable
without
a
bunch
of
hacks
and
workarounds,
it
should
be
tenable.
It
should
be
easy,
but
like
so
yeah
that
that
seems
like
an
interest
like
a
better
thrust
for
it
for
me,
because
it
would
also
be
easy
to
hop
on
the
trendiness
bandwagon
and
be
like,
like
you
know,
everyone
should
be
using
es
modules
right
now,
but
it's
it's
just
not
practical
for
most.
E
A
That's
actually
what
I
was
thinking
like
we're
doing
these
next
ten
mini
summits,
to
like
identify
like
what
are
the
key
things
that
the
project
needs
to
do
to
be
successful
going
forward.
I
could
see
one
of
those
mini
summits
like
esx
being
the
topic
right
and
you
could
say
well,
we've
got
any
sex
implementation
but
like
if
that's
not
the
end
of
it
and
there's
like
these
five
key
things
that
have
to
happen.
A
That
would
be
a
great
place
to
surface
those
to
say
you
know
if,
if
nothing
else,
you
know
writing
down
somewhere
in
the
project
that,
like
we
understand,
these
are
five
key
things.
So
if
people
are
interested
in
es6
now,
I
know,
there's
there's
actually
a
fairly
active
group,
so
maybe
the
s6
team
is
already
on
top
of
all
those,
but
but.
C
A
Yeah,
certainly,
I
know
that,
like
some
of
the
there's
a
few
key
things,
I
think
back
to
the
specific
thing
here
like
so
it's
maybe
like
a
round
table
series
would
be
an
interesting
that
would
be
good
yeah.
Well,
you
know
one
a
quarter
and
we
could
have
like
just
off
the
top.
My
head,
a
couple
of
things
are,
like
you
know,
a
maintainers
summit,
a
round
table
a
consumer's
roundtable
and
then
whatever
other
topics
like
maybe
an
es6
roundtable.
C
Yep
yep
I'll,
join
in
with
you
pavel.
Let's,
we
just
need
to
attract
a
few
more
people
to
get
a
round
table
together.
A
I
think
yeah
so
like
if
you're,
I
don't
know,
if
you're
volunteering
to
try
and
sort
of
pull
that
series
together
or
pull
one
of
those
together,
yeah
but
I'll
work
with
pavel
okay,
because
I
think
yeah
like,
if
you
know
we
can
help,
we
can
help
with
whatever
is
needed
to
you
know,
make
that
an
a
node
package,
maintenance
team
event
thing
that
that
sounds
good
and
the
article
yeah,
I
think
you're.
You
know,
writing
an
article,
that's
kind
of
like
hey
here.
Here's
like
a
refresher
on
our
goals.
A
We
could
probably
actually
pull
some
of
that
from
the
existing
docs
where
we're
at,
and
you
know,
highlighting
the
key
things
we're
working
on
are
kind
of.
It
definitely
would
be
it's
it's
time
to
do
something
like
that
for
sure
it.
C
C
A
B
A
Okay,
I'm
just
thinking,
though,
especially
when
you
have
little
kids,
if
you,
if
you
said
to
your
significant
other,
oh
by
the
way,
not
only
am
I
going
to
be
away
for
a
week,
but
the
two
weeks
afterwards,
I
can't
actually
help
look
after
the
kids.
I
know
how
that
well,
that
would
have
gone
over
for
me.
Yeah.
That's.
A
No
exactly
so,
I
guess
like
next
steps
here
you
know
so
glenn
do
you
want
to
get
together
with
pavo
one-on-one
or
something,
and
I'm.
C
Gonna
I'll
reach
out
to
pavel
I
set
up
I'll
set
up
a
zoom.
Actually
so
you
you
see
my
email
on
the
documents
pavel
and
I
so
shoot
me
an
email
pavel.
So
I
have
your
email
and
we're
we're
getting
together.
Yep.
A
Because
yeah,
I
think
that
would
be
a
that'll,
be
an
interesting
roundtable
it'll
be
real.
I
think
those
will
be
really
interesting
and
in
terms
of
the
article
you
know
again,
I
guess
like
the
next
step
is
just
somebody
just
to
start
to
put
things
together.
A
Even
even
like
often
what
we
do
is
we
can
create
a
document
like
a
google
doc
shared
in
the
in
an
issue,
and
you
know
somebody
puts
in
the
sections
and
then
you
know,
we'd
start
to
fill
in
different
sections.
Maybe
in
the
next
meeting
we
can
talk
about
like
volunteers,
for
the
different
sections,
that
kind
of
stuff.
B
A
Yeah,
I
think,
like
a
separate
issue
to
coordinate
the
article
definitely
makes
sense
and
the
round
tables
here
yeah.
I
think
all
three
of
them
really
like
that,
because
the
status
talk.
I
assume
you
mean
it's
it's
like
that's
a
talk.
We
proposed
to
open
js
world,
for
example,
okay,
yeah!
No,
I
think
an
issue
for
each
of
those
makes
a
lot
of
sense
for
sure.
C
I
will,
I
will
start
kicking
this
off.
A
contact.
Pavel's
got
my
email
from
the
documents.
If
I
click
on
pavel's
one,
I
think.
D
A
Yeah,
okay,
yeah
and,
like
maybe
you
know,
for
the
article,
if
you,
if
you
have
cycles,
you
know,
pasting
a
link
to
a
gold,
google
doc
where
then
we
could
start
to
edit
or
even
like
next
week.
Next
time
we
get
together,
we
could
spend
some
time
working
on
it
too.
So
sure,
okay,
yeah,
yeah
and
then
glenn
glenn
will
talk
to
you
directly
on
some
of.
A
Okay,
any
other
things
we
want
to
chat
about
this
week
before
we
close
out.
C
A
Sorry,
I'm
just
I
think
I've
got
everybody
and
let
me
see,
can
I
I'm
going
to
try
and
see
if
I
can
get
the
link
I'll
be
streaming
there
we
go.