►
From YouTube: Package Maintenance Team meeting 2019-03-25
Description
A
A
Hello,
everyone
and
welcome
to
today's
package
maintenance
meeting
we
Michael
Dawson
is
out
today,
so
we're
gonna
be
working
as
a
group
to
get
through
the
meeting
and
and
share
awesome
so
to
get
started.
If
everyone
could
add
themselves
everyone
in
attendance,
if
they
could
add
themselves
to
the
minutes,
talk
the
Google,
Doc
and
github
link
to
get
a
repo
I'm,
just
adding
yourself
as
present
right
now.
So.
A
A
A
B
B
Think
so
I
mean
I
can
review
it
again,
but
there's
like,
let's
see,
I,
think
it's
men.
Well,
let's
see
who's.
This
Yemen
well
and
Jordan
were
talking
a
little
bit
about
testing
guidelines
and
what
dependencies
are
but
I'm
not
really
sure
how
to
resolve
that
and
I
think
there's
some
comments
from
Michael
that
I
probably
need
to
review
as
well.
A
So
yeah
I
will
go
ahead
and
review
this
today
and,
let
you
add,
like
all
book
review
the
PR
and
also
just
go
ahead
and
like
reach
out
to
you-
and
you
know
if
there's
anything
like
I
would
do
that.
That
would
be
really
great.
Thank
you.
Yeah
no
problem
cool
any
other
thoughts
on
this
PR.
It's
PR
169.
A
A
A
C
A
Cool
in
that
case,
I
will
comment
in
this
issue
that
nobody-
nobody
was
in
the
meeting
today
that
had
context
on
bowls.
A
A
A
A
E
A
A
A
A
Anyone
have
anything
else,
they'd
like
to
add
to
this
I'm,
not
sure
if
there's
anything
actionable
specifically
right
now
for
us
to
do
outside
of
like
I
guess,
do
we
want
to
discuss
that
tool
and
is
I
can't
tell
if
this
is
actually
being
suggested
that
something
we
pull
into
the
order
if
this
is
just
something
that
exists
in
the
system?
I.
Imagine
it's
bullying
but
work,
but
I'm
not
entirely
certain.
A
C
A
A
C
A
Cool
so
I
guess
on
that
one.
You
know
everyone
here
should
probably
go:
try
to
spend
some
time
and
review
that,
if
you
have
thoughts,
are
specifically
interested
in
defecation,
mottle
defecation
and
have
time
to
I'm.
Also
gonna
add
that
same
comment
around
nobody
in
today's
meeting
was
nobody
outside
Viktor
was
around
to
discuss
this
more
specifically
give
any
additional
context,
or
you
know
to
do
on
this
specific
PR.
A
A
C
F
C
A
No
cool
I
will
add
that
same
kind
of
discussion
comments
there
and
I
believe
that's
the
disaster
of
our
agenda.
Is
there
anything
additional
that
people
would
like
to
discuss
that
wasn't
on
today's
agenda.
A
A
F
So
this
is
the
first
package
maintenance
called
I've
joined.
My
name
is
Beth
I
work
with
Michael,
IBM
and
I'm
just
here
to
kind
of
demo
some
of
the
work
we've
done
with
modules
and
how
how
we
can
kind
of
help
people
across
different
LTS
versions,
seeing
which
modules
work
across
which
versions
and
platforms.
So
this
isn't
a
sales
pitch.
F
F
Think
the
interesting
bit
is
that
we've
extended
Sitchin
and
added
kind
of
like
custom
bits
to
how
you
rents
it
Jim.
So
we
can
actually
say
push
the
results
here
or
and
we're
even
looking
at
a
module
and
saying
this
module.
Wainy
declare
support
for
node,
8
and
10.
Therefore,
don't
run
it
on
node
6
and
just
return
not
supported
on
that
version.
So
I
think
it
kind
of
relates
to
some
of
the
issues.
Packaged
maintenance
team
are
trying
to
solve
and
and
I'm
just
hoping
that
there's
something
we
can
reuse
from
this.
F
A
One
question
I
have
is,
like
I've,
been
working
a
lot
with
NPM
LS
recently,
that
sounds
weird,
but
yeah
I've
been
doing
a
lot
with
NPM
LS
and,
like
now,
I'm
I'm
curious.
If
this,
instead
of
like
defining
a
predefined
list,
if
I
can
pass
it
in,
like
my
package
Jason
and
get
this
info
box
like
is
that
is
there
a
basically
a
way
I
can
pass
in
a
list
in
terms
of
like
Jason
or
some
similar
format?
That
then
I
can
get
this
information
not.
F
At
the
moment,
so
it's
all
all
the
data's
stored
on
a
like
in
a
RESTful
API.
So
there
would
be
a
way
of
saying
give
me
all
the
results
for
this
list
of
modules.
If
we
wrote
that
at
the
API,
but
it
doesn't
exist
yet,
but
the
data
shall
be
okay.
D
F
Running
it
against
this
list
of
modules
here
and
so
56
of
them,
and
we
need
to
look
at
extending
it
and
how
how
easy
it
is
for
us
to
extend,
because
at
the
moment
I
think
we've
got.
We've
got
two
machines
per
platform
connected
to
our
Jenkins
server,
so
that's
not
too
bad,
but
we'd
have
to
look
at
how
we
can
might
exponentially
grow.
This
also
really
I
think
in
another
package
maintenance
issue.
A
Yeah,
that's
that's
something
we
did
when
I
was
at
node
source
and
it's
it's
difficult.
So
yeah
one
question
from:
let's
an
issue:
any
is
there
any
info
from
NPM
sio?
They
can
be
used
for
the
module,
so
basically
I'm,
assuming
enhanced
additional
scores
here.
F
Definitely
we
can
probably
am
tell
in
like
number
for
number
of
stars,
I
think
there's
already
some
rating
from
NPM
si
added.
We
could
bring
in
it's
just
a
matter
of
extending
the
date
space.
At
the
moment,
the
infrastructure,
I
will
admit,
is
a
bit
flaky,
it's
a
bit
of
a
proof
of
concept,
but
just
seeing
how
we
could
take
it
forward
and
make
it
more
useful
for
the
wider
patch
maintenance
team.
F
We've
got
is
we're
running.
One
of
our
custom
stitching
commands
is
to
run
NYC
and
just
pipe
and
cam
testing
to
NYC
and
that
the
issue
with
that
is,
if
the
modules
already,
if
a
modules
to
NPM
test
command,
is
already
NYC
NPM
test,
we
kind
of
pipe
NYC,
NPM
tester
NPM,
seeing
we
get,
we
get
some
weird
numbers,
so
there's
definitely
some
checking.
We
need
to
do
and
there
and
make
that
a
bit
more
stringent
does.
A
A
F
We
have
actually
up
streamed,
it
I
believe
it's
landed.
Basically,
what
we've
added
is
an
option
to
search
him
say
that
you
can
do
like
custom
test,
and
then
you
can
give
it
a
script
for
ever
for
you
like,
and
it
will
run,
but
instead
of
the
normal
NPM
Testament
gotcha,
you
can
just
pass
it
whatever
you
like.
F
A
That's
that's
interesting.
Do
you
do
you
have,
so
is
the
format
the
file
that
you're
I
assume
that
standardizing
the
goldmine?
Is
that
format
like
usable
or
is
it
I'm
looking
forward
that
I
can
find?
Is
that,
like
well-documented
as
a
way
that
like
I,
could
build
this?
You
know
format
things
I'm,
looking
for
myself,
I'm.
F
D
F
A
I
definitely
think
that
there's,
like
you
know,
comparing
it
to
the
issues
that
we've
gone
over
today.
It
does
seem
like
there's.
You
know
some
things
like
even
going
through
and
checking
to
see
if
the
tests
the
tests
meet
actually
does
look
the
testing
guidelines.
You
know
outline
or
you
know,
if
there's
a
support
section
in
the
support
section,
validator
can
actually
be
used.
You
know
in
this
way,
yeah
I
think
there's
very
likely.
Some
use
utility
there
yeah.
F
I'm
not
sure
what
this
is,
the
format
can
be
used.
Maybe
a
CLI
tool
is
a
better
arm
so
that
we
could
just
use
to
get
the
test
results
for
all
the
modules
that
you're
using
and
get
a
nice
little
response
back.
That
might
be
a
nice
way,
but
it's
still
interacting
with
the
same
API
in
the
same
data,
so
yeah.
D
D
A
C
A
C
C
C
A
A
A
Cool
with
that
I
think
we
can
end
the
meeting
thanks
everyone
for
joining
today
and
I.
Guess
we'll
see
you
in
to
me
fight.