►
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
B
Looks
like
we
got
recording
so
yep,
so
just
to
recap,
we
started
recording
just
a
little
bit
late.
This
is
the
package
maintenance
working
group
session,
I'm,
Wes,
I'm,
Glenn
and
I
are
are
hosting
today
and
so
we're
a
couple
slides
in.
But
you
know
that's
the
way
it
is
so
so
we're
talking
about
tooling
now
so
we've
got
so.
We
started
a
github
organization
called
PK
gjs.
B
We
had
I
think
the
first
tool
that
was
created
was
created
in
the
node
org,
partly
because
of
that
the
naming
was
you
know.
I
was
trying
to
find
a
name
on
the
public
and
p.m.
scope
or
sorry
pub
not
on
a
scope
just
on
the
global
namespace.
So
it
was
a
little
bit
harder
to
find
naming.
So
we
said:
hey,
let's,
let's
maybe
pick
a
scope
that
we
can
use
and
and
managed
by
the
team.
B
B
Cool
so
we
started
a
few
tools,
so
some
of
these
examples
here
we
have
one
that
is
called,
will
I
break
you,
WI
dy,
and
so
this
one
will
help
folks
test
their
dependents.
Sorry,
yes,
their
dependents,
not
their
dependencies
right.
So
this
is
their
if
they
are
the
a
dependency
on
an
an
upstream
package
that
will
help
identify
and
run
tests.
B
As
you're
going
to
release
conversions,
we
have
of
I
think
a
few
things
in
the
dependents
space
which
is
trying
to
identify
and
give
you
back
a
list
of
your
and
then
we
have
a
tool
for
node
versions.
So
this
one
will
give
you
back
based
on.
So
we
have
so
one
of
the
initiatives
we
started
I
think
Dom
was
the
initiator.
B
Here
is
identifying
common
aliases
for
that
align
with
the
node
version
releases,
so
we've
got
like
LTS
maintained
and,
and
the
idea
there
is
having
those
aliases
will
be
used
in
a
bunch
of
different
contexts.
The
support
spec
that
that
Glenn
was
talking
about
previously
things
for
CI.
We
have
a
I've
been
working
with
Jordan
and
what's
his
real
name,
shadow
spawn
is
his
github
handle,
who
he
runs,
n
and
then
Jordan
runs
nvm.
So
getting
these
aliases
supported
across
those.
But
then
the
the
underlying
thing
is:
what
does
that
alias
map
to?
B
So
we
have
a
module
that
map's
the
aliases
to
the
different
versions
based
on
the
release,
Jason
and
the
schedule.
So
you
can
say
like
what
is
the
current
LTS
or
you
can
actually
go
post
or
in
the
future
and
say
what
will
the
LTS
be
in?
You
know
later
this
year,
and
so
then
it
returns,
though,
so
you
could
do
things
with
automation
around
that.
So
that's
just
a
couple
of
examples.
There's
a
bunch
of
others
going
on
in.
B
A
One
of
the
the
most
discussed
and
loved
topics
is
dependencies,
and
this
just
wasn't
a
slide,
so
I
could
use
a
penguin.
Perhaps
it
was
I
said
I
find
this
really
cute
penguin,
this
most
dependent
picture
I
could
find
and
one
of
the
things
we
did.
We
talked
to
NPM
and
later
in
the
year
they
said.
Perhaps
the
fourth
quarter,
David
Starr
on
providing
an
API
which
would
give
dependents
with.
A
So
what
we'd
like
to
talk
about
now
quickly
is
what
are
the
practical
ways
we
can
help?
Okay,
so
currently
we're
engaged
in
in
the
nodejs
module
and
where's
is
going
to
talk
about
that
in
a
second,
but
I
only
got
involved
in
December
in
2019,
but
the
montreal
conference,
when
where's,
was
appealing
for
help.
We've
taken
this
one
project
as
a
first
candida
and
I'm
gonna
hand
over
now
straight
to
him
to
talk
a
little
bit
about
our
practical
case
of
helping
out
a
project,
so
West
yeah.
B
Absolutely
so
also
as
we
were
bootstrapping,
we
came
up
with
a
plan
for
how
we're
going
to
operationalize
these
different
things
were
working
on.
So
we
said
we're
going
to
start
with
some
pilot
projects,
ones
where
there
was
specific
need
in
the
in
the
ecosystem
for
help
and
so
I
being
one
of
the
members
of
the
Express
project
said:
that's
that's
us
please,
and
so
since
then,
we've
done
a
few
things
and
they've
actually
been
incredibly
successful
and
and
I
want
to
thank
folks
like
Glenn,
who
have
stepped
up
and
really
helped
recruit
people.
B
B
Well,
I
guess
that
was
part
of
the
main
conference,
but
but
anyway
since
then,
we
have
on
boarded
I,
think,
like
twelve
or
fourteen
triage
team
members,
not
everyone
is
as
active,
but
we've
got
a
few
that
have
really
just
stepped
up
and
and
done
such
great
work.
So
basically,
we
as
the
the
the
team
sort
of
built
a
document
on
what
it
takes
to
become
a
treasurer
member,
how
it
works,
and
this
the
goal
of
that
testing
it
out
and
express
is
that
we
can
then
take
those
Doc's
up
level
them
with
the
package.
B
Maintenance,
working
group
and
use
the
same
sort
of
template
for
other
ecosystems
and
say:
look
we
we
tried
this
out
and
express
it
worked.
Well,
you
know,
Babel,
are
you?
Are
you
looking
to
grow
your
support
base?
You
know
whatever
projects
might
come
to
us
in
the
future,
we
can
say:
hey,
look,
we
here's
a
thing
that
worked
really
well
for
Express,
just
copy
and
paste,
here's,
the
here's,
the
section
and
the
contributor.
You
know
dot,
MD
and
you're
ready
to
go.
B
Hopefully,
we'll
also
have
some
automation
and
around
how
to
manage
that
stuff.
Like
Glenn
was
saying
and
shows
in
the
slide
here,
on-boarding
and
off-boarding,
you
know
there's
there's
orchestration
work
that
just
needs
to
be
done
when
you're
getting
people
on
and
then
also
when
you're,
when
you're
saying
when
they
say:
hey,
I'm,
no
longer
you
don't
want
to
be
a
part,
and
then
recruitment
is
obviously
very
important
in
their.
B
You
know.
The
the
team
is
is
really
good
about
putting
the
word
out.
You
know
it's,
it's
not
as
much
that
there's
formal
help
being
done.
It's
just
you
know.
People
come
to
the
the
package
main
it's
working
group
and
say:
hey
I'm,
looking
for
help
recruiting,
and
then
you
know
we
as
the
members
have
our
our
you
know,
context
of
people
that
we
that
might
come
to
us
asking
hey
I'm,
looking
to
get
into
open
source.
So
we
also
provide
just
like
a
group
of
people
who
are
helping
facilitate.
A
A
We
all
know
that
one
of
the
most
common
issues
we
have
is
getting
long-term
commitment
and
long
term
means
different
things
to
different
people.
Our
communities
tended
to
coalesce
around.
Let's
say
the
latest
fashionable
projects,
and
this
mainly
is
reflection
of
like
a
menu
that
many
of
the
contributors
are
very
young
and
still
in
the
early
stages
of
their
career,
and
when
they
make
a
commitment,
it
can't
be
helped.
You
know
they
can't
they
cannot
make
that
forever,
and
so
we
we
equally
need
to
have
a
pipeline
on
each
one
of
these
projects.
A
A
So
so,
if
we've
told
you
a
little
bit
about
a
package
maintenance
committee,
so
firstly
you
know:
if
you
are
maintaining
a
project,
you
know,
do
you
align
with
some
of
the
things
with
we've
been
talking
about
the
proposals
and
do
you
believe
that
what
we're
proposing
is
correct,
I
know
we
want
to
offer
help
and
tooling
in
a
general
way,
and
we
also
want
to
be
an
area
that
writes
you
know,
governments
and
good
best
practices.
The
group
is
meant
to
have
a
broad
me
remit
and
anyone
is
welcome.
A
So
if
you
have
an
issue
that
doesn't
easily
fall
into
the
other
working
groups
and
the
community
would
benefit
from
it,
I'm
proposing
that
the
package
maintenance
committee
might
be
the
place
for
you,
so
in
a
broader
way,
how
do
we
help
the
ecosystem?
So
I
have
my
own
particular
view
on
this,
so
everyone
here
is
already
probably
contributing
in
some
way
and
and
just
the
contribution
shouldn't
be.
The
only
thing
that's
measured,
as
is
that
the
triage
team
is
set
up
explicitly
just
to
answer,
questions
or
unexpressed,
because
so
many
questions
are
answered
on.
A
It
asked
on
a
daily
basis
and
we
want
a
healthy
and
vibrant
community
to
each
one
of
these
modules.
So
what
we
also
understand
is
that
it's
a
miniscule
number
of
proportion
of
the
community
to
such
a
contributing
back
again
and
we
need
to
reach
out
and
engage
more
of
the
communities
that
are
not
engaged,
and
my
first
suggestion
is
that
actually,
that
is
actually
more
important
than
writing
code
at
a
moment
for
a
lot
of
very
wide
to
use
modules.
A
I
think
you
should
actually
think
rather
about
how
to
maintain
your
health
and
outer
add
in
the
latest
features
so
historic
rate,
a
great
deal
of
has
been
placed
on
the
development
of
software
and
less
on
its
sustainability
and
I.
Think
we
actually
need
to
change
that
sort
of
ratio
a
little
bit
more
and
start
engaging
with
the
medium
and
large-sized
Enterprise.
A
Most
of
us
work
at
those,
so
I'd
like
to
suggest
that
sustainability
and
a
direction
and
stability
are
very,
very
important
and
that
the
enterprise
wants
to
actually
get
involved,
but
we
haven't
engaged
them
quite
accurately
or
in
quite
and
in
the
way
that
works
for
them.
So
I'd
like
there's
a
takeaway
for
everybody
to
actually
go
away
and
actually
think
about
how
they
can
actually
engage
other
people
or
more.
A
So
how
do
we
do
that?
How
do
we
actually
engage?
How
do
we
keep
how
to
keep
this
maintenance
going,
as
I've
said,
I
don't
think
for
established
projects.
We
should
actually
stop
thinking
about
new
features
and
start
thinking
about
engagement
and
perhaps
coding
not
to
be
the
priority
evangelizing
and
that
the
enterprise
as
number
one
sort
of
a
partner's
you
know
like
functions
as
first-class
citizens.
A
Well,
perhaps
engagement
should
be
a
first-class
citizen
too,
because
there
have
been
other
ecosystems
in
the
past
that
have
grown
as
rapidly,
perhaps
not
as
rapid
as
this
and
of
fallen,
and
we
need
to
start
looking
at
the
health
of
the
bigger
system,
as
those
maintainer
z'
reach
certain
points
in
their
life.
Where
they
can't
maintain
over
to
us.
B
C
D
B
E
B
If
we
can
share
effort
and-
and
you
know,
multi-purpose
some
of
the
stuff-
we
are
working
on
to
work
on
both
I
think
that
would
be
great,
and
also
that
would
just
really
establish
this
practice
and
and
I
think
you
know
many
more
maintainer
groups
would
probably
be
willing
to
adopt
it
with
saying
both
both
express
and
no
to
use.
This,
like
that's,
I,
think
it's
shining.
That
would
be
a
shining
example
of
like
yes,
this
is
a
great
best
practice,
so
I
was
going
to
show
a
couple
of
things.
Actually,
I
should
have
done.
B
My
muscle
memory
goes
to
the
discussions
repo,
which
is
another
thing
that
is
great
to
have.
If
you
have
a
lot
of
repos
like
Express,
does
having
a
place.
That
is
a
public
where
we
the
issue
tracker.
As
the
discussions
I
know,
github
has
their
discussions
thing,
but
we've
we
found
the
issues
are
really
successful
for
that.
So
let
me
pop
open
our
this
is
in
contributing,
so
we
added
a
section
on
becoming
a
triage
er
here
and
it
yes,
so
there's
two
different
pieces
here,
so
this
one
is
sort
of
the
actual.
B
A
You
sharing
your
screen,
you
know
screen.
B
B
Well,
I,
don't
I,
don't
wanna
I'm,
not
sure
exactly
if
there's
any
private
stuff
as
soon
as
I
go
in
there
with
security
or
you
know,
team
membership.
If
people
keep
it
private,
but
so
I
won't
go
in
and
show
that,
but
basically
they
just
open
a
PR.
Somebody
comes
by
says:
shirk
merges,
goes
and
adds
them
to
the
team
on
all
three
orgs.
We
would
like
to
get
some
automation
around
that.
B
B
So
here
we
have
somebody
opened
three
days
ago,
admission
said:
hey
look,
I
I,
think
I
found
I'm
guessing
a
memory
leak
here,
memory
increase
until
the
hundred
percent
sounds
like
a
memory
leak
and
they
gave
some
details
and
Glenn
came
in
and
said
hey.
This
looks
like
a
question,
so
we
have
a
few
standard
tags
that
we
use,
and
these
are
standardized
across
the
orgs
I
have
to
move
this
over,
so
I
can
see
the
well
I
have
to
move
it
to
the
other
side
of
the
screen.
So
we
have.
B
A
few
question
is
one
of
our
most
popular
so
being
expressed.
That's
a
lot
of
new
to
note
people
sometimes
they're.
Just
you
know,
I,
don't
even
have
a
package
Jason
yet
and
I
tried
to
run
NPM
install
Express
and
it's
airing,
like
you
know,
there's
lots
of
just
question
style
things.
So
that's
one
of
the
most
important
ones
we
also
have
awaiting
more
info
is
also
a
very
common
one.
So
somebody
comes
in
and
reports
a
bug.
Oftentimes.
Their
bug
report
is
really
you
know
low
on
details.
B
This
one
is
great
as
a
ton
of
details
mini.
Don't
so
we
have
this
awaiting
more
info.
This
is
a
great
way
to
come
in
and
say
we
need
something
from
you.
You
know
the
user
who
reported
it
and
then
we
have
discuss
so
oftentimes
question
and
discuss
go
together.
These
are
things
where
we
it's
not
necessarily
a
bug
report.
Maybe
this
is
a
new
feature
and-
and
we
say
hey,
we
think
this
is
might
be
a
good
idea.
B
B
Typically,
this
one's
used
also
close
out
and
then
people
will
we
coached
the
triage
team
to
be
respectful
and
nice
and
not
you
know,
closing
smart
duplicate
and
not
give
any
feedback,
but
we
want
people
to
feel
like
they're
being
heard
so
oftentimes
we'll,
say
hey.
This
looks
like
the
same
issue.
Is
here
I'm
going
to
close
this
and
mark
it
as
duplicate?
B
If
you
disagree-
and
you
think
it's
a
different
issue-
feel
free
to
reopen
all
right,
so
we've
had
a
bunch
of
discussions
with
the
triage
team
about
how
to
properly
and
I
say
properly
how
to
be
an
open
and
welcoming
community
right.
We
want
people
to
feel
really
good
when
they
come
in
and
open
an
issue
on
an
express
project
that
they're
they're,
you
know
being
helped.
So
that's
a
good
one,
and
then
we
have
good
first
contribution
and
Help
Wanted.
We
actually
added
good
first
contribution.
B
E
C
E
For
the
most
part,
I'd
say
definitely
more
labels
than
then
respond
most
the
time.
One
thing
to
note
that
I've
noticed
that
we
do
differently
than
a
lot
of
other
open-source
projects
that
I've
interacted
with
is
that
we
don't
use
the
debug
label.
Unless
is
a
verified
reproducible
bug
which
is
kind
of
cool
yeah.
B
Is
the
only
thing
that
I
have
that
I
think
is
a
meaningful
metric,
so
at
the
conference
in
December
I
built
this
and
it
has
been
having
it
isn't
being
built
regularly,
but
the
status
board
had
dug
at
the
top
with
about
a
400
and
say
about
the
same
400.
Some
I
was
second
most
and
I
had
like
200
some.
B
This
is
it
as
of
like
maybe
two
weeks
ago,
I
don't
know,
maybe
a
little
bit
more.
So
this
is
90
days
worth
of
activity
and,
as
you
can
see,
the
triage
team
has
been
just
killing
it
right
like
like
then
the
numbers
here
it
used
to
go
straight
from
Doug
to
me
down
to
somebody
with
like
10,
and
they
were
not
even
a
member
of
the
project.
Now
we
have
a
group
of
people
who
are
regularly
engaging
in
the
project.
You
know
like
Jess
here
with
a
hundred
and
nine.
B
You
know
and
I
think
actually,
if
we
rebuilt
this
today,
like
I,
think
John
would
be
up
pretty
high
too
and
I.
Think
we'd
have
a
few
more
of
the
the
triage
team
members
showing
up
here.
I
just
need
to
get
the
github
action
working
again,
I
think
I
built
this
locally
and
pushed
so
that
that's
the
only
metric,
I've
I've
actually
looked
at
I,
don't
know
if
anybody
else
has
has
looked
at
anything
gorg
wide.
A
Can
speak
to
express
session,
which
is
what
I
was
looking
at,
so
we
will
try
to
pick
one
of
the
repos
in
Express
I
chose
session.
I
can
say
that
the
number
of
issues
is
now
flat
since
at
least
I've
been
looking
at
it
and
that's
six
months.
You
may
go
up
down
one.
What
one
or
two
we've
tried
to
address
them
generally,
what
happens
there?
We
go
and
we
give
advice.
Sometimes
it's
obvious.
Sometimes
it's
nor
sometimes
people
want
free
advice.
A
Often
they
just
want
somebody
to
listen
to
them,
which
is
odd,
but
understandable
and
we've
managed
to
keep
it
down.
There
haven't
really
been
any
new
issues
that
have
been
pr's
raised
because
of
the
maturity
of
the
project,
a
lot
of
PR
czar
for
things
that
we
have
to
actually
question
whether
people
really
want
them
or
not,
and
so
there's
a
lot
of
discussion
with
some
of
the
PRS
and
often
I
ask
you
know
we're
doing
due
diligence
on
our
a
well-used
project.
A
A
Just
not
wanted
really
not
widely
wanted,
but
we
have
managed
to
keep
session
down
to
about
33
34
ever
since
I've
been
doing
here
in
February,
and
there
are
questions
they're
open,
they're,
almost
daily,
the
usually
one
or
so
Dennis
we're
up
and
concentrating
I
will
go
in
and
Mark
and
the
Express
ones.
Question
I
looked
at
that
performance
one
and
said
no
I,
don't
think
that
one's
for
me
just
yet.
A
A
That's
why
you
need
quite
a
lot
of
triage
as
we're
trying
to
build
up
a
team
a
pipeline,
so
people
can
come
on.
Learn
a
bit
about
Express,
learn
a
bit
about
the
ecosystem
and
at
some
point
a
year
later
can
come
off.
Knowing
that
they've
done,
they've
done
something
good
they've
contributed,
they
say:
I
have
made
a
significant
contribution.
B
Yeah,
absolutely
sorry
and
I
also
I
could
have
sworn
we
had
a
treasure
guide.
This
is
the
thing
I
was
going
to
look
for,
so
we
we
also
have
this,
which
I
think
would
be
a
nice
document
to
uplevel.
So
it
also
talks
about
the
different
tags
we
use
so
and
needs
triage
actually
isn't
implemented
everywhere.
B
B
You
know
it's
like
oh
I'm,
coming
in
to
express
like
what,
if
I
mess
it
up
or
what,
if
I
say
something,
that's
wrong
or
you
know
what,
if
I
close
an
issue
that
shouldn't
have
enclosed,
like
am
I
gonna
piss
somebody
off
or
am
I
good
I,
don't
know
you
know,
there's
a
lot
of
a
lot
of
like
I.
Don't
know,
I
don't
contribute
a
lot
to
open-source.
Is
this
like
this
seems
like
a
very
important
project?
B
B
But
you
know
that's
a
lot
of
effort
and
and
being
able
to
have
some
folks
who
can
come
in
with
you
know.
They
don't
need
to
answer.
I.
Think
I
found
a
memory
leak
like
that's
fine
to
say,
hey
you
may
have.
Could
you
provide
a
reduced
test
case
so
that
when
somebody
from
you
know
when
Doug
can
can
come,
look
at
it,
he
will
have
more
info
like
otherwise
Doug
would
have
had
to
do
that
right
and
then
he
wouldn't
been
spending
his
time.
Debugging
the
memory
leak.
He
would
have
been
spending
his
time.
B
A
A
Dominique
is,
do
we
have
any
contacts
in
in
github,
because
one
of
the
things
I'm
trying
to
emphasize
back
to
the
enterprise
is:
please
don't
just
value
writing
code.
If
we
could
value
triaging
labeling
this
stuff
to
stuff
that
we're
talking
about
and
and
for
that
to
be
seen
as
a
contribution
on
github,
they
can
measure
it
and
when
they
do
is
ease.
So
it's
not
like
labeling
issues
is
not
really
measurable.
You
you're
not
gonna,
get
any
like,
and
some
of
the
enterprise's
want
to
see
what
their
personnel
are
doing.
B
Look
at
this,
this
is
this-
is
commits
most
of
these
triage
efforts.
Don't
show
up
here
you're
trying
to
go
to
your
boss
and
say
look
I'm
helping
with
these
projects
we
use
if
all
you're,
doing
and
I
say
all
you're
doing.
I
should
I
should
I
should
careful
about
how
I
say
because
I
think
I
agree
here.
It
is
incredibly
valuable
where's.
B
The
comment
where
is
the
like
in
this
little
thing
and
on
this
like,
where
is
the
I
labeled
and
issue
like
it's
not
present
right,
but
that
value
is,
is
incredibly
high
and
I
and
I
do
think,
and
you
know
maybe
maybe
we
have
some
ends
now
with
three
working
at
a
github
that
he
can.
He
can
find
the
right
people
to
to
get
that
at
if
they
just
added
it
to
the
darn
board
here
like
that,
would
just
be
so
much
better
than
what.
A
I've
brought
it
up
at
my
Enterprise
saying:
look:
this
is
a
thing
they
want
tune
in
every
they
say
everyone
has
to
start
somewhere
because
I'm
picky
about
who
I,
who
I
introduce
saying
I,
don't
want
just
a
young
developer
if
they
have
a
way
in
and
it
can
be
measured,
they're
very
much
into
measuring
things
like
usually
it's
very
simple,
its
profitability.
This
is
something
they
can
measure
if
we
can
get
those
contributions
on
it,
I
think
that
would
really
help
get
for
me
to
get
people
on
boarded.
D
B
I
brought
it
up,
I
had
a
I
was
on
a
call
with
I
guess
it
was
around
when
and
PM
was
being
bought.
They
were
doing
a
couple
of
like
user
interview,
things
with
with
people
who
are
invested
in
this
ecosystem
and
I
brought
I
brought
that
up.
You
know
it's
one
of
those
things
that
it'll
get
done,
I'm
sure
someday,
but
they're
busy
changing
master
domain.
So
you
know
there's
more
important
things
in
the
in
the
world
happening
like
buying
NPM.
B
B
Think,
from
the
triage
side,
no
I
do
think.
We've
had
growing
pains
as
the
t
as
the
as
we
are
trying
to
onboard
new
people.
You
know
having
an
existing
project
that
has
been
run
in
a
certain
way
for
a
very
long
time
when
you
try
to
change
that,
there's
challenges
so
we're
you
know
we're
trying
to
adapt
to
the
new.
You
know
the
goals
that
we've
set
out.
B
You
know,
I
I
came
in
to
the
project
and
it
already
had
a
TC
and
I
wasn't
on
it
right
and
a
few
years
of
contributing
and
and
now
I
am
and
I'm
saying,
hey
I
want
to
make
some
changes
that
one
of
the
changes
is
the
triage
team.
Well,
you
know
people
in
the
project.
Sometimes
things
there's
you
know
contention
and
we
have
had
some
of
that.
I
think
that.
B
B
You
need
to
make
sure
that
the
people
are
in
the
room
that
have
the
right
discussions
and
some
of
them
people
are
gonna,
make
mistakes
right
and
and
and
you
need
to
call
them
out,
but
you
also
need
to
you
know,
respect
fully
help
them
learn
from
those
and
I
and
I
think
that's
definitely
been
something
that
we've
had
a
couple
of
cases
where
you
know,
there's
there's
been
some
some
contention
like
hey
I,
open
this.
You
know
PR
to
help
this
thing
that
people
kept
on
asking
a
question
for
for
triage.
B
B
You
know
I,
it
wasn't
perfect
nothing's
going
to
be.
You
know
when
you
have
changes
happening
like
this
and
I.
Think
a
lot
of
people
aren't
happy
with
the
speed
that
expressed
is
moving
at
you
know,
I
know
I'm,
not
I
wanted
to
move
faster,
but
if
you
just
try
to
push
it
to
move
faster
with
no,
you
know
without
doing
your
your
the
legwork
to
make
everybody
comfortable
with
that
pace.
You
know,
there's
gonna,
be
battles
and,
and
and
and
so
I
think.
B
That's
one
thing
to
know
with
the
triage
effort
is
that
you
know
the
goal
is
to
take
people
from
brand
new
contributors
through
the
triage
or
team
up
to
contribute.
Collaborators
are
on
a
repo
through
to
like
repo
owners,
up
to
a
technical
committee
right
and
and
some
people
will
drop
off
at
each
step.
B
But
like
the
goal
is
to
start,
you
know,
building
the
that
pathway
right
and-
and
so
you
want
to
make
sure
that
you
are
very
conscientious
of,
but
you
know
talking
with
the
triage
team
members
and
making
sure
you
and
they
understand
how
that
you
know
how
that's
gonna
happen,
what
level
of
investment?
How
is
the
project
run
like
what
level
of
investment
can
they
expect
from
the
existing
people
in
the
project?
Right
like
an
Express?
That
means
we
were
volunteers
when
nobody's
paid
to
work
and
Express
nobody's
working
on
it
full-time.
B
So
you
know
coming
in
and
saying
well,
let's
set
a
schedule
is
like
well,
that's
that's
not
gonna
happen,
like
you
know,
by
all
means.
If
you
want
to
do
that
and
try
to
keep
to
it
great
you
know,
but,
but
that
you're
not
going
to
be
able
to
get.
You
know
the
existing
TC
members
to
do
that,
because
they're
had
they
have
day
jobs
right.
So
those
kind
of
things
I
think
are
are
gonna
happen,
but
luckily
they
haven't
happened.
B
A
B
B
No
okay,
I
put
my
two
questions
here,
but
I
was
hoping
we'd
get
some
from
from
the
audience.
So
how
do
I
join
the
working
group
show
up
that's
about
it.
We
do
have
a
PR
process.
It's
really
loose
I
think
there
will
be
some
small
changes
once
the
Charter
lambs,
but
I
don't
think
it
will,
and
similarly
with
the
PK
gjs
org,
you
know
joining
the
the
working
group
is
one
part,
but
joining
the
the
place
where
we're
actually
working
on
the
tools
is
another.
B
Similarly,
we
have
a
process
in
the
Charter
that
we're
working
on
to
open
a
PR
to
say:
hey
can
I,
join
the
PK,
gjx
org
and
right
now,
I
think
I'm,
an
admin
I
think
I
just
made
dumb
an
admin
as
well,
because
he
needed
some,
some
Travis
things
set
up
and
it
didn't
work
but
I
think
in
the
future.
We'll
also
have
a
management
team
for
that,
but
it's
very
I.
B
B
Don't
okay,
so
then
maybe
we
can
use
the
last
eight
minutes
to
discuss
this,
which
I
think
was
a
one
thing.
I
take
away
from
glen's
points
is
I
think
we
have
been
doing
a
better
job
at
engaging
the
community,
but
is
there
a
way
we
could
better
engage
sort
of
major
players?
He
was
saying
you
know
enterprise,
but
it
doesn't
necessarily
need
to
be
enterprise
like
is
there?
Is
there
something
we
can
do
to
better
engage
github?
Is
there
something
we
can
do
to
better
engage?
B
A
So
so
it's
always
the
week
we
haven't,
because
the
contributors
are
like
a
miniscule.
It's
the
number
of
packages
downloaded
today,
so
we've
really
got
to
come
up
with
ideas
for
this.
It's
it's
easy
to
get.
People
excited
about
current
projects,
but
one
of
the
things
is
they
don't
realize
that
they
will
sit
on
top
of
existing
modules
and
those
modules
need
help
and
that's
the
actual
message
we
get
out.
A
It's
an
entire
ecosystem,
like
the
the
foundations,
are
underpinning
quite
a
lot
of
things
and
people
don't
know
that
there
are
a
lot
of
dependents
out
there
and,
as
Michael
said,
we've
got
to
get
the
value
proposition
across
to
the
enterprise
and
immediately
like.
If
you
participate,
you
have
a
say
you
will
be
listened
to
like
these
are
not
like
dominating
leader
type
organizations
that
everyone
is
listened
to.
So
I
think
it's
a
value
proposition
as
we've
talked
about,
but
we're
not
going
out
making
that
at
least
I
don't
see
it
being
made
a
lot.
F
Yeah,
it's
it's
something
we've
always
had
on
our
radar.
We
just
haven't
figured
out
how
to
do
it
yet
I,
don't
think
or
maybe
not
spent
enough
time.
I
know
that
at
one
point
oh
and
I'm
gonna
blank
on
the
name,
but
he
you
know
there
was
the
thought
of
you
know
some
tooling
to
help
businesses
like
see
all
the
modules
that
they
were
dependent
on
and
cuz
I,
as
I
may
have
said
too
many
times,
like
I
kind
of
see
it
for
businesses.
It's
a
risk
management
thing.
E
F
Their
work,
how
do
I
manage
that
risk
and
and
convincing
them
that
actually
getting
involved
in
the
open-source
projects
is
a
good
way
to
help
manage
that
risk,
and
so
it's
it's
a
win
for
for
everybody,
but
it's
also
a
win
very
specifically
for
them
on
that
front
and
I.
Think
adding
to
that.
You
know
the
talk
by
Toby,
where
he
pointed
out
that
it's
actually
a
good
way
to
grow
and
build
the
capability
of
your.
Your.
Your
employees
is
actually
another
very
significant
part
that
companies
get
out
of
it.
B
B
F
It's
like
if
there
are
any
tools
that
can
help
you
know
business
understand.
That's
where,
like
you
know,
I
think
the
support
information
is,
is
one
aspect
of
that
and
is
something
that
we
are
doing,
because
hopefully
that
will
help
surface
more
information
that
makes
businesses
say.
Oh
okay,
I
need
to
focus
here
or
contribute
there.
F
F
If
an
organization
is
convinced
and
tells
its
people
to
go
out
and
contribute
to
open
source,
that
can
sometimes
be
hard
for
individuals
to
figure
out
what
to
do,
and
you
know,
one
of
the
things
we
had
in
mind
was
like
a
backlog
of
things
that
that
modules
needed
help
with
I
think
having
a
very
tangible,
oh
okay,
I've
gotten
some
time.
Here's
a
tangible
thing,
I
can
do
you
know
versus
having
to
go
and
find
it
that
kind
of
work
and
structuring
what
needs
to
happen
would
significantly
help.
B
F
A
few
of
them
yeah
yeah
yeah,
we've
got
it.
We've
got
one
under
way,
the
other
one
we've
talked
about
in
terms
of
like
how
would
we
surface
a
sort
of
a
global
like
a
more
concrete
here,
specific
things
that
are
a
prioritized
list
of
things
to
help
on?
You
know,
I
think.
As
you
said
it,
a
number
of
these
things
are
sort
of
long-term.
You
can't
just
come
in
and
change
everything
overnight,
so
the
work
we're
doing
and
expressed
to
kind
of
understand
what
does
work.
B
Yeah
I
agree:
I
think
that
the
part
where
we're
still
missing-
and
we
don't
even
have
I-
think
a
proposal
for
would
be.
How
do
they
once
they've
done
that?
How
do
they
then
go?
Take
that
back
to
their
managers,
their
directors,
their?
You
know,
teams
and
say:
look
here's
what
I've
done
like
here's,
the
proof
that
I
I
went
to
them.
I
said
I'm
going
to
do
this
now,
here's
what
I
did
and
here's
how
it
benefited
our
team
or
our
company.
You
know
I,
don't
think
we
have
the
other
end
of
the.
F
Yeah
and
that
that's
hard
like
I
know,
the
the
risk
management
side
is
kind
of
like
insurance.
You
know,
III
early
in
my
career,
I
worked
for
a
number
of
security
companies
where
you're,
basically
selling
insurance
and
it's
a
hard
sell,
sometimes
right,
because
unless
it's
in
the
forefront
of
people's
minds,
they're
like
yeah,
you.
E
F
I
can
manage
my
wrist
by
just
taking
the
risk
or
I
could
spend
money,
and
you
know
so
that
side
is
always
a
bit
of
a
challenge,
because
it's
it's
not
always
a
fuzzy.
We're
gonna,
save
you
X
dollars
and
you
can
measure
it.
Similarly,
like
I,
think
the
discussion
from
the
earlier
part,
where
it's
like
making
it
visible
that
people
have
contributed
is
important
too.
F
It's
kind
of
like
that,
the
recognition
that
people
can
take
back
to
the
the
organization's
is
you
know
it's
not
something
you
want
to
make
the
end
goal,
but
is
important
in
helping
to
support
peeping
people
to
be
able
to
continue
to
do
it
long
term
right
like
to
show
that
yes,
you've
come
to
the
package.
Maintenance
team.
You've
made
a
contribution,
and
it's
just
obvious
that
you've
had
you.
You
have
versus
having
to
try
and
convince
people
that
you
know
that
you
have
yeah.
A
It's
very
important,
a
lot
of
organizations.
You
know
they
want
to
measure.
Had
the
first
thing,
I'll
ask
you,
and
if
you
want
to
organize
a
conference
that
they
say
well,
how
do
we
measure
the
success
of
what
we've
done
and
for
a
lot
of
things?
It's
very
ephemeral
like
okay,
we're
gonna
do
this,
even
though
we
can't
measure
it,
because
it's
pretty
obvious
is
good,
but
for
long-term
things
for
getting
engagement,
long
term,
they
they
want
to
measure.
They
want
to
measure
improvements
where
they're,
starting.
A
If
the
contributions
are
not
noted
in
github,
somehow
it's
gonna
be
very
hard
for
them
to
measure
that
level
of
engagement,
especially
for
junior
people
and
subjects.
We've
talked
about
one
side
committing
code,
that's
fine!
But
if
we
look
at
entire
ecosystem,
we're
gonna
there's
only
going
to
be
a
small
fraction
contributing
code
and
mainly
talking
about
issues
planning
things.
Yeah
will
actually
reflect
what
the
enterprise
does
with
a
number
of
people
writing
code,
a
number
of
people
deciding
what
build
a
number
of
people
designing
it
doing
infrastructure
so.
B
F
B
So
I
think
we
should
just
end
it
there
can
you
this
conversation
come
join
the
package,
maintance
meetings,
we
do
them
by
a
weekly
I,
think
an
alternate
time
zones,
but
also
a
synchronous
communication.
So,
if
anybody's
interested
in
joining
it's
a
great
low
commitment
way
to
start
these
conversations,
so
thank
you
all
and
we'll
see
you
all
in
github
issues,
doctor.