►
From YouTube: 2022-04-26-Package Maintenance Team meeting
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
Okay,
so
welcome
to
the
node.js
package
maintenance
team
meeting
for
april
26
2022
we'll
follow
the
agenda
that
was
generated
in
the
issue
in
the
repo
which
was
issue
number
524.
A
A
A
Yeah,
maybe
I
have
created
that
since
then,
so
this
is
the
first
time
we're
discussing
it
and
it's
basically
just
the
collaborator
summit.
It's
open
and
ready
for
topics
to
be
submitted.
So
I
just
opened
this
to
say:
hey.
We
should
probably
discuss
whether
there's
like
you
know.
We
want
to
propose
a
session
and
see
if
there's
volunteers,
to
sort
of
lead
and
run
that
session
at
the
collaborator
summit.
A
A
I
guess
the
question
is
is
like
you
know,
is
there
any
topic
that
we
want
to
propose
where
it
would
be
useful
to
do
it
in
person
or
to
do
it
where
you
know?
Maybe
we'll
have
a
broader
audience,
because
that's
sort
of
the
two
things
that
are
going
to
be
different
right
like
one.
It
is
an
opportunity
to
get
into
a
room
for
people
who
are
there
and
then
two
other
people
who
are
there,
who
wouldn't
normally
come
to
our
calls,
might
also
be
interested
if
we,
if
we
describe
it.
Interestingly,.
A
So
I
don't
know
if
how
we
you
know
what
we
gotta
figure
out
is
like
yeah.
Do
we
do
we
think
there's
something
interesting
and
should
we
propose
it
and
then
who
will
propose
that.
C
Yeah,
I
think,
last
time
we
had
the
in-person
summit.
I
remember
we
did
like.
I
think
it
was
kind
of
like
half
trying
to
gather
attention
from
new
people
to
participate.
B
C
Yeah
I'm
just
kind
of
like
coming
back
right,
oh
wow,
but
maybe
yeah.
Maybe
if
there
is
you
know
I
I
would
need
a
couple
more
weeks
to
see
how
much
okay.
A
We
can
leave
it
on
the
the
agenda
for
now
and
if
you
do,
you
know
ramp
up
and
say,
hey,
that's
something
you
want
to
do
just
chime
in
so
I
think
we're
probably
good
if
you
know
if
we
wait
till
the
next
meeting
to
submit
something
or
something
like
that.
But
it
is
we're
getting
closer,
because
it's
only
maybe
five
or
six
weeks
away
now
seems
to
be
coming.
A
Now,
yeah,
okay,
okay,
so
that's!
The
next
issue
was
how
to
accelerate
modernization
of
ecosystems.
So
this
is
number
513.
B
What's
the
what's
the
call
to
action
specifically,
is
it
to
just
update
your
libraries
or
is
it
like
use
newer
language
features.
A
A
B
I
mean
I
I
I
kind
of
directly
have
experience
with
this
because
of
I
did
work
with
email,
js
library,
where
they
were
a
library
that
was
in
the
0.1.8.
You
know
that
kind
of
old
mindset
days
where
it
was
like
written
in
that
really
old
style
of
code.
So
I
did
update
that
library
to
use
typescript
and
stuff
like
that.
B
So
I
mean
that's
the
that's
the
whole
process
like
it's
not
easy
to
do
in
any
in
any
stretch
like
it
takes
a
while,
so
I
mean,
I
think,
that's
probably
the
biggest
blocker
is
like
it's
not
easy
for
people
to
just
adopt
new
features
and
stuff
like
that,
because
they
have
like.
I
had
to
go
through
all
the
legacy
code
and
and
updated
to
use
classes
and
updated
to
use
modules
and
all
this
stuff
and
like
that's,
not
insignificant
changes,
you
know,
so
I'm
not
sure
like.
B
A
That's
where
I,
I
suspect
that
we
asked
three
different
people.
They
wouldn't
immediately
agree
like
this.
You
know
just
reading
through
here.
One
of
the
way,
one
of
the
things
that
might
advocate
is
like
you
know
you
should
stop
using
packages
which
don't
have
that
aren't
actively
being
maintained
right
right.
I
think
some
people
might
flip
sides
say,
but
there's
a
lot
of
those
that
are
just
done.
A
I
hate,
I
hesitate
to
say
it,
but
you
know:
there's
the
there's
the
good
part
of
having
like
four
different
choices
and
innovation,
but
the
flip
side
is
you've,
fragmented,
your
effort,
so
you
have
now
four
things
that
have
one
quarter,
the
investment
or
effort
on
them,
and
so
they
all
are
like
on
life
support
versus.
If
you
only
had
one
and
you
had
the
same
number
of
people
interested
in
them,
you
might
be
much
more
vibrant
and
active
right.
A
So
it
is
an
interesting
sort
of
area
topic
with
no
easy
answer,
but,
like
you
know,
if
you
could
get
everybody
to
agree
that
no
okay,
let's
all
pick
one
some
people
might
say
hooray,
and
maybe
that
is
the
right
answer
right.
Other
people
might
say
no,
no
you're,
killing
innovation
or
something,
but
maybe
there's
something
in
between
that.
If
we
could
come
up
with
we,
it
could
actually
help
the
ecosystem.
In
terms
of
the
approach
yeah,
I.
B
Mean
it
works
on
the
flip
side
too,
because,
like
one
of
the
examples
is
like
q
and
bluebird
that,
where
that
predates
the
native
implementation
and
is
the
basis
for
the
standard
itself,
so
like
the
argument
is
oh,
they
should
usually
switch
the
name
implementation
because
it's
the
native
implementations
out
now
better
versus.
A
C
B
B
Just
be
like
making
decrees
and
all
this
stuff
because,
like
like
I
mean
this,
is
about
maximum.
It's,
like,
I
think,
about
stuff
like
free
speech,
for
instance,
where,
like
court
decision,
save
more
free
speech
is
better
just
because
when
you
try
to
go
the
opposite
direction
like
you,
you
end
up
stepping
all
over
all
sorts
of
thorns
like
it's.
The
same
kind
of
thing
where
it's
like
more
innovation
is
always
better
because
otherwise,
like
it's,
it's
really
thorny.
It's
really
hard
to
say
I
don't
know.
B
E
C
C
A
A
C
Maybe
there
can
be
like
discussions
on
strategies
to
kind
of
like
work
around
or
or
improve
on
some
of
the
problems
they
are
describing
here.
So
let's
say
the
request.
Example
is
a
very
good
one
right
like
it's
one,
that
I
know
like
many
tools
in
the
ecosystem
suffer
from
because
requests
like
that
tends
to
be
like
transitive
dependency
of
a
lot
of
other
tools,
we're
using
so
like,
and
maybe
now
like.
Maybe
there
can
be
like
a
talk
or
something
that
we
can
put
together
like
showing
how
to
use
maybe
npm
overrides.
C
I
know
yarn
also
have
I
think,
resolutions
like
to
basically
alter
your
own
install
tree
so
that
you
can
replace
request
with
some
some
compatible
84
or
just
different
module.
That
has
a
compatible
api
and
you
can
use
that
instead
of
relying
on
a
deprecated
package
right.
So
maybe
we
can
tackle
like
specific
problems
highlighted
here,
but
I'm
not
sure
like
you
can
come
to
a
unified
conclusion
for
for
all
of
these
problems.
A
E
A
A
I
do
know
that
world
events
have
kind
of
interfered
with
the
the
champion
we
had
on
that
front,
so
you
know,
I
think
we
can
leave
it
in
there
and
open.
But
at
this
point
the
main
thing
I
would
say
is
the
you
know
opengs
world.
If
we
do
want
to
do
something
on
this
front,
that's
probably
a
good
opportunity
for
our
next
good
opportunity
to
do
something.
E
A
A
A
I
think
I
think
you
know
you're
right
that
if
we
land
this,
it
addresses
the
initial
sort
of
update
review.
I
think
what
you're
suggesting
is
we
should
document
like
some
activity
requirements.
A
A
You
know
you,
you
need
to
be
involved
in
the
the
meetings
and
or
issues
that
are
taking
place.
I'm
not
meant
you
know
not
that
you
need
to
be
like
me.
Not
everybody
can
make
meetings
but
like
it's,
some
combination
of
those
would
make
sense-
and
I
know
you've
mentioned
just
a
pattern
for
that
across
the
project
would
make
sense.
E
I
mean
yeah,
I
agree
with
that.
I
think
codifying.
That
would
be
good,
and
by
codifying
I
mean
literally
writing
code.
That
does
that
and
sharing
that.
I
think
we
have
some
kind
of
action
that
does
that
in
tsc.
A
A
Now
I
don't
think
we
don't
have
votes
so
often
here
you
know,
I
think,
even
something
as
simple
as
you
know,
comments
and
issues
and
or
involvement
in
the
meetings
would
be
would
be
an
equivalent
right,
yeah.
E
I
think
comments
and
issues
opening
pr
is
often
issued
like
authoring
issues.
Authoring
prs,
commenting
and
attendance
in
meetings
is
chill.
A
And
I
think
I
think
so
like,
like
you
said,
like
actually
writing
automation.
That
would
do.
That
would
be
fantastic
and
even
better
if
we
had
some.
I
think
that
automation
would
apply
to
any
working
group,
and
many
working
groups
would
probably
say
alex.
Let's
take
that,
but
I
think
before
you
turn
on
the
automation,
you
need
to
still
update,
like
our
readme,
to
say
this
is
the
membership.
So
if
somebody
wants
to
pr
in
a
suggestion
for
that,
I
think
that
would
be
kind
of
a
next
step
on
that
front.
A
I'll
I'll
I'll
leave
it
out.
If
anybody
wants
to
volunteer
just
opening
it,
you
know,
I
basically
say
just
open
a
pr
that
has
the
suggestion
with
it
and
we
can
use
pretty
easily.
I
think
discuss
them
in
that
in
that
issue
or
pr.
A
So
two
things
is
we'll
try
and
get
the
that
initial
pr
landed
and
I'm
actually
going
to
find
that
again
and
paste
it
into
the
issue
here.
If
I
can
write
this
one
here,
so
try
and
get
that
initial
one
landed
and
then
the
next
step
would
be
like
yeah.
We
could
put
in
some
minimum
activity
requirements,
and
then
you
know
after
three
months
or
whatever
you
know
we
can
even
manually
review
them
or
you
know.
Ideally,
the
automation
is
even
better.
A
Okay,
the
next
one
is
number
458
status
and
update
status,
update
and
next
steps
for
pkgs
create.
A
B
I
I
had
been
trying
to
work
on
it,
but
I
don't
have
free
permissions.
I
had
a
issue
that
opened
a
while
back
and
I
posted
that
in
the
link
in
chat.
A
All
right,
so
let
me
find
that
thanks.
So
I'm
going
to
put
that
there
and
then
I'm
going
to
look
at
your
number.
79
right
is.
A
D
A
And
so
I'll
do
that
and
I
will
send
michael
to
send
email
to
to
rest
of
the
we
have
like
an
instead
of
admin,
members
for
the
pkgs
pkg
js,
so
I'm
just
going
to
send
an
email
saying
hey.
This
is
what
I
suggest
anybody
have
any
concerns.
A
If
I
don't
hear
anything,
I
will
just
go
ahead
and
do
it
then
after
that,
so
I
guess
what
I'll
say
is
I'll.
Try
I'll
put
that
on
my
list.
If
you
don't
hear
anything
within
like
I'll,
send
the
email
after
a
meeting
today
and
if
you
don't
hear
anything
from
me
say
in
like
next
wednesday,
just
ping
me
again
because,
like
that
you
know
I'll
do
my
best
to
remember.
A
But
if
you
don't
that'll,
be
my
reminder
to
go
back
and
look
and
say:
yeah,
okay,
nobody
responded
I'll
turn
things
on
sound
good,
yeah
I'll
bring
you
in
the
issue.
Okay
sounds
perfect.
A
E
A
Okay,
well,
yeah.
I
know
I
got
enough
there
like
that's
my
e.
I
don't
necessarily
get
rid
of
them
all,
but
it's
like
okay.
What
do
I
have
to
respond
to
and
I
try
and
do
that
every
day
or
two
days
so,
whereas
the
notifications,
I
do
try
and
do
it
every
week,
but
it's
pretty
hard,
sometimes
so
the
suggested
list
of
modules
to
get
help
support
on.
I
just
no
update,
I'm
just
going
to
say
no
update
on
that
this
week.
A
I
guess
I
still
haven't
totally
abandoned
that,
so
I
leave
it
on
the
agenda,
but
I
haven't
done
anything
so
and
that
takes
us
to
the
end
of
what
was
on
the
agenda.
Is
there
other
things
or
topics
that
people
want
us
to
talk
about
or
think
we
should
talk
about
this
week?.
E
I
I
do
have
an
issue
that
I
created
on
march
10th
that
I'd
I'd
like
to
bring
up.
I
don't
think
we
need
to
necessarily
go
over
it
like
fully
in
this,
but
at
least
getting
eyes
on
it
would
be
nice
sure
which
one
it
is
issue
517
and
package
maintenance.
I
can
drop
a
link
in
chat.
E
But
yeah
this
is
this
is
an
issue
I
I
began
working
on
a
project
to
help
kind
of
automate
updating
engines
in
package.json,
and
I
tried
using
envy
as
as
a
tool
for
that
and
part
of
nv
is
the
aliases,
and
I
I
in
in
doing
that
work.
I
basically
realized.
E
I
had
to
rip
out
envy
because
partially
because
of
me
and
partially
because
of
the
aliases
the
aliases
currently
aren't,
particularly
they
don't
cover
everything
and
they
don't
fully
they're,
not
neutral
in
how
they're
written
so
they
they
can't
be
used
easily
or
as
easily
in
like
the
command
line.
I
believe
is
it's
been
a
while
since
I've
gone
through
this,
but
there's
a
specific
reasoning
of
why
I
think
the
underscores
are
challenging.
E
And
v
envy
is
like
the
letter
in
the
letter
v,
that
is,
the
pkgs
node
versioning
data
right.
E
So
that
data
set
is
also
it
doesn't
correctly
fully
correctly
represent
the
data
that
it
should,
but
outside
of
that,
the
aliases
are
particularly
challenging.
I
outlined
the
reasons
here:
I'm
not
gonna,
not
gonna,
basically
regurgitate
the
issue,
but
yeah
going
through
this.
I
I
propose
some
updates
to
how
package
support
names.
The
aliases.
E
And
kind
of
provide
a
little
bit
more
coverage
a
little
bit
more
of
a
composable
way
to
get
versions
out
of
those
aliases.
That
is
more
straightforward,
because,
right
now,
it's
basically
a
matrix
and
that
matrix
you
can
just
have
with
a
single.
You
can
recreate
that
matrix
with
a
single
set
of
names
which
dramatically
reduces
kind
of
the
developer
overhead
that
you
have
to
have
for
this.
You'd
have
to
have
a
lot
less
context,
and
it
brings
it
a
lot
closer
to
what
the
naming
structure
that's
supported
by
the
release.
A
E
A
Right,
yep
yep,
so
I
think
the
you
know
what
would
be
interesting
and
make
it
easiest
for
me
to
understand
is
like
how
would
it
affect
like
basically
you're
looking
at
this
table,
which
there's
the
node
name
space?
Okay
right?
A
E
I
mean
that
would
by
the
naming
I
propose
it's
that
would
be
eol.
E
That
is,
that
is
the
difference,
because
I
think
there
are
situations
where
you
want
the
latest
lts,
which
is
different
from
active,
because
multiple
release
lines
can
be
active,
but
it
is
not
necessarily
the
latest
like
in
a
situation
where,
like
16
and
14,
can
both
be
active,
but
lts
or
16
is
technically
latest,
and
I
don't
know
if
that's
true
presently,
but
that
there
is
a
world
in
which
that
has
happened.
A
Right,
the
first
question
I
I
want
to
double
check
is
like
these
were
intended
to
be
what
you
intend
to
support
right:
yep,
yep,
okay,
so
it's
still
in
that
context.
It's
like
100,
it's
not
not
current
versions
but
like
k
as
a
module
owner.
My
supply
and
descent
intends
to
support
everything
or
I
intend
to
support
just
some
other
things.
A
E
End
of
life
right
like
that,
is
one
to
one
end
of
life.
They
are,
they
are
not
something
we
will
support
or
maintain
period,
so
everything
under
I
think
10
and
under
right
now
or
11
and
under
I
guess,
is
eol,
which
is
would
consider
be
considered
abandoned.
E
So
like
we're.
We're
also
kind
of
part
of
this
issue
is
we're
also
worsening
the
the
complication
that
we
currently
have
of
release
lines
and
naming
people
already
struggle
with
the
concepts
of
lts
and
how
we
define
these
different
things
and
so
adding
an
additional
like
basically
making
it
a
matrix
only
like
amplifies
that
it
exacerbates
that.
So
what
well.
A
E
E
I
feel
like
it
doesn't
fit
here,
then
I
don't
think
abandoned
should
be
in
the
no
name
space.
If,
if
that's
what
that's
representing,
because
I
honestly
I
don't,
I
don't
think
I
looked
at
that
line
like
I
was
not
paying.
E
To
that
line
at
all
that
one
doesn't
I
don't
think
that
fits
at
all
in
the
name.
A
E
A
Yeah,
I'm
just
looking
for
the
you
know,
maybe
that,
as
we
went
through
the
different
versions
of
defining
things
yeah,
so
we've
got.
This
is
under
the
support
turn
now.
This
is
under
the
standards
right.
So
this
isn't
a
support
target.
So
we're
basically
saying
the
platform
versions
of
the
okay
right.
E
B
E
A
E
So
right
now,
my
proposal
is
to
change
this
to
current
lts
latest
lts,
active
lts
maintenance
and
eol.
Just
have
five
things
all
of
the
and
have
that
b.
Have
that
be
like
a
composable
matrix
right,
so
anything
in
this
matrix.
Currently,
as
you
can
see
by
the
check
marks
with
the
you
know,
the
exception
is
there
would
be
an
additional
column,
basically
conceptually
of
lts
latest,
which
is
just
the
latest
version
of
lts
right.
E
So
the
newest
lts,
which
in
my
experience,
is
what
a
lot
of
people
do
pin
to
so
I
think,
there's
extreme
value
in
having
that
scope.
The
set
of
those
five
map.
All
of
these
values
can
be
expressed
by
those
five.
So
given
that
there
is
a
more
limited
set
that
is
more,
what's
sort
of
expressive,
I
think
having
the
ability
to
kind
of
have
that
easier
expression
or
better
expression.
E
More
concise
expression
is
probably
a
better,
a
better
goal
for
us,
but
yeah.
So
everything
here
can
already
be
expressed
by
any
of
these
five
options
in
an
array.
E
Them
yeah,
so
each
one
of
them
is
in
in
a
single
thing.
You
can
also
just
specify
a
single
thing
with
how
I've
defined
a
mirror.
You
can
just
specify
current
you
can
just
specify
latest
it
allows
you
to
then
also
have
it
be
a
little
bit
more
composable
and
have
it
be
cool.
I
want
current
and
lts
latest
like
there
are
people
who
want
that,
and
that's
not
currently
possible,
like
you
can't
do
that
with
how
this
is
defined.
A
B
E
So
I'm
I'm
kind
of
not
saying
we
should
rename
it.
I'm
saying
we
should
change
it,
because
I
I
do
not
believe
that
this
structure
particularly
works
in
the
way
that
it's
intended
to,
and
I
you
know
I
outlined
that
in
here.
So,
like
an
example,
you
can't
say
there's
a
way
to
say
that
you
only
support
maintenance,
lts
versions,
like
maintenance,
isn't
in
here,
and
I
think.
E
Sure
it's
same
for
eol,
which
then
like
you're.
Getting
to
the
point
where
you're
just
like
this
matrix
is
dramatically
increased
complexity
for
something
that
can
be
much
simpler
and
I
think
that's
what
I'm
trying
to
push
for
is
instead
of
adding
to
this
and
making
it
more
complex,
stripping
stepping
back
a
little
bit
and
reducing
complexity
in
favor,
of
helping
people
kind
of
express
what
they
want
to
express
easily.
A
Yeah
I'd
be
interested,
I
think
I
think
that,
like
we
should
get
feedback
from.
A
Oh
and
from
dominicus,
because
I
think
he
was
using
this
in
the
like-
he
had
some
things
to
help
you
get
testing
automatically
in
ci,
so
there's
already
templates
out
there.
That
would
use
these
to
say
like
if
you
said
hey,
I
want
to
support
lts
it'll,
then
in
your
github
actions,
and
it
was
originally
on
travis
help.
You
get
things
that
will
test
on
those
versions
and
update
them.
A
A
E
For
sure
the
other
thing
is,
I
have
also
built
tooling
around
my
proposal.
I've
like
regardless
of
whether
or
not
it's
adopted.
I
I
pretty
strongly
prefer
mine
my
proposal
as
like
a
way
to
communicate
note
versions,
so
I
built
my
own
tooling
around
this,
I'm
happy
to
transfer
that
in
if
that's
something
the
project
wants,
but
I
built
my
own
tooling
around
this.
That
also,
you
know,
is
again
used
by
that
engine.
E
Sync
tooling,
that
allows
you
to
update
engines
automatically,
so
that
tooling
is
available
and
I'm
happy
to
make
changes
and
share,
give
it
to
the
project.
If
it's
something
that
you.
E
It
relate
to
this,
so
no,
it
is
more
specifically
a
replacement
or
not
necessarily
a
replacement,
but
a
parallel
to
nv.
It
does
the
calculation
automatically
it
and
it
also
delivers
more
information
and
it
delivers
it
more
correctly
than
mv
does
and
v
has
some
problems
around
its
api
that
I
created
issues
for.
A
E
If
I
mean
to
yeah
for
sure,
I'd
be
happy
to
more
than
happy
to
help.
Why
is
my?
My
keyboard
is
like
typing
in
latin
characters?
Sorry
yeah
I'd
be
more
than
happy
to
help
update
the
support
package.
If
this,
like
I'm
happy
to
take
on
that
work,
if
this
proposal
is
accepted.
A
E
I
mean
it
would
be
it's
almost
like
literally
like
I
said,
the
the
five
I
provided
are
a
one
to
one
like.
There
is
combinations
of
them,
basically
like
think
of
it
as
an
array,
rather
than
as
a
string,
there's
combinations
of
them.
That
would
are
one-to-one
mappings
of
the
other
options
that
are
currently
available
yeah.
So
that's
that's
trivial.
Almost
like
that's
a
few
hours
of
work.
A
Right
and
so
okay,
it's
almost
I
mean
it's
almost
like.
If
that's,
if
the,
if
it's
basically
like
now,
it's
going
to
be
an
array
or
like
it
could
be
updated
to
say
this
could
be
a
single
value
or
an
array,
and
that
doesn't
break
anybody
right,
because
if
it's,
if
it's
a
single
value,
it's
still
valid
and
then
if
there
were
these
existed
as
aliases
for
multi-value
ones.
E
Yeah
one
thing
the
thing
I'd
say
is
the
the
dx
of
that
would
be
really
bad
because
you
have
they're.
Basically,
the
some
of
them
are
the
same
words
because
of
how
it's
currently
defined,
like
I
think,
like
lts,
underscore
active
versus
lts,
active
or
dash
active
where,
like
that
concept
exists
in
both
and
so
that'd
be
confusing
for
users
and
that's
dx,
I
wouldn't
I
I
wouldn't
recommend
anyone
actually
adopt
just
because
it's
it
ends
up
getting
really
confusing
of
well.
E
A
A
E
Fully
support
that
yeah.
I
totally
support
that
and
I'm
fully
on
board
with
that
and
I'm
happy
I'd
be
happy
to
implement
that.
I
think,
additionally
like
having
a
simple,
I'm
not
familiar
with
the
support
module
but
like
update,
like
I
guess,
looking
at
the
examples.
Npx
pkgis
support,
slash
or
slash
support
and
then
running,
update
or
like
validate
or
something
like.
A
A
If
we
can
figure
out
that
I
know,
there's,
maybe
not
a
huge
number
of
people
that
have
used
it,
but
like
there's
enough
that
it
would
be
nice
to
have
a
you
know,
we
didn't
throw
out
all
the
old
stuff
yep,
and
I
it
sounds
like
that.
Actually,
from
what
you're
saying
should
be
pretty
straightforward
is
like
these
would
just
be
alias
to
an
array
now
right.
Somehow
yep.
E
A
A
E
And
also
providing
like
a
github
action
that
people
can
throw
in
and
say
like
this
is
the
thing
to
check
automatically
and
automatically
apr
and
update.
If
there
is
one,
I
think
is
also
good
for
the
future.
B
E
Myself,
I
don't
know
if
jordan
committed
to
any
of
them,
but
I
think
jordan.
They
seemed
to
make
sense
to
jordan
earlier
in
my
discussion
with
him.
So
so.
A
E
Set
and
yeah-
and
I
also
think
the
other
additional
benefit
of
this
is
this-
is
the
array
or
the
kind
of
five
that
I'm
proposing
are
almost
like,
with
the
exception
of
lts
latest
they
are
one-to-one
of
what
node
does,
which
I
think
is
very
important
in
terms
of
actually
helping
the
ecosystem
have
better
understanding,
because
that
is
consistently
every
time.
I
talk
to
someone
the
number
one
thing:
they
don't
understand,
sorry
for
the
language,
but
they
don't.
E
They
do
not
understand
it,
and
it's
very
hard
and
like
lowering
that
barrier
would
be
really
really
helpful.
I
think
and
like
providing
more
more
exposure
to
that,
would
be
really
helpful
across
the
ecosystem
to
help
people
kind
of
address.
That
and
right,
you
know,
get
to
that
point.
So
yeah.
A
I
I
I
have
to
run,
unfortunately,
but
I
think,
like
the
one
other
comment
was
there's
a
few
of
these-
that
weren't
necessarily
a
one
like
they
were
meant
to
be
lts
actually
says:
there's
a
few
more
things
in
there.
So
we'd
have
to
think
about
that.
But
if
you
put
a
pr
like,
I
think,
a
pr
that
shows
what
we
just
talked
directly
to
this
dog,
that
file
okay,
yeah.