►
From YouTube: 2020-10-12-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
october
12
2021.
We
will
follow
the
agenda
that
was
outlined
in
the
issue
within
the
repo,
which
was
issue
number
four
85..
Before
we
get
started.
Does
anybody
have
any
announcements
they'd
like
to
share.
A
Okay,
if
not,
we
might
as
well
start
on
to
the
first
issue,
which
was
the
status
update
and
next
steps
for
pkjs
create.
A
That
one
I'm
just
trying
to
take
a
look.
I
know
we
have,
you
know,
moved
all
the
stuff
we
needed
to
into
the
repo
and
I'm
just
scrolling
down
to
the
bottom.
B
No
updates,
since
I
haven't
been
able
to
join,
I
haven't
been
able
to
also
follow
up
on
it.
No,
my
name
was
kind
of
attached
to
this
in
the
initial
and
then
talked
to
wes,
and
things
went
crazy
from
there
and
then
john
came
and
I
haven't
had
a
chance
to
sync
up
with
john
either.
So
I'll
probably
try
to
do
that
again
now
that
I've
got
a
little
bit
more
free
time
again,
a
little
bit
sounds
great.
If
you
have
a
bit
more
cycles,
that
would.
A
A
I'm
really
happy
either
way
like
it
probably
needs
to
be
usefully
on
the
agenda.
It
probably
needs
a
few
more
like
some
more
specific
thoughts,
so
I'd
be
happy
to
close
this
and
then
come
up
with
some
other
things,
but
I'm
also
happy
to
kind
of
leave
it
on
as
a
reminder,
so
I
don't
mind.
C
I
think
I
mean
if
it
works
for
yourself
in
terms
of
you
know,
reminding
you
yeah
it's
I
I
think,
as
so
as
my
understanding
correct,
that
it's
mostly
kind
of
there's
a
reminder
from
a
like
a
socialization
perspective
like
just
okay,
that's
pretty
much
why
the
next
issue
is
on
the
agenda.
So
I
think
it's
fine.
A
C
Pretty
much
it's
there's
like
a
half
out,
there's,
maybe
only
three
or
four
of
them
left
now,
but
yeah.
It's
just
kind
of
like
a
top
level
checklist
and
kind
of
safe
thing,
just
a
single
place
to
kind
of
share
that
general
effort,
one
action
or
one
action
item
I'd
hoped
to
achieve
and
still
thinking
I
should
be
able
to
do
it
this
week
was,
you
know,
see
if
it's
an
opportunity
to
share
as
part
of
hacktoberfest.
C
You
know
they
don't
really
require
it's
mostly
just
administrative
stuff.
So
I
thought
to
maybe
try
and
say:
hey
if
anybody's,
looking
for
a
way
to
help
out
in
the
new
js
package
rates
project,
there's
a
couple
kind
of
some
low-hanging
fruit
and
work,
your
way
towards
a
I
guess,
a
t-shirt
or
or
planting
a
tree.
A
C
Yeah
I
mean
if
someone
wants,
you
know
someone
submitted
a
pr
with
the
last
three
or
four
all
done
it
once
but
yeah.
Sometimes
it's
a
little
easier
to
divide
and
conquer.
So
just
yeah
someone's.
D
C
Oh
yeah,
that's
that
yeah,
I
think
yeah.
I
think
part
of
the
only
reason
to
break
them
up
was
that
at
least
from
myself
and
maybe
others
we
didn't
really
know
the
state
of
them.
So
it
wasn't
necessarily
just
a
simple
shift.
We
did
wanna,
you
know
the
opera.
It
was
an
opportunity
to
kind
of
take
a
quick
editorial
review
and
be
like.
Actually
this
should
stay.
That
way
you
know,
but
if.
C
Then
there
probably
wasn't
any
reason
to
not
promote
it,
so
it
just
I
mean
that
could
probably
take
someone
like
you,
five
minutes
to
be
like
yeah,
good
enough
great
move
it
you
know
good
and
if
any
of
them
need
more
time,
just
do
two
out
of
the
three
and
leave
the
third
one
for
someone
else.
You
know
so
everybody.
A
A
I
guess
the
question
there
is-
would
do
we
would.
Would
we
as
a
community,
want
to
take
that
over?
D
A
D
I
think
it
would
be
a
good
thing
for
node
community
as
long
as
we
can
as
long
as
we
have
the
capacity
to
take
that
on
judging
by
the
number
of
issues,
the
traffic,
that's
the
new
issues
that
are
getting
created,
the
the
pull
requests
and
that
repo-
it's
not
that
active.
There
are
some
long-standing
issues
that
nobody
is
looking
into,
which
is
it's
hard
to
understand
whether
it
is
a
capacity
planning
issue
or
whether
there
are
some
architectural
decisions
to
explicitly
not
implement
certain
things.
D
But
otherwise
it's
it's
not
a
very
high
volume
repo,
but
we
still
need
to
have
a
team
of
people
looking
into
it,
because
it
is
very,
very
central
to
github
actions
generally
speaking,
right
everything
all
the
examples,
all
the
everything
that's
node
related.
It
depends
on
that
which
means
that
any
change
in
that
repository
can
have
a
very
high
knock-on
impact
on
both
the
users
of
these
actions,
but
also
on
github
themselves.
D
So
there
definitely
would
be
a
need
for
some
collaboration,
but
I
am
very
much
rooting
for
for
for
getting
that
involvement
and
and
and
getting
that
community
feedback
into
that
repo,
because
it's
been
not
as
active
as
as
I
would
have
personally
liked
to
see
that.
I
know
that
some
long-standing
issues
have
been
resolved
recently,
such
as
support
for
keywords,
but
then
there's
other
issues
that
are
not
necessarily
moving
that
are
coming
from
the
community
right.
So
there's
it's
it's
hard
to
tell
what's
the
actual
situation,
so
I
ideally
I
would.
D
I
would
love
to
see
this
under
the
node
foundation
umbrella
and
I'm
sure
that
you
know
there's
there's
people
who
would
be
interested
in
contributing,
but
I
don't
know
how
to
find
them
and
reach
out
and
how
to
yeah.
A
A
Question
like
if,
if
yeah
I,
I
think
my
understanding
is
like
one
of
the
versions,
one
for
some
other
runtime
was
moved
into
that
runtime
scope.
So
it's
not
impossible.
Interesting
question
would
be
from
our
perspective.
You
know
if,
if
we
got
the
question,
do
you
want
to
take
this
on?
Would
we
would
we
just
say
yes
move
it
over
or,
like
you
said,
do
we
need
to
try
and
see
if
we
can
find
the
volunteers
to
maintain
it.
D
D
You
know
their
needs
right
chris,
because
I
mean,
and
then
this
does
get
back
to
the
discussion
of
who
has
paid
time
to
do
that
because
not
everybody
does
and
certain
aspects
of
it
are
a
commercial
tool
that
is
being
maintained.
D
So
so
there's
a
bit
of
you
know,
there's
there's
some
medical
concerns
there
as
well
right
so,
but
if
we
can
assemble
more
people
that
would
like
to
be
involved,
then
I
I
would
say
that
it
would
be
very,
very,
very
good
for
the
community
if
this
had
more
community
involvement
and
that
community
involvement
got
actually
accepted
and
and
fed
back
into
the
repository
right.
Okay,.
A
B
I
know-
and
you
know,
enterprise-wide
at
our
company
we're
trying
to
make
that
initiative
of
you
know
moving
into
the
enterprise
cloud
and
utilizing
you
know,
actions
as
more
of
the
stable
ci
cd
framework,
or
you
know,
for
a
lot
of
those
things
so
having
it
moved
into
the
node.js
umbrella,
does
make
a
lot
of
sense
in
my
mind
as
well,
but
I
agree
with
dominicus
there's
a
lot
of
questions
in
terms
of
you
know:
there's
our
paid
resource
on
it
and
being
that
we,
you
know,
github
is
the
original
owner
of
that,
like
where
you
know
what
what
wines
did
that
come
into
so
I
agree.
B
There's
some
definite
questions
need
to
be
clarified
and
clear,
but
as
far
as
helping
maintain
it
happy
to
help
out
been
diving
into
have
actions
a
lot
lately
so
been
in
terms
of
efforts
on
our
side.
So
it's
been
kind
of
fun
doing
it
so
happy
to
help
okay,
so
I'll
include
you
as
well.
A
Yeah
right
exactly
well
yeah.
Hopefully
it
won't
take
too
long,
but
we'll
see
if
we
can.
You
know,
have
the
discussion
see
if
there
if
there
is
an
option
or
not,
because
I
know
we,
you
know
we
reached
out
to
some
people
and
everything
and
I
think
it
just
needs
closing
the
loop
now
so,
okay.
So
that's
what
we
had
for
go.
D
D
A
Okay,
that's
all
we
had
on
the
agenda
for
this
week.
Anything
else
we
should
talk
about
before
we
close
out.
D
I
did
have
a
I
yeah,
I
didn't
have
the
label
because
it's
another
repo-
and
I
forgot
that.
Actually
I
could
be
doing
that,
but
I
did
add
a
small
issue
there.
I
have
a
new
repository,
pcg.js
action.
I
have
an
issue
there
for
the
mvp
and
I
have
a
pull
request
there
and
basically,
what
that
repository
does.
Is
it
wraps
setup
node
and
creates
a
node
matrix
based
on
the
keyword
so
similar
to
what
we
did
with
travis
a
while
back?
D
Basically
last
week
was
last
week
yeah,
it
was
only
last
week.
I
think
that
github
came
out
with
shareable
workflows,
so
there's
a
one
more
primitive
that
can
be
used
for
constructing
things
in
in
in
github
actions,
which
allows
better
even
better
code
reviews,
which
means
that
it
allows
generated.
D
D
D
Correct
yes,
so
I
do
maybe
open
up
the
readme
changes
in
there.
That
can't
just
be
the
best
option.
Okay,
because.
D
Yeah
yeah
yeah,
so
yeah
there's
the
usage
and
basically,
if
you
define
your
engines,
the
this
action
will
read
the
minimum
version
from
the
engines
and
then
it
will
construct
a
matrix
based
on
the
upgrade
policy.
And
if
you
look
at
the
ci
yaml
example
in
in
the
step
two
there,
that's
basically
what
you
need
to
include
and
you
get
a
full
node
matrix,
including
it
will
basically
generate
a
matrix
for
the
all
the
lts
versions,
starting
with
minimum
10.
It
will
npm
install
and
it
will
run
in
vm
test.
B
It
I'll
give
it
a
review
a
little
bit
later
today.
D
B
B
B
That,
if
I
find
the
docks,
I
can
send
it
to
you
because
it
was
it
wasn't
he
definitely
a
doctor
marked
it
and
there's
something
talking
about
entrance.
I
mean
I,
I
would
love
it
to
handle
this
this
way,
because
that
just
makes
it
you
know
more
flexible.
You
don't
have
to
really
hard
list,
your
matrix
or
anything
like
that.
So
this
is
definitely
a
more
flexible
way
of
going
about
it.
D
B
D
D
C
Backwards,
I
think
part
of
the
the
issue
was
that
people
upgrading
from
or
upgrading
npm
version
would
allow
them
to
update
npm
seven,
even
if
they
were
on
like
npm
10,
so
they
upgrade
npm
go
to
like
npm
install
and
then
everything
would
just
break.
And
so,
if
it
sounds
like,
maybe
you
know
I'm
assuming
they'll
use
engines.
But
this
way,
if
you
went
to
npm,
install
npm
six
and
you're
on
node
10
and
for
npm
8
technically
it'll
be
like
hey.
D
Yeah
but
even
then
it's
sort
of
octagonal
to
any
of
the
problems,
because
it
doesn't
it's
still
a
field
that
people
use
and
it's
a
useful
field
to
communicate.
What
you
support,
whether
you
break
or
don't
break
during
the
install
is,
is,
is
kind
of
not
the
whole
point.
The
point
is
that
in
your
package.json
you
communicate
which
versions
you
support.
So
that's
that's
metadata
and
that's
useful
metadata
in
travis.
D
When
I
did
the
same
thing
for
for
the
travis
includes
I
I
we
have
to
define
the
version
in
in
in
the
config
itself,
because
we
have
no
way
of
reading
the
package
json,
but
because
we
can
read
the
package
json
and
the
action
we
don't
need
to
duplicate
that
information.
So
maybe
there's
an
option
like
maybe
it
should
be
optional
and
there
should
be
another
parameter
which
allows
you
to
override
that
or
something
like
that.
D
But
that's
maybe
a
bit
after
the
mvp,
and
I
think
I
think
I'll
try
to
open
up
some
issues
in
node.js
organization
to
see
if
people
are
willing
to
try
it
out
and
ideally,
ideally,
we'd
get
some
feedback.
Before
note,
16
comes
out,
which
means
that
we
could
potentially
recommend
that
people
start
using
this
to
automatically
upgrade
their
test
matrices,
while
they're
at
it
right
just
opt-in
to
the
automatic
update
behavior.
So
that
was
the
intent
there
and
yeah
I'll
appreciate
any
reviews.
Now
for
the
pr.
C
D
D
Wish
we
could
do
that,
you
can.
I
can
give
you
instructions
on
how
on
how
to
test
it.
Basically,
you
can't
use
the
pr
directly.
You
will
need
to
fork
and
you
will
need
to
update
some
paths,
because
in
your
in
the
include
that
I
have
there,
it
has
to
reference
a
repository
and
that
repository
is
itself
which
is
not
merged.
A
D
C
C
D
B
D
Yeah
you
can
fork
it
find,
replace
pkg.js
action
with
your
repository
and
then
and
then
you
remove
it.
I
see
I
see
all
right
good
to
know
yeah,
that's
something
I'd
like
to
fix
very
very
soon,
because
working
with
forks
will
be
very
very
hard.
Otherwise,
it's
not
not
a
trivial
thing.