►
From YouTube: Package Maintenance Team meeting - March 11 2019
Description
A
A
B
A
Yeah
make
sense
my
general
thought
too
was
that
it'd
be
good.
If
we
could
get
more
sort
of
concrete
advice,
you
know,
it
seems
to
say
a
fair
amount
about.
You
know
that
you
should
have
tasks
but
I
think
if
we
can
come
up
with
some
guidance
or
some
suggestions
that
will
make
people's
lives
like
make
it
easier
for
package
maintainer
is
to
add
tests.
That
would
be
good,
as
well
as
any
sort
of
standard
things
that
could
make
reusing
those
tests.
A
So,
for
example,
if
if,
if
external
people
can,
if,
if
it's
set
up
in
a
certain
way,
it
may
mean
that
we
can
run
them
more
easily
in
insid
Djem,
for
example,
or
in
other
situations
where
people
want
to
run
a
packages
test
having
some
consistencies
might
help.
So
getting
some
suggestions
along.
That
would
be
another
thing
to
continue
to
work
on.
A
D
D
D
And
you
know
two
modules
do
anywhere
from
two
hundred
three
hundred
megabyte.
So
I
we've
been
a
kind
of
doing
a
lot
of
looking
right
into
node
module
to
see
what
kind
of
files
we
can
trim
down
and
we've
been
seeing
like
files
like
tests
and
a
whole
bunch
of
other
files
like
even
coverage
files
and
operating
system.
Father
yes
store,
and
so
that's
why
I
opened
this
ticket
the
bomb.
D
Of
course
they
are
like
opinions
on
both
side
of
fence,
where
some
believe
believe
that
you
should
publish
your
test
and
your
documentation
and
some
who
believe
that,
oh
and
then
also
if
you
used
fight
another
JavaScript
dialogue
like
typescript
or
you
use
JSX,
then
you
you
know
there
are
two
two
camps.
One
is
they
believe
that
you
should
publish
everything,
documentation,
all
the
original
source
code
and
and
test
and
the
other
camps
right.
You
don't
and
I
think.
A
D
D
Yeah
so
last
time
after
meeting,
you
know
you
mentioned
about
the
contacts
and
thank
you
very
much.
That
was
very
helpful
like
that,
because
I
was
also
kind
of
not
sure
where,
where
I
was
going
with
the
doc-
and
you
know
I'm
asking
that
question.
What's
the
context
really
really
make
a
lot
of
clarification
and
I
was
able
to
update
the
documentation
to
make
much
much
more
sense
and
so
I've
actually
added
to
section
created
two
sections.
D
Well,
that's
kind
of
still.
Maybe
these
are
little
bit
more.
Discussion
is
I,
have
an
item
in
in
there
for
the
night,
the
action
that
a
user
or
package
owner
can
take
if
they
identify
and
maintain
packages
that
I
told
them
that
they
can
reach
out
to
the
package
maintenance
cool
to
a
file
issue
for
us
that
may
be
it
take,
take
some
actions
and
what
I
have
in
mind
with
that
is.
You
know,
I
think
the
the
best
we
can
do
is
actually
just
go.
D
Ask
NPM
for
ownership
the
package,
so
then
we
can
keep
it
and
in
case
someone
comes
out
around
say:
hey
I
I
can
take
over
that
and
we
can
transfer
ownership
to.
Whoever
is
interested.
That's
that's
as
much
as
I
think
this
group
can
do
and
maybe
for
some
more
popular
package
that
we
get
do
a
little
more,
but
that
that
is
what
it
stands
for
now.
Right.
A
I
guess
we
could
potentially
keep
a
prioritized
list
of
modules
that
need
unmaintained
modules
that
need
help
right,
yeah
but
yeah,
so
that
that
that
seems
like
a
good
baseline.
It's
like,
if
you
let
us
know
it's
like
okay,
and
if
it's
really
popular
one
we
may
you
know,
try
and
think
about
harder.
If
it's
one,
that's
better,
you
know
hardly
used.
We
can
just
put
it
lower
down
on
the
list,
but
I
mean.
A
Right
and
I
guess
is
it
the
I
mean
we
could.
We
could
put
it
on
a
list
without
taking
ownership,
but
what
they
know
taking
ownership
is
another
step
that
I
guess
prevents
it
from
getting
into
the
wrong
hands
or
something
like
that.
I
think
yeah,
let's
you
know,
sounds
good.
We
should
we
can
continue
to
discuss
in
in
github
and
we'll
come
to
something.
A
F
So
yes
yeah,
we
as
Joe
has
just
said.
Actually
we
would
probably
be
best
served
by
starting
relationship
with
somebody
in
the
NPM
registry
who
we
could
actually
engage
with,
and
you
know
I've
already
engaged
with
somebody
this
week
and
I
have
no
idea
if
I
get
a
response,
because
there's
a
very
high
level
and
I
was
out
met
them.
But
we
may
may
want
to
do
this
because
you
know
we're
helping
it's
a
symbiotic
relationship.
F
F
A
A
Got
it
maybe
maybe
would
it
make
sense
to
open
an
issue
in
our
repo
saying
you
know,
find
a
contact
in
NPM.
You
could
just
comment
that
you've
reached
out
to
one
person
if
that
goes
well
great,
if
not
I
can
try
and
think
of
who
I
could
ping
as
well,
and
just
that
way
we
won't
forget
about
you
know
and
actually
tag
that
with
the
agenda,
because
that's
probably
something
we
should
make
sure
we
remind
ourselves
to
do
yeah.
D
A
Okay,
so
yeah
so
Joel,
that's
a
good
update
on
where
it's
at
I
guess
everybody.
If
we
can
go
in
there
and
comment
I
haven't
I
was
out
a
bit
last
end
of
Locke's
last
week,
so
I'm
not
up
to
date,
but
I'll
make
sure
I
do
that
this
week
and
if
everybody
else
can
any
other
things
you
want
to
sort
of
point
out
or
get
people's
opinions
on
today.
D
G
I
had
a
question
there
on
the
issue
and
maybe
it
needs
a
broader
discussion
and
I
was
just
wondering
whether
reaching
out
to
this
group
is
the
correct
step.
I
mean
sure
if
there's
a
sort
of
big
package
where
a
lot
of
people
depend
on
it's,
then
and
possibly
yes,
it
has
an
impact
on
a
big
community,
but
then
there's
the
very
long
tail
of
very
small
packages
and
then
there's
the
case
that
there's.
G
Npm
may
or
may
not
be
willing
to
do
that.
There's
been
some
interesting
happenings
there
right
in
the
past,
where
they
were
contacting
people
that
they
are
going
to
lose
the
package
and
then
there's
the
name
squatting
problem,
but
whether
reaching
out
to
this
group
is
that
the
correct
first
step
right,
because
if,
if
somebody
is
a
user
of
that
package,
should
we
not
encourage
them
to
take
ownership
of
of
maintaining
that
package
if
they
depend
on
it,
which
is
a
general
principle
right
if
you're,
depending
on
open
source
and
you're,
not
happy
with
it?
D
Those
are
quick
points,
I
list
a
list,
some
of
those
are
actually
on
the
kind.
Sorry,
are
we
talking
about
talking
about
that
yeah
I
list?
Some
of
those
are
those
things
you
mentioned
in
the
guidelines
like
hey
you,
you
have
a
package
that
you
use
and
you
found
some
issue
all
want.
Some
recoil
enhance
enhancements.
You
know,
here's,
here's!
A
G
G
A
G
A
G
A
The
thing
that
did
come
to
mind
is
we
may
want
to
put
a
threshold
like
you
know
if
it
gets
more
than
X
downloads
like
because
if
it
gets
one
one
download
a
week
or
something
or
whatever
its
you
want
to,
we
do
want
to
avoid
being
swamped
with
notifications
right.
So
thinking
about
what
kind
of
threshold
might
make
sense
would
be
good
to,
but
I'll
look
at.
It
didn't
suggest
that
in
the
in
the
issue
too,
okay.
H
I
A
Okay,
so
we
should
yeah,
we
should
come
up
with,
and
actually
this
may
be
more
of
a
general
thing
that
we
should
kind
of
come
up
with
our
when
you
look
at
a
module.
When
is
it
one
that
we
think
we
can
reasonably
get
involved
win
because
it's
it's
important
used
enough,
whatever
that
same
set
of
criteria
is
probably
going
to
be
needed
in
a
whole
bunch
of
places
right.
D
A
So
it
sounds
like
our
next
step
is
to
talk
to
the
maintainer
zuv
the
pilot
packages
and
try
and
get
their
top
issues
Matteo
just
chimed
in
saying
he
won't
be
able
to
do
that
for
a
few
weeks,
though
so
that
was
two
weeks
ago.
So
hopefully
that
means
that
now
he's
back
I
know
he
was
at
like
the
diagnostic
summit
with
where
I
was
last
week
and
he
had
other
things
going
on.
So
maybe
we'll
just
leave
that
and
come
back
to
it
next
time.
A
J
I
know
when
you
take
a
look
at
open
source
tools:
there'll
be
the
tab
that
shows
you
how
compliant
they
are
with
best
practices
and
so
I
put
in
a
ticket
to
recommend
that
billion
tool
to
validate
the
recommendations
that
we're
making.
So
we
have
a
submission
the
ticket
has
been
addressed
so
I
just
wanted
to
open
it
up
to
feedback
on
the
issue
to
make
any
suggestions
for
2010,
like
that
before
we
close
the
discussion
on
the
validator,
we
are
waiting
for
the
last
time
we
looked
at
it.
J
The
ticket
for
the
support
section
still
has
a
few
comments
that
needed
to
be
addressed.
I
haven't
looked
at
it
today,
but
I
might
wait
to
close
the
ticket
for
building
the
validator
until
we
wrap
up
the
discussion.
So
in
the
meantime,
if
we
could
get
any
reviews
on
the
code
that
was
written,
excellent
job,
so
yeah
just
want
to
make
sure
that
a
bachelor
week
more
while
were
still
in
the
process
of
defining
the
standards.
A
Okay,
so
for
support,
support
levels,
lands
right,
yeah,
no,
that's
good
said:
yeah,
you're
right,
there's
still
a
few
comments.
I
have
to
get
back
to
on
the
support
levels.
I'd
addressed
a
few
last
week,
there's
a
few
new
ones
and
yeah
I'd
agree
that
we
should
probably
because
the
validator
may
change
until
that.
That
goes
so.
We
should
wait
until
that.
A
I
guess.
You
know,
since
we're
talking
about
that
one
as
everybody
on
the
call
at
least
comfortable
with
the
content.
That's
there
have
concerns
issues
that
we
should
discuss.
I'm
hoping
we
can
get.
You
know
the
remaining
comments
addressed
and
then
get
that
landed,
and
my
plan
would
be
then
at
the
next
meeting
to
kind
of
discuss
how
we
should
start
to
evangelize
it.
If
we're
ready
to
do
that,
but
I
guess
maybe
now
my
call
is
like.
J
A
And
I
think
this
just
came
out
of
you
know.
The
one
of
the
initial
comments
was
like
hey.
If
we're
suggesting
this,
we
should
provide
a
tool,
a
tool
to
validate,
which
makes
a
lot
of
sense
to
me
and
I
could
see
the
same
thing
happening
if
we
come
up
with
other
guidance
and
something
which
helps
validate
that
or
is.
J
There
I'm
not
sure
what
tool
is
used.
I
forget
what
the
name
of
the
pages,
but
it
shows
when,
when
an
open
source
module
aligns
with
like
the
Community
Guidelines,
is
there
like
a
way
to
add
in
our
validators
to
to
do
this
same
kind
of
thing?
Let
me
pull
one
up.
Is
that
mean
keeper
or
something
I'll,
pull
up
an
example
of
what
I'm
talking
about?
Okay.
A
Cuz
yeah
I
guess
on
that
one.
You
know
what
I
kind
of
think
is.
Once
we
get
it
landed
as
a
draft,
then
we
probably
want
to
do
a
push
to
get
more
input.
Like
you
know,
basically
say:
we've
got
this
draft
and
try
and
make
a
you
know
broadcast
to
all
package
owners.
Saying
hey
is
this
something
you
think
you
could
follow
and
in
parallel,
without
we
can
think
of
other
things
like
you
know
if
this
is
a
tool
that
might
help
encourage
people
to
do
that,
I
see
so
this
is
community
Pro.
A
A
I
Think
yeah
I
don't
know
we
can
talk
to
them,
but
this
is
more
generic.
What
they've
done
I
think
to
the
context
of
github,
like
maybe
part
of
the
outcome
of
this,
is
creating
a
starter
kit
or
a
template
of
sorts
for
people.
Grading
packages
that
pre
includes
these
things
that
were
talking
about
right.
A
One
of
the
things
we
talked
about
was
talking
to
NPM
so
that
when
you
did
an
NPM
in
it
it
would
pre
populate
it
with
the
feel.
Maybe
the
lowest
or
the
you
get.
No
support
right
is
your
first
starting
point
and
then
it's
something
that
you'd
see
in
change.
Right,
I,
think
that
does
fit
back
to
the
earlier
comment
that
building
you
know,
contact
with
NPM
would
be
a
good
idea
because
we
could
start
bouncing
some
of
those
ideas
off
as
well.
D
A
I
D
D
And
do
we
want
to
offer
any
kind
of
standard
guideline
on
how
how
their
package
owner
can
advertise
that
in
in
addition
to
what,
in
the
tobacco
start
Jason,
you
know,
typically,
maybe
in
just
rimi
I-
know
that
most
leakage
most
package
asks
for
that
it
uses
a
list
like.
Please
support
me
on
patreon
and
then
put
a
lei
in
there,
but
I
don't
see
the
common
way
of
everybody.
Do
it
slightly
differently.
D
A
D
D
D
A
K
K
It's
too
much
time
for
me
and
they
are
just
like
leaving
and
going
and
and
that's
it
I'm
trying
to
like
express
it,
explain
it
in
my
local
society,
my
local
community
and
it's
hard
for
him
to
understand
where
we
are
going,
and
they
just
see
that
key
packages
and
key
to
tend
Express
and
are
they
thinking?
Okay,
there
are
a
lot
of
other
people.
They
will
just
like
everything
good
and
that's
it.
It's
the
so
I
was
I
wish
to
ask
if
we
can
explain
and
short
short
sentence
few
like
thesis,
because
it's.
A
K
H
Ivy
I
can
start
up.
We
can
start
up
a
project
in
there.
A
lot
of
the
base
practice
stuff
that
we
have
right
now
can
be
exactly
started
up
as
a
project
underneath
the
the
the
repo
and
then
I
can
assign
I
put
all
the
issues
that
are
part
of
it
in
there.
That
should
keep
it
a
little
bit
more
organized
yeah.
A
That
sounds
good,
cuz
I
mean
we
can
and
we
might
even
create
some
four
things
we'd
like
to
get
to,
but
don't
have
any
work
going
on
at
this
point,
like
you
know,
we
could
have
one
for
like
build,
prioritized
list
of
modules
that
need
help
or
something
yeah,
absolutely,
even
if
we're
not
actually
doing
that
work.
Yet
it
would
show
you
know.
Maybe
the
the
road
map
a
little
bit
a
little
bit
more.
K
K
H
Good
question
not
sure
how
much
agile
type
methodology
we
can
really
use
on
this
since
we're
more
of
a
volunteer.
Not
just
we
don't.
We
don't
run
in
agile,
sprints
or
anything
like
that.
So
this
this
would
be
a
ball
and
take
a
volunteer-based
thing.
I
dunno
we
can
set
up
at
least
triggers
for
particular
like
if
we
have
an
issue,
that's
in
progress
and
we
have
some
triggers
where
it
has
two
or
more
approvals
or
on
it.
H
There's
requests
like
it
can
auto
move
the
stories
or
stories
the
issues
to
the
particular
Kanban
path
or
whatever
I
forget
the
name,
agile
name
for
it,
but
on
that
we
can
set
those
particular
triggers
up
in
side
of
the
project,
but
as
far
as
like,
if
we're
gonna
thinking
in
an
agile
sense,
it
would
be
trickier
since
we
don't
do
sprints
or
we
do
meet
every
two
weeks,
but
we're
not
it
effectively.
Holding
people
like
you
didn't
get
this
done.
H
A
My
suggestion
is,
is
that
you
build
out
a
project
board
and
then
we
look
at
it.
Next
meeting
and
I
I'd
say
create,
create
an
issue
which
is,
like
you
know,
build
out
our
our
project
board
slash
planning
methodology.
If
you
can
take
a
first
cut,
we
can
then
all
look
at
it
together
in
the
next
meeting
and
sort
of
say,
okay,
what
would
be
useful
in
terms
of
columns
and
you
I
agree.
H
100%-
and
this
could
be-
is
like
a
like-
a
very
templated
one,
to
see
what
we
want,
because
I
am
looking
at
right
now
and
there
are
several
different
templates.
They
offer
like
basic
needed
automated
with
review
stuff
like
that,
so
yeah
I'm,
gonna
kind
of
toy
around
with
a
few
of
them
and
see
what
they
have
and
then
kind
of
get
one
ready
for
the
next
meeting
and
then
see
you
know,
watch
what
works
out
well
for
for
our
use
case.
That.
H
A
A
I
Don't
know
if
they're
initiating,
particularly
about
that
we
just
talked
about
how
do
we
generally
talk
about
companies,
sacha
enterprise,
engagement,
yeah,
but
there's
there's
a
lot
of
topics
within
that
we
can
talk
to
Sara,
I.
Think
back
to
the
point
I
was
just
made
in
terms
of
world.
We
all
got
jobs
in
the
world
with
unions,
so
on
maybe
there's
an
angle
to
that
in
terms
of
guidelines.
A
I
think
that,
like
the
you
know,
you'd
mentioned
a
few
times
to
me,
the.
How
do
you
build
the
case
to
say
we're
using
these
modules
they're
important
to
our
business
I'm,
just
thinking
to
be
great
to
have
something
that
that's
on
our
agenda
so
that
we
we
start
to
think
about
that
one
talk
about
it
and
figure
out.
What's
the
next
step
in
getting
making
some
progress
on
that,
because
that
seems
pretty
key
for
me.
Oh.
I
A
M
So
I
feel
like
this
a
huge
gap
between
the
knowledge
of
someone
who's
starting
up
right
now,
and
someone
who's
already
been
working
on
open
source,
so
I
mean
because
there
are
a
lot
of
members
right
now,
especially
when
I
joined
them
as
well.
So
is
there
anything
that
can
be
done
to
bridge
this
gap
between
the
two,
so
everyone
can
participate
as
well.
I.
J
Other
ways
but
I
had
a
lot
of
questions
when
I
started
and
I
reached
out
to
the
group,
and
people
gave
me
not
only
encouragement
but
also
suggestions
and
suggestions
on
how
to
contribute
in
suggestions
on
what
the
boundaries
are.
That
are
like.
If
you
feel
strongly
that
there
is
an
idea
that
you
have.
J
Up
an
issue
begin
the
conversation
between
meetings
and
add
it
to
the
agenda
for
the
next
meeting.
If
it
becomes
a
topic
of
conversation
that
people
agree,
you
know
we
should
move
forward,
but
basically
I
guess
from
my
limited
experience
in
open
source
and
being
the
person
that
you're
talking
about
the
person
who's
new
to
open
source
and
is
looking
to
maximize
my
contributions
just
reach
out
to
the
group.
J
If
there's
one
way
to
communicate
that
you
know,
if
adding
a
bulleted
list
of
like
one
of
those
encouragement
posters,
you
know
to
all
eaten,
but
if
you
feel
it
it
would
open
up
a
pull
request.
Let's
talk
about
your
encouragement
poster
for
our
readme
or
your
bulleted
list
of
things
to
keep
in
mind
as
a
contributor
and,
let's
let's
discuss
it
and
let's
build
it
into
something
so.
H
Contributions
can
manifest
in
many
ways
with
just
opening
an
issue,
as
you
mentioned,
create
adding
on
to
the
conversation
or
even
if
you
do,
someone
has
open
a
PR
reviewing
that
PR,
adding
your
comments
and
feedback
that
that
in
turn,
is
still
contributing
because
you
are
contributing
to
you
know
the
overall
success
of
that
that
code
base
for
that
module.
So
I
guess
what
we
are
trying
to
look
and
I,
say
and
I
think
this
might
be.
A
J
I
don't
know
if
this
is
the
project
that
you
were
talking
about
Rick,
but
the
all
contributors,
CLI
kind
of
sounds
like
what
you're
talking
about
where
it
recognizes
not
only
that
people
have
contributed,
but
also
has
like
badges
for
the
different
kinds
of
contributions.
You
know
to
make
sure
that
everybody.
J
J
H
That
you
want
how
about
that.
Thank
you
for
pointing
that
out,
because
no,
we,
this
is
actually
kind
of
manifests
itself
as
part
of
a
hack
at
our
in
our
company
on
or
a
hackathon
that
we
were
running.
So
thank
you
for
that
cuz.
We
was
basically
just
eating
up
the
github
API
directly,
with
graph
QL
grabbing
from
it
and
building
it
together.
So
no
that's
perfect.
You
I'd.
A
H
It's
not
open
source
yet,
but
it
is
something
we're
looking
at
eventually,
maybe
moving
it
to
open
source
eventually,
but
yes,
I'd
be
happy
to
once.
We
have
that
provides
in
data
or
see
what
we
can
provide
back,
but
it's
been
really
interesting.
Working
on
this.
This
project
just
says
this
sort
of
a
we
did
I
packed
it
together
in
24
hours,
but
it's
not
even
it
was
complete
or
whatever,
but
you
know,
yeah
I'd
be
happy
to
share
the
group
once
we've
got
something
going.
H
A
Sounds
good
so
so
Dula
going
back
to
your
initial
question,
you
know
I
can
now
think
of
two
things.
We
concrete
things
we
could
do.
One
is
to
get
a
PR
to
add
in
the
kind
of
things
that
Edward
went
over
that,
like
you
know,
if
you
want
to
contribute,
feel
free
to
open
an
issue
to
talk
about
something
you
know.
M
A
M
M
J
A
J
J
Errors
or
whatever
you
know
so
I
think
a
lot
of
the
issue
that
people
face
when
they're
first
getting
into
something
new
is
the
perception
that
everybody
knows
something
or
they
don't
so
I
would
say
whatever
yours,
whatever
the
new
person's
strengths
are,
they
should
try
to
see
how
they
can
apply
those
to
what
they're
working
on
and
if
they
run
into
issues,
then
ask
for
help
and
I
know
that
whether
we
have
an
official
onboarding
process
or
not
like
pair
programming
or
whatever
you
know,
people
will
be
happy
to
help
yeah.
That
makes
sense.