►
From YouTube: Package Maintenance Team meeting - Dec 3 2019
Description
A
B
I,
don't
think,
there's
been
any
update,
isn't
we're
waiting
for
Darcy
and
folks
from
NPM
to
link
to
an
RFC
and
we'll
see
where
we
take
it
from
there
I
think
we
can
remove
the
agenda
label
and
we
have
more
news.
Okay,.
A
A
A
C
So
we
have,
we
have
to
get
together
this,
and
this
might
be
one.
We
have
the
community
corner
one,
and
then
we
have
what
we're
going
to
do
in
initial
collaborators
called
conference.
Do
we
want
to
actually
get
together
at
the
conference
to
flesh
this
out
or
do
we
want
to
try
and
do
it
before
next
week?
That's
that
was
the
question
cuz
that
was
ours.
C
C
C
You
know
this
is
our
in
a
modus
operandi,
we're
looking
for
people
to
come
along
and
collaborate,
I
can
get
that
done
in
the
next
day
or
so
and
put
something
up
on
a
Google
Docs
and
we
can
talk
through
it'll,
be
very
much
along
the
lines
of
what
we've
done
before,
but
generally
a
sort
of
selling
of
what
we're
doing
so.
People
understand
it.
Yep.
A
A
A
C
C
Yet,
okay,
we
discover
when
we
get
here
so
don't
rely,
I'll
write
something
up
in
the
next
couple
days:
I
get
it
up
there
and
we
can
go
through
and
critique
it
and
there's.
One
thing
I
should
have
said
announced
with
LJ
Hobbs
LTS
build
things.
We've
Travis
I've
started
using
those
those
work
quite
nicely.
Okay,
I
said
that
it
beginning
that
is
a
good
advancement
there,
but
yeah
I'll
have
something
up
in
the
next
day
and
I'll
promote
it
within
the
group.
Okay,.
A
That
sounds
good
cuz,
yeah
I.
Think
if
we
have
that
for
the
community
corner,
we
plan
on
making
it
just
a
working
session.
You
know
we
had
a
list
of
topics
there.
If,
if
it
is
just
the
single
track
and
everybody's
there,
you
know
we
might
go
through
the
same
deck
that
you
put
together,
but
we'll
play
that
by
ear
I
think
is
good
enough.
Yeah.
C
A
Okay,
the
next
one
that
was
tagged
was
241,
which
is
the
future
direction
for
support
field
that
hit
the
seven
days
so
I
landed
it
yesterday.
So
I
don't
think
anything
too
much
specific
to
talk
about
that
one
we
do
have
number
192,
though,
and
that
one
I
think
we
could
spend
a
little
bit
of
time
just
working
on
in
terms
it
lists.
That's
not
the
right
thing
that
I
just
pasted
it.
Sorry,
it
is
192,
though
so
no
192
has
sort
of
a
list
of
things
that
we
want
to
do
going
forward.
A
C
C
A
A
A
A
A
And
Wes
since
we're
not
here,
can
you.
A
A
Okay,
so
moving
on
to
the
next
issue,
the
standard
grammar
keywords
with
reference
to
noches
release
lines,
I
went
through
the
release,
repo
and
the
node
repo
and
I.
Couldn't
find
anything
that
I
thought
needed
to
be
updated
so
I've
closed
that
one
it
doesn't
mean
I
didn't
miss
something.
So
if
you
do
see
something
you
know,
let
me
know
or
submit
a
PR,
but
otherwise
I
think
we're
closed
on
that
one
and
then
the
document
current
top
ten
Express
issues,
I,
don't
think.
There's
anything
new
to
really
report
on
that.
A
A
So
that
was
that
what
was
tagged
for
the
agenda
any
other
things
we
think
we
should
talk
about
this
week.
We
we.
C
C
A
A
C
C
If
anybody
heard
about
does
there's
been
some
other
progressions
just
the
other
day
github
there
was
sort
of
a
listen
to
a
podcast
they're
looking
for
some
like
funding
support,
a
disorder,
the
github
level
and
I,
don't
if
people
have
actually
heard
about
that
so
there'd
been
some
other
sort
of
advancements
and
I'll
I
try
and
put
up
a
link
to
that
somewhere.
That
I
haven't
heard
anyone
talk
about.
It
seems
very
similar
in
some
ways
to
our
support
field:
yeah,
okay,
I'm
I'm,
just.
A
A
C
C
A
B
B
So
this
is
basically
about
trying
to
figure
out
as
a
package
brainer.
How
do
you
do
LTS
and
what
are
the
practices
there?
So
I
went
through
the
thread.
I
think
there
were
a
couple
of
discussions
there
around
trying
to
automatically
back
for
two
commits,
and
all
of
that
which
kind
of
came
to
the
conclusion
that
it's
not
exactly
feasible
or
would
require
more
effort
than
it
would
be
right
useful.
B
So
I
wonder
if
there's
a
lot
of
point
in
trying
to
figure,
you
know
trying
to
write
up
our
own
if
we
can
link
to
something
and
then
the
there
is
that
this
probably
already
existing
tubing.
That
makes
that
easier.
So,
as
an
example,
I'm
familiar
a
little
bit
with
Symantec
released,
so
there's
a
beta
I'm,
not
sure,
if
that,
if
it
does
that
in
the
latest
version,
but
in
the
beta
version
it
does
have
multi
branch
and
maintain
its
release
support
and
it
is
a
tool.
It
is
a
specific
tool.
B
A
A
Certainly,
from
my
perspective,
if
there's
only
one
tool,
it's
it's
not
bad
to
mention
it,
and
even
even
if
we
like
say,
and,
for
example,
here's
one
way
you
can
do
it
with
the
tool
and
somebody
we
could
leave
it
open
to
like
if
there's
some
other
tool
that
people
want
to
PR
in
similar
examples,
so
I
I
think
we
can
handle.
You
know
the
mentioning
it
to
specific
tool
that
way
and
and
I
definitely
agree
if,
if
there's
existing
documentation,
let's
reuse,
but
it
would
be
interesting
to
kind
of
think
through
the.
A
If
there's
like
the
LTS
process
that
we
talked
about,
where
you
know
you
support
a
node,
LTS
version
or
whatever
yeah
working
through
that
and
seeing
you
know
what
it
looks
like
and
what
tools
would
would
be
very
valuable,
so
yeah
it's?
How
do
you
think?
Is
it
best
to
get
started
like
trying
to
do
a
survey
trying
to
write
down
like
we
have
a
good
enough
documentation
of
what
the
process
is
or.
B
Yeah,
so
just
not
sure
right
now,
that's
right!
Okay,
in
case
this
yeah
I
think
there
are
some
notes,
specific
aspects
of
maintaining
a
note,
specific
package
and
maintaining
the
pops4
that
and
because,
as
you
mentioned,
you
know,
there's
the
supporting
LTS
versions
and
just
the
fact
that
if
you
have
an
LTS
version
of
your
package,
you
may
want
to
align
the
release
dates
or
the
support
dates
to
know
that
they
as
support
dates
right
yeah.
Simply
simply
because,
like
if
note
six
drops
off,
you
cannot
drop
note
six
off
without
bumping
major.
B
A
B
B
B
A
A
B
A
A
B
A
You
l
at
the
conference
next
week:
okay,
oh
yeah,
I,
just
wonder
if
we
should
make
it
a
topic
or
not,
but
otherwise
we
should
probably
then
oh
man.