►
From YouTube: 2020-05-04-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
Free
I'm
going
to
pass
in
the
link
here,
so
people
can
add
themselves
to
the
agenda.
A
So
now
we
don't
have
any
of
the
people
who've
sort
of
been
actively
participating
there
or
trying
to
move
that
forward.
I
don't
know
if
anybody
has
any
updates
or.
A
A
If
not,
I
suggest
we'll
we'll
skip
till
next
time
too,
and
we
may
we
have
somebody,
you
know,
there's
a
few
people
who
are
actively
working
up
since
we
don't
have
them
we'll
just
skip
till
next
time.
A
The
next
one
is
suggested
list
of
modules
to
get
help
support
info
into.
I
don't
know
if
there's
any,
I
don't
have
any
updates
on
that
front.
Does
anybody
else
have
any
updates.
A
A
I
think,
as
I
know,
we're
still
waiting
to
kick
off
the
first
meeting
for
the
collaboration
space.
Hopefully
that
still
will
happen
soon,
but
I
don't
have
any
updates
yet.
A
We'll
just
leave
that
as
no
updates
this
time.
So
I
think
that's
actually
what
we
had
tagged
on
the
issue
and
so
maybe.
B
Yeah,
you
did
add
the
agenda
label
on
one
of
my
issues.
We
may
as
well
cover
it
shortly.
Although
sounds.
B
Yeah
go
for
it
yeah,
just
not
sure.
If
we
have
enough
people
interested,
maybe
we
should
just
not
do
it
but
yeah.
Basically,
I
suggested
that
maybe
we
should
effectively
fork
action,
setup
node,
which
is
the
official
github
action
that
they
recommend
for
when
you
want
to
basically
run
node
in
your
ci
because
well
for
one,
it's
not
getting
many
features
that
people
are
asking
for.
It's
also
been
very
hard
to
push
through
the
even
the
basic
support
for
the
keywords
such
as
you
know,
lts
active
latest.
B
A
B
Yeah,
well,
it's
the
I
yeah.
I
assume
that
that
whole
organization
is
the
official
github
actions,
okay
from
github
right,
okay,.
B
Yeah
yeah,
so
I
know
jordan
maintains
his
own
and
I
guess
his
is
is
pretty
well
worked
out
and
researched
and
I
guess
it
suits
him
at
the
very
least,
but
I
figure
that
maybe
there's
a
point
in
you
know
getting
something
that
would
be
official
for
node
as
opposed
to
something
that's
official,
that's
provided
by
github
and
then
and
then
then
maybe
we
could
have
more
influence
in
trying
to
basically
steer
it
in
the
way
we
would
want
the
community
to
to
run
their
ci
and
even
even
even
it's
hard
to
do
a
matrix
matrices
in
in
actions
as
it
stands.
B
It
requires
a
lot
of
boilerplate,
but
I
know
they're
working
on
that,
but
it's
been
shifted
to
q3
according
to
their
roadmap.
So
even
just
getting
the
basic
keywords
in
there
would
already
be
an
improvement.
So
I
don't
know
yeah,
basically,
maybe
there's
a
way
to
reach
out
to
whichever
team
works
with
the
official
action
and
try
to
see.
If
we
can,
you
know
collaborate
better
there.
B
So
that
was
a
suggestion
there.
I
I
just
don't
know
whether
there's
enough
enough
of
a
will
and
whether
there's
enough
of
of
a
team
that
we
can
assemble
to,
I
don't
suppose
it
will.
Famous
last
words
require
a
lot
of
maintenance,
but
it's
something
that
I
find
would
probably
be
useful.
I've
also
resurrected
the
detect
node
support.
B
I
had
a
long-standing
issue
there
to
try
to
build
a
thing
which
detects
versions
from
github
actions,
so
it
works
for
the
simple
cases
already.
It
doesn't
work
for
jordan's
stuff.
B
We
just
need
to
add
more
code
to
parse
out
his
configurations
and
and
and
his
setup,
because
I
assume
there
will
be
a
bunch
of
modules
that
used
to
that
do.
Use
that
so,
but
even
which
is
by
random
poking
around
people
will
be
staying
behind.
C
Yeah
the
question
regarding
the
the
pull
requests
that
you
link
to
in
number
26
is
the
issue
that
that
project
won't
support
the
aliases
or
that
github
actions
doesn't
support
the
aliases.
B
C
The
if,
if
the
if,
if
node.js,
was
to
fork
or
you
know,
create
an
official
one,
would
we
have
to
update
like
every
time
the
release
schedule
changes?
We
would
push
a
new
version
that
so.
B
We
yeah
we
already
have
tooling,
which
kind
of
helps
you
do
that
we
do
have
pkgs
envy,
which
automatically
fetches
the
support
json,
which
is
maintained
by.
I
guess
the
release
group
right,
which
has
all
the
dates
which
tells
you
which
versions
are
released
when
and
how
long
they're
supported
so
there's
there's
a
there's
a
file
already
for
that
and
there's
modules
that
parse
that
file,
so
I
would
assume,
would
build.
C
C
D
B
C
But
there's
a
it
sounds
like
it's:
it's
more
just
the
maintenance
side
on
the
github
side,
less
about
the
ability
to
do
things
it's
like.
If
someone
had
the
time
they
could
do
the
things
we're
talking
about
it's
just
it's
not
so
there's
a
user
land
solution,
it's
just
where
you
just
need
a
user
to
land
it
as
a
solution.
B
Yeah
yeah
so,
like
I
said,
the
user
has
a
solution.
Jordan
links
to
his
stuff
in
the
thread
there,
so
that's
that's
definitely
worth
looking
into
and
then
then
there's
a
question
of
of
blessing
that
and
maybe
working
together
with
getup
to
get
a
new
blessed
thing
which
is
recommended
for
people
to
use
which
does
get
the
maintenance
and
which
does
get
the
input
from
the
way.
B
B
A
C
A
C
I
guess
just
a
another
sorry
clarification
question,
because
I
like
the
idea,
I
guess
the
question
is:
if
say,
I'm
using
this
as
a
github
action
today
I
run
a
build
right
now
and
then
tomorrow
you
know
the
next
lts
for
the
release
schedule
shifts
tomorrow
and
then
I
build
with
my
action
tomorrow.
Is
that
alias
mapping
happening
in
the
background,
or
would
I
have
to
bump
my
action
to
a
new
version
to
get
the
new
release
schedule?
B
So
it
depends
on
the
setup
we
can.
We
can
probably
flesh
out
the
details,
but
I
would
assume
most
of
the
people
would
get
a
static
list
of
the
versions
that
they
support
and
on
top
of
that
they
would
add
latest
at
the
very
end,
which
means
that
as
a
keyword,
which
means
that
as
a
new
version
comes
out,
they
would
start
testing
in
it,
which
means
that,
like
today,
they
somebody
would
probably
have.
I
don't
know
10
12,
14
plus
latest,
which
today
would
be
10
12
14
16.
B
A
And
today
I
mean
earlier
today
I
looked.
I
was
reviewing
something
with
somebody
today
and
it's
like
oh
yeah,
and
I
guess
we
need
to
add
16
to
that
list
right.
So
it's
very
easy
to
forget
to
add
the
latest
one
into
the
list
and
stuff
so
yeah
and
it's
a
thing
that
it's
a
step
you
need
to
take
and
it's
a
maintenance
burden
right
yeah
I
mean
like
the
lts
one
like
for
that
case.
A
A
So
I
wonder
if
we
should
like
reach
out
to
tyranny
and
and
miles
to
say,
what's
your
take
right
like
do
you
think
you
can
connect
us
with
the
people
so
that
we
can
have
ongoing
contribution
feedback
from
the
project
or
is
it
like
yeah?
I
know
they're
just
too
busy
and
it's
not
a
priority.
So
do
your
own
thing
right
make
sense.
I.
D
Think
they
are
engaging
on
that
thread.
At
least
peony
has
already
yeah.
So
I'm
not
sure
like
to
me.
I
don't
see
any
problem
with
us,
forking
it
and
playing
around
with
it
in
the
pktjs
or
something
like
that
and
then
even
moving
it
over
to
node.
If
we
do
want
some,
even
more
recommended
kind
of
under
that
organization.
I
see
no
issues
with
that
and
particularly
if
we
started
in
pkg
js,
because
that's
just
proving
out
like
it's
useful
for
us
as
package
maintainers.
A
C
C
Well,
if
jordan's
got
like
a
kind
of
a
proof
of
concept
somewhere,
couldn't
we
build
that
proof
of
concept
on
to
the
well
submit
a
a
pr
with
the
work
or
say,
like
hey,
jordan's
got
a
proof
of
concept.
We
might
have
a
leg
up
already
and
if
we
can
just
get
it
over
the
finish
line,
we
can
submit
the
pr
and
then
hopefully
it
gets
blessed.
If
not
the
work's
done,
we
can
take
it
back
to
the
other
org.
B
That's
that's
the
issue,
but
that
particular
issue
for
abs
is
has
apr,
which
has
been
open
for
a
year
and
a
half.
A
Yeah,
like
I
don't
think,
I'm
active,
and
it's
not
just
that
hey,
we
have
one
pr,
it's
more,
the
we're
looking
for
a
path
that
lets
the
project
have
ongoing
input,
and
so
it's
that's
kind
of
the.
Where
I
think
it's
it
is.
I
still
still
think
it's
useful
to
try
and
say
to
you
know
the
contacts
we
do
have
were
active
in
the
project
and
say
hey
this
is
this?
Is
our
view
you
know?
C
B
A
Right,
like
I
think
the
ask
would
almost
be
like:
can
we
become?
Can
some
of
the
people
from
this
team
or
the
project
become
maintainers
right
like
it's?
It's
not
it's
not
really
that
hey
just
take
this.
One
thing
is
that
it's
a
you
know
is:
this
is:
is
that
one
going
to
be
like
a
a
github
controlled
project,
or
is
it
going
to
be
one
where
maintainers
you
know
there
can
be
broader
maintainership,
in
which
case
it
could
be
suitable?
If
not,
then
the
pkgs
is
where
we
can.
A
You
know
basically
have
broader
collaborators
participate.
C
Is
it
to
want
to
make
an
issue
for
that,
or
because
I
mean
it
seems
like
that's
the
the
subtext
which
may
or
may
not
be
captured
in
the
current
issue.
But
you
know
I
don't
know
how
those
things
get
worse.
A
C
Well,
I
guess
it
was
more
from
the
you
know.
That's
probably
something
I
I
can't
do,
but
I
didn't
know
if
there
was
someone
here
we
knew
someone
on
the
team
that
we
could
follow
up
with
and
say:
hey
we
had.
This
idea
check
the
meeting
notes.
We
had
this
idea,
you
get
a
a
feel
of
it
for
us
from
them,
I'm
not
sure
who
that
would
be.
Maybe
if
that's
one
thing
we
can
figure
out
is
like
who
could
arbitrate
that
discussion
or
initiate
that
discussion?
A
Yeah
that
I
mean
it's
for
you
know
I
could
I'd
be
happy
to
send
emails,
but
it
would
be
tierney
and
and
and
miles
that
I
would
reach
out
to
okay.
I
think
if
they
are
like
you
know
it's,
because
it's
finding
somebody
who's
interested
as
well,
and
I
think
they
could
at
least
pass
it
on
and
if
then
there's
no
interest.
It's
like
yeah,
okay,
we're
not
going
to
get
any.
A
C
Yeah,
I
guess
it
was.
It
also
seemed
like
it
was
part
of
the
optics
like
do
we
send
an
email,
wait,
a
couple
weeks
and
then
see
like
hey,
we'll
give
it
a
couple
weeks
and
then
we'll
start
prototyping
on
our
own.
You
know
or
something
like
that
or
just
go
both
at
the
same
time.
If
the
optics
was
a
factor.
A
C
Yeah,
because
I
mean
it
makes
sense
to
just
you
know,
for
whatever
we'd
like
to
try
out
yeah,
certainly
keep
that
going,
but
you
know
people
get
busy
and
it
might
take
a
while.
So
it'd
be
good
to
be,
you
know,
as
you
say,
you
know,
be
able
to
run
parallel
or,
as
beth
says,
be
able
to
run
parallel,
probably
just
overthinking.
It
so
never
mind.
D
D
B
What
the
plan
would
be
if
there's
anything
yeah,
I'm
not
sure
if
I
would
have
time
to
start
the
script
itself,
the
the
the
fork
itself
this
month.
So
I
guess
we
can
talk
before
we
start
unless
somebody
else
is
very
anxious
to
do.
A
A
A
A
If
not
thanks
to
everybody
for
taking
the
time
to
come
and
those
who
are
watching
and
we'll
see
you
all
next
next
time,
all
right
and
hold
on,
don't
everybody
leave,
though,
I'm
just
going
to
stop
the
stream.