►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-08-26
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
B
The
the
Thursday
call
has
been
internal
at
this
point
for
the
sake
of
grooving.
Does
that
hug
board,
obviously,
and
now
that
we're
recording
I
will
mention
this
as
well?
If
anybody
who
is
listening
once
to
get
in
on
our
our
somewhat
pragmatic
grooming
call
either
Monday
meeting
or
violent
issue
and
github
totally
everybody's
welcome
it's
just
usually
it's
just
flat-out
grooming.
At
that
point,
you
know
and
anything
that
the
communities
all
could
benefit
from.
B
We
save
for
this
Monday
meeting
with
that
in
mind,
hello,
everybody
good
morning,
welcome
to
the
I,
confess,
documentation,
task,
force,
I'm
teach
and
develop
user
experience
task
force.
Meeting
today
is
Monday
the
26th
of
August
20
19.
My
name
is
Jessica
and
I.
Am
your
planning
Monday
addled
host?
For
today
we
have
a
smaller
group
than
usual
because
it
is
a
British
bank
holiday.
So
those
of
us
who
are
not
on
this
call
I
hope
you
are
having
a
wonderful
day.
B
We
will
be
as
always,
uploading
this
video,
it's
probably
going
to
be
a
somewhat
truncated
meeting,
just
because
there
are
fewer
of
us
here
and
we
spent
most
of
the
week
sort
of
all
handling
on
one
specific
item
which
we
can
talk
through.
I'm
gonna
just
go
through
and
highlight
with
things
as
I
speak
to
you,
then
perhaps
it's
annoying
if
it
is.
A
B
Me
know
just
don't
wanna
I
know
we
are
in
vacation
season.
It
is
August
people
go
on
holiday
because
it's
beautiful
matter
where
you
are
in
the
world.
If
you
do
a
lot
of
a
keishon,
please
remember
to
unlock
as
much
as
you
can
before
you
go
on
holiday.
We've
all
been
very,
very
good
about
that,
but
it's
just
an
ongoing
reminder
so
part
of
that
season,
since
three-quarters
of
the
team
will
be
away
next,
Monday
I
am
proposing
that
we
cancel
next
Monday's
meeting.
B
As
a
result,
I
can
check
in
with
Chris
wearing
who
may
be
holding
down
the
fort
for
us
next
Monday
to
see
if
he
wants
to
do
it
being
that
I
think
external
contributor
presidents
of
the
meeting
is
fairly
slim.
You
know
we
do
have
contributors
hanging
out
in
the
repos
and
we're
chatting
with
folks
in
that
way,
I
think
we're
probably
safe
canceling
next
Monday's
meeting
but
I'll
double-check
with
Chris,
unless
either
of
you
have
any
reasons
not
to
do
so
cool
all
right.
B
So
as
usually
with
this
meeting
we're
just
running
through
the
okay
ours,
one
by
one
content
audit.
Frankly,
this
hasn't
changed
since
last
week.
The
results
work
is
being
deprioritized
since
we
lost
the
team
member
who
is
working
on
this
work
and
need
to
say
that
prints
up
on
the
hiring
effort,
and
then
this
last
week
on
the
quiz
launch
I,
do
have
the
audit
document
and
intend
to
sift
through
for
the
results
gathering
in
its
next
steps
as
soon
as
possible.
B
Moving
along
to
D
Docs
platform
features
inventory
again.
This
is
something
that
we're
adding
on
the
rolling
basis.
The
aim
is
wrap
this
up.
At
the
end,
a
quarter
you
were
ranking
exercise
so
that
it
can
duck
tail
pretty
nicely
with
the
actual
platform
discussion
that
we've
been
having
as
well,
so
that's
just
being
added
to
in
an
incremental
basis.
The
nice
thing
about
the
work
that
we're
doing
what
he
knows.
It's
just
continuing
to
expose
needs
for
features
that
we
want
to
have
on
that
platform.
B
Chris
I
understand
it
just
added
this.
The
docs
platform
tech
second
framework
I
know
that
he
didn't
get
as
much
time
as
he
wanted
to
last
week,
because
we
ended
up
ramping
up
super
super
hard
on
the
quiz
which
we
decided
that
we
were
going
to
do
some
testing
on
early
in
the
week
and
big
thanks
to
Eric
for
mobilizing
in
that
super
quickly.
We
got
a
lot
of
very
interesting
conclusions
out
of
that,
both
in
terms
of
the
quiz
itself,
we
didn't
have
some
changes
made.
B
We
did
a
lot
of
really
good
things
on
that
a
second
but
then
also
just
on
some
of
our
overall
methodology.
For
you,
access
in
general
suits,
it's
been
a
very
valuable
exercise.
I
know
that
Chris
intends
to
continue
working
on
the
data
source
stuff
when
he
gets
back
on
Wednesday
again.
Stop
me
if
I'm
moving
too
quickly
the
recurring
okay,
our
item
of
hiring
our
Doc's
specials,
that
is
continuing,
Molly
I,
know.
B
You've
got
some
meeting
this
week
with
some
folks
that
I
think
both
of
those
people
who
are
who
are
on
your
book
search
folks
that
have
been
spoken
with
with
a
bunch
of
people
that,
since
you
were
away
in
Berlin,
so
you
may
be
the
last
person
that
some
of
these
people,
speaking
for
that
so
curious,
is
to
to
oil.
What
you
hear
without
you
know,
breaking
confidentiality
for
things
that
is
recording
and
being
in
line.
B
We
can
have
separate
conversations
about
this
as
well:
I,
just
preservative
privacy,
keeping
in
mind
as
well
that
we're
also
now
I'm
I've
gone
through
every
single
candidate,
for
both
our
role
and
for
the
file
role,
which,
at
the
very
highest
level,
is
an
extremely
similar
role
in
the
sense
that
you
could
be
split
file
and
wherever
we
put
ipfs
in
a
certain
degree,
at
least
at
this
point.
That
doesn't
mean
that
if
we
get
to
the
point,
we've
got
a
couple
of
people
that
we
really
like
that.
B
B
B
B
Persona
stuff
yeah,
so
so,
as
I
said
as
far
as
it
all
trying
I'm
gonna
suggest
that
we
table
that
for
this
week,
see
how
we
feel
this
time
next
week
and
see
you
see
if
it's
something
that
we
want
to
change
our
first
two
weeks
time
for
saddle
we're
meeting
on
Tuesday
where
we
went
through
the
draft
I've
had
a
lot
of
really
good
conversation
about
it.
The
challenge
everybody
was
pleased
out
of
your
comments
and
the
mural
document
by
roughly
the
end
of
Wednesday
I
know
Terry's
been
through
it.
B
I
know:
mom
we've
been
through
it
I'm,
not
sure
I
keep
its
really.
They
think
you've
been
pretty
much
the
crisp
top.
That's
been
a
huge
effort.
I
think
request
is
just
please
go
through
and
your
feedback
on
Wednesday
so
that
you
know
I've
been
incorporating
known
as
I
go
along
resolving
keys.
B
B
You
know
how
they
feel
about
the
line
that
was
one
or
more
the
roles
and
use
that
as
a
baseline
exercise,
plus
I've
also
been
talking
to
Dan
shields
in
Denver
and
we're
gonna
do
probably
a
combination
of
a
day-long
open-access
discussion
about
person
a
as
well
as
he's
gonna,
host
and
ifs
Colorado.
You
know
in
Boulder
and
October
that
was
the
next
date
he
was
able
to
do
is
something
like
October
6
thing.
B
Moreover,
that's
going
to
be
prefaced
by
Rico
working
technically,
we
need
to
sort
out
the
budget.
That's
a
discussion
that
I
need
to
have
to
see
what
we
can
budget
in,
because
your
degree
would
be
subsidizing
Necco
working
for
folks.
So
people
who
want
to
take
part
in
that
coming
to
work
at
Boulder
Peregrine's
for
a
day
and
then
help
seconded
and
sitting
with
us
and
have
a
discussion
about
the
persona.
I
could
actually
be
usually
found.
B
Evil
I
just
need
to
figure
out
the
best
way
to
approach
the
budgeting
situation,
for
that
I
need
to
have
a
college
half
of
them,
but
still
so
that's
cool.
You
know
we're
still,
even
even
though
that
that
in
October
I
think
that
still
has
helped
us
out.
As
far
as
okay
are
wise,
we
will
have
completed
what
we
said
we
would
complete,
which
is.
B
A
batch
offense,
which
would
be
this
this
quiz
testers
that
I'll
follow
up
on
before
the
end
of
the
quarter,
so
that
does
overlap
into
some
of
the
work
for
presenting
for
for
q4,
which
is
which
is
grades
that
mean
we're
already
certified
continuing
on
tactical
hot
fixes.
This
is
entirely
on
my
head
and
I'm
not
quite
sure
how
to
resolve
this.
At
this
point
we
did
ship
a
whole
bunch
of
the
right.
B
If
you,
if
you
go
through,
if
you
go
through
the
Sun
hub
board,
we
did
ship
a
rather
large
variety
of
protocol
fixes.
Not
all
of
them
are
hot
fixes,
but
one
of
them
are
sort
of
certain
minor
incremental
changes
and
advances.
Diego's
departure,
since
Terry
shepherded,
those
I'm
afraid
I,
can't
go
too
deep
into
exactly
what
was
done
for
each
of
them,
but
they
they
scramble
super
hard
last
week
to
get
that
done,
and
the
remainder
of
our
team
was
distracted
because
we
all.
B
Testing
and
implementation
not
pretty
much
killed,
everybody,
which
was
great
because
we
got
a
lot
time,
but
to
be
completely
honest
about
it,
we
need
to
do
better
at
maintaining
our
original
pace
of
hotfixes.
Even
though
we've
lost
a
third
of
our
team
members,
that's
going
to
be
the
that
is
the
metric
by
which
the
communities
is
getting
benefit
from
what
we're
doing
the
strategic
stuff
that
we're
working
on
is
just
fine,
but
even
though
we've
lost
a
third
of
our
team,
we
need
to
be
maintaining
the
original
cases
hotfixes
anything
less
than
that.
B
Just
isn't
good
enough,
and
that
is
entirely
on
my
head
because
I
have
not.
You
know
we
had
a
list
of
these
things
that
Porsche
was
accumulating
as
she
was
doing
her
content
on
it
and
those
were
the
ones
that
were
the
low-hanging
fruit.
They
were
the
ones
that
were
easy
to
fix
for
work
very
rewarding
to
fix,
I
need
to
go
through
and
look
at
what
she's
put
together
and
I
need
to
be
prioritizing.
B
Honestly,
I
think
what
that
means
is
is
going
to
be
second
shift
until
that
guy's
fixed
or
it
doesn't
get
fixed,
and
we
need
to
make
that
position
so
either
that's
something
that
I
need
to
somehow
create
time
for
or
or
it
doesn't
get
done,
and
considering
that
this
is
the
that
this
is
the
work
that
the
public
sees
I.
Think
it's
it's!
You
know
it's
important
that
that
gets
taken
care
of
yeah
I.
A
Think,
especially
because
the
the
docs
repo
has
been
getting
more
attention
from
folks
in
the
community.
Now
that
there's
been
more
progress
and
I
think
people
are
also
kind
of
excited
as
some
place,
where
there's
not
a
super-high,
intense
bar
of
contribution,
where
you
know
great,
you
need
to
be
a
distributed
systems
programmer
with
X
many.
You
know
experiences,
building
file
systems,
blah
blah
blah
and
so
to
the
extent
that
maybe
it's
possible
to
create
an
issue
for
the
task
of
looking
through
this
and
trying
to
prioritize
like.
A
B
That's
that's
definitely
a
good
approach,
sort
of
sort
of
my
devil's
advocate
ischium
on
that
is
that
I
know
we
do
have,
and
one
of
the
things
that
we
did
right
off.
The
bat
was
go
through
all
of
the
existing
open
issues
and
label.
Anything
that
would
be
sort
of
you
know
not
a
little
barn
entry.
That's
something
that
you
don't
have
to
be
super
deep
in
the
system
to
be
able
to
commute
to.
There
are
a
number
of
open
issues
that
are
open
to
community
contribution
effort.
B
I
mean
there's
definitely
there's
definitely
a
lot
of
folks
who
contribute
to
should
they
wish,
but
I
I'm
thinking,
I'm
thinking
more.
You
know
we
were.
We
were
very,
very
diligent
about
being
able
to
not
have
some
of
the
very
small
sorry
Hewitt
related
code
changes.
Things
like
this,
like,
oh,
no,
here's,
here's
the
set
of
checklist
here,
some
broken
links
push
you
did
a
wonderful
job
at
addressing
whole
bunch
of
those,
and
we
got
a
bunch
of
them
look
through
I
think.
B
B
B
In
person
and
knocking
this
work
out,
but
whether
or
not
that's
viable
is
kind
of
a
different
question,
so
so
yeah
I'll
keep
on
that.
But
it's
something
it's
something
I
feel
that
you
know
that
I
need
to
prioritize,
and
if
that
mean
night,
if
that's
my
second
shift
for
a
while,
then
that's
my
second
shift.
B
Moving
on
Eric.
Do
you
want
to
talk
about
the
front
page
quiz
work
since
you
shepherded
a
lot
of
lists?
There's
a
there's
a
lot!
That's
that's
gone
on
here
and
probably
maybe
to
add
some
notes
to
this
document
as
well
sure.
C
C
So
we
laid
it
on.
You
know
that
the
two
buttons,
this
being
literally,
how
it
works
literally
taken
from
the
from
the
header
on
the
page,
but
this
is
this-
is
very
similar
to
what
we
had.
We
kept
to
get
started,
although
it
might
be
a
bit
of
an
over
promise.
In
terms
of
you
know,
some
of
this
is
not
immediately
actionable.
C
We
do
want
to
you
know.
Ipfs
is
indeed
you
know,
we
want
to
put
it
out
there,
something
that
can
be
used
and
should
be
used
right
now,
especially
for
forward-thinking.
You
know
people
who
want
to
help
make
this
new
internet,
so
we
simplified
the
selection.
We
removed
the
just
the
basic
learn
more
and
we
figure
that
most
of
these
people
will
go
to
the
how
it
works,
and
so
as
we're
tracking
both
of
these
buttons.
B
There's
a
couple
of
reasons:
justjust
because
of
how
the
site
is
published:
yeah
there
doesn't
exist,
a
mechanism
for
including
an
open-ended
form,
considering
very,
very
significant
changes
real
soon.
Now
what
Chris
has
done
with
the
metrics
is
set
up
a
sort
of
miniature
funnel
with
this
as
it
were,
you
know
we
we
are
aware,
and-
and
some
of
this
was
confirmed
in
our
in-person
testing-
that
these
links
themselves
are
not
an
ideal
finish
estate.
You
know
in
a
deal
finished
state
we're
offering
very,
very
good
parted
out
means
of
an
end
in
here.
B
What
this
is
is
about
getting
baseline,
metrics
in
place,
which
Chris
has
outlined
in
the
test
plan,
which
is
linked
to
in
the
in
the
meeting
notes
as
to
you.
This
is
going
to
help
us
prioritize
the
sorts
of
documentation
that
people
are
going
to
be
looking
for
first,
so
using
this
in
conjunction
with
the
information
that
we
come
up
with
in
the
content
on
it
and
just
our
overall
strategic
approach.
This
is
this
is
gonna,
help
us
prioritize
the
documentation
that
we
write
and
produce
and
improve
first.
B
B
This
also
gives
us
this.
First,
two
buttons
at
the
very
top
give
us
an
initial
branch
of
people
who
give
the
depth
to
which
they
want
to
learn
about
idea.
Passive.
You
learn
more
versus
get
started.
Folks,
that's
helping
us
really
just
have
an
initial
inventory
of
the
sorts
of
branching
that
we
want
to
do.
This
is
going
to
help
us
zoom
in
a
little
bit
harder
on
whether
our
personas
are
effective
and
what
aspects
of
which
personas
we
also
want
to
include
as
we
as
we
can
get
new
things.
B
That
said,
we
also
and
and
Eric,
is
writing
a
test
result.
Summary
we
sort
of
divided
and
conquered
on
this
I
I'm
went
through
the
results.
It
did
a
whole
bunch
of
implementation
in
the
code
wish
Chris,
then
cleaned
up
and
fixed
for
me,
and
then
we
spent
we
spent
a
lot
of
time
on
Friday
walking
for
our
motivations
for
acting
on
on
all
of
the
test
feedback.
B
So
while
I
was
doing
that,
so
Eric's
been
working
on
actually
putting
together
a
summary
of
what
we
learned
other
than
just
flat-out
implementing
it
and
then
because
a
lot
of
things
we
learned,
you
know
flat-out
weren't
related
to
this
quiz
ever
in
itself,
but
related
to
the
front
page
of
Io
itself.
Those
are
going
to
be
invaluable
as
we
started
thinking
about
changes
that
we
want
to
make
to
this
page
overall.
B
B
B
That
also
that
also
hugely
underscored
a
lot
of
the
things
that
we're
learning
from
a
variety
of
angles,
about
the
importance
of
what
I've
been
kind
of
calling
quasi
case
studies
and
our
approach
to
that
level
of
real
goal
based
depth
of
integration,
tutorial
stuff
and
and
and
that
that
was
hugely,
not
lying,
well,
I'm,
thinking
a
little
bit
deeper
than
that.
That
said,
we
are
running
out
of
time.
B
The
final
agenda-
I'm
critical
updates
tearing
a
year,
did
an
amazing
job
of
pushing
a
ton
of
stuff
out
before
we
lost
Diego,
but
it
remains
to
be
seen
how
we
move
forward.
In
that
sense,
I
will
kill
off
this
recording
and
let
us
all
have
the
remainder
of
our
day
back
unless
anyone
else
has
anything
at
this
point
all
right.
Thank
you.
So
much
everybody
for
your
time.
I
will
upload
this
to
YouTube
ASAP
and
we'll
go
from
there.
Thank
you
so
much.