►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-09-16
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
Greetings:
people
of
the
internet
and
welcome
to
this
week's
ipfs
documentation
and
user
experience
task
force
meeting
today
as
Monday
the
16th
of
September
2019
and
I.
Am
your
unofficial
official
host
being
attacked
by
flies
because
I'm
working
outside
Jessica
you
can
follow
along
in
the
notes
that
are
available
every
week,
links
to
all
of
the
above
are
available
in
the
docs
repo
github.com
slash,
ipfs,
slash
Docs,
so
we
will
just
start
I.
Think
at
this
point
we
don't
have
anything
outstanding
as
far
as
I
am
aware
other
than
the
usual
recurring
items.
A
All
right.
Excellent
I
shall
then
believe
that
from
the
agenda,
the
content
audits,
okay,
are
we're
actually
going
to
call
this.
Okay
are
done.
Last
week,
Eric
and
I
wrapped
up
consolidating
the
content
inventory
last
week,
captured
all
of
that
and
github
issues,
which
is
great.
So
the
this
exercise
is
more
or
less
done.
That
said,
we
will
dig
deeper
into
that
content
wise
in
q4,
pending
the
onboarding
of
our
new
documentation.
A
Specialist
dinner
with
the
docs
platform,
features
inventory
the
second
item
on
the
agenda
that
is
finished,
there's
a
link
to
the
features
inventory
in
the
in
the
agenda.
The
one
note
on
that
is
that
we
want
to
discuss
how
we're
prioritizing
ipfs
hosting
and
fetching
in
more
detail.
There
is
an
issue
in
the
github
board
open
for
that
that
we
just
need
to.
We
need
to
devote
a
more
detailed
discussions.
A
The
best
way
to
solve
that
Doc's
platform,
tech
stack
and
framework
okay
are
chris,
is
on
holiday
until
I
think
the
25th
I
believe
he
did,
however,
stand
up
a
doc.
I
saw
as
proof
of
concept
before
he
left
he'll
do
the
same
for
you
press
when
he
returns.
We
all
got
spring
very
interesting,
interesting
exercise
and
I'm,
looking
forward
to
seeing
his
his
Asin
had
to
head
comparison
of
darkest
ores
versus.
If
you
press,
moving
along
to
the
okay,
are
to
hire
our
new
documentation
specialist,
we're
getting
close.
A
We
are
doing
some
internal
discussions
this
week
about
the
available
strong
candidates,
visa
V,
the
ipfs
rule
that
we've
got
and
then
also
the
sort
of
analogous
file
coin
role.
So
watch
this
space
again
want
to
be
conscious
that
we're
on
a
public
call
and
went
to
respect
their
candidates
privacy.
So
if
you
have
any,
if
you
want
to
catch
up
with
me
individually,
please
feel
free,
we'll
be
happy
to
talk
through
any
of
that,
because
things
are
looking
very
optimistic.
A
Moving
on
to
the
gold
based
persona,
we
had
three
really
Eric
and
I
had
three
really
useful
conversations
with
engaged
partners
this
week,
audience
query
and
textile
really
interesting.
Conversations
sounds
like
we're
for
the
most
part
going
in
the
right
direction
with
the
personas,
but
there
were
some
very
interesting
caveats
and
additional
thoughts
on
that.
My
job
this
week
is
to
consolidate
those
amend.
The
persona
accordingly.
A
Add
some
notes
to
like
best
practices
for
use
of
the
persona
and
then
ship
it
which
in
this
case
means
making
it
publicly
available
at
the
top
of
our
repo
and
in
a
few
other
places,
the
okay.
Our
item
for
tactical
hotfix
is
weird,
approximately
20
hot
fixes
for
the
quarter
so
far,
and
that's
just
stuff
that
we've
noted
on
with
the
okay,
our
hot
fix
label
in
the
docs
repo.
A
So
you
know
if
you
want
to
attract
and
see
exactly
what
got
done,
just
do,
search
by
label
for
okay,
our
hot
fixes,
we've
got
I.
Think
something
like
we've
got
something
like
another
30
hot
fixes
queued
up
so
I
mean
we
haven't.
We
have
an
endless
pool
of
hot
fixes
that
we
can
choose
from.
So
that's
just
the
reminder
that
you
know
if
you
find
yourself
with
a
little
bit
of
free
time,
I
want
some
bite-sized
products
to
nibble
on
those
exist,
which
is
excellent.
B
A
There's
I
mean
there's:
there
is
some
sort
of
a
Demark
prioritization
being
done
on
these,
just
because
we've
been
a
small
team
with
that.
At
this
point,
we've
been
able
to
we've
been
able
to
sort
of
discuss
that
between
us
is
the
idea
of
things
that
are
easy
versus
things
that
are
important.
That
said,
ones
that
are
particularly
ripe
for
community
contribution
have
also
been
noted
as
such
as
Help
Wanted.
A
Those
are
generally
some
of
the
more
bite-sized
or
more
entry
point
sort
of
issues,
but
we
we
can
definitely
look
into
whether
it's
gonna
be
advantageous
to
prioritize
those
I
mean
we've
had
a
pretty
a
pretty
good
internal
sense.
At
this
point,
although
that
said
once
once
we
bring
out
no
new
Docs
person,
we're
probably
going
to
want
there
and
put
in
that
as
well.
So
alright
did
you
have
you
gonna,
say
something:
okay,.
A
So
the
front
page
quiz-
okay,
are
you
we're
continuing
to
collect?
Metrics
will
take
further
steps
from
Chris's
back
from
holiday.
We
did
also
get
I
didn't
note
this
in
the
agenda,
but
I
will,
but
we
did
also
get
our
first
in
our
first
community
note
in
the
forums
on
the
forum
issue
that
we've
sent
people
through
to
to
introduce
themselves
and
their
motives
for
using
IP
FS.
So
so
that
was
cool
I.
Have
it
on
my
things
to
do
to
write
back
to
at
least
say
hello,
and
thank
you
to
that
person
today.
A
C
Sure
so
one
of
the
biggest
things
were
still
working
on
for
Preta
school
is
reviewing
camp
content
to
see
what
we
can
adjust
into
protocol
format.
So
as
kind
of
related
to
that
camp
content
review
I
drafted
a
blog
post
for
the
course
video
release
that
will
hopefully
happen
later
this
week.
So
there's
a
link
to
a
PR
for
that
for
anyone
who
likes
proof
and
then
I
posted
links
here
to
first
drafts
of
q3,
okay,
our
scoring
and
q4.
Okay,
our
draft
both
of
what
you're
so
kind
of
works
in
progress.
I.
C
Think
you
ain't,
no
scoring
I've
put
some
kind
of
question
marks
on
the
ones
that
there's
like
some
chance,
we'll
push
a
little
further
than
where
we
are
before
the
end
of
this
quarter.
But
the
biggest
thing
we'll
do
on
that
front
in
the
time
that
we
have
left
for
me
will
be
camp
content
and
for
Jill
after
you
know,
more
onboarding
stuff
would
be
trying
to
start
the
tutorial
on
the
non
em
FS
Files
command.
So
those
are
gonna
be
the
highlights
if
we
can
get
to
any
more
of
it
but
I'm.
C
B
Very
good
question:
it
would
your
your
point
on
this
is
literally
reminding
me
that
I
was
supposed
to
create
the
github
issue
where
it
collects
all
of
our
stuff
and
we
can
post
our
updates
as
well.
I
think
the
aim
for
scoring
we
should
try
and
get
that
done
like
last
last
time
to
get
bettin
would
be
around
the
20th
so
the
end
of
this
week
and
then
aim
for
the
27th
for
having
drafts
of
all
of
our
and
q4
grades.
B
And
but
it's
gonna
be
also
kind
of
like
meta,
overarching
doc,
trying
to
prioritize
across
groups
as
well,
and
that
you
should
have
done
by
Friday
of
this
week
and
to
share
out
with
everyone
as
well,
so
that
people
can
use
that
to
how,
with
the
cross
coordination
side,
though
I
think
every
group
kind
of
has
a
decent
idea
of
the
main.
The
main
priorities
within
and
its
might
just
just
help
be
kind
of
a
top-level
view
into
how
things
interconnect
with
each
other
Gotenks.
This
Friday
grading,
next
Friday,
new,
ok,
ours
and.
A
A
B
A
We
went
through,
we
have
a
lot
of
discussion
as
the
core
team
last
week,
when
Eric
and
I
were
co-working
and
I
think
we
actually
knocked
a
whole
lot
of
active
discussion
out
during
that
time,
which
may
explain
why,
we're
being
so
incredibly
efficient
today,
we
had
some
very,
very
good
discussion
around
okay,
our
own
features
prioritization
that
actually
took
a
very
long
very
long
time.
So
thank
you.
A
D
B
C
A
C
There's
a
nom,
I'm
coding,
one
that
we
have
right
now
is
kind
of
confusingly
mixing
a
couple
of
topics
in
a
way.
That's
not
clear
what
the
point
isn't:
mixing
them
so
separating
that
one
out.
So
those
are
the
key
things
that
we
envision
for
the
content
and
obviously
this
will
take
shits
shape
from
that
exploration
of
camp
content
and
then
the
next
section
is
kind
of
learner
experience
user
experience.
C
So
this
is
a
lot
of
that
like
how
stuff
works
under
the
hood
or
what
they
with
the
user
sees
so
I
need
to
finish
up
the
documentation
for
like
designing
effective
tutorials.
We
already
have
a
lot
of
very
detailed
content
on
building
them
in
view,
but
not
on
what
makes
for
a
good
tutorial.
So
that's
super
top
priority
because
it's
going
to
allow
for
more
contributions
from
the
community.
We
do
have
at
least
one
person
who
has
expressed
an
interest
in
building
content,
which
is
awesome.
C
We
wanted
like
put
a
little
pause
on
and
review
other
online
coding
tutorial
platforms,
just
in
case
there's
something
out
there.
That
would
be
a
good
fit
for
us
so
that
if
we
want
to
do
something
else,
instead
of
continuing
to
build
out
our
own,
that
we
know
sooner
and
move
over
sooner
and
one
thing
that
comes
out
of
camp
content
is
that
there's
that
cool
CID
inspector
available
now
that
was
demonstrated
in
Alan's
course.
That
could
be
neat.
C
Don't
think
our
team
is
in
a
place
where
we
have
the
right
skill
sets
to
do
that,
and-
and
these
are
two
suggestions
that
came
from
Andrew-
that
are
both
great
and
I-
think
won't
be
too
hard
to
implement.
So
now
that
we
can
tell
that
you've
completed
every
single
lesson
in
a
tutorial
we
can
set
something
up
so
that
when
you
have
finished
a
whole
tutorial,
you
can
their
savior
saved
the
completed
code,
because
the
last
lesson
in
the
tutorial
is
basically
all
of
the
lessons
adding
up
to
you.
C
We
could
save
as
adjust
the
code
from
the
successful
code
from
the
last
one,
and
then
we
could
also
do
something.
That's
like
starting
a
tweet
to
promote
the
fact
that
you
just
simply
do
the
tutorial
just
a
couple
of
things.
That
would
be
a
little
more
like
publicity
or
integration
with
different
things,
not
incredibly
important,
but
nice
tweets
to
have
yeah
go
ahead.
My.
B
Saving
code,
as
it
just
is
genius,
as
someone
who
has
literally
used
protocol
tutorials,
is
like
how
do
I
do
that
command
again,
like
I'm,
not
actually
using
it
for
documentation,
because
I
want
to
understand
it,
but
then
I
do
want
to
like
reuse
that
going
forward
letting
people
kind
of
like
hold
onto
that
and
save
it
somewhere.
That's
genius
really.
C
And
so
that's
that's
the
stuff
on
this
sort
of
user
experience
kind
of
front,
which
is
none
of
it
is
like
ginormously
time
consuming
in
theory,
but
lots
of
little
cool
things
to
pick
off
and
then
that's
the
place
where
we
end
up
getting
a
lot
of
feedback
throughout
both
content
and
UX
are
things
where
we
end
up
getting
a
lot
of
feedback
as
we
go
along
that
we
need
to
respond
here
on
the
chapter
section.
C
I
feel
same
only
that
a
lot
of
this
is
based
on
the
issue
that
you
opens
that
I
responded
to.
So
we
have
this
struggle
because
there's
not
enough
content
for
our
chapter
leaders
to
do
what
we
want
them
to,
which
is
why
I've
been
intentionally
prioritizing,
building
content
over
doing
more
on
the
chapter
front
or
pulling
in
more
chapters.
C
You
nurse,
but
something
we
do
want
to
do
is
make
sure
that
we're
documenting
kind
of
best
practices
for
facilitating
protocol
tutorials,
so
there's
a
specific
request,
which
is
to
create
documentation
that
helps
you
like
lead.
A
tutorial
live
whether
or
not
you're
a
chapter
leader,
and
this
came
from
molly
thinking
about
folks
who
might
be
at
a
conference.
C
On
that
issue,
myself,
that's
the
chapter
in
leadership
stuff
that
we
have
planned
and
which
this
these
last
two
sections,
the
top
two
sections
involve:
Joe
and
I
both
and
the
bottom
sections
are
kind
of
me
driving
them.
Then
the
bottom
one
is
just
some
stuff,
some
ongoing
stuff
to
think
about.
What's
the
future
of
the
project,
what
yeah
capacity
support
do
we
need
that
kind
of
stuff,
whether
we
want
to
start
a
blog?
Yes,.
A
C
B
I'm
going
to
one
of
the
places
where
we're
not
that
list
of
issues
came
from
was
going
to
web
3
and
talking
to
a
number
of
chapter
organizers
and
sitting
in
on,
like
watching
people,
give
proto
school
tutorials,
which
was
super
awesome
and
and
like
being
able
to
synthesize
I
gave
you
back.
I
did
not
come
up
with
it.
I
I
copied
it
down
from
what
other
folks
told
me,
and
but
they
were
really
good
recommendations
and
so
definitely
I'm
claims.
B
You
go
to
DEFCON
as
part
of
meeting
with
other
folks
in
IBM
s
ecosystem
in
a
month,
and
so
I
expect.
If
there
are
more
things
that
we
specifically
want
to
get
people's
feedback
on,
we're
gonna
have
kind
of
a
captive
group.
Together,
we
are
planning
to
do
some
more
protocol,
tutorials
and
a
couple
of
different
meetups,
and
it
would
be
awesome
if
there
was
something
that
we
could
like
it's
like
the
very
beginning
of
October
it.
So
it
doesn't
make
any
sense
to
like
assume
they.
B
Just
because
people
are
gonna
be
like
mindset
on
in
terms
of
hey,
I,
literally
just
tried,
leading
a
protocol
chapter
here,
all
the
things
that
it
would
help
me
try
and
do
this
better
or
you
know,
I
saw
here
and
I
read
this
entire
thing
that
everyone
was
reading
at
the
same
time,
I
wish
there
was
something
I
could
read.
That
is
not
just
reading
the
thing
that
everyone's
looking
at
or
something
like
that.
That
would
kind
of
help
give
you
a
feedback
loop
from
those
people
that
are
gonna,
be
on
site.
A
Jessica
and
ditto
with
and-
and
you
may
have
already
talked
to
Dan
shields
about
this,
but
it
sounds
like
we're
still
gonna
be
able
to
do
the
in-person
meetup
in
Boulder
on
the
15
16th
of
October,
whatever
that
Wednesday
is,
and
so
so
it's
going
to
be
under
the
auspices
of
an
IP,
FS,
meetup
and
Dan
is
going
to
lead
a
pretty
school
tutorial
for
the
evening
discussion.
In
some
ways
this
is
sort
of
intended
as
a
scaffolding,
to
do
some
UX
discussion
during
the
day.
A
The
plan
is
to
let
people
hang
out
at
this
super
awesome
co-working
space
in
Boulder
for
the
day
in
exchange
for
also
attending
an
evening,
which
gives
me
the
chance
to
do
some
UX
work.
That
said,
let
me
know
as
the
day
gets
closer.
What
you
want
me
to
specifically
like
take
notes
on,
because
I'm
not
going
to
be
leading
the
evening.
Meetup,
that's
going
to
be
Dan
and
so
I
can
I
can
definitely
be
the
person
in
the
corner,
who's
just
sort
of
hanging
out
watching
how
this
goes
down
and
taking
some
notes.
C
A
And
you
probably
hear
you
probably
hear
my
my
boyfriend,
who
has
a
musical
instrument
lesson
in
the
background.
So
if
you
hear
someone
practicing
an
instrument,
sorry
about
that,
all
right,
I
think
we've
actually
been
horrendously
efficient.
Probably
everybody
had
a
very
very
good
weekend.
We
have
another
meeting
in
five
minutes,
so
let's
all
disband
and
get
ready
for
our
next
meeting
in
five
minutes,
I
shall
see
all
y'all
on
the
internet.
You
know
where
to
find
us
those
of
you
in
the
outside
world
who
may
be
watching.
Please
stay
stay
in
touch
with
us.