►
From YouTube: 📦Package Managers SIG Weekly Sync May 21, 2019
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
Was
perfect
and
the
mini
step
on
stage
no
IP
address
I
think
I've
been
running
it
repeatedly,
just
to
make
sure
that
it's
still
actually
work,
which
meant
there
was
no
question
yeah
at
first
we
say
so
very
everyone
was
very
happy
split
some
people.
Afterwards
they
were
very
excited.
I.
Try
to
you
know
plug
that
placate,
APR
and
I
hope
that
they
comment
on
the
issue
and
maybe
get
a
bit
more
attention
to
that
and
get
that
merge.
Yeah,
but
yeah.
That's
still
ongoing.
A
So
next
up
is
look
at
the
performance
of
the
async/await
refactor.
More
specifically
for
package
manager
is
to
try
and
update
and
like
it,
NPM,
unlike
the
first
barrel
of
update
video,
so
he
first
version
undependable
I've
got
access
to
ECS.
Now
so
I
can
deploy
on
a
scalable
cluster
rather
than
just
like
one
machine,
that's
prone
to
falling
over
occasionally,
so
that's
going
to
be
super
good
I
will
say:
let's
start
talking
about
bringing
MPM
in
a
box
to
ipfs
camp
using
quite
nice.
A
D
Sorry,
I
only
just
finished
writing
my
own
notes
in
the
grip
pad
I
have
been
doing
two
different
things.
I
guess
mostly
I
finished
off
the
writing
up
my
research
into
more
decentralized
publishing,
work,
kind
of
come
up
with
a
couple
of
terms
around
making
resolution
resilient
to
availability
problems
in
individual
registries,
whether
that
be
someone
deleting
something
or
the
registry
no
longer
being
available
or
you
being
offline
or
behind
a
corporate
firewall.
D
That's
linked
up
with
about
some
of
those
topics.
A
little
bit
more
I.
Also,
then,
did
some
brainstorming
on
what
decentralized
publishing
on
MPM
would
look
like.
So
from
kind
of
the
initial
steps,
basically
trying
to
take
everything
that
alex
has
already
been
doing
as
part
of
the
packet,
a
patch
and
say
like
well
from
basic
starts.
Where
does
that
lead
you,
which
then
I
actually
kind
of
like,
went
through
and
tried
to
do
and
try
to
publish
something
myself
today
and
to
reuse
it
from
level
one
to
four
turns
out
level.
D
D
If
you
try
and
pass
anything
that
isn't
just
a
name
to
npm
install
or
you
put
it
in
your
package,
jason
and
say
NP
install
from
my
package
jason
if
it
looks
like
a
URL
or
a
git
path
like
a
URL
identified
to
a
git
resource
or
a
local
file
path,
it
will
basically
always
expect
there
to
be
a
package
jason
in
whatever
it
gets
back.
So
if
you
give
it
the
URL
to
a
packer
meant
it
goes.
Oh
there's
no
package
jason
here
this
doesn't
work.
I
wasn't
expecting
the
adjacent.
D
D
The
ipfs
camp
and
I've
got
a
couple
more
of
those
I
think
a
couple
I
want
to
say
coming
on.
Friday
and
I
also
have
yet
to
get
round
to
merging
all
of
the
issue.
Documentation
stuff
in
the
package.
Managers
repost
I-
definitely
want
to
get
that
done
and
other
than
that
I'm
fairly
open.
So
if
anyone
wants
to
try
and
put
something
on
my
plate,
that
needs
investigating,
otherwise
I
will
go
and
I
have
not
thought
too
much
about
what
else
I'll
be
up
to
this
week.
C
Like
you,
I
just
finished
taping,
in
what
I
did
this
week,
yeah
honestly,
not
a
tremendously
productive
week,
I
apologize,
we
cleaned
up
the
github
labels,
finally
got
rid
of
waffles
automatic
in
progress
thing,
because
waffle
is
dead.
If
any
of
you
are
interested
in
the
what
replaces
waffle
discussion
hit
me
up
and
I
can
point
you
toward
a
long
series
of
comments
and
a
github
issue.
All
right,
Andrew
I
will
find
those
for
you
and
send
it
to
you
yeah
your.
E
B
Whole
lot
updates,
I,
guess
over
in
I,
guess
ipfs
in
web
browsers
land
and
still
experimenting
with
web
package
and
I
enhance
that
it's
not
quite
a
demo
yet,
but
I've
got
like
a
little
web
extension
that
that
intercepts
when
you
click
on
things
in
the
domain
and
it
loads
websites
that
have
been
distributed
using
this
HTTP
signed
exchanges,
which
is
a
google
chrome,
feature
yeah,
and
so
it's
pretty
neat
but
there's
a
tricky
thing.
Niroula
is
a
demo
because
I
have
to
keep
purchase.
B
C
I,
don't
even
know
where
I
found
that
link
to
February
I
thought
so
yeah
refactor
the
github
labels
a
bit.
If
anybody
cares
to
know
about
the
replacement
for
a
waffle
discussion,
if
that
is
a
route,
that
thread
is
relevant
to
any
of
your
interests.
Let
me
know,
and
I
can
show
you
in
the
direction
of
that
discussion-
sort
of
an
interesting
one,
a
few
minor
edits
to
the
the
cladistics
tree
diagram,
the
next
step
on
Andrew.
You
had
a
good
point
about
seeing
how
that
overlaid
with
here
integration
levels.
C
C
Vincent
talks
about
the
road
maps
in
the
ipfs
camp,
which
will
continue
doing
moves
to
angry
cats
2,000
miles
and
this
week
again
just
want
to
I
think
my
big
focus
this
week
is
whatever
I
can
do
to
help
facilitate
all
of
us
figuring
out
what
we
want
to
do:
visa
Vee,
NPM
and
ipfs,
or
some
other
thing
for
the
camp
and
sort
of
a
more
immediate
sort
of
tactical
roadmap
for
the
next
two
months.
I
think
is
probably
the
most
important
thing
to
figure
out
this
week.
D
One
other
thing:
I
forgot
to
mention:
I,
also
collated,
a
long
list
of
package
manager,
related
academic
papers,
half
of
them
I
already
collected
and
stored
locally
in
some
notes,
and
then
I
was
going
through
and
for
me
like
this
would
be
useful
to
other
people.
It
turns
out
very
useful
lots
of
people
on
Twitter
seem
to.
C
E
A
F
No
I'm
just
joining
in
because
I'm
interested
in
the
work
that
you're
doing
and
so
I
think
the
use
case
of
publishing
snapshots
versions
of
software
and
then,
depending
on
the
cheap
shots
and
keeping
the
pendulum
depending
on
it.
Even
though
it's
free
might
have
deleted
it,
those
kind
of
situations
if
they
could
be
really
nice.
D
I
guess
you
need
to
make
sure,
there's
a
good
amount
of
kind
of
long-term
archiving
effort
to
keep
those
things
there.
It's
easy
to
to
do
the
ad,
but
there's
not
necessarily
always
going
to
be
someone
connected
that
has
all
of
those
old
archives,
but
maybe
foul
coin
will
eventually
encourage
people
to
keep
those
things
around
well.
F
D
Yeah
I
definitely
agree
that
it
feels
like
there's.
A
lot
of
people
expect
someone
else
to
be
responsible
for
their
own
open
source
packages
and
encouraging
people
to
take
a
little
bit
more
responsibility
without
it
being
as
long
as
it's
not
painful
to
do.
If
it's
easy,
then
I
think
a
lot
of
people
and
businesses
already
do
this.
They
recognize
the
risk
and
they
will
buy
into
price
Oh
waiting
for
them.
But
there's
no
reason
why
individuals
and
smoothly
the
same
thing.
D
B
I'm,
not
topic
I,
just
think.
There's
a
broad
areas:
UX
research,
that
that
probably
falls
on
our
what
we're
we're
we're
working
it
both
health
indicators
and
like
how
can
you
be?
How
can
you
communicate
to
the
user
that
you
know
the
content
that
they
can
use
today
they
can
use
tomorrow,
or
can
they
rely
on
it
to
be
available
into
the
future.