►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-10-21
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
Good
morning,
everybody
out
there
in
internet
land
was
maybe
afternoon
middle
of
the
night
in
case,
welcome
to
the
ipfs
documentation
and
developer
UX
working
group.
This
is
our
weekly
meeting
today
as
Monday
the
21st
of
October
2018.
You
can
follow
along
in
the
notes
or
get
more
information
about
what
we
are
doing
in
our
github
repo.
All
the
info
is
in
the
readme
and
that
is
github.com
/iq
FS
/
Docs
I
am
Jessica
your
official
unofficial
host
for
the
week,
and
we
have
today
our
before
he's
even
started,
which
is
awesome.
A
B
A
A
A
C
I
could
fill
in
a
notes
afterwards
I'm
gonna
actively
list,
let's
just
roll
through
but
yeah
I'd
say
last
week
we
made
some
good
progress
on
I,
would
say
more
on
the
semantic
structuring
and
making
sure
that
we
all
on
the
same
page
with
how
we're
going
to
lay
things
out.
So
a
lot
of
effort
is
put
into
the
content
structure
and
the
individual
pages
and
Jessica
booted
up
a
view
press
dock
app,
which
is
essentially
just
visualize.
C
What
we
are,
how
we
have
a
building
at
me
beside
nerve,
so
that's
allowed
us
to
to
get
ahead
with
some
prototyping
on
individual
areas
that
we're
going
to
segment
out.
So
we've
got
a
workflow,
a
document
that
we've
been
using
as
the
main
content
site
nerve
and
now
we're
breaking
it
down
into
individual
subsections.
That
will
essentially
form
the
top
tier
navigation.
C
So
I
would
say
this
week
is
the
main
aim:
it's
basically
merged
those
two
forces
together
and
then
combined,
so
that
we've
got
the
opportunity
to
migrate
some
of
the
content
across
and
that
combined
with
the
the
setup
of
the
CLI
and
all
the
pointman,
then
we'll
essentially
have
our
first
prototype
level
out
public.
We,
we
also
had
some
conversations
around
the
what
what
our
aims
are
in
terms
of
a
roadmap
for
initial
release
of
this.
C
So
we
were
aiming
quite
aggressively
towards
lab
week
to
actually
have
a
full
version
of
this
live
and
ready
to
play
with
lab
week.
For
anyone
externally
was
watching
it's
essentially
a
internal
summit
frog
for
a
frog
lab,
so
we're
all
getting
together.
Then
so
we'll
have
a
lot
of
our
and
staff
on
the
ground
that
we
can
all
actually
work
on
work
with
and
play
with
the
product
and
interface
face
to
face,
and
so
that
will
be
a
good
opportunity
for
us
to
do
initial
user
testing
and
feedback
with
everybody
and
yeah
in
person.
C
And
so
that's
the
main
aim.
We've
got
a
an
issue:
I'll
link
to
it
in
a
duct,
but
we've
got
a
milestone,
basically,
which
is
breaking
out
all
the
individual
tasks
that
were
required
to
complete
before
that
date.
So
that'll
be
their
kasich
watch.
While
we
go
through
those
and
then
we
go
back
to
the
box.
C
C
It's
very
soon,
yeah
I,
don't
afford
date
on
it
exactly,
but
yet
well,
let's
make
sure
that
we've
got
something
that
we
can
both
work
towards.
I,
wanna,
I
wanna
make
sure
it's
ready
this
week,
so
we
can
actually
start
migrating
the
content,
because
otherwise
we'll
will
duplicate
effort
and
that's
it's
not
an
ideal
situation.
So.
A
C
I'm
fragmenting
by
trying
out
it's
two
different
themes,
there's
a
way
it
is
an
approach
to
essentially
extend
it.
A
base
theme
that
we
can
I
don't
want
to
have
to
fork.
The
individual
seems
that
we
end
up
having
to
maintain
it
ourselves.
Ideally,
if
I
can
extend
the
base
theme
and
work
upon
that,
then
we'll
have
some
better
options
for
updating
and-
and
that
requires
like
two
different
structures
to
set
out
and
so
I
don't
want
to
break
in
the
meantime,
yeah
any
other
questions.
D
D
A
D
D
E
D
D
And
in
a
little
status
bar
we've
gone
over
this
before,
but
we
moved
the
we
move
these
buttons
up
to
try
and
get
feedback
on
how
important
people
feel
the
contact
is,
and
we
can
hopefully
strategize.
You
know
prioritize
based
on
what
people
click.
Oh.
This
is
extremely
important.
Everyone
really
wants
this.
So
let's
bump
that
up
in
the
priority
I
need
some
just
some
simple
tweaks
to
copy.
You
know
help
us
write
this.
You
know
just
really
call
to
action,
oriented
right
from
the
get-go
Linda's
hand
on
github
very
friendly.
D
D
B
A
Exercise
now
structure
for
the
Vita
site
and
as
we
did,
that
we
built-in
affordances
for
a
bunch
of
content,
it
doesn't
exist
yet
so
that
we
could
test
on
your
getting
that
long,
existing
content
into
the
NAM.
So
what
that
does
mean
is
the
other
BTSA
there's
gonna
be
a
handful
pages
that
just
say
nothing
here
yet
so
we
just
want
to.
We
wanted
a
go-to
elegant
solution
for
that
right
off
the
bat,
but
then
also
something
that
we
give
us
an
affordance
to
to
even
like
gauge
interests.
B
A
A
way
to
make
that
automatic,
since
we're
dealing
in
the
in
the
initial
video
migration
of
like
dozen
pieces
of
content,
we
decided
that
we
would
just
do
by
hand.
It
wasn't
worth
the
effort.
But
if
we
end
up
using
this
a
lot,
we
might
want
to
come
up
with
a
better
solution
of.
C
Yeah,
we're
actually
trying
to
give
you
a
helping
hand
as
well
by
just
gonna
slide
in
to
our
metric
story,
so
we're
gonna
have
some
tracking
on
there
to
say,
like
oh
I
am
interested
in
it,
so
basically
on
some
passive
voting.
So
whilst
we
better
do
a
poll
each
week
and
see
what
pieces
of
content
the
most
people
are
looking
for,
so
give
us
at
least
a
rough
prioritization
list,
and
so
it
should.
It
should
help
us
with
that.
A
Anyway,
I
move
that
into
blocked.
You
know-
and
it
occurred
to
me
that
we're
gonna
be
in
this
sort
of
weird
space
for
like
the
next
month
or
so,
where
I'm
like
moving
a
ton
of
issues
into
chvotkin
and,
ideally
we're
all
moving
issues
in
the
box,
because
we're
doing
a
little
bit
of
our
management
and
that's
just
because
we're
not
ready
to
build
them
out
yet
and
I
know.
A
Block,
looks
awfully
negative,
but
it's
also
truthful
in
this
case,
so
take
that
block
designation
with
a
little
bit
of
salt,
but
also
just
a
good
idea.
Do
you
know
where
dependencies
lie,
and
that
brings
us
to
another
thing:
we're
not
gonna
be
moving
all
that
much
on
in
the
super
new
future
is
next
the
next
okay,
our
which
is
legacy
Docs
deprecation
plan,
yeah
we're
all
taking
this
on.
This
I
know
we're
all
taking
them
to
this.
A
Recurring
item
Vita
site:
is
this
helpful
feedback
mechanism
visuals
for
this
are
done
in
305
and
again
that's
one
of
those
things
that
that's
blocked
and
spilled
in
306
until
the
video
takes
a
little
bit
further
along
and
we're
ready
to
actually
build
that
in
there
I
also
pushed
a
PR
on
Fridays
356.
It
takes
two
things
out
of
this
and
puts
it
in
the
legacy
site
that
moves
that
and
again
hub
link
up
for
the
feedback
buttons
like
we
talked
about
and
then
also
in
that
text.
A
Links
adds
another
like
that
says,
open
an
issue
and
that
populates
an
automatic
issue
in
the
docs
repo
with
the
page
title
and
the
subject
of
the
issue,
and
they
just
saw
your
notes
about
taking
a
screenshot
of
that
it
could
be
really
snarky
and
I.
Could
you
just
like
put
the
site?
I've
got
your
local
but
I'll.
Take
a
screenshot
for
you
right.
D
A
C
D
C
E
F
A
A
A
A
But
it
was
wonderful
because
it
was
sort
of
one
of
these
things
where
we
had
no
idea
who
we're
gonna
get
in
this
conversation,
because
this
was
the
day
part
of
an
evening
event
that
was
like
I
passed
a
six-night.
So
there
were
people
at
all
different
areas
of
expertise.
A
Colorado
has
been
like
informally
called
krypter
Otto
for
like
the
last
year
or
so
so
we
had
a
whole
lot
of
people
who
were
like
super
into
cryptocurrencies,
so
who
had
a
lot
of
interesting,
interesting
knowledge,
but
not
necessarily
IPS
related
knowledge,
but
a
lot
of
a
lot
of
background
info.
So
that
was
really
interesting
to
sort
of
get
their
feedback.
We
also
had
somebody
who
was
doing
an
archival
project
for
an
unusual
organization
that
had
some
pretty
specific
needs.
A
So
we
got
to
flitetest
the
archivist
for
some
on
her
and
it
turned
out
that
actually
yeah
that,
like
even
better
than
we
thought
archivist,
was
one
of
the
sort
of
less
research
months,
because
I
face
this
all
on
and
knowledge
I
got
from
DPLA
Fest
in
Chicago
in
April
it
turned
out
to
check
out
really
well,
which
is
pretty
sweet.
Also.
We
really
really
helped
us
pinned
down
the
now
structure
in
the
that's
in
that
sort
of
like
like
fake
repo,
Thank
You
pres
Rico
that
I
made
and
referenced
above
it.
A
It
feels
like
you
know.
Eric's
does
a
couple
of
review
it's
a
few
months
to
make,
but
but
it
sounds
like
we're
at
a
point
where
we
can
throw
this
out
in
front
of
people
without
too
much
worry
and
then
sort
of
lump
that
into
the
umbrella
of
lunch
testing
and
then
also
was
discussed
earlier.
A
lot
of
really
good
feedback
on
the
nothing
to
see
here
page,
which
enabled
us
to
sort
of
finish
that
up,
which
is
great.
A
Moving
on
recurring
items
features
voting
I
had
a
long
discussion
with
the
the
folks
at
canny
over
the
last
week
or
so,
and
they
were
kind
enough
to
give
us
a
free
account
for
open
source
nature
of
our
work,
which
is
super
sweet.
You
should
all
have
admin
invites
if
you
don't,
and
that
feels
wrong
hit
me
if
I
get
home
and
I'll,
send
you
a
link
to
do
so.
John
I'm
gonna
hold
off
on
you
for
that
until
you
other
protocol,
you
know
just
because
it's
easier
that
way.
A
There's
a
link
to
the
public
facing
voting,
page
Doc's
features,
so
it's
more
or
less
done.
I
took
all
the
features
from
our
prioritized
features
list
them
threw
them
in
there
as
items
aside
from
the
ones
that,
like
we
knew,
takes
the
next
steps
on
that
is
I.
Would
my
request
to
all
of
you
all
is
sometime
in
the
next
day
or
two
look
at
that
public
facing
zoning
page.
A
That's
like
two
in
the
notes
make
sure
that
those
items
make
sense
to
you
that
they're
correct
and
then
we
need
to
figure
out
the
best
way
to
socialize
and
ship.
This
I
think
an
item
in
the
you
know.
Obviously
this
an
item
in
the
weekly
newsletter,
probably
some
social
media
and
then
on
the
front
page
of
the
Ducks
repo
on
the
readme
and
then
also
on
the
legacy
site.
Yet
we
want
to
incorporate
that
you
know
lunch
yeah.
C
I
feel
like
it
burns
more
in
parallel,
just
not
to
confuse
people
between
the
Association
a
bit
so,
but
there
are
ways
we
can
use
the
API
as
well
to
basically
embed
that
and
this
nicer
into
the
actual
display.
So
well,
you
know
we'll
see
well,
I
think
we'll
try
at
first
by
linking
people
linking
it
to
people
and
then
yeah.
If
we
get
get
the
usage
we
want
and
if
you
back,
then
we
can
go
be
with
inspirations.
C
A
A
A
So
we
separated
that
those
out
the
two
buckets
they're,
tagged
ins
and
hub
accordingly
and
we're
saying
get
hub
accordingly
and
I
can
walk
you
through
that
later
of
user
driven
issues,
eight
of
them
are
in
the
soon
column
we
did
push
to
in
to
review
since
last
week,
and
then
Terry,
you
and
I
are
talking
about
clarifying
the
community
section.
The
dock
state
navigation
I
saw
that
you
just
I
just
got
a
ping,
but
I
didn't
read
what
you
said
so
we'll
keep
talking
I
just.
F
A
Cool
all
right,
the
legacy
issues
24
of
them
are
in
the
icebox.
16
of
them
were
in
soon
that
has
not
changed
since
last
week.
The
blockers
on
that
are
just
that.
You
turn
user
testing
and
working
in
the
be
decide
all
week.
It's
bandwidth
limitation
and
hopefully
yeah
I'm,
nagging
myself
as
much
as
anyone
yeah.
F
Jerry
sorry
I
just
wanted
to
say,
as
I
was
in
there
looking
for
the
community
information
I
think
something
that
I
find
confusing
about
the
dock
site
is
that
I
envisioned?
F
What's
on
the
left
as
like
us
like
this
structure,
that
I
will
then
find
in
the
content
I'm
reading
on
the
right,
and
it's
not
at
all
that
and
I
find
like
I
find
that
relationship
confusing
like
if
I'm
in
a
header
of
a
some
section
here
I
would
expect
the
next
subhead
that
I
see
here
to
be
over
here
as
the
next
thing
so
I,
just
like
the
layout
of
that,
is
very
good
to
me.
Yeah.
F
A
F
A
Totally,
you
totally
know
you
record
what
some
of
the
stuff
that
we
heard
on
Wednesday
too
so
sweet,
it's
good,
we're
on
the
same
page,
mercury
I
am
content
closer
reading
John.
This
is
like
your
big
onboarding
cast
that
you
can
get
to
know
the
docs
well.
This
is
still
like
providing
some
value
cool
you're
already
looking
at
this
a
little
bit,
but
we'll
talk
about
it
when
you
join,
which
is
cool,
pretty
cool
stuff,
Terry
yeah.
F
G
G
So
as
as
with
last
week,
I'm
still
going
through
runs
of
feedback,
we
asked
more
feedback
now
and
Helen
show
also
gave
us
a
few
clues,
as
well
as
the
V.
What
to
writes
on
some
specific
sessions,
which
we
didn't
know
exactly
how
to
put
things
in
the
in
the
content
part.
So
yeah,
it's
still
a
work
in
progress
so
far,
but
I
think
we
can
still.
We
can
start
to
see
the
light
at
the
end
of
time.
F
Yeah
we're
getting
there
we're
getting
there,
it's
so
this
for
you
when
you
missed
the
context.
This
is
a
new
protocol
tutorial
on
the
regular
miles,
API
I'm
very
unclear,
even
on
what
to
call
it
and
need
like
a
decision,
I
think
from
Alan
on
that.
But
the
thing
that
is
not
MF
s
that
it's
used
to
add
in
cat
and
get
files,
so
there's
also
a
thread
going
in
I.
Think
it's
in
in
slack
about
the
like
tips.
F
If
anybody
has
resources
for
us
to
add
to
the
resources
page
other
educational
materials,
or
especially
things
on
like
what,
when
would
you
use
this
over
m
FS?
When
would
you
use
this
over
dag
I
think
that
Jill
and
I
together
did
a
reasonable
job
getting
at
the
basics
of
that
and
there
people
have
added
a
little
bit
more
color
and
that
thread
and
are
doing
so
in
the
issue.
So
I
went
through
and
copy
edited
lessons,
one
two
three
on
Friday
and
hopefully
we'll
get
to
four
today
and
then
Jill
you.
F
Let
me
know
when
the
rest
of
the
stuff
that
you
were
reworking.
You
feel
like
it's
ready
for
that
level
of
attention
and
I
can
do
that
then
so
someday
when
I
have
time.
So
this
will
be
I
mean
I,
think
we've
probably
with
various
forms
of
proof.
You
probably
still
have
a
few
days
a
week
whatever,
but
but
we're
definitely
getting
close.
It's
really
cool.
F
Sorry
one
total
side
note
for
anyone
who
occasionally
pops
onto
the
proto
school
call
that
was
weekly,
that's
now
monthly
as
a
time-saving
device
and
responsive
to
the
level
of
participation
that
we
have
they're
trying
to
cut
back
and
such
as
I
can
on
some
of
the
admin
stuff,
and
we
also
have
some
community
community
focused
task
like
resources
to
help
chapter
leaders.
Molly
was
kind
enough
to
put
together
like
a
intro
to
ipfs
slide
deck,
which
I
will
take
a
look
at
soon.
F
A
E
Really,
just
back
from
Asia
finally
and
trying
to
catch
up
on
all
the
things
so
I
watched
last
week's
meeting
and
don't
have
any
any
major
items.
I
think
the
one
thing
is
I
did
loop
Chris
in
with
a
an
email
conversation
with
some
folks
from
the
etherium
gorg
website,
who
are
also
using
view
press
for
their
documentation
and
an
other
website
and
would
like
to
put
it
on
my
PFS.
A
C
Some
work
has
already
began
on
that
and
all
he's
written,
a
relative
ization
script
that
I
might
be
able
to
inherit
and
use
a
spark
plug
in
and
we've
got
it
visually
working,
but
the
Java
scripts
migrating.
All
the
relative
paths
in
the
Jas
is
another
at
least
entirely,
so
if
that
will
be
tackled
later
on,
but
yeah
I'm
comfortable,
better,
that's
awesome.
Thank
you.
Thanks
for
that,
big.