►
From YouTube: ⒿⓈ⚡️ js-ipfs Core Dev Team Weekly Jan 29, 2018
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
All
right,
cool,
okay,
so
recording
so
welcome
everyone
to
that
first
or
to
the
first,
as
we
reset
the
counter
JSF
EFS
core
dev
team
weekly
hang
up.
The
purpose
of
this
call,
or
the
reason
why
we
are
bringing
these
calls
back
is
so
that
we
can
find
we
can
understand
where
everyone's
minds
are,
that
we
can
understand
what
are
our
priorities
and
if
we
can
adjust
our
priorities
in
and
then,
if
I,
what
what
people
are
being
blocked
on,
so
that
we
can
unblock
them
faster.
A
Exactly
exactly
we.
We
don't
do
it
daily
because
it's
really
expensive
on
people's
time
to
do
a
daily
distributed,
stand
up,
but
we
have
experimented
with
weekly
and
worked
pretty
well
in
the
past
and
yeah
like
we
can
always
adjust
and
I
understand.
This
still
works.
It's
still
the
right
pattern
and
upgrade
until
I
posted
here
the
link
to
the
with
the
agenda
for
today.
A
A
A
All
right,
so
I
kind
of
already
went
through
the
first
item.
The
agenda
like
what
are
the
goals
with
this
call
so
far
so
good,
like
everyone,
everyone
cool,
so
the
way
that
I
expect
these
calls
to
function
is
again.
We
do
a
run
all
updates.
Everyone
says
what
they
have
accomplished
last
week.
We
just
like
we
let
people
describe
what
they
got.
What
and
what
they
want
to
work
on.
A
Next,
after,
like
everyone
gets
the
chance
to
share
these
three
things,
we
will
make
sure
like
we
all
just
like
review
it
and
make
sure
that
we
all
agree
that
those
things
are
the
most
important
and
we
have.
If
we
have
time
left,
we
will
just
go
to
the
waffle
board
and
identify
issues
that
are
top
priority
that
we
probably
should
be
thinking
about,
but
like
no
one
is
thinking
about
then,
and
just
to
give
you
like
view
into
what
is
our
waffle
board.
B
A
Okay,
I
see
some
people
smiling
so
I
guess
it's
the
first
time
is
that
am
I
reading
it
correctly.
Okay,
all
right
so
perfect,
I
just
wanted
to
make
sure
that
people
were
familiar
with
the
waffle
board.
And
so
let
me
explain
how
we
organize
our
issues
in
the
just
a
previous
project.
We
we
have
five
columns
in
box
backlog,
ready
in
progress
and
done
all
the
issues,
all
the
peers
that
get
created
to
the
project
and
we
are
tracking.
Initially,
we
are
tracking
every
single
repo
on
the
just
because
project.
A
So
it's
from
just
the
top
level
module-
and
you
can
see-
there's
like
a
leaf
stuff
here-
there's
no
tea
formats.
There
is
ipfs
leap,
your
peers
are
tracked
here.
We
peer
to
peer
instructor
and
on
its
own
waffle
board,
and
you
can
access
it
by
replacing
whip.
It
appear
and
well
J
asleep.
It
appear
I'm
not
going
to
do
that,
because
the
waffle
born
dance
and
like
I
guess
you
will
see
this
now.
Okay,
this
is
fast
because
we
have
attached
so
many
reproves
to
one
waffle
board.
A
Sometimes
you
might
experience
a
waffle
board
to
take
a
little
bit
of
time
to
load
and
so
be
careful
with
opening
and
closing
off
work
like
once
you
load
it.
You
know
and
just
to
keep
it
open
and
because
all
the
updates
that
follow
will
happen
in
real
time
and
you
can
see
like
the
way
she's
moving
from
these
columns.
So
everything
that
gets
open
goes
to
inbox
from
the
inbox.
Typically
I
do
the
work
of
reviewing
the
issue
and
assigning
things
like
priority,
and
you
can
see
these
labels
p1
p2.
A
Well,
there
are
others,
it's
like
frumpy
before
so
p0,
the
most
critical
most
urgent
before
last
critical,
please
Arjun!
Some
of
these
issues
get
tagged
with
difficulty
when
it
is
possible
and
of
course,
difficulty
hard
difficulty
easy
difficulty,
but
it
is
really
just
like
best
guess
for
me,
and
it
is
basically
my
way
of
telling
everyone
that
is
following
the
project:
hey.
A
There
is
an
issue
that,
given
the
understanding
of
the
whole
stack
of
ipfs,
should
not
take
you
too
much
to
figure
out
if
it's
difficulty
easy
and
my
my
expectation
is
like
if
there
is
an
issue
with
that
label,
I
should
take
you
less
than
a
morning
like
you
should
not
be
f2
like
here
over
10
repos.
You
should
not
have
to
do
like
very
complex
setup
stops.
It
should
be
something
that
is
contained
at
back
in
the
West.
In
like
four
hours,
you
should
be
able
to
tackle
that
issue.
A
I
understand
what
is
the
problem
at
hand
and
tackle
that
issue?
There
is
a
an
extra
level
that
typically
gets
added
to
these
issues
with
the
difficulty
which
is
out
planted
and
help-wanted
means
that
the
issue
as
in
natural
formation,
or
should
there
be
in
that
information
for
a
contributor
that
is
not
familiar
with
the
project
to
understand
what
is
the
real
problem
like
to
understand
what
that
issue
is
about
and
from
that
to
gather
the
rest
of
information
he
needs
to
solve
the
issue.
A
If
the
issue
is
outside
with
help-wanted,
then
it
means
that
probably
there's
like
information
that
is
not
present
there
and
you
can
still
try
to
solve
it.
You
can
like
be
brave
and
just
like
jump
it
in,
but
it
might
be
harder
so
far,
so
good
I
can
trying
to
like
scroll
through
all
the
phases.
Just
make
sure
everyone
is
still
following.
A
I've
been
also
putting
the
issues
with
questions
here,
because
typically
issues
that
are
questions
I,
give
an
answer
or
at
someone
in
the
community
gives
an
answer,
and
then
we
wait
a
little
bit
to
see
if
that
the
person
had
opened.
The
issue
as
like
is
successful
at
using
that
answer
to
solve
that
problem,
and
if
it
is,
if
that
happens,
and
because
the
issue,
if
not,
we
keep
like
having
a
discussion,
but
but
it's
more
like
a
slow
paced
issue
like
so
that
it
gets
put
in
the
back
wall.
A
A
Working
on
it,
which
is
the
difference
from
the
in
progress
column
in
progress,
means
that
there
is
some
work
that
needs
to
be
done
and
there
is
a
personal
sign
and
that
person
is
currently
focusing
on
that
issue
at
hand,
and
so
one
of
the
things-
and
this
is
like
a
really
important
detail
right,
because
it
is
not
useful
for
the
community
and
for
the
team
to
see
someone
tagged
to
like
ten
different
issues
if
they
are
different
types
of
work.
For
example,
we
see
here
the
back.
A
A
But
if
you
have
multiple
things
that
you
are
talking
like
a
feature
or
a
bug
fix
and
if
you
have
multiple
of
those
in
being
progress,
column
probably
means
that
a
cure
attention
is
being
spread
too
thin
over
multiple
things
and,
and
you
are
locking
that
work
from
being
worked
by
someone
else.
So
the
good
practice,
the
best
practice
here
is
like
if
you
are
working
on,
for
example,
bit
swap,
and
you
have
three
more
issues-
DHT
and
relay
you-
should
move
those
issues
to
the
ready
column
so
that
someone
else
can
pick
it
up.
A
Once
an
issue
is
done
so,
and
that
means
like
issue
is
closed
or
a
pure
request
is
merged.
The
waffle
board
moves
it
automatically
to
the
down
column
and,
like
they
stay
here
for
a
week,
so
after
a
week
of
them
being
done,
they
disappear
from
the
downtown
and
so
so
yeah.
We
can
always
accommodate
any
point
in
time,
but
the
fact
that,
like
it's
a
week,
pace,
makes
it
really
useful
for
us
to
come
back
like
in
the
next
weekly
call
and
I
just
review
everything
that
was
done,
everything
it
was
worth
done.
A
It
is
a
good
way
for
us
to
worry
what
was
achieved
and
and
if
there
was
some
piece
of
work
that
was
done.
That
now
unblocks
me
until
overall,
like
this
is
a
pretty
useful
tool,
really
good
way
to
see
the
work
that
is
available.
You
can
use
filters.
One
of
my
best
feel
like
my
favorite
filters,
is
really
just
going
here
and
putting
the
p0
label
and
I
see
you
can
see.
There's
like
a
lot
of
stuff
that
is
critical
now
for
the
well.
The
project.
A
Of
course,
like
there
might
be
some
issues
that
are
not
your
domain
expertise
or
that,
like
you,
are
already
so
in
so
deep
in
something
else
that,
like
shifting
your
focus,
would
actually
just
create
more
noise.
So
unless
there
is
some
critical
dependencies
on
some
event,
some
mouse
on
it,
we
have
to
achieve
that.
These
issues
are
required.
Don't
feel
that,
like
you,
have
to
stop
the
world
and
stop
everything
that
you
are
doing,
I
shifts
to
a
completely
different
thread,
just
because
an
issue
Easter
that's
critical
and
yeah.
A
So
for
contributors
like
for
first-time
contributors
like
a
good
way
to
know
how
to
help
the
project
is
just
like
children,
my
Help
Wanted
and
they're
like
seeing
what
is
it
all
out
there
for
people
to
work
on?
And
so
you
we
can
see
that
there's
more
than
100
issues
available
that
have
enough
information
for
someone
from
the
community
to
jump
into
the
project
and
start
contributing
with
something
valuable,
I.
A
Don't
know
if
you'll
get
asked
a
lot,
but
I
definitely
get
a
lot
of
questions
like
how
can
I
help
the
people's
project
until
we
created
this
label
system
to
how
people
see
how
they
can
contribute
all
right?
Okay,
so
this
was
a
waffle
board
part.
Is
everyone
clear
on
how
we
organized
work
and
how
we
communicate
to
others?
What
we
are
working
on
so
I
see
sometimes
a
cool
any
questions.
So
far,
any
comments
could.
A
Supposedly,
you
know
it's
cool.
It
is
also
present
on
if
you
go
to
IPA.
First,
just
defense,
one
of
the
cool
things.
Well,
if
you
like
metrics,
like
me,
one
of
the
cool
things
one
gets
from
the
waffle
board
is
that
through
photographs
that
is
now
loading
here,
okay,
there
you
go,
you
can
see
the
amount
of
things
that
are
operating
on
the
project.
I
think
it's
pretty
cool,
like
don't
stress
about
it.
It's
a
symmetric
like
the
development,
steel
cool,
all
right,
so
the
the
next
thing
I
wanted
to
bring
up.
A
There
are
no
questions
about
the
waffle
for
the
spare
programming
sessions
in
the
past.
Something
that
has
worked
pretty
well
for
knowledge
transfer
is
when
someone
is
tackling
some
and
like
there
are.
There
are
things
that,
like
you,
can
definitely
go
and
learn
by
yourself
and
like
read,
books
and
like
read,
papers
and
read,
specifications
and
read
the
co-pays
and
like
spend
a
lot
of
hours
and
like
you
will
eventually
get
it
for
sure.
A
There
is
a
lot
of
ideas,
a
lot
of
design
decisions,
a
lot
of
knowledge
that
the
other
person
will
learn
just
from
the
discussion
right.
It's
not
that
it
doesn't
mean
necessarily
that
we
prepare
a
lecture
to
explain
how
multiplexing
only
peer-to-peer
words,
but
it's
more
okay,
there's
a
multiplexing
issue,
but
you
dig
through
the
curves
and
like
as
one
person
is
helping
the
other
debug.
A
A
Yeah
cool
cool,
so
so
so
again,
this
is
just
like
a
thing
that
it's
out
there.
It
has
worked
very
well
in
the
past.
You
don't
have
to
use
it,
but
if
you
are
plucked
on
something
what's
iconic
together,
typically,
it's
a
lot
more
fun
anyway
discover
a
lot
on
yourselves,
all
right
cool.
So
this
was
the
warm-up
section
of
today's
call.
We
have
nine
minutes
left.
A
I,
hope
that
everyone
and
caught
up
to
speed
on
how
we
track
work
on
the
project,
and
so
let's
do
the
actual
stand
up,
sounds
good
cool
cool,
so
L
sub
screen
share
for
now,
so
that
I
can
see
everyone's
face.
Oh
so
much
weather
and
the
proposal
on
how
to
present
this
information
is
very
simple:
we
go
one
by
one
and
I'll
put
here
my
name
and
we
can
copy
the
bullet
islands,
so
so,
okay,
I'm,
just
just
like
writing
so
that
you
can
see
what
I
was
thinking.
A
Oh
no,
what
can
work
and
and
now
I
just
have
to
answer
these
questions
right
and
by
answering
these
questions.
Hopefully
everyone
gets
a
clearer
picture.
So
from
my
end,
this
is
my
stand
up.
What
I
have
accomplished
last
week,
like
I've,
been
trying
to
just
like
go
through
all
my
notifications,
backlog
and
I
answered
all
the
questions
there
are
out
there,
issues
and
pull
requests,
I
have
merged
or
reviewed
and
merged
a
ton
of
those
that
involve
other
work
like
that
be
feschi
and
IP
FSG,
CTL
and
interruptus.
A
The
I
there
is
nothing
that
I'm
blocked
right
now
and
the
thing
that
I
think
that
it's
more
important
for
me
to
focus
on
for
this
week
is
refactoring
late
appear,
so
that
we
can
then
remove
the
centralized
render
by
using
whippy-tippy
nodes
as
the
connections.
There
is
an
issue
to
try
to
that.
I'll
tie
myself
to
that
issue
and
the
only.
D
So
last
week,
I
guess:
I
worked
on
continued
working
on
on
I
profess
the
CTL
and
in
drug
tests
and
trying
to
get
stupid.
Finally,
that
be
included
and
down
and
tested,
and
eight
no
blockers.
Well,
there
was
a
blogger
with,
but
I
think
we
figured
out.
It
was
basically
champions
with
the
being
one
of
those
addict
was
kind
of
good
something,
but
that's
it
it's
kind
of
like
her
anymore.
D
A
D
Yeah
the
plan
was
to
get
it
done
today,
but
with
a
little
bit
with
some
of
the
CIA
shoes
and
some
other
things
who
pulled
it
by
the
end
of
the
day.
I
both
happen
and
with
the
dogs
that
are
I,
think
that's
the
only
thing
that's
outstanding
daily
and
just
the
tests
getting
all
the
sea
ice
cream
and
we
were
almost
there
in
terms
of
G-
is.
A
C
Issues
basically,
I'm
blocked
right
now
on
trying
to
get
one
set
of
tests
to
run
its
some
interaction
between
IPS,
D,
IPS
and
IPS,
API,
I
really
don't
know.
What's
going
on
right
now,
I'll
send
Demetri
a
copy
of
what
my
issues
are,
maybe
in
help
and
next
is
actually
using
the
keychain
to
clip
messages
and
sign
them.
Yay.
A
Alright,
so
if
I
understood
correctly,
the
work
is
almost
done.
There
is
some
walkers
in
especially
testing
like
especially
CI
testing
right
there's,
like
some
specific
walkers
on
on
Windows
stuff.
Do
you
want
to?
Could
you
post
the
issues
to
the
few
describe
those
problems
to
these
notes
and,
and
then
I
see
that
you
already
have
talked
with
the
mitri
to
follow
up
and
to
solve
those
issues
like
if
we
could
track
them,
so
that's
it.
We
can
also
check
and
help.
It
will
be
helpful.
Yeah.
B
C
A
C
A
Okay,
okay,
so
we
need
to
fix
the
signal
ratio
or
probably
just
skip
for
now
and
then
follow
up
on
Dimitri's
proposal
to
get
some
notes
to
work
in
the
windows
in
the
same
way
that
they're
working
in
Linux
and
Mac
all
right.
Thank
you,
okay!
So
we
are
one
minute
left
from
the
call
our
people,
okay,
spending
our
three
extra
or
like
five
extra
minutes
today.
Even
it
was
the
first
Jared
you
want
to
share
nothing.
F
Right
now
is
the
resolving
IP
LD
objects
within
the
window.
So
I
spoke
with
Stephen
about
that
when
I
met
with
them
out
in
Palo
Alto,
it
actually
might
be
going
there
back
in
Palo
Alto
in
a
couple
days.
So
I
might
try
to
ping
him
again
just
to
see
what
the
status
of
IPL
Diaz
in
resolving
it.
You
can
do
it
through
the
API,
a
JSI
PFS
api.
Nobody
can't
publish
it
to
IP
and
s
and
so
I
think
it's
an
ongoing
issue.
Mm-Hmm.
A
Got
it
it's
true,
especially
because
there
is
some
work
on
the
record
spec
that
then,
will
be
the
base
for
IP
NS
records
in
DHT
records.
Cool
cool,
like
stephenie's,
was
actually
here,
I
mean
it
ago.
I'll
tell
you
just
to
make
sure.
Thank
you
all
right.
Next
up
we
have
Rob
Rob,
give
a
rejection,
update.
G
G
That
kind
of
connects
all
the
pieces
of
ipfs
for
people
and
so
I
wanted
to
pop
in
here
and
get
a
sense
of
how
everybody's
doing
work
and
how
that
connects,
in
particular,
with
the
ongoing
work
in
this
project
and
hopefully,
as
part
of
a
result
of
this,
we
can
find
ways
to
encourage
better
documentation,
practice
code
practices
going
forward.
Hopefully
that's
just
like
creating
a
good
architecture
for
you
to
all
SWAT
things
into,
but
also
you
know
what
can
we
do
in
the
work
process
here?
A
There
is
one
issue
that
I'm
not
sure
if
it
is
on
your
radar
right
now,
the
awesome,
endeavor
IP,
fest
accommodation,
API
recommendation,
and
that
is
like
a
work
that
we
did
last
year
on
creating
the
tooling
to
support
automatic
dog
generation
from
Jess
Docs,
and
so
it
is
a
very
large
issue
with
winters
too
many
repos
on
like
work.
That
is
like
often
some
of
repos
ever
done.
A
A
H
Alright
yeah
so
last
week
I've
been
working
on
yes
still
getting
up
to
speed
with
the
whole
IPL,
D,
stuff
and
yeah,
so
I've
kind
of
finished
the
chase
IPL
the
Bitcoin
format,
implement
implementation
at
the
C
cash
and
I'm
currently
blocked
due
to
a
de'vide,
because
he
needs
to
review
pull
requests.
So
I
can
publish
the
C
cash
picnic
on
NPM
and
next
week,
I
will
again
go
through
the
spec
and
the
open
issues
and
just
yeah
polish
IPL
D
a
bit
yeah.
A
A
There
are
still
some
hiccups
on
using
a
die,
a
P
I
specially
from
the
CLI
because
of
the
changes
that
happen
internally,
that
now
this
UI
given
enough
tests,
things
kind
of
like
change
underneath
and
now
the
TOI
doesn't
really
work
well
for
all
the
formats
is
there?
Are
you
hoping
to
get
some
work
done
on
the
CLI
for
Jessie
BFS
this
week
or
yes,.
H
A
I
Haven't
worked
on
the
JavaScript
project
directly,
but
what
I'm
working
on
currently
is
to
get
all
the
projects.
Yes,
I
mean
Jenkins,
and
then
eventually
we
can
migrate
away
from
Travis
and
we
can
migrate
away
from
circle.
So
everything
gets
a
bit
faster.
The
most
important
build
right
now
is
for
JSI
PFS,
so
die
spending.
The
the
windows
fixes
that
I
was
on
tour
on
how
to
fix
as
well.
I
A
Yeah
super
excited
for
all
that
work,
making
tests
so
much
faster
small
requests,
while
you
are
at
it
King
King.
Can
we
just
agree
like
remove
Travis
from
the
equation
as
soon
as
possible,
because
it's
a
slow
and
can
we
also
just
do
coverage
testing
on
circle?
Because,
right
now
we
have
the
I
know.
There
is
a
token
management
problem.
I
like
circle
coverage
really
well
and
its
best,
so
we
would
have
Jenkins
to
do
all
the
tests
and
then
circle
see
I
to
where
the
coverage
chests
and
publish
the
results
to
cover
else.
I.
I
Don't
think
now,
when
I
did
the
the
websites,
automation
stuff,
we
have
some
secrets
management
and
we
are
not
super
careful,
maybe
about
the
for
being
able
to
upload
like
coverage
reports.
It's
not
like
a
supers
security
hassle.
If
people
do
that,
so
we
could
do
the
coverage
report
on
Jenkins
as
well,
I
believe
and
then
we
can
remove
both
circle
and
Travis
and
then
we
will
have
super
fat
pills
awesome.
Thank
you.
A
J
I'm
here
so
during
last
week,
I've
worked
on
this
test.
Spec
one
interface
interface,
IP,
FS
core,
also
on
the
rep
pool
and
I.
Had
the
mfsl
spec
I
also
implemented
it
on
GSM,
FS,
API
and
I.
Think
that's
it
anything
that
you're
blocked
or
that
you
are
hoping
to
get
e-cig
I.
Think
I'll
start
to
do
the
status
spec
implement
start
at
the
stats
interface
on
gsfs,
because
it's
one
of
the
things
that
is
needed
for
I
guess
desktop
to
work
with
Jesus.
E
Embedding
support
to
Jess
ipfs
with
directory.
It
is
needed
for
ipfs
companion.
You
wax
issue.
That
is
right
now,
when
you
download
the
file,
it
doesn't
support.
He
when
they
use
a
lot
of
the
font
of
the
browser
he
is
there.
She
doesn't
preserve
the
file
name.
So
with
this,
if
we
add
this
feature,
then
it's
possible
to
in
ipfs
companion
that
support
to
when
the
users
on
with
the
file
the
directory
will
be,
the
family
will
be
preserved.
A
E
A
A
Alright
yeah
I
know
you're
busy,
with
activists
in
web
browsers
were
cool,
so
this
is
it.
We
took
ten
minutes
more
than
what
was
planned,
but
again
we
I
have
all
the
warm-up,
which
was
pretty
much
20
minutes
so
I
expect
next
week.
We
can
do
this,
maybe
even
15
minutes,
depending
how
many
people
show
up
one
of
things
happening.
We
didn't
get
to
review
what
other
critical
issues
that
no
one
is
only
let's
make
sure
to
do
that
next
week,
so
that
we
we
understand
what
the
priorities
for
the
project
right
now.
A
Any
any
final
remarks,
any
questions.
Any
comments
feels
that
they
know
what
they
need
to
work
on
this
week.
Is
it
clear
all
right
cool?
Thank
you
so
much
for
joining
and
yeah.
This
was
the
first
disagree.
Fest
they
have
team
core
weekly,
sync
up
full
names
and
econo-mode.
That's
the
model
here
enjoy
your
week
and
see
you
again.
Next
Monday.