►
From YouTube: Node.js Package Maintenance Meeting - 19 May 2020
A
A
A
A
A
So
we
have
a
one-hour
collaborate
session
submitted,
so
I
guess:
we've
still
got
time.
We've
probably
got
like
one
or
two
meetings,
if
not
free
before
that
session,
so
I
guess
the
plan
is
to
come
up
with
an
agenda
in
advance.
So
I
don't
know
whether
we
want
to
do
that
today
or
just
call
that
out
in
the
minutes
and
ask
for
people
to
place
their
suggestions
or
what
we
should
talk
about.
I.
B
B
So
you
know
curious
if
it
was
because
everybody
was
there
if
it
was
the
topics
or
out
of
maybe
try
and
think
about
what
was
good
and
positive
about
last
year's
and
try
and
roll
that
in
or
you
know,
maybe
it's
more
of
a
snapshot
of
what
we've
seen
over
the
past
year
in
terms
of
outreach
triage.
The
things
that
we're
working
on
and
it's
like.
Is
it
a
preview
of
what
we've
been
working
on
or
is
it
you
know
more
peer-to-peer
with
package
maintainer
or
maybe
a
little
bit
of
both
it's
an
hour?
A
C
A
C
Think
it's
you
know
we
want
to
do
something
which
will
engage
additional
collaborators
either
to
get
them
engaged
in
this
process
or
to
get
feedback
on
topics
or
whatever
other
reasons,
but
that
that
was
sort
of
the
key
discussion
was.
You
know
we
have
a.
We
have
a
good
group
of
people
who
get
together
and
meet
regularly.
So
what's
just
getting
together
since
it's
going
to
be
virtual,
wouldn't
be
that
much
different,
but
it
is
an
opportunity
to
hopefully
get
new
different
people
get
feedback
on
a
topic
or
okay.
A
B
B
B
But
we
have
seen
activity
from
collaborators
to
packages
who
aren't
actually
the
maintainer,
so
between
Axios
and
no
factions
and
things
like
that.
We've
seen
a
lot
of
activity
from
people
wanting
to
help
out,
but
when
they
try
to
figure
out,
how
do
we
help
out
packages
that
aren't
actually
being
sustained
or
promoted
by
their
own
maintainers?
Because
is
there
a
limited
amount
of
help
we
can
give?
If
you
know,
aside
from
documentation,
I
guess
a
lot
of
times,
people
were
asking
for
health
for
like
hey,
the
maintainer
is
not
around
and
we
can't
release.
B
A
C
B
Almost
like
a
case
study,
where
expressed
in
share
their
experience
so
far
and
trying
to
formalized
triage
process,
maybe
tie
in
the
efforts
of
this
group
and
how
they're
able
to
okay,
we
weren't
able
to
use
this
tool
or
we
were
able
to
collaborate
on
this
tool
with
this
team
and
kind
of
self
promote
both
of
the
crap
in
the
process.
Maybe
yeah.
B
Yeah
they
could
be
helpful
or
other
packages
to
see
a
package
like
you
and
there
I
think
a
case
study
perspective
could
be
helpful,
may
be
another
package
maintainers
like
oh
yeah
I.
Do
that
those
problems?
Oh
that's
how
they
solved
some
of
those
problems.
I
didn't
know
that
those
resources
were
available.
A
C
Know
just
I've
been
spending
a
bit
of
time
working
on
it,
and
you
know
it's
not
complete,
but
I
think
it
would
be
good
to
start
getting
things
landed
just
so
that
we
can
continually.
You
know.
If
other
people
wanted
to
then
extend
it
a
little
bit.
They
can
do
it
versus
an
open
PR,
which
is
a
bit
hard
for
people
to
write.
A
C
Unfortunately,
today
that
will
mostly
be
there
isn't
any
except
for
you
know
some,
and
there
are
a
number
of
unit
tests.
I
extended
the
unit
test,
so
that
it
would
run
for
the
testing
for
the
command
line
as
well.
So
there's
a
bunch
of
test
testing.
You
know
I
think
there's
like
20
different
combinations.
There's
still
lots
to
go
on
that
front
to
but
sort
of
starting
to
build
that
out.
Okay,.
A
E
Give
a
quick
bit
background,
so
the
main
work
on
this
now
now
we
have
the
initial
tool
to
get
the
pendant
is
to
work
on
leaf
for
you,
for
the
actual
testing
of
the
pendants
to
me,
and
Beth
have
been
talking
about
this
and
best
open
to
PR
on
pkg.
Guess
we'll
be
we've
and
with
just
a
light
initial
overview,
an
initial
flow
and
definitely
needs
some
people
to
take
a
look
at
this
and
just
get
as
much
consensus
on
this
as
possible.
A
F
It
was
sorry,
I
haven't,
had
a
chance
to
go
through
in
detail
regarding
the
opening
the
peers,
I,
think
we
discussed
this
at
some
point
and
I
think
that
the
initial
version
should
be
so
baby
JSON.
The
configuration
file
should
allow
you
to
select
whether
you
want
to
open
the
pod
requests
or
whether
you
want
to
fork
and
or
rather
it
should
be
smart
enough
to
or
configurable
enough
to
know
that
a
repo,
basically
whatever
is
defined
in
will
be
JSON.
You
should
be
opening
the
pull
request
against
that.
F
As
a
if
you
own
the
repository,
then
you
probably
don't
need
to
fork
it.
However,
if
you
do
not
own
the
repository,
then
you
do
want
to
port
it,
in
which
case.
If
it
is
a,
then
you
probably
want
Wiebe
to
to
know
that
this
is
a
fork
and
that
it
should
take
the
source
repository
and
sink
master
just
so
that
you're
opening
against
the
latest
master
basically
make
sure
that
the
fork
is
updated.
F
So,
to
summarize,
maybe
should
open
up
against
the
repository
that
is
defined,
but
it
should
have
a
configuration
option
to
make
that
repository,
updated
with
the
source,
repository
and
I
think
going
forward.
It
should
be
some
sort
of
a
small
tool
which
allows
you
to
create
these
Forks
that
make
sense
yeah.
A
F
Yeah
I
think
that
is
correct.
At
the
same
time,
these
credentials,
at
least
in
travels
in
Travis
II
you
can
select,
which
ones
are
available,
which
ones
are
not
available
on
pull
requests
and
they
require
human
confirmation
and
I
think
it
is.
It
is
a
valid
concern.
I'm,
not
sure
we
have
to
solve
it
right
now,
simply
because
I
think
just
having
the
two
out
will
uncover
more
edge
cases
than
just
that
and
at
the
same
time
you
should
be
able,
if
we
these
configured
to
open
the
pull
request
against
a
specific
repository.
F
It
should
just
do
that
right
and
if
it's
a
fork,
then
yes,
you
don't
have
the
credentials.
However,
in
that
case,
there's
not
much
you're
going
to
be
able
to
do
about
that
other
than
set
up
the
fork
to
have
some
credentials
right
or
you
will
have
to
contact
the
original
maintainer
and
ask
them
whether
you
can
open
up
the
pull
request
directly
on
their
on
their
repository.
So
I
think
these
are
sort
of
things
that
do
not
necessarily
need
a
technical
solution.
Right
now,
yeah.
A
I
think
I
think
when
Andrew
and
I
were
talking.
Maybe
it's
worth
creating
some
like
fake
modules,
with
the
module
dependent
relationship
in
pkg
Jas
and
with
those
just
so.
We've
got
two
modules
in
there:
I'm,
not
sure
whether
they
should
be
completely
fake
modules
or
whether
we
should
actually
like
fork,
something
like
motor
and
it.
A
Okay,
so
I
think
I
think
Andrew
was
going
to
extend
the
dependence
tool
that
returns.
The
list
of
dependents
say
that
we
can
get
like
it
to
either
return
the
random
turn
or
the
downloaded
or
all
that
was
requested
in
the
ER
and
then
I
think.
Maybe
the
next
steps
would
be
to
define
the
structure
of
the
web'
jason
and
just
try
to
gain
some
more
reviews
and
consensus
in
this
PR.
I.
A
Think
yeah,
once
we've
got
the
structure
of
the
web'
Jason
and
the
flow
approved
at
least
would
be
MVP,
then
we
can
probably
actually
get
started
coding
and
building
and
then
review
and
iterate
on
that.
That's
probably
all
we
need
to
talk
about
I
guess
on
this
one,
but
today
we
can
have
deep
dive
sessions
on
this
for
those
interested.
If
we
think
it
would
be
useful.
C
A
C
A
B
Yeah
so
yeah,
starting
with
that
one
so
related
to
the
issue
below
it
as
part
of
working
on
a
document
to
contribute
some
governance,
some
recommendations
and
suggestions
on
governance
models.
One
of
the
early
action
items
was:
maybe
we
could
structure
able
contents
for
the
Ducks,
so
I
did
that
that's
333
and
since
then,
I've
also
been
able
to
provide
a
first
draft
of
governance
models,
documentation
so
yeah.
Those
are
mostly
just
looking
for
feedback,
and
you
know
peer
review
and
things
like
that.
B
There's
a
lot
of
Docs
that
were
in
draft
States
and
some
we're
missing
so
I
also
created
issues
which
could
maybe
be
good
labels
for
like
a
good
first
issue,
labeled,
so
yeah
just
looking
for
some
feedback.
This
one's
pretty
simple,
just
creates
a
table
of
contents,
give
some
some
motivations
for
the
the
team
in
general
and
then
just
defers.
All
the
content
to
you
know
already
created
doctor
sections
to
be
created.
B
B
A
C
B
Yeah
I,
don't
think,
there's
really
anything
in
particular,
I
mean
obviously
the
may
be
that
over
be
well,
maybe
not
the
overview,
but
the
overview,
and
certainly
the
vision
might
certainly
be
subjective.
Obviously
its
kind
of
speaking
in
the
first
person
from
the
perspective
of
the
package,
meetin's
group,
I,
guess
and
yeah
I
guess
in
general,
just
curious
as
to
thoughts
on
the
overall
structure.
B
The
general
recommendations
I
tried
not
to
rely
too
heavily
on.
Oh,
do
github
feature
X,
Y
or
Z
I
mean
I
assume
most
packages
will
be
on
github,
but
I
tried
to
emphasize
like
the
process
a
little
bit
more
like
you
know
how
to
have
code
owners
or
the
other
concept
of
code
owners,
or
both
options
are
continuous
integration
and
then
at
the
bottom,
I
left
a
section
just
for
github
that
links
to
things
like
github
issue
templates
and
all
the
github
yeah
they're
all
the
way
at
the
bottom
there.
B
High
level
so,
like
I,
said
it's
just
it's
a
first
draft,
and
so
you
know
just
curious
as
to
the
approach
structure,
outline
topics
items
you
know
overall
sections,
I
guess
mini
feedback
would
be
appreciated.
I
think
there's
a
lot
of
yeah
discussion
initially,
because
I
kind
of
did
an
initial
draft
that
spawned
the
making
the
table
of
content.
So
I
think
once
I
got
that
out
of
the
way
it
helped
refocus
this
solely
it's
a
little
more
fully
form
this
time
review.
A
B
And
I
think
it
was
also
ties
in
a
little
bit
to
the
other.
The
sect,
the
community
outreach,
triage
we've
gotten
outreach
from
a
couple
of
projects
and
looking
like
Axios
in
particular,
was
one
where
we're
a
little
torn
because
it
was
contributors
who
were
helping
to
triage
the
project,
but
no
one
had
spoken
to
or
was
a
in
contact
with
the
maintainer
at
all,
so
it
was
kind
of
like
a
realtor
in
terms
of
what
could
we
do
or
what's
our,
what
are
our
boundaries?
When
you
know
the
maintainer
is
at
the
app?
B
Isn't
the
one
actually
coming
looking
for
help
and
so
I,
don't
I
guess
in
a
way
spawn
the
motivation
to
kind
of
for
me
to
move
on
the
docks
a
little
bit
more
cos
worst
case
scenario
say:
well,
hey!
Here's
that
here's
all
our
docks
in
one
place.
You
know
these.
You
can
enable
some
of
these
with
the
permissions
that
you
have.
B
So
yeah
I
guess
I,
don't
know
if
we
so
yeah
anyway.
It's
also
just
kind
of
wanted
to
draw
attention
in
one
place
to
various
packages
package
teams
that
have
reached
out
to
us
looking
for
some
help,
since
that
is
part
of
the
goal
of
the
project.
I'm
just
wanted
to
make
sure
that
the
owner
buddy,
who
was
aware-
or
you
know,
we're
now
that
we
have
some
examples,
maybe
outside
of
express
to
help
you
know
we
could
apply
some
more
of
the
things
that
we've
learned
with
express
to
those
projects.
B
Big
similar
the
gun,
jerk
who's,
also
the
one
helping
to
Shepherd
the
triaging
effort
from
Axio,
so
I
think
we're
you
know,
maybe
starting
in
a
good
way,
maybe
getting
a
reputations
like
hey.
There
is
a
team
that
is
trying
to
work
on
this
stuff,
so
I
think
it's
similar
to
Axios.
It's
a
similar
kind
of
request
for
help.
I,
don't
know
if
they're
in
the
same
position,
ISM
like
the
maintainer
is
not
available
at
all,
but
I
didn't
know.
B
If
these
were
out
used
to
be
like
well,
hey
we
got
Docs,
maybe
take
a
look
at
those
we've
got
governance
models.
Take
a
look
at
those
yeah.
If
you
want
to
start
putting
some
of
our
work
to
out
in
the
wild
needs
to
try
if
I
had
just
like
that
or
Walker
we're
ready
yet
or
maybe
wanted
to
wait
to
the
collab.
B
That
was
one
of
the
things
I
was
curious
about
in
the
table
of
contents
issue
that
I
raised
cuz
I
made
issue
to
fill
in
some
of
the
gaps.
I
wasn't
sure
there
was
a
policy
or
review
process
by
which
something
would
get
lifted
out
of
drafts
into
like
just
the
docks
instead
of
the
drafts,
folder
and
docks,
but
I
did
label
the
ones
that
are
in
draft
versus
the
ones
that
are.
B
B
B
B
C
B
Yeah
sure
I
can
definitely
go
through
the
at
least
the
draft
ones
and
create
PRS
to
move
them
out
of
draft
state,
and-
and
you
know
maybe,
if
there's
any
additional
content
ad
I
can
try
and
do
that,
but
I
think
I'm
wondering
it
fast.
As
prerequisite
you
know
getting
the
table
of
contents
established
would
be
good
as
well.
I.
C
C
B
B
Yeah
I
think
that's
good.
Maybe
we
can
make
a
dough
when
we
meet
and
talk
about
collab
summit,
if
there's
any,
if
we
want
to
take
into
account
any
of
the
outreach
from
Axio
standard
fetch
to
see
if
that
would
influence
what
we'd
want
to
talk
about.
You
know
if
there's
a
common
theme
to
what
they're
asking
for
you
know,
maybe
not
say
at
least
worth
the
bullet
point
or
two
as
part
of
the
class
I
does
not
be
the
entire
focus,
but
a
little
acknowledgement
might
be.
You
know,
good
faith,
good
credit
make.
G
I
been
very
busy,
as
I
said:
I
am
oops,
I
will
be
doing
it,
I
will
be
out
and
making
a
submission.
I
think
this
will
be
a
part
of
it.
I
just
been
very
busy
with
the
Express
stuff
and
I
think
that's
the
learning
I'm
takin
away
for
this,
like
what
I
think
we
have
found
is
that
getting
more
triage
is
on
like
we
bring
them
in,
we
be
on
board
them,
but
it's
like
you
said
there
are
members,
but
then
there
are
active
members
and
it's
getting
those
people
to
be
active.
G
That
is
I,
think
the
sticking
point
and
I
think
the
learning
from
this
is
even
from
express,
which
is
extremely
a
widely
used.
It
is
quite
difficult
getting
people
to
come
in
and
actively
take
part
rather
than
that's
just
attend
a
meeting
once
and
that
I
think
might
be
one
of
the
larger
items
in
the
the
collaborators
conference
and
we
need
to
get
outside
of
the
bounds
of
the
actual
conference,
meaning
where
we're
talking
to
people
that
are
already
active
by
the
fact
that
they're
there
and
it's
the
people
that
are
not.
G
We
really
need
to
reach,
and
you
know
we
see
it
in
our
daily
day
jobs,
that
people
are
using
these
tools,
but
they
are
not
involved
in
any
way
whatsoever,
with
the
maintenance
or
upkeep
of
the
tools
and
that's
gonna
be
I,
think
a
part
of
it.
How
do
we
do
this?
How
do
'quite
an
ecosystem
alive
and
fresh
and
ongoing.
C
G
Is
a
framing
question
for
the
especially
for
the
collaborate
to
summit
with
me
by
default
the
people
they
already
participate
in
the
fact
that
I've
turned
up,
but
it
is
actually
quite
hard.
I
mean
the
ecosystem
is
now
enormous
and
I
have
trouble
explaining
to
people.
You
know
the
various
parts
we
see
here.
I
must
say
Axios
during
when
I
interview,
people
and
my
thing
is,
you
know
and
make
them
suggest
how
they
would
fetch
something.
Now
I
have
like
a
loaded
question.
G
For-Profit
companies
like
using
free
stuff
they're,
not
so
keen
on
doing
stuff
for
free,
so
that
that
be
part
of
the
form
to
form
that
journey
like
how
do
we
phrase
that,
but
by
default,
if
we
go
to
collaborators-
and
we
talk
the
audience
there
is,
is
you
know
his
reflection
of
us?
It's
like
reading
a
liberal
newspaper
if
early
abroad,
you're
just
going
to
get
a
mirror
of
your
own
thoughts,
and
we
need
to
find
a
way
of
breaking
out
of
that.
C
Yeah,
hopefully
we
get
a
few
more
people,
but
you're
right,
it'll
largely
be
the
same.
Similar
group
I
mean
and
from
the
beginning,
that's
kind
of
been
one
of
our
are
sort
of
the
challenges
we've
been
trying
to
figure
out
is.
How
do
we
show
businesses
that
it's
not
you
know
doing
things
for
free,
but
that
it's
in
the
best
interests?
That's
right.
G
D
C
From
the
way,
from
my
perspective,
it's
risk
management,
it's
great
to
use
things
that
are
open
source
and
that
you
get
for
free,
but
if
you
simply
use
them
you're
likely
taking
on
more
risk
than
than
you
should
and
and
so
by
contributing
back,
you
can
actually
mitigate
that
risk
and
businesses
are
good
at
mitigating
risk
if
they
understand
it.
Just
that's
and
I'm
working.
C
G
G
C
To
show
businesses
the
dependency
trees
and
you
know
whether
things
are
maintained
or
not,
that
kind
of
stuff
to
help
hopefully
raise
at
least
some
of
the
visibility,
and
yes,
so
again
that
that
might
be
like
you
know
again.
That
could
be
if
we
had
time
that
might
be
a
brainstorming
session.
Although
I
think,
as
we
discussed
last
time,
we
really
want
to
use
that
session
for
things
that
are
not
just
topics
we
could
discuss,
and
these
meetings
ourselves
sort
of
leverage
the
fact
that
we'll
probably
have
a
larger
group
versus
just
regular
attendees.
That's.
G
G
G
The
conference
itself
is
a
reflection
of
the
problems,
that's
happening
in
the
marketplace.
People
can't
go
to
work.
It's
a
remote
conference,
but
we're
now
going
to
have
to
obviously
reflect
the
fact
that
people
are
not
working
and
collaborating
as
they
were
before,
Passos
better
forests.
Perhaps
they
have
more
time
I'm
going
to
I'm
going
to
write
something
up
for
the
issue.
275
our
heart
on
that
today,
I've
just
I'll
have
to
do
less
express
stuff.
G
Spend
about
an
hour
and
a
half
just
looking
at
Express
stuff
every
day,
and
that's
what
it's
made
me
realize
that
even
simple
things
you
have
to
go
away
and
research,
and
even
then,
if
it
just
results
in
closing
an
issue,
it
is
very
time-consuming.
It's
made
me
realize
it's
quite
a
miracle
how
some
of
these
projects
have
been
continuing.
G
A
F
C
H
Guess
one
question
I've
had
recently
is
with
some
of
the
packages
one
of
the
things
like
as
someone
who's
relatively
been
uninvolved
and
is
starting
to
kind
of
ramp.
Up
involvement
in
the
package
j/s
or
like
one
of
the
challenges
I've
had
is
the
read
knees
are
like
relatively
sparse
and
I'm.
It's
kind
of
hard
for
me
to
jump
in
is
that
something
that
has
been
talked
about
it
all
or
discussed
at
all
to
any
degree.
I.
C
C
H
A
Okay,
so
there's
nothing
ready.
That's
been
opened
recently
that
we've
not
already
mentioned
in
the
meeting
so
yeah
that
we've
got
quite
a
few
things
from
the
agenda
where
we're
kind
of
needing
to
gather
some
more
reviews.
So
once
the
minutes
are
open,
if
anyone
does
have
time
to
take
a
look
and
share
their
view
on
some
of
the
open,
pr's
and
issues,
please
do,
but
if
there's
nothing
else,
I'll
probably
stop
recording
and
in
the
meeting.