►
From YouTube: 2020-12-01-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
december
1st
2020
we'll
follow
the
agenda
that
we
have
in
the
issue
that
was
generated
in
the
repo
which
is
issue
number
434.
A
B
I
did
I'm
just
pulling
it
up
for
myself,
but
just
in
a
short
so
after
the
the
last
meeting,
I
believe
it
was
christopher
had
had
chimed
in
looking
for
some
opportunities
to
help,
and
I
think
in
general,
the
or
rather
the
general
takeaway
was
maybe
it's
a
little
bit
harder
for
newcomers
to
maybe
understand
what
we're
up
to
at
any
given
point
in
time.
You
know
if
there's
any
cross-cutting
themes
that
we
may
be
working
on.
B
You
know
just
basically
try
and
get
a
snapshot
bird's-eye
view
of
our
team
and
working
group
at
least
that's
what
I
inferred
so
just
to
kind
of
get
the
ball
rolling
on
that
a
little
bit.
I
just
did
a
couple
things.
I
made
a
project
in
github
just
to
span
next
year,
it's
kind
of
like
a
general
bucket.
B
I
don't
think
we
move
fast
enough
that
we
need
to
get
like
you
know
granular,
but
it
might
be
the
equivalent
of
like
a
a
sprint
in
like
an
agile
approach,
but
you
know
that
time
is
relative,
that
nobody
has
taught
us
anything.
So
I
figured
for
now.
It's
just
like
it's
just
a
project
called
general
activities,
2021
and
it's
mostly
just
anything
that
we're
working
on
as
an
issue.
B
You
can
just
kind
of
go
in
there
and
it's
just
got
your
typical
left
to
right
swim
lanes
like
to
do
I
made
one
column,
that's
just
to
do
slash
gfi,
good,
first
issue,
so
you
know
over
time.
Sometimes
those
priorities
come
and
go.
So
you
know
always
chalk
or
remove
things
and
pretty
much
anything.
That's
been
on
our
agenda
or
anything,
that's
like
active,
which
pretty
much
maps
to
the
milestones
I
just
put
into
that
now
in
a
month
they
may
all
be
gone,
but
I
figured
it'd
be
easier
to
just.
C
B
Buddy
21,
and
so
then
the
last
thing
I
did
was
I
made
three
milestones
just
to
capture,
at
least
for
my
purview
and
attendance
of
kind
of
what
our
three
big
themes
are
right
now,
as
a
team
in
which
there's
like
multiple
issues
about
it,
and
one
was
the
support
levels
that
you've
been
networked,
one
pretty
much
or
leading,
I
should
say,
spearheading
the
draft
documentation,
promotion,
which
is
just
getting
things
out
of
the
drafts
into
just
you
know,
higher
visibility
and
then
the
pkgs
or
kind
of
bootstrapping.
B
B
Like
that,
but
at
least
now
with
a
link
or
two-
you
can
just
be
like
milestones.
These
are
our
current
initiatives.
The
pr
project
board,
here's
what
anybody's
working
on
at
any
given
time,
and
if
you
want
to
jump
in
here's
a
list
of
to
do
or
good
first
issues
I
mean
you
could
use
the
label
too,
but
you
know
sometimes
those
get
old,
as
I
was
going
through
the
issues
I'm
like
yeah.
Some
of
these
could
maybe
be
closed
as
duplicates
or
it's
been
superseded
by
similar
requests
earlier.
B
So
there
could
be
a
maybe
as
part
of
2021,
maybe
a
grooming
of
just
you
know
the
backlog
of
issues
so
to
speak.
Anyways
that'd
be
a
good
idea.
A
I
guess
I
could
see
a
couple
more
of
those
milestones
like
I
don't
know,
whibby
something
around.
That
makes
sense
absolutely,
and
then
I
think
you,
you
know
you've
been
spearheading
work
around
the
it
was
for
travis
for
the
the
files
for
testing.
I
know
that's
pretty
much
done,
but
now
I
think
you
were
starting
to
look
at
github
actions
right
because
that's
becoming
more
the
the
go-to
yeah,
the
action
stuff.
C
I
think
there's
no
easy
and
there's
no
easy
and
obvious
way
to
do
it
and
github
is
working
on
a
feature
to
enable
some
of
these
behaviors,
but
that
feature
is
q2,
so
I
don't
know,
but
as
part
of
webby
work,
I'm
currently
working
on
webby
specific
github
action
which
allows
you
to
like
post
a
web
test
comment.
It
kicks
off
with
the
work
workloads
and
all
that
and
once
that
is
in.
C
A
B
On
that
one
yeah,
I
think
that's
to
be
what
I
was
seeing
is
the
value
because
you
know,
obviously
anybody
could
apply
their
own
kind
of
value
or
use
out
of
the
various
tools,
so
yep
yeah,
we
were
obviously
could
do
whatever
we
want,
but.
D
B
The
milestones
was
more
just
as
a
way
to,
and
I
think
maybe
is
a
great
example.
I
didn't
want
to
go
overboard
right
off
the
bat
hoping
to
use
this
but
yeah.
I
think
something
like
that.
I
think
so.
Milestone
is
really
good
to
maybe
for
at
least
this
group
to
think
about
it
is
you
know
something
that
a
task?
That's
probably
going
to
involve
not
only
multiple
issues
but
potentially
multiple
people
right,
and
so
you
know
it's
something
that
I
think
most
of
this
is
just
like.
B
Is
there
a
good
way
that
we
can
just
kind
of
you
know
either
see
progression
or
get
a
punch
list?
Real
quick
of
you
know
big
things
so
yeah
I
certainly
saw
a
few
webby
related
ones,
and
so
I
think
that
might
be
helpful
and
also
because
a
lot
of
times
when
we're
talking
about
one
of
these
things
we're
often
looking
for
multiple
related
issues
or
trying
to
find
like.
B
B
B
I
guess
the
main
I
guess
the
main
litmus
test
for
for
this
is.
Does
this?
Does
this
approach,
or
at
least
trying
these
things
feel
reasonable
without
maybe
being
heavy-handed
in
process
you
know,
is
it
the
right
touch?
If
I
think
if
it's
the
right
touch
to
at
least
get
us
started,
and
you
know
everyone
feels
comfortable
and
that
you
know
we're
not
about
to
you,
know,
start
writing,
estimates
and
stuff
and
then
yeah,
but
I
think
yeah,
it's
it's.
A
C
B
So
I
think
from
the
project
perspective
it
can
span
repositories
and
organizations.
So
if
there's,
if
there's
something
that
we
want
to
track
across
repos,
we
could
still
use
projects
for
it
and.
A
B
So
there
you
go,
but
you
can,
but
you
can
basically,
I
believe,
let
me
just
pull
one
up
here
yeah.
So
if
I
I
can
share
my
screen,
real
quick.
B
Can
oh
hold
on,
I
got
to
enable.
B
I
upgraded
mac,
so
I
have
to
restart
zoom
to
give
it
permissions
to
share
my
screen.
So,
okay,
if
anybody
wants
to
share,
but
basically
the
short
answer
is,
if
you
go
to
any
issue
and
you
look
in
the
right
column
for
the
the
project
settings
when
you
click
that
gear,
you
can
see
that
it's
got
three
tabs,
but
the
far
two
are
the.
I
guess
the
important
ones
is:
it's
a
quick
filter
by
repository
and
a
quick
filter
by
organization.
B
So
I
know
in
some
projects
in
some
organizations
you
might
see
maybe
a
repo
that's
dedicated,
just
like
top
level
initiatives
like
almost
like
an
rfc's
repo
and
then
then
you
know:
if
it's
like
an
ecosystem
of
products,
then
they
might
have
like
a
repo
per
like
a
front-end
tool,
a
back-end
tool
like
some
messaging
tool.
Right
and
so
in
theory.
You
could
have
one
repo,
be
the
umbrella
and
use
its
project
to
sum
issues
from
multiple
repo.
So
if
you
want.
D
B
Umbrella,
you
can
but
yeah
let.
A
B
Can
you
just
type
general,
maybe
see
if
that'll
help
the
so
it
could
be
an
issue
of
permissions?
Maybe
I'm
not
right.
Okay,
that's
where
you
clicked
is.
Maybe
click
repository,
I'm
not
sure.
If
there's
any
projects,
yeah
there's
no.
B
Yeah,
because
I
mean
I've
certainly
done
that
in
my
open
source
project,
where
I've
had
this
kind
of
like
rfcs,
repo
and
okay,
I've
been
able
to
create
a
project.
That's
like
I
want
to
do
this
stay
across
five
repos
right
in
one
place,
so
I
can
look
into
that
to
see
if
it's
just
like
a
settings
or
something
like
that,
or
maybe
if
it's
at
an
org
level
setting
or
a
repo
level
setting,
but
I
can
check
that
out.
But
yes,
we
could
enable
that
if
we
want.
A
B
A
A
A
A
Yeah,
okay,
next
issue-
that
is
tagged
for
the
agenda,
then,
is
dependency
management
wording
improvements.
It's
number
425.
A
C
Yeah,
I
think
it
was
just
from
the
last
time
around,
but
basically
this
is
the
follow-on
from
the
other
one
from
the
302..
I
removed
the
agenda
from
both
of
those.
I
think
we
have
an
agreement
and
I
have
the
necessary
approvals
for
the
other
one.
Okay,
once
I
just
need
to
wait
one
more
day
for
the
timing,
stuff
and
once
that's
merged.
I
will
retarget
four
two
five
and
maybe
mark
that
ready
for
you,
yeah
no
need
to
go
in
depth.
C
C
C
Jordan
has
a
thing
that
does
a
similar
thing
in
a
very
similar
approach,
so
maybe
people
want
to
use
that
it
works.
I
guess
it's
nice
and
then
for
the
rest
of
it
all
yeah
we'll
have
to
revisit
that
later
I
mean
this
is
on
github's
site
to
make
to
make
these
things
manageable,
because
yeah,
I'm
I'm
sure
I'll
get
a
chance
to
start
looking
into
it
before
they
do
it
because,
like
if
you're
managing
hundreds
of
repos
doesn't
scale.
D
A
Okay,
suggested
list
of
modules
to
get
help,
support
info
I've,
actually
pr
the
support
info
into
node
add-on
api.
So
that's
should
land
this
week.
I
think
we're
also
working
at
red
hat,
to
add
it
to
a
number
of
our
modules
as
a
starting
starting
point
to
sort
of
check
it
out,
and
so,
if
anybody
else
has
some
other
modules
that
they
think
we
should
start
peering
peering
in
that's
the
issue
to
kind
of
track.
A
A
C
A
A
C
C
C
A
A
That
one,
I
think
we
were
kind
of
waiting
for
yeah
some
stuff
from
wes
right
to
push
it.
I
don't
know
if
that's.
A
A
A
I
just
know
that
both
wes
and
darcy
have
been
really
very,
very
busy
lately,
so
just
still
waiting
on
that,
I
don't
think,
there's
anything
unless
there's
anything
else
to
talk
about
on
that
one
we
can
move
on.
C
A
And
then
next
steps
on
the
support
levels
and
packs
jason.
I
guess
we
talked
a
little
bit
about
that.
I
am
going
to
publish
a
new
version
of
support
today
because
I
found
a
couple
issues
when
I
was
generating
the
support
info,
and
I
guess
that
I
did
have
a.
I
think
I
had
a
pr
open
that.
Let
me
just.
A
Let
me
just
make
sure
I
think
so,
though
yeah
okay
never
mind
so
that
one
yeah
I'm
going
to
publish
new
release.
Otherwise
it's
just
about
encouraging
people
to
start
adding
it
into
the
into
modules
so
that
we
can
get
some
modules
with
some
data
to
start
feeding
the
process.
A
If
not,
I
guess
we'll
call
it
for
this
week
and
we'll
talk
to
everybody
next
time.