►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-10-14
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
B
A
Everybody
out
there
in
internet
land
and
welcome
to
the
echo
fest
documentation
and
developer
UX
working
group
today
is
Monday
the
14th
of
October
20
19
I,
am
your
official
unofficial
leader
Jessica.
You
can
find
more
information
about
these
calls,
including
where
you
can
find
the
notes
document,
for
we
will
link
to
all
the
things
we
talk
about
in
the
readme
of
the
Knox
repo
at
github.
Calm,
slash,
ipfs,
slash,
Docs,
thank
you
for
joining
us
for
this
meeting.
A
Whenever
and
wherever
you
may
be
in
the
universe,
I
don't
believe
we
have
any
sort
of
outstanding
sort
of
one-off
items,
so
we
can
just
knit
they're
requiring
recurring
items
on
this
agenda
and
this
Wales
remand
order,
keeping
in
mind
that
we
have
many
epochs
in
this
quarter
and
some
of
them
not
all
of
them.
They
have
activity
every
single
week.
Okay,
docks
Peter
logic,
1a
Chris
anyway.
A
C
Is
the
the
big
epic
beginning
so
I
did
make
some
Headroom
onto
this
the
last
last
week.
Unfortunately,
then
I
got
a
little
bit
sick
as
of
last
weekend,
so
I
lost
a
bit
of
time
and
so
I
was
in
low-power
mode
from
until
Wednesday.
But
then
the
main
update
for
this
particular
call
is
that
I've
been
setting
up
the
individual,
tooling,
the
abstract.
You
are
looking
at
plugins
and
the
various
systems
that
we'll
use
to
to
basically
orchestrate
the
the
betta
app
and
launch
that
into
a
prototype
stage.
Eric
and
I
had
a
discussion.
C
A
A
I
think
1b
is
just
the
the
legacy
dock
system
deprecation
plan,
since
we're
still
in
the
early
stages
of
the
quarter.
We're
not
really
adding
a
whole
lot
of
notes
on
that.
Just
just
a
reminder
to
ourselves
that
if
anything
occurs
to
you
as
you're,
working
on
anything
else
with
the
docks,
Vita
or
anything
related
that
will
require
us
to
do
some
work
as
we
deprecate
the
old
site.
Please
continue
to
add
it
to
that
issue.
That's
kind
of
it
for
that
one,
underneath
epic,
to
a
metrics
definition
and
collection
for
the
Vita
site.
A
We're
gonna
hold
off
on
this
for
a
little
while,
based
on
two
things,
one
a
little
bit
more
Vita
site
definition
under
epic
1a
and
then
also
wing
John
on
boards
to
put
together
the
requirements
for
the
nemetrix
themselves.
So
no
movement
there
and
that's
that's
fine.
Moving
on
to
epic
to
be
II.
Did
this
amazing
thing
for
the
is
this
helpful
feedback
from
is
if
it's
all
knocked
up.
C
A
C
So
if
someone
said
no
I
don't
like
this,
and
then
he
said
what,
if
that
is
because
the
contents
out
of
date
or
it's
because
it
didn't
solve
my
problem,
maybe
it's
a
base
set
of
four
or
five
things.
Then
at
least
then
we'd
be
able
to
graph
out
the
different
sort
responses
and
in
more
of
a
metric
driven
sort
of
high-level
approach,
rather
than
having
to
pass
all
the
feedback
manually,
and
so
that
might
be
one
thing
we
could
consider,
or
it
could
be
that
we
do
that
as
an
additional
phase
later
on.
C
So
we
could
say,
we
have
a
loose
input
now
and
you
see
what
happens
and
then
and
then
we
could
all
benefit
or
meant
that
in
the
future,
with
some
kind
of
stock
answers.
If
that
doesn't
work
out
very
well,
so
we
still
don't
we're
still
yet
to
know
whether
we
get
any
actionable
input
from
those
and
things
anyway.
So
I
love.
D
A
Posted
yeah
I
mean
I,
think
it's
interesting,
because
if
we
give
them
like
three
options
like
yeah
contents,
out-of-date
or
didn't,
you
know
something
broke
when
I,
liner
or
whatnot
I.
Think
if
we
do
that
you're
right,
that's
gonna,
give
us
a
lot
more
mathematically,
useful
metrics,
I
think
it's
also
going
to
increase
the
chances
of
people
not
filling
as
a
verbatim
dramatically,
but
I'm
not
sure.
If
that's
necessarily
a
bad
thing
for
our
purposes.
A
C
Yeah,
it's
a
difference.
We
didn't
as
I
say
we
should
test
both
approaches,
I
think
because
it
could
be
that
the
responses
are
so
detailed,
and
this
points
that
people
will
spend
the
time
and
energy
to
reply
or
it
could
be
that
actually
we'll
get
more
responses.
Just
because
it's
one
click
away
and
you
know,
convenience
usually
wins
most
kind
of
most
cases
especially
scale,
but
we
don't
have
like
tremendous
amount
of
traffic
that
we're
trying
to
analyze
through
this.
C
It's
more
like
I
mean
someone
wants
to
indicate
a
specific
problem
about
a
piece
of
content
and
it
really
nice
to
have
the
exact
feedback
so
somewhere
in
the
middle.
We
definitely
want
to
optimize
it
for
ease
of
use
so
that
we
get
the
input
and
there's
no
barrier
to
entry.
So
creating
an
issue
feels
like
a
big
blocker
right.
So
it's
a
it's
going
off
somewhere.
You
gotta,
set
titles
up
and
did
it
tagged?
C
You've
got
described
it
so
unless
someone's
by
the
time
and
energy
to
do
that,
they
might
not
necessarily
do
that
so
I'm
trying
to
find
ways
where
we
could
at
least
get
hints
and
clues
towards
how
we
can
take
actual
input
without
too
much
user
generated
input
and
usually
maybe
yeah
I'll.
Try
and
summarize
those
thoughts
put
them
on
the
issue.
I
think
that's
breast
perception,
but
just
to
get
it
all
at
my
brain,
yeah.
A
A
C
A
D
A
C
D
A
C
We
could
we
could
basically
capture
that
into
without
getting
too
technical
Nicole,
but
we
can
throw
it
into
the
event
log,
but
it
doesn't
get
formatted.
We
don't
capture
who
did
it
so
you
have
made
follow-up
all
those
type
of
so
those
downsides
to
both
the
issues
the
best
way,
because
then,
obviously
we
can
track
it
all
the
way
through
we
can
alert
on
status,
and
we
can
reply
to
people
just
to
you
know
clarify
what
they
were
saying
just
in
case.
C
B
A
D
C
How
about
one
thing
then,
so
they'll
make
it
a
simpler
implementation
and
a
lot
quicker
to
deploy
we've.
We
do
the
first
step,
which
is
when
anyone
clicks
yes
or
no.
We
create
an
issue,
link
and
a
template
just
to
start
with,
so
that
we
force
people
there
and
then,
if
that
doesn't
work
out
and
people
don't
have
any
feedback,
then
we
think
about
you
ways
to
implement
other
metrics,
because
that
way
we
start
pushing
people
in
tonight.
Yes,
you
can
send
us
your
thoughts
if
this
didn't
distant
work
out
for
you
and
I.
C
A
If
you,
if
you
had
the
intermediate
step
of
like
the
click,
the
button
for
the
thing
that
you
didn't
like
and
then,
if
you
wanted
to
go
further,
then
that
person
searching
I,
think
that
gives
them
sort
of
an
initial
step
where
they
could
give
a
little
bit
more
feedback.
I
think
if
we
just
said
I'm
straight
through
to
get
hug
like
that,
can
feel
daunting.
A
Like
oh
wow,
even
with
you
know,
even
a
really
well
fleshed
out
template,
like
paradoxically
looks,
looks
like
it's
probably
gonna,
take
longer
to
fill
in
because
there's
like
all
this,
like
scaffolding
text
in
the
issue,
so
yeah
I
can
see
both
sides
of
that.
Maybe
maybe
we
talked
through
that
a
little
bit
or
does
this
continues,
but
that's
a
thought.
A
D
Ya,
I
think
it's
a
super
fascinating
thing
to
try
and
figure
out,
because
there's
so
many
layers
of
what
there
there's
like.
Is
this
person
comfortable
with
github
and
that
and
then
there's
does
this
person
feel
like
oh
I'm,
being
a
little
bit
too
forward
by
filing
a
full
on
issue
as
opposed
to
you
know,
I
was
just
a
little
annoyed
by
this
page,
so
I
want
I,
saw
a
thing
to
click
so
yeah.
There.
A
C
Why
I'm,
supposing
they're
thinking
actually
those
two
things
so
see
if
we
think
about
the
metric
step
with
set
of
decisive
actions
as
a
new
thing?
So
that's
that
we'd
have
to
discuss
and
figure
out
what
kind
of
things
we
wanted
to
track.
So
that's
gonna,
take
a
little
bit
more
time
between
us
to
finalize
on
implement,
but
the
migration
of
all
the
moving
of
the
link
and
proposing
that
they
file
an
issue
of
some
sort
or
ID.
The
page
is
actually
very
quick
because
we
essentially
just
adding
some
additional
text,
is
just
saying.
A
C
That's
the
I
so
that
I'd
happy
to
commit
to
with
what
we're
doing
right
now.
So
that's
actually
something
to
do
so
because
they're,
the
ones
a
bit
or
unknown
and
I'd
rather
develop
that
within
the
context
of
whatever
we're
building
and
for
an
improvement
step.
So
I
think
that's
a
useful
thing
to
port
I.
A
A
A
A
So
I
think
that's
Colorado's
interesting
day
is
Wednesday
Eric
and
I
will
be
there.
I'm
talking
to
the
peeps
potentially
and
handing
out
some
swag.
A
If
not
we're
gonna
sacrifice
a
personal
unused
swag
lately
lately
unused
swag,
it's
gonna
be
ad
hoc
testing,
just
based
on
who
shows
up
I
think
we
have
I
think
we
have
two
confirmed
scheduled
appointments
for
folks
who
are
not
organizers,
just
like
people
in
the
community.
The
two
organizers
also
want
to
do
the
testing
and
they
have
a
level
of
expertise,
and
that
can
prove
very,
very
useful,
which
is
awesome,
and
then
we
have
some
people
who
are
coming
in
through
the
day,
I'm
gonna,
paying
all
the
attendees
today.
Just
say
like.
A
C
Have
I
do
have
a
page
structure
already,
but
I
don't
have
all
the
steps
written
out
and
so
Eric
and
I
were
discussing
about
it.
So
what
we're
gonna
do?
The
phase
is
actually
creating
all
the
templates
manually
and
then
porting
in
the
content
that
we
want
for
each
piece
which,
unfortunately,
will
take
longer
so.
A
A
A
C
A
A
Future
is
voting
issues
routine
Christy
put
in
some
really
good
platforms.
I
contacted
canny
to
see
if
they
special
pricing
is
an
open-source
project.
I
just
heard
back
from
them
like
20
minutes
ago.
This
is
we
pricing
for
early-stage
startups.
How
old
are
you
or
like,
like
five
years
so
like
this
may
not
be?
We
may
not
have
access
to
special
pricing
for
them.
We're
just
because
I
do
feel.
Like
you
know,
like
I,
was
a
very
canny
pot
like
a
really
really
good
fit.
It's
just
you
know.
A
C
It's
pretty
simple
tool
and
unless
we
get
a
whole
higher
number
of
track
users,
then
the
pricing
doesn't
jump
up
to
the
high
tiers
anyway.
So
we
could
commit
to
just
giving
it
a
try
at
trial
and
see
how
we
go,
and
but
there
are
plenty
of
other
clones
that
are
very
similar,
that
will
also
do
an
equal
or,
if
not
a
good
job,
so
could
spend
half
an
hour
just
checking
out
the
others
and
see
if
there's
something
similar.
It
doesn't
really
make
much
difference
to
me,
which
we
use
in
the
end.
C
Like
it
to
continue
to
live
by,
the
whole
premise
of
starting
us
out
is
that
we
can
integrate
this
into
a
workflow
long
term.
So
if
it
doesn't
work,
then
yeah,
but
I'd
like
to
give
it
a
best
chance
possible
to
integrate
and
I
wish.
I
wish.
There
was
like
voting
features
on
github
issues,
because
that
would
be
a
nice
and
nice
way
of
doing
it
rather
than
just
using
emojis,
and
you
can't
really
count.
A
Okay,
all
right
I'll
write
them
see
what
they
say.
Yeah
I
mean
the
intro.
The
entry
tier
isn't
that
expensive,
I
guess.
The
only
danger
is
that
you
know
the
thing
is
like
an
amazing
success
and
we
use
it's
prioritizing
stack,
ranking
bunch
of
other
things
and
then
we're
on
a
platform.
This
is
a
little
worried
about
my
luck
in,
but
but
we
can
we
keep
talking
about
that.
A
You
know
on
ecosystem
audit
Eric's
do
another
stuff
watch
this
space,
yeah
and
then
content,
improvement,
user
driven
and
legacy
come
to
improvement,
epics,
3a
and
3b
right.
You
know
we're
all
working
on
other
priorities
and
we
haven't
had
a
lot
of
time
to
adjust
these,
but
continuing
on
with
nine
open
user-driven
issues
and
40
legacy
issues.
17
of
those
issues
are
in
the
same
queue
on
the
remaining
of
the
four-year
like
long
term
projects
and
they're
sitting
in
the
icebox.
So
you
know
we're
not
we're
not
in
the
horrible
way.
A
This
will
change
soon,
as
once
john
gets
on
board
it.
You
that'll,
be
consumed
the
book
if
its
attention
moving
on
epochs
three
c
content
clips
reading.
This
is
gonna
be
known
as
primary
onboarding
tasks
when
he
joins
us
in
november,
he's
already
doing
a
little
bit
of
exploratory
work
on
this,
which
is
awesome
so
and
then
produce
cool
updates,
Joe.
What's
up
so.
B
A
More
of
the
thing
it
is,
it
is
half
past.
Whatever
time
zone
you
live
in,
so
this
meeting
is
actually
officially
over
I
can
deposit
or
stop
the
recording
unless
anybody
alright.
Thank
you
so
much
world
of
the
Internet.
We
will
see
you
next
Monday
at
five
o'clock,
UTC
same
bat-time
same
bat-channel
have
a
wonderful.