►
Description
Meeting description here:
https://github.com/ipfs/team-mgmt/issues/992#issuecomment-590306671
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
Good
evening,
everyone,
how
are
you
doing
all
right,
we're
recording
this?
Is
the
ipfs
core
implementations
weekly
sick?
It
is
the
24th
of
February
2020
I.
Am
your
host
for
today
here
put
your
name
in
the
attendees
list.
I
just
asked
you
to
do
that,
but
I'm
gonna
ask
you
again:
Jacob
has
volunteered
to
be
the
note-taker
Thank
You
Jacob,
that's
super
cool
and
we
will
get
on
with
what
we
normally
do
and
what
we
normally
do.
A
Is
we
go
through
our
high
priority
initiatives
and
share
updates
on
those
we
also,
if
you
have
a
sink
updates
for
what
you've
been
working
on,
then
please
add
them
to
the
end
of
the
document.
We
won't
go
through
them
in
this
meeting,
but
it
means
that
everyone
can
share
what
they've
been
on
and
we
can.
We
can
look
at
it
asynchronously
and
ask
questions
if
we
need
to
later.
So,
let's
get
back
to
it.
High
priority
initiatives
are
my.
My
thing
is:
jumping
around
people
are
adding
stuff
at
the
rate
of
knots.
A
A
Finally,
which
is
cool,
and
since
then
I
think,
we've
actually
released
a
bug
fix
anyway.
So
a
number
of
chip,
and
so
the
highlights
from
that
is
that
async/await
refractor
finally
got
shipped.
If
you
have
been
paying
attention
at
all,
then
you
will
know
that
it
has
been
a
big
refactor
to
the
code
base,
which
leaves
us
with
asa
weights
style
code
and
spacing
intervals
by
default.
That's
super
cool.
A
There
is
a
release,
blog
post,
which
also
links
to
another
big
blog
post,
where
we
explain
what
all
those
changes
actually
mean
and
the
other
highlight
is
unix
FS
version
1.5,
which
is
now
in
there.
So
you
can
now
add
metadata
to
your
files
as
you
import
them
and
when
they
come
back
out
they
still
have
metadata.
So
that's
that's
super
cool
for
a
number
of
reasons,
which
is
also
explained
in
a
reflog
post.
So
you
guys
should
go
and
check
that
out.
A
C
B
B
This
should
work
99%
of
the
time
once
20
percent
networks
upgrade
it
and
move
it.
Five
nines
one,
forty
five
percent
of
the
network
has
operated
and
the
convicted
sister
knows
other
than
that.
We
also
have
the
housing
news
to
work
on
this
ground.
We
have
some
concerns
around
lambdas
APNs
between
to
fix
to
figure
out
a.
B
C
A
Cool
I
also
likes
the
addition
of
a
little
walking
tour
of
New
York.
At
the
same
time,
alright,
let's
move
on
then
sub
the
main
gate,
mail
gateway
Lydell.
Would
you
like
to
give
an
update
here.
B
B
A
F
So,
on
the
main
gateways
front,
not
much
happened.
I
was
at
idea
fasting
week.
Her
I
plan
to
learn
this
here,
make
it
ready
for
review
this
week.
Hopefully,
what
we
must
be
done
is
to
finish
writing
tests
basically,
and
we
want
to
land
it
with
ship.
It
will
go
back
with
us
open
five
during
her
to
fasting
week.
We
we
got
agreement.
F
The
short
version
is
that
we
will
be
upgrading
output
if
the
IP
ceoddi
on
the
output
would
be
that
console
or
some
other
means
like
web
service,
API
API.
If
it's
CA
DB
0,
we
would
automatically
upgrade
output
to
see
adv
one
in
Bedford.
It
will
be
the
same
multi
harsh,
no
changes
of
internal
tag
and
if
someone
passes
Darcy
ID
version
1
like
explicitly
that
will
not
only
make
that
will
and
for
force
use
of
CID
p1
in
entire
Doug,
changing
not
only
dark
but
also
like
enabling
reliefs.
F
A
F
A
B
B
G
C
A
Thank
you
all
right,
in
which
case
is
anyone
have
any
questions
for
Peter?
First
of
all,
okay,
all
right.
So
we
have
finished
our
list
of
important
top-level
initiatives.
We
have
other
initiatives
that
I'll
just
read
out
the
titles
quickly.
If
anyone
has
any
updates,
then
shout
out
as
I'm
doing
it
and
we
can
do
it,
but
we
have
eunuchs
if
that's
one
point:
five
adding
performance.
A
G
A
A
A
All
right,
in
which
case
I,
think
we're
pretty
much
done.
This
note
stock
will
be
pool
requested
to
the
team
management
repo,
where
you
can
look
at
other
people's
async
updates
and
put
comments
on
them
and
ask
questions
if
you
so
need
to,
but
otherwise
thank
you
very
much
for
attending
everyone.
You
may
have
some
of
your
time
back
now
of
your
day
and
I'll
see
you
next
week
for
another
exciting
installment
of
ipfs,
core
implementations,
weekly
sync
goodbye
for
now.