►
From YouTube: 📦Package Managers WG Weekly Sync March 19, 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
Hello,
welcome
to
the
package
managers
weekly
sink
I
am
a
brain.
I
will
be
your
host
in
the
game
of
what
we
did
last
week,
what
we've
locked
on
what
we're
gonna
do
next
week,
okay
I
have
put
a
link
to
the
pad
in
the
chat.
If
people
who
have
been
accused,
some
updates
could
put
their
updates
on
that.
That
would
be
great.
Would
anybody
like
to
be
a
note-taker
thanks,
ollie
cool,
so
I'll
go
first?
A
So
there's
a
github
issue
with
kind
of
a
write-up
of
the
notes
that
the
took
during
that
meeting,
let's
link
to
from
the
from
the
crib
pad
I,
am
not
blocked
on
anything
next
week,
I'm
going
to
be
in
Lisbon
to
participate
in
the
GUI
and
browsers
hack
and
clown
week,
which
is
gonna,
be
great
because
we
can
have
some
input
into
a
kind
of
package
manager,
II
kind
of
UI
stuff.
That
needs
to
be
done,
of
which
there
is
some
and
I'm
gonna
help
Anna
and
shift
shift
ship
I.
C
B
B
Registries
are
doing,
and
next
week,
I'm
going
over
to
Portugal
as
well,
for
the
Meetup
and
there'll
be
a
good
number
of
people
there
that
are
interested
in
package
managers.
As
well
as
just
after
some
of
the
stuff,
we
talked
about
and
London,
the
idea
of
having
like
an
NPM
desktop
ipfs
NPM
on
ipfs
on
desktop
project
would
be
an
interesting
thing
to
discuss
with
some
of
the
other
web
browser
and
GUI
people,
because
I
haven't
really
looked
into.
B
B
That
is
hardware.
Ok,
I!
Think
that's
about
everything!
Oh
and
the
other
thing
that
I
wrote
up
just
today
is
something
that's
been
bouncing
around
in
my
head
around
how
we
could
potentially
break
the
the
paradigm
that
exists
in
most
package
managers,
where
you
need
an
index,
because
individual
packages
don't
have
any
knowledge
or
context
of
where
they
exist
in
the
world,
and
so
the
issue
is
in
the
crypt
pad.
B
B
D
My
second
point,
which
is
it
sounds
like
there's,
going
to
be
a
lot
of
people
congregating
in
Portugal
next
week
from
across
the
project
and
so
suggestion
either
physically,
while
you're
there
like
make
a
presentation
that,
like
talks
about
the
research
like
aim
it
at
people
who
maybe
haven't
been
following
along
with
this
so
like
go
over
the
categories
and
glossary
and
like
understanding
of
this
is
what
a
package
manager
is
and
what
it
does.
And
here
are
the
different
categories,
but
also
then
feed
that
into
you
like.
D
These
are
the
things
the
problems
we
are
seeing
like
ask
to
this
community
record
it,
and
then,
let's
just
distribute
it
to
everyone
in
the
project,
so
that
we
can
all
use
that
to
feed
into
our
q2.
Prioritization
of
this
is
the
stuff
that
we
need
to
take
on
to
really
deliver
solutions
to
the
problems
that
package
managers
assume.
So
it
sounds
like
something
that's.
A
B
Maybe
it'd
be
interesting
to
try
and
have
it
all
kind
of
ship,
along
with
the
queue
to
kind
of
resulting
okay
hours.
That
might
be
a
good
time
to
be
like.
Oh
here,
is
it
okay,
as
they
happen
to
align
nicely
with
this
group
of
package
management
related
things,
but
also
I,
guess
the
okrs
might
shake
out
more
interesting
things
that
can
align
well
with
like
feedback
into
the
where
package
should
go
next,
no.
A
Sir
I
mean
like
when
to
go,
public
will
be
when
we
can
talk
about
like
what
would
what
would
what
we
wanna
do,
what
we're
gonna
do
and
how
we're
going
to
do.
You
know
we
can
answer
those
kind
of
questions.
Then
it
becomes
a
lot
easier
to
kind
of
tell
a
story
about
what
what
package
managers
on
my
PFS
actually
means.
A
D
Just
like
flip
flip,
the
repo
public
start
putting
the
stuff
out
there
I
think
that
read
me,
you
have
is
already
doing
a
really
good
job
of
like
this
is
what
we're
trying
to
do
and
we're
doing
a
lot
of
learning
about
this
and
we're
gonna
do
work
based
on
it
and
that's
gonna
be
kind
of
landing
as
to
two
hits.
So
that's
my
take
curious.
If
Steve
has
a
different
one,
I
really.
E
Molly
and
I
know
I,
think
I,
even
more
important
to
consider
is
exactly
like
which
audiences
we
want
to
reach
when
we
go
public
right
because,
like
just
moving
a
repo
by
itself,
doesn't
necessarily
do
anything
extra
in
terms
of
like
gathering
information.
It
just
means
like.
We
now
can
I
discuss
on
some
public
forum.
Some
public
venue,
one
of
the
things
that
as
a
whole
project
that
we
need
to
get
better
or
just
get
the
habit
on,
is
actually
using
the
multiple
communication
channels.
Right.
We
have
a
newsletter,
we
have
the
blog.
E
A
blog
is
typically
a
very
useful
resource
because
it
gives
you
like
a
snapshot
in
time
or
like
what
our
thinking
is
in
in
like
what
our
ask
so
the
community
our
until
we
can
then
use
that
blog
to
them
acceded
to
some
other
conversation
that
we
we
want
to
to
bring
to
that
Rico
and
then
well,
of
course,
like
all
delusional
thinking
about
the
next
quarter.
So
having
these
pública
or
making
it
obvious
for
the
community.
E
That
research
exists
so
that
when
the
community
sees
the
conversation
around
okay
arts,
they
can
also
relate
to
these
discussions.
That
are
private
will
be
extremely
important
in
into
yeah
summary.
It's
just
like
whenever
you
feel
ready,
I,
probably
ship
it
early
rather
than
later,
but
but
I
also
probably
do
strongly
consider
like
reading
a
blog
posts
so
that
we
we
have
some
reference
point
to
to
send
to
people.
F
Somewhere
related
to
that
I'm
actually
running
it
right
now,
I'm
getting
all
the
data
from
2015
to
2018
on
the
docker
ecosystem.
So
I
did
a
bigquery
query
to
find
all
the
docker
all
the
repos,
with
docker
files
in
them.
There's
like
four
hundred
thousand
so
now
I'm
getting
like
some
sort
of
that
did.
It
did
an
analysis
on
and
yeah
any
findings
that
we
have.
There
could
probably
be
a
pretty
cool
blog
post
that
people
would
be
into,
and
then
we
could
use
that
to
sort
of
point
at
our
other
package
manager
work.
F
B
B
Also
thinking
of
reaching
different
audiences,
something
that
I've
been
pondering
would
be
to
get
Alex
on
the
podcasts,
the
manna-fest
podcast,
because
that
reaches
literally
that,
like
500
people
that
are
interested
in
package
management
in
the
world,
it
will
require
it's
easy
to
schedule
the
call
and
do
the
recording
it's
the
editing.
That's
a
bit
of
a
pain
in
the
ass,
but
I
can
always
spend
money
on
an
editor,
rather
than
just
wait
for
a
volunteer
to
have
the
time
to
do
it
when
we
would
need
to
get
it
out.
There.
F
That
that's
a
tough
one,
that's
yeah
they're
doing
a
good
job
with
that.
Now,
though,
yeah,
if
you're
interested
I
can
bring
it
up
to
Isaac
I
think
he'll,
be
it
my
daughter's
first
birthday
party
this
weekend.
D
Isn't
a
question,
but
it's
a
pointer,
so
megahertz
has
put
up
two
blocks
of
time
for
doing
this
kind
of
workshop
that
she
and
Matt
designed
around
kind
of
how
to
encapsulate
the
set
of
things
that
ipfs
wants
to
enable
within
package
managers.
I
know
that
Eric
or
Fork
and
Hector
went
through
it
along
with
I,
was
there
for
the
first
half
hour
and
then
had
to
jump
out
like
a
month
or
two
ago,
but
it
generally
was
really
fun
and
it
percolated
a
lot
of
really
good
ideas
and
and
helped
kind
of
structure.
G
Quick
last
one
for
that,
having
been
like
a
ridiculously
good
use
of
time.
Last
time
we
had
some
very
interesting
conversations
and
they
had
some
mechanism
for
conversation.
Guidance
which
didn't
have
anything
presupposed,
but
like
was
very
good
at
drawing
out
the
questions
that
we
already
had
in
our
minds
and
getting
along
paper,
and
it
was
just
it
was
a
really
productive.
Discovering
what
we've
and
wanted
I
was
really
excited
about.
G
G
Like
extremely
like
just
one
layer
under
the
surface,
so
I
think
a
lot
of
that
description
came
up
with
like
one
way
you
could
hang
a
bunch
of
Merkel
trees
around
package
management
and
I.
Think
there's
a
bunch
of
different
ways.
We
could
do
that
and
I
don't
know
if
I
have
a
well-developed
framework
for
how
to
compare
them.
If
we
had
multiple
propositions
like
that
yet,
but
it
would
be
really
cool
if
we
came
up
with
one
and
I
think
megahertz
would
probably
be
really
good
at
helping
us
do
that
as
well.