►
From YouTube: Package Maintenance Team meeting - June 2 2020
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
A
A
B
Yeah
I
think
there's
probably
some
overlap
between.
So
there's,
probably
some
overlap
between
a
couple
of
these
topics
for
this
week.
So,
in
addition
to
note,
fetch,
there's
also
Axios
both
might
have
different
opportunities
for
support,
as
I
know,
part
of
it
is
making
sure
we
can
reach,
maintain
errs
of
the
actual
repository
or
the
package
in
some
capacity,
but
I
think
between
those
two
projects.
B
The
governance
models
that
we've
been
working
on
proof,
documentation,
lapsim.
It
I'm
wondering
if
there's
maybe
like
a
broader
umbrella
like
could
these
projects
be
additional
pilots
along
with
Express?
Do
they
should
we
just
say:
hey
check
out
our
new
table
of
contents
and
our
governance
Docs
and
come
to
collab
summit?
B
You
know,
rather
than
just
kind
of
spot,
treat
I
wonder
if
there's
a
maybe
a
write
higher
level
of
support
that
we
can
pull
them
in
that
they
can
then
kind
of
like
follow
some
breadcrumbs
at
Lee.
So
they
can
do
something.
Well,
maybe
work
on
something
higher
level
through
collapse
on
bit.
So
maybe
that
additional
context
is
a
good
way
to
look
near
fetch,
but
anyway
those
I
think
they're
intertwined.
Maybe
I'm
wrong
but
happy
to
have
the
discussion
either
way
right.
A
B
I
think
originally
started
with
Axios
outreach
where
collaborators
on
the
project
we're
trying
to
triage
and
assist,
and
they
came
open
an
issue,
and
you
know
we
replied
said
like
hey
yeah.
If
you
can
get
the
owner
involved,
then
there's
probably
a
better
chance
to
you
know,
provide
some
direct
meaningful
help,
because
at
that
time
we
established
that
you
know,
there's
probably
only
so
much
we
can
do
outside
of
Docs.
If
the
maintainer
xanax
right.
C
B
C
B
In
light
of
not
having
the
maintainer,
we
can
say
you
know,
say:
hey
go
check
out.
Our
Docs
give
us
some
feedback.
If
there
is
a
maintain
or
maybe
that's
a
way
to
bring
them
into
the
same
pilot
program
that
expressed
had.
Maybe
that
gives
lab
some
in
or
something
like
that.
I,
don't
know,
that's
a
path
or
not,
but
it
seems
like
there's
two
ways
to
help.
If
your
maintainer-
and
you
actually
mean
have
you
know-
admin
access,
you
can
probably
actually
implement
changes
that
we
recommend
if
you're
just
a
collaborator.
B
So
I.
Guess
in
the
case
of
note,
fetch
I
can't
remember
if
it
was
I,
think
there's
another
collaborator,
so
I'm
not
sure
I
mean
I
guess
this
is
just
an
opportunity.
You
know.
Is
there
like,
maybe
not
to
dilute
it
now
to
a
script,
but
like
a
talk
boy
script,
but
if
more
collaborators
come
is
there
maybe
something
we
want
to
write
down
somewhere
like
hey?
We
definitely
want
package
maintainers
to
come
and
get
involved.
Just
know
that
you
know
if
you're,
just
if
you're
an
owner,
then
you
know
maybe
help
you
with
this.
B
D
A
B
Yeah
it's
a
between
now
and
then.
If
we
have
actual
me
well,
I
mean
I.
Guess
it's
collapse,
I
don't
know
if
it's
should
be
limited
to
maintain,
errs
but
terms
of
being
able
to
impact
things
but
yeah
I.
Guess
it's
just
more
or
less.
How
do
we
you
know?
B
A
B
B
I,
guess
maybe
that
maybe
it
falls
under
well,
not
maybe
about
governance
models,
but
governance
of
this
group
in
general
like
what
can
can't
we
do
with
you
know,
with
some
with
whatever
resources
the
project
makes
available,
but
maybe
it's
just
yeah.
Maybe
it's
just
right
for
an
issue.
I
could
open
and
maybe
try
and
string
these
together,
not
daddy
to
the
another
string
of
issues,
but
you
know.
Maybe
this
is
the
one
that
binds
them
all
together.
So
this
we
basically
could
just
be
like.
B
Yeah
and
maybe
tie
that
in
with
some
of
the
recent
documentation
work,
so
at
least
I
can
open
the
issue
kind
of
summarize.
You
know
what
we
just
talked
about
say
that
we're
at
least
trying
to
work
through
documentation
to
collab
summit,
but
you
know,
maybe
there
could
be
some
more
more
that
we
could
discuss
on
it
and
I
could
at
least
link
back
to
those
other
issues
like
hey
we're
in
the
process.
If
you
want
to
help
shape
the
process
of
how
package
maintenance
team
can
help
right,
your
situation
come
contribute
to
this
issue.
B
So
what
is
yeah
in
a
basically
that
kind
of
first
draft
state
I,
have
another
interesting,
open
source
project,
not
sure
figure
familiar
with
Rome
Jas
from
the
original
creator
of
babble,
but
they
have
a
a
good
governance
doc.
So
I
was
going
to
take
a
look
at
that
see
if
there's
any
additional
material
that
would
be
worth
putting
into
that.
But
yeah.
At
this
point,
that's
just
basically
open
that
issues
open
for
feedback
and
suggestions.
A
B
A
B
B
So
yeah
yeah
I'd,
say
you
know,
that's
useful
for
collab
summit.
Maybe
it
could
be
linked
into
the
collab
some
Doc's.
If
we
you
know,
want
that
or
not
just
because
I
was
taking
a
look
not
to
jump
ahead,
but
I
was
taking
a
look
at
the
collapse
on
the
docks
and
they
look
good.
So
you
know
I,
don't
know
you
know
if
we
want
to
piggyback
on
that
further,
but
we
can
wait
till
we
talk
more
about
that.
A
D
D
Well,
as
I've
told
previously,
this
may
change
a
bit
depending
upon
developments
that
are
going
on
my
place
of
work
I'm,
a
it
maybe
I'd
have
more
people
involved,
so
I
also
contacted
jury
and
said
how
long
should
this
be,
and
they
said
they
want
more
time
for
talks
and
interaction.
The
natural
house
stands
in
there
talking
so
I
think.
D
If
we
just
have
about
10
or
15
minutes
and
open
up
the
floor,
we
should
be
good
and
I
think
that
we
have
plenty
of
material
for
10
or
15
and
I
typed
up
enough
I
think
we're
gonna
have
to
start
emphasizing
the
fact
that
we're
doing
these
things,
but
hey
what's
more
crucial,
is
once
we
have
a
framework
is
how
do
we
get
people
involved?
And
it's
not
just
writing
code
from
what
we're
seeing
on
express
what
we
more
it's
like.
D
They
need
almost
a
full-time
scrum
master,
almost
like
just
a
handle,
all
the
stuff
coming
in
and
organized
people
and
John
Church
is
kind
of
doing
that
as
well
on
on
the
cause
that
so
it
is
more
than
just
code.
It
is
in.
It
is
just
actual
involvement
and
long-term
collaboration,
which
is
what
I'm
highlighting
in
the
document
of
I've
shared
on
Google,
Docs,
so
engagement
and
then,
secondly,
not
just
code.
It's
there
is
more
it's
being
involved
than
just
churning
our
code
in
it
to
keep
an
ecosystem
healthy.
D
What
we've
seen
as
the
triage
is
making
quite
a
big
impact,
just
answering
replies
being
there,
so
that
one
or
two
maintain
is
don't
get
burned
out
and,
as
we
just
saw
in
the
no
fetch
one,
the
main
maintain
I
just
said:
I'm
no
longer
gonna
be
working
in
this
area.
Full-Time
and
I
can't
support
it
and
that
sort
of
thing
so
I
think
we've
covered
the
correct,
correct
areas
there.
E
D
A
B
A
B
Yeah
I
I
took
a
brief,
look
and
yeah
I.
Definitely
like
the
you
know
where
it's
going
yeah
so
I
could
definitely
well
I
was
thinking.
I
can
make
that
issue
about.
You
know
how.
So
we
can
start
the
conversation
about
how
we
can
have
this
group
can
help
teams
like
we're
just
talking
about
that.
I
can
add
some
additional
thoughts
or
own
governance
models
and
all
that
and
then
drop
that
as
a
comment
in
the
doc.
B
D
C
D
D
B
D
B
F
E
A
B
A
A
B
G
Yeah,
okay,
yep
I,
think
done.
This
me
me
and
Beth
have
been
working
on
this.
For
the
past
couple
weeks,
we've
been
coming
up
with
an
initial
flow
which
are
think
of
place
to
pile
into
the
chair,
so
we're
trying
to
find
consensus
on
the
full
flow
for
you
for
the
testing
tool
for
dependence
in
parallel.
G
A
C
We're
still
struggling
between
whether
we're
gonna
make
it
run
on
Forks
or
not
folks,
but
I
think
the
last
suggestion
was
for
now.
We
were
just
hard
code,
the
full
path
to
the
repository,
so
it
doesn't
matter
whether
it's
a
fork
or
a
the
actual
repo
itself
opens
up
er
on
so
for
now
we're
testing
it
on,
like
our
own
Forks
of
a
repo,
so
I've
walked.
My
ultra
and
Express
I
can
test
it
with
those
because
he's
at
all
what
the
moment
needs
to
have
push
access
to
push
a
branch
to
the
repo.
A
G
I've
got
at
the
moment,
looks
like
it
can
be
easily
modified,
so
it
can
run
against
the
full
core
and
the
more
repo.
So
it
looks
default
to
try
and
push
to
the
repo
and
then
check
if
it's
got
admin.
The
right
access,
I,
think
I'll,
wait.
I
haven't
got
admin
the
right
access,
let's
create
a
full,
can
push
to
that.
So
I
can
incorporate
that
into
the
tool
itself.
It.
G
Secondly,
I
assume,
if
they
or
even
if
they
opted
in,
you,
could
still
push
to
the
fork
as
long
as
the
fork
was
kept
updated.
G
F
So
great
problem,
the
problem
with
just
pushing
the
branch
and
not
opening
the
poor
request
is
that
some
CI
systems
do
not
run
off
branches.
Jenkins
is
horrible.
If
you
want
to
I'm
looking
forward
to
the
next
step
of
using
this,
not
just
for
open
sources,
but
that's
what
am
I
thinking,
I,
suppose,
there's
not
many
public
open
source
modules
using
Jenkins
in
the
node
ecosystem
when
there's
Travis
around
so
I.
F
Think
that
may
just
be
another
option
there,
but
also
having
a
full
request.open
means
that,
if
there's
an
option,
if
it's
configurable
I
think
it's
best,
because
you
might
also
want
to
open
up
the
pull
request
simply
because
you
will
need
to
discuss
it
with
the
maintainer.
You
know
you
open
up
a
space
where
you
can
talk
about
code,
where
you
can
have
a
code
review,
because
if
you
just
open
up
a
pull
request
with
the
braking
changes
of
your
next
release,
you
probably
want
to
push
some
commits.
F
A
C
A
F
A
F
Yeah,
but
if
you're
granting
access
to
someone
to
push
a
branch,
then
you,
if
we
B
works
as
a
service,
you
also
need
Granta
Texas,
not
to
the
all
of
we
be
potentially
everywhere,
but
you
want
to
grant
access
to
specific
user
specific
dependencies
that
you're
testing
against,
not
not
not
all
of
it.
So
there's
a
bit
that
extra
step
right.
A
A
C
A
E
F
C
A
A
A
F
Yeah
I
think
that
was
the
discussion
because
we
had
sort
of
the
opposite
discussion
in
in
some
other
threads
yeah
I,
don't
I
think,
like
I
said
just
having
that
code
of
conduct
in
D
at
the
root
of
the
repo
it
it's
a
statement,
a
much
better
statement.
Then
then
the
default
gear,
a
behavior
where,
when
you
open
up
an
issue,
there's
a
small
pop-up
somewhere
with
a
couple
of
links
right.
E
F
A
I
think
I
think
in
my
mind,
that
does
make
sense,
like
the
code
of
conduct
could
just
be
a
single
line
that
says
here's
the
link
to
our
full
code
of
conduct
in
the
dark
github,
but
from
my
perspectives
not
having
it
in
the
repo
doesn't
seem
discoverable
enough
and
and
because
it'll
be
that
link
that
really
won't
be
any
maintenance
all
right.
So
it's
a
one
time
magician
and
I
think
the
license
pretty
much.
The
same
thing
would
be
in
my
mind
as
well.
F
A
A
A
Okay,
so
we'll
get
that
started
the
next
one
is
next
steps
on
support
levels
for
patches
of
Jason.
Our
main,
the
next
step.
We're
working
on
there
is
to
get
the
support
tool
to
the
MVP
state.
So
we
can
then
start
promoting
and
asking
people
maintain
errs
to
put
that
in.
We
did
have
a
meeting
I
forget
late
last
week,
anyway,
probably
Thursday
I
think
we
have
agreement
on
just
a
couple
things
that
I'm
gonna
look
at
and
then
hopefully
get
that
landed,
and
so
you
know
hope
just
a
hope.
A
You
know
how
to
promote
actually
might
be
good
to
get
it
done
before
the
summit.
If
we
can
anything
else,
people
want
to
bring
up
on
that
one.
There
is
a
you
know:
there
is
a
prototype
there
in
the
PRS.
If
you
want
to
go,
try
it
out
and
there's
some
unit
tests.
You
could
look
at
to
see
what
it's
currently
validating
and
doing.
A
D
D
G
Okay,
so
to
run
the
tools
you
assume
that
you're
in
these
top
level
of
the
parent
package,
so
my
parent
package
is
something
called
I
should
pass
so
I
forgot
this
and
I
have
a
child
dependent,
but
I
can
also
find
with
the
dependents
tool
which
nice
and
quickly,
okay,
cool,
so
yeah,
okay,
my
child's
package
is
called:
do
you
pass
by
from
github
and
then
to
use
the
wiki
tool?
All
you
need
is
at
the
moment.
All
you
need
is
the
URL
to
your
child
package.
G
G
It
creates
the
patch
which
will
be
then
applied
on
to
the
child
package
Jason
and
that
more
point
to
a
specific,
commit
heads
or
tag
or
anything
at
the
moment
it's
pointed
so
they
commit
thus
on
Martha
for
this
repo
and
then
it
will
create
a
commit
and
push
that
to
the
following
BIC,
which
they're
now
out
Chris
go
to.
These
should
see
my
versions
been
changed
cool
yeah,
so
the
version
has
been
changed
to
point
to
the
latest,
commit
or
on
the
I
suppose.
G
A
G
The
initials
or
how
far
the
initial
prototype
doesn't
do
that
it
only
takes
the
single
euro.
In
theory
we're
in
the
flow
we're
trying
to
define
something
called
a
we
be
Jason
which
should
host
all
the
names
of
your
dependents,
and
then
it
will
loop
through
that
Jason
file
and
open
the
PRS
on
each
one.
Okay,.
G
G
G
Okay,
she
don't
want
you,
don't
want
you
see.
A
light
ought
to
just
be
hanging
around
waiting
for
your
CI
runs
happen
because
sometimes
CLI
run
this
might
take
half
an
hour
or
so
so
be
easier
to
just
do
a
will
be
a
result
to
try
and
get
the
result
of
this
CI
run
separately.
Does
it
then
tell
you
if
you're
not.
A
C
Think
we
thought
we
talked
about,
maybe
having
like
a
log
file
for
each
run
and
that
stores
all
of
the
links
like
the
changes,
push
to
the
link
that
Andrews
got
there
and
then,
when
we
run
result,
it
goes
through
all
of
the
links,
so
it
could
be
multiple,
it
could
be
individual
and
then
just
outputs
like
a
table
to
the
screen
saying
see:
I
ran
past
on
this
run
or
is
still
pending
using
the
Travis
or
the
github
checks.
Api.
G
C
Question
how
how
many
people
would
want
that
running
in
like
a
CI
place
like
I,
can
certainly
imagine
on
Travis
or
github
actions.
You
won't
want
to
use
up
your
allowance
with
a
long-running
job.
That's
taking
the
time
it
takes
is
dependent
on
all
of
your
other
packages.
Cie
runs
so
if
their
backlog,
you're
gonna
back
off
even
more.
C
A
C
F
As
a
separate
job
somewhere,
so
yeah
one
cool
place
to
store,
the
URLs
could
be
get
notes
because
that
is
associated
with
a
commit.
This
is
something
that
Symantec
release
does
as
well.
It
adds
a
get
notes
on
on
tags
for
pre-releases
to
record
the
pre-release
status,
which
is
a
nice
because
it
lives
in
the
repo
it's
it's
kind
of
obscure
the
API
itself
and
sometimes
annoying
to
use,
and
it's
sometimes
hard
to
understand
because
it
behaves
like
it
differently,
then
get
itself
when
you're
pushing
commits.
F
A
F
B
Because
there's
the
the
vision
of
something
like
this
is
that
I
guess
I
could
in
my
mind
something
like
this
for
like
say
the
express
team
right
every.
Maybe
they
have
a
github
action
so,
every
time
a
merge,
a
PR
lands
into
master.
It
could
trigger
the
job
like
this,
that
you
know
picks
three
or
four
of
their
identified
dependencies
and
you
know
patches.
The
latest
commits
from
master
on
to
the
version
in
that
projects,
package
JSON
and
runs
those.
B
B
Mean
like,
for
instance,
I,
could
see
adding
this
as
a
dev
dependency
to
your
project
and
then,
as
part
of
that
projects
build
pipeline,
they
could
save
run
dependent.
You
know
run
dependents
package
with
my
config
against.
You
know
what
I
consider
to
be
the
most
consumed
or
what
I
consider
to
be
the
projects
that
consume
my
project.
The
most
you
know,
then
do
the
normal
flow.
It's
so
still
from
a
CLI
perspective,
like
you
just
run
a
a
bash
command
that
you
know
runs
the
binary,
so
you
could
add
both
I.
A
C
I'd
probably
ask
him:
if
anyone
has
time
to
read
free
to
flow
and
PR
I,
think
it's
the
one
and
read
in
the
chat.
Please
do
and
add
some
comments.
Some
of
the
things
I
haven't
thought
about
properly
enough,
yet
so
I
plan
to
get
back
to
that
when
I've
had
time
to
think
about
something
about
having
some
more
input,
probably
be
pretty
good.