►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-11-25
Description
Learn more about the work of the IPFS Docs & Developer UX Working Group and how to join our weekly syncs: https://github.com/ipfs/docs
Notes: https://docs.google.com/document/d/1EOD-pJi4GvRmGi9HHocgVV8uVHMFIZlyVgJDkvC3DQ4/edit#heading=h.dgr8wcldbq68
A
Okay,
good
morning
afternoon
or
evening,
everybody
and
welcome
to
the
ipfs
dachshund
developer
user
experience
working
group.
This
is
our
weekly
meeting.
You
can
follow
along
in
the
notes
which
are
available.
All
the
information
about
this
meeting
is
available
either
if
you're,
watching
this
on
youtube.
After
the
fact
in
the
YouTube
video
information
or
you
can
visit
the
docs
repo
at
github.com,
slash,
ipfs,
slash
docs
for
more
information.
A
B
A
Alright,
we
are
missing
some
folks
this
week
due
to
a
number
of
things
we
have
American
Thanksgiving
this
week
and
as
such,
our
internal
huddle
and
Thursday
and
I
propose
that
we
cancel
that,
and
we
see
everybody
here
in
this
space
on
Monday
awesome
I
am
on
vacation
on
Monday,
but
I
will
I
will
make
this
meeting
anyway.
So,
additionally,
we
did
looking
through
these
debts.
A
Please
keep
in
mind
that
it
looks
like
we
didn't
get
a
whole
lot
done
and
we
didn't
get
a
whole
lot
done,
because
a
few
of
us
had
the
chance
to
gather
in
person
and
get
some
user
testing
done
over
the
last
week,
which
was
splendid,
but
that
does
require
travel
times,
and
so
it
does
look
as
though
we've
been
moving
a
little
bit
more
slowly
than
usual.
I
asked
everybody
on
this
call,
please
add
themselves
as
a
participant
and
I
can
go
ahead
as
we
do
that
and
continue
to
walk
through
our
agenda.
A
Obviously
the
biggest
recurring
item
our
agenda
is
the
Ducks
FINA
launch.
We
got
a
lot
of
that
in
the
last
week
with
user
testing.
That
is
fantastic,
I
will
not
lie.
We
are
considerably
behind
on
our
ability
to
ship
by
the
end
of
the
year
and
we're
gonna
have
to
scramble
really
hard
to
be
able
to
do
that.
You
know,
while
the
biggest
blocker
to
that
is
addressing
the
API
guest
hosting
issue,
which
Chris
is
there.
That
is
his
primary
responsibility
over
the
next
three
weeks.
A
We
do
have
a
large
number
of
issues
that
are
still
outstanding.
If
you
click
on
the
link
for
epic
1a
you'll
see
what
those
are
you
know
we
don't
have
to
achieve
all
of
those,
but
in
order
to
actually
launch
effectively
we're
gonna
have
to
add
the
new
content
here.
Stubs
I'll
link
to
all
these
issues.
I
didn't
have
time
to
do
that
yet,
but
I'll
make
all
the
issues
in
the
notes.
The
no
content
here
stubs
need
to
be
fixed.
A
The
back
and
forth,
linking
between
the
legacy
site
and
the
beta
site
is
going
to
need
to
be
implemented.
I
am
responsible
for
the
socialization
and
communications
plan
we
need
to
implement.
Is
this
helpful
mechanism
on
the
video
site
that
exists
on
the
legacy
site
and
will
need
to
offer
people
a
way
to
get
to
the
features
running
in
at
least
a
bare-bones
way?
I
knew
we'd
intended
to
eventually
integrate
that
more
firmly
using
candy,
but
you
know
that
that
really
doesn't
seem
probable
at
this
point.
A
So
we
need
to
figure
out
another
way
to
actually
get
that
implemented
in
a
way
that
folks
can
see
that
to
me
it
was
a
quick
look
through
our
issue.
A
So
you
know
not
to
not
to
put
the
fear
of
God
and
in
anyone
other
than
myself,
but
I'm
just
trying
to
be
extremely
realistic
about
that,
and
if
we
want
to
ship
this
by
the
end
of
the
year,
we
got
a
lot
to
do
so.
Carrying
on
recurring
I
know,
legacy
ducks
er
deprecation
plan
we're
continuing
to
work
along
this
as
we
go
along
that
lips
in
308.
A
As
you
think,
if
things
please
continue
to
add
them
to
308
and
well,
we'll
call
it
this
as
we
go
along
metrics
definition
in
collection
for
me
to
say
that
was
on
hold
until
Johnny
got
on
boarded.
He
is
and
now
that
we're
all
one
sprawl
back
from
our
travels
you
know,
I
want
to
check
in
with
Chris
and
with
Johnny
on
onion
that
started
recurring.
I
have
an
epic
to
be
the
betta
site.
A
Is
this
helpful
feedback
mechanism,
as
is
before
this,
is
ready
a
toship
writing
implement
and
we
just
need
to
get
that
implemented
usability
testing?
We
did
great
usability,
testing
I,
don't
know
Eric.
If
you
want
to
do
you
want
to
go
into
more
detail
about
that,
since
otherwise
I'm
gonna
be
doing
all
the
talking
here,.
C
Yeah
sure
we
we
we
did
a
share
of
our
work
in
progress,
view
pass
view
press
built,
Doc's
website
and
it
reflects
all
reflected.
A
lot
of
you
know
a
lot
of
backs
and
fourths
and
previous
testing
with
ipfs
users
like
yourselves,
our
viewers
and
evolution
significant
parts
significantly,
the
the
the
navigation
is
a
little
overwhelming
in
our
current
dockside
and
we've
tried
to
distill
that
down
into
you
know
really
a
much
better
organized
much
easier
to
to
iraq,
collection
of
information,
and
we
we
brought
the
results
of
all
those
distilled
them
into.
C
You
know
that
this
rapid
for
me
to
interact
among
expert
you
know
with
experts
in
this
specific
product
and
so
yeah.
We
we
got
really
good
feedback
and
notes.
I
will
shout
out
huge
to
Jessica,
who
not
only
was
always
engaged
in
in
guiding
the
discussion,
but
also
took
these
notes,
as
well
as
Chris
wearing
I
believe
and.
C
C
A
All
right
futures
voting-
this
is
same
pay,
the
same
same
stages.
Before
we've
got
the
public
facing
voting
page.
We
had
thought
about
doing
some
deeper
canny
integration.
3B,
don't
launch,
that's,
probably
looking
to
be
a
little
bit
optimistic,
but
the
fact
is,
it's
keyed
up
and
ready
to
go
at
least
on
a
standalone
page,
which
is
awesome.
A
You
can
system
audit.
Sorry
I
threw
that
in
there
we
did
make
and
for
the
purposes
of
this
call
as
we
didn't
ever
mid-quarter
evaluation,
we
didn't
remove
that
because
system
caught
it
from
our
okay
ours
for
this
quarter,
the
intent
is
to
hopefully
make
that
up
in
q1,
but
watch
that
space
and
I
welcome
any
feedback
from
anybody
who
may
have.
A
It
was
an
issue
in
prioritization
and
as
a
priority
to
a
PC
wish.
You
know,
unfortunately,
it's
one
of
the
things
that
were
gonna
have
to
push
recurring
item:
content,
improvement,
user,
driven
or
legacy.
We
closed
five
issues
since
our
last
meeting
two
weeks
ago,
it
has
been
slow
because
of
travel
and
in
person,
discussion
time
and
user
testing
expects
a
bit
of
me
return
to
the
normal
cadence.
A
Next
time,
however,
we're
gonna
have
to
scramble,
or
none
launched
before
the
end
of
the
year,
so
that
is
a
blocker
to
getting
the
content
issues
done
and
Noble
Locker
as
it
is
so
do
expect
sort
of
a
slower
pace
between
now
the
end
of
the
Johnny's
content
close
reading
audit.
He
took
a
stab
at
this
last
week.
I
have
seen
the
beginnings
of
his
report,
but
he
still
needs
to
capture
that
in
the
issue.
B
Yeah
you
like
how
if
we
leave
Jill
to
keep
working
for
a
week
while
the
rest
of
us
get
distracted
thing
to
actually
keep
happening,
I
mean
yeah,
although
I
noticed
that
we've
been
away
for
a
couple
of
weeks,
so
we
have
a
lot
of
updates
as
a
result
of
that,
so
Jill
finished
up
the
regular
files
API
tutorial,
which
is
amazing.
It's
really
awesome
to
have
some
new
content
out
the
door
and
he's
also
been
starting
to
take
a
look
at
other
like
alternative
platforms,
just
in
case
there's
something
out
there.
B
B
If
anyone
has
ideas
on
platforms
that
might
work
that
way,
please
add
them
to
the
issue
that
you
see
listed
there
and
then
we've
done
a
lot
on
the
front
of
applying
ipfs
camp
content
to
proto,
school
and
Johnny
will
take
some
of
these
same
things
that
we
call
it
later
and
see
where
they'll
feel
well
in
the
documentation.
But
things
we've
done
include
adding
core
course
a
which
is
the
understanding
how
ipfs
works
with
files.
A
lot
of
the
resources
pages
across
the
site.
B
I
also
incorporated
the
CID
inspector
that
Allen
belts
and
introduced
that
ipfs
camp.
So
now,
if
the
results
of
the
the
code
challenge
is
a
CID,
in
addition
to
the
view
and
I
peeled
the
Explorer,
you
now
have
a
view
in
CID
inspector
button
that
you
can
use
and
then
we've
also
been
going
through
the
various
courses.
So
just
looking
at
the
elective
ones,
a
couple
of
the
core
ones
we've
already
looked
at,
but
we're
still
just
cranking
through
the
list
trying
to
jot
down
all
of
the
ideas
we
have
for
applying
content.
B
So
this
issue
261.
If
anyone
has
ideas,
please
feel
free,
that's
open
for
anyone
to
add
those
ideas
to
and
then
once
we
get,
that
elected,
we'll,
go
back
and
start
knocking
off
somewhere
those
so
we're
partway
on
collecting
ideas,
part
way,
I'm
making
the
plan
and
we're
partway
on
executing
on
the
plan.
We're
just
gonna
turn
in
side
by
side
at
the
moment.
So
that's
that's
the
book
of
what
we
have
anything
I
missed
Joe,
no.
A
A
A
I
propose
that
we
have
a
second
meeting
a
longer
meeting
on
this,
like
maybe
next
Tuesday,
to
really
take
a
hard
look
at
the
launch
schedule
and
where
we're
gonna
be
for
that
and
actually
prioritize
and
triage
those
and
figure
out
exactly
what
do
you
think
each
of
us
is
going
to
be
spending
the
next
three
weeks
of
our
work
on
so
I
will
get
that
on
everybody's
books,
students
if
people
have
thoughts,
I'm,
not
I,
mean
I
hate
to
be
dragged,
but
do
people
have
do
people
have
thoughts
on
that
because
we
are
entering
our
crunch
time
and
I
want
to
make
sure
that
we
do
this
in,
like
the
most
positive
and
proactive
way.
A
First
yeah
I
have
a
feeling
a
couple
of
us
are
in
travel
for
American
Thanksgiving
on
Monday,
so
I
would
suggest
that
we
have
that
meeting.
Maybe
next
Tuesday
and
we'll
groom
will
groom
the
board.
I
will
prioritize
every
single
piece
of
it
in
the
meantime.
I
do
ask
that
that
we
we
do
have
a
lot
of
catch-up
to
do
and
that
before
those
of
us
who
are
leaving
for
the
holidays
over
over
this
week,
let's
please
make
sure
that
we
communicate
very
clearly
everything
that
we're
working
on
capture
everything
in
issues.
A
You
know
we
were
we've
been
scrambling
so
much
the
last
fortnight
that
a
lot
of
things
didn't
get
captured
your
github
and,
as
a
lot
of
us
are
sort
of
just
personally
coming
back
together.
As
things
be
panicked
for
the
end
of
your
holiday,
that's
more
important
than
ever
that
we
keep
things
captured.
Then
the
issues
themselves
so
I'm
going
to
actually
go
ahead
and
pause.
The
recording
I
have
a
couple
of
administrative
issues
that
we
should
probably
check
through
after
that.