►
From YouTube: 📦Package Managers WG Weekly Sync October 15, 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
Cool
okay,
I
can,
if
that's
so
last
week,
yes,
we
published
the
rc4,
the
new
chase,
ipfs,
that's
very
exciting,
so
we've
got
like
some
missing
missing,
API,
it's
being
implemented
and
some
performance
improvements
for
uploading
stuff
in
the
browser.
It's
going
to
be
added
laser
automation,
so
we
won't
leave
with
examples
that
get
run
and
oh
wow.
It's
tedious
running
those
examples.
A
Through
my
browser,
automation
and
general
general
testing
tasks,
which
is
great
I'm
blocked
on
UNIX
FS,
so
I
was
really
able
to
hopefully
to
be
able
to
do
this
release
that
has
in
a
metadata
in
it
metadata,
but
we're
still
waiting
for
Steven
to
put
his
thoughts
down
on
how
the
metadata
should
get
added
to
the
directory,
and
so
I
can't
really
do
anything
on
that.
So
I've
been
picking
up,
lots
of
joy
I
give
her
stuff,
so
next
up
is
as
part
of
the
async/await
refactor.
A
A
A
Is
there
we're
just
automating
as
much
as
possible
to
say
now,
like
the
only
kind
of
manual
thing
to
do,
is
going
to
be
to
look
into
any
failures
for
running
third
way,
repos
and
then
just
to
gather
feedback
from
early
testers,
which
would
hopefully
be
pre
low
impact.
So
it's
not
going
to
like
consume
someone's
time
like
as
a
full
time
kind
of
thing
which
it
kind
of
hasn't.
Until
now,
that's
awesome,
good
work,
I.
B
B
So
with
those
out
of
the
way,
we
should
now
have
like
confidence
in
the
operations
performing
in
the
pipeline
that
they're
expected
to
work
in,
so
that
should
make
writing
not
like
more
feasible
or
less
feasible,
but,
like
those
will,
we
can
make
guarantees
around
them
and
make
tests
for
them.
That
should
guarantee
things.
B
So,
to
sum
that
up
basically,
the
the
read-only
portions
are
are
good
and
then
the
writable
portions
are
coming
soon
after
and
then
test
for
them
will
follow,
and
hopefully
this
should
be
close
to
being
able
to
be
merged,
at
least
in
an
experimental
stage.
The
read-only
portions
at
least,
and
then
the
right
right
will
follow,
but
yeah,
that's
it
for
me.
I've
got
like
more
detailed
stuff
in
the
notes
there,
but
yeah.
That's
it
any
questions
on
that.
D
B
D
I
guess
I
can
go
next,
I
have
minimal
things
to
say:
I
was
at
Def
Con
last
week,
which
was
very
interesting,
there'll,
be
a
trip
report
shortly,
which
talks
about
some
of
the
takeaways
and
observations
and
conversations
with
people
hallway
track
was
a
big
component
of
it.
But
the
thing
that
I
know
is
still
on
my
plate
from
our
last
meeting
is
sending
intro
emails
to
some
of
the
folks
on
the
package
mentor
side
that
we
want
to
consume.
D
Some
of
these
changes
that
were
were
landing
this
quarter,
and
so
that's
on
my
docket
I
would
like
to
do
that,
but
I
want
to
make
sure
that
the
the
emails
that
I
send
have
kind
of
a
partner
on
the
other
side,
where
it's
like
cool,
like
openSUSE,
like
we
would
like
to
land.
This
thing
here
is
the
person
who
is
working
on
that
thing.
Let's,
like
create
a
closer
tie
of
communication.
D
Do
we
do
we
know
which,
which
one
is
which,
like
his
openSUSE,
the
mound
and
Geeks,
is
unix
sp2,
they're
UNIX
in
a
suit
1.5
and
so
I
intro
Dominic
to
openSUSE
and
I
intro
Alex
to
geeks
I
mean
you
already
know
geeks
as
well
as
I
do
probably
Alex,
but
just
in
terms
of
kicking
off
like
hey.
This
is
what
we're
playing
a
and
next
steps
and
do
we
feel
confident
that
I
should
send
those
emails
now
or
should
I
wait
another
week,
I.
A
Think
until
I
see
geeks
is
requirement
was
the
executable
bit
and
until
we
have
a
story
about
how
I
got
she's
gonna
implement
now
I
wouldn't
I
wouldn't
send
the
email
for
a
business
there's
nothing
to
say,
because
nothing
nothing's
really
changed
for
them.
And
since
since
IP
those
camps,
yeah
I
think
the.
D
B
B
D
Yeah
I
can
totally
wait
another
week.
My
aim
is
to
also
give
them
enough
lead
time
where
it's
not
like
hi.
Please
do
this
right
now,
because
that's
not
always
feasible
for
people
but
you're
right
that,
like
hey,
we
would
like
this
thing
in
like
three
weeks,
is
a
rather
overly
forward-looking
statement,
perhaps,
and
so
we
should
at
least
have
have
a
plan
nailed
down
on
our
end.
We're
like
these
are
the
things
that
we
are
going.
D
We
foresee
happening,
and
this
is
our
high-level
vision
so
to
Alex's
point
we
kind
of
need
the
UNIX
fSV
1.5
stack
at
the
very
least
such
that
we
can
describe
exactly
how
they're
executable
that
would
fit
into
the
mode.
Okay
I
will
then
hold
off
on
my
action
item
for
another
week.
Perfect
glad
I
wasn't
locking
anyone
while
I
was
out
and
we
can
revisit
I'm
moving
this
to
block
done.
D
Cool
chugging
along
I've,
been
watching
Dirk's
continued
progress
on
on
bit
swap
stuff,
I'm
sure
he'll,
give
us
kind
of
an
async
update
and
the
notes
maybe
but
seems
like
continued
improvements
using
the
the
have
and
don't
have
messages
to
optimize,
not
sending
duplicate
blocks,
which
is
snazzy
and
exciting
and
hopefully
well
we'll
get
a
a
sync
update
from
him
on
exactly
all
of
the
thinking
and
experimentation.
That's
gone
into
that.