►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-11-04
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
We're
going
alright,
hello,
everybody
out
there
in
internet
land
and
welcome
to
the
monday
weekly
meeting
of
the
ipfs
docs
and
developer
user
experience.
My
name
is
Jessica
and
I.
Am
your
official
unofficial
host,
so
I
may
turn
the
video
off
don't
be
stirred
it's
for
your
own
good.
So
the
purpose
of
this
meeting
is
to
more
or
less
walk
through
our
progress
in
ours
for
the
year.
A
Sorry,
as
the
purpose
of
the
meeting
is
a
walk
through
ok,
ours
and
our
progress
against
them
as
such.
That
is
how
the
notes
for
this
document
are
set
out.
The
link
is
in
the
chat,
but
I
shall
also
share
my
screen
if
I
can
find
it
and
we
can
follow
along
in
the
document
together,
all
right,
I.
So,
first
of
all,
please
add
your
names,
which
you
have
that's
awesome,
alright
and.
A
B
I
generally
go
of
Johnny
because
it
makes
me
feel
younger.
Ok,.
B
A
Right
all
right,
that's
awesome!
We
are
so
so
so
glad
to
have
you
here.
You
have
joined
us
pretty
much
precisely
one
month
into
our
quarter,
so
we
will
be
trying
to
keep
you
as
up
to
up
to
date
as
our
progress
so
far.
Well,
we
continue
our
our
plans
and
our
noble
goals
for
next
year.
A
Yeah
I
will
here
all
right,
yeah
and-
and
this
is
sort
of
one
of
these
like
halfway
American
holidays,
so
some
of
us
they
get
off
and
some
of
us
don't
I,
always
suggest
that
we
actually
not
have
Mondays,
meaning
if
that
is
okay
with
everybody.
That
said,
if
you
want
to
have
an
ad-hoc
chat,
let's
just
hit
each
other
up
on
sac
or
via
some
other
me
apologize
in
advance
to
anybody
out
there
in
the
internet
who
might
drop
in
on
a
meeting
that
doesn't
exist.
Let's.
A
Perfect
yeah,
that's
a
really
good
point:
yeah
all
right
just
for
continuity
sake,
I
suspect
that
next
week
is
gonna,
be
like
just
sort
of
more
of
the
same
of
this
week.
To
be
completely
honest,
so
that's
cool!
So
alright,
sorry
I,
forgive
me
I'm
a
little
bit
a
little
bit
out
of
it
this
morning.
So
moving
a
little
bit
slowly,
but
let's
work
through.
Let's
work
through
our
opening
hours,
one
by
one
recurring
item,
Docs
veto
lunch
content
is
migrated
to
the
veto,
repo,
which
is
awesome.
All
that
content
is
in
there.
D
A
Do
everything,
but
there
are,
there,
are
just
all
wrap
things.
C
So
with
that
in
mind
as
well-
and
you
also
have
to
and
make
a
note
that
from
here
on
out,
we
are
going
to
be
any
Content
that
does
go
into
the
existing
Docs
love.
So
you
have
to
be
managed
differently
because
we'll
make
sure
any
updates
will
get
pushed
both
areas
rather
than
just
being
one
one
way
operation
now.
C
So,
but
that's
all
in
hand
from
what
here
first
thing
so
last
week
was
mainly
to
do
with
various
configuration
to
do
with
the
UI
and
the
app
config
itself,
so
getting
the
the
embedded
modules
and
setup
so
that
we
can
have
the
markdown
plugins
that
are
required.
So
now
we
have
embedded
responsive
video.
We
have
a
very
various
other
things
for
like
tasks,
this
foot,
foot,
notes
and
other
things
that
we
need
for
for
linking
relative
things
and
things.
So
that's
all
configured
now.
C
It
seems
like
tweaks
based
on
feedback
to
for
now
removing
the
in
page
navigation
between
individual
articles.
We
can
still
turn
that
on
on
a
page-by-page
basis,
if
you
want
or
a
section
by
section
basis
and
it's
just
because
our
content
typically
doesn't
have
a
more
of
a
chapter
style
navigation
flow
right
now.
So
it
was
a
little
bit
confusing
for
polling,
left
and
right
between
those
things.
So
the
options
are
there.
If
we
need
it,
but
we
can
essentially
turn
it
off
in
the
meantime,
just
this
morning,
actually
added
at
the
github
link.
C
So
now
we've
got
some
continuity
from
the
existing
site
and
the
opportunity
to
say
to
edit
through
edit
content.
Not
they
were
expecting
any
of
that
yet
because
we
haven't
actually
promote
this
new
further.
Yet
just
for
us
to
have
a
shortcut
to
individual
pages
and
then
the
bigger
piece,
which
is
three
for
two.
C
C
E
You
don't
have
to
respond
to
it
now,
but
I
was
just
curious,
like
the
left's
the
expand,
as
you
click
along
versus
the
using
either
a
right
side,
accordion
or
other
things
like
that.
I'm
just
curious.
If
we've
like
looked
at
what
other
people
are
doing
because
I
keep
getting
confused
I'm
like
wait,
there's
now
another
thing,
the
thing
I
just
clicked,
and
so.
C
D
C
That
we
actually
had
some
discussions
around
what
we're
going
to
do
with
this,
so
that
is
the
default
sort
of
out
of
the
box
set
up
with
this
currency
and
it
seems
to
work
okay,
it's
it's!
The
good
thing
is
it's
consistent
across
mobile
and
a
web-based
layout,
because,
obviously
on
a
mobile,
you
don't
get
the
opportunity
to
have
multiple
columns,
and
so
that's
the
main
advantage
of
having
it
in
one
kind
of
long
narrative.
C
C
Yes
for
now,
I'm
thinking
we're
just
rolling
with
the
defaults
until
we
get
all
the
content
laid
out
and
we
start
to
feel
how
it
works
and
flows,
but
then
yeah,
it
might
make
sense
for
us
to
say
put
that
as
a
on
this
page
type
navigation,
we're
going
to
make
sure
it's
clear
that
you
you
see
those
links,
because
they
don't
really
need
to
be
clicked
on.
It's
more
as
you
scroll
through
the
content,
then
it
highlights
at
the
position
and
it's
more
like
a
table
content
so
yeah.
C
A
C
C
A
All
right
carrying
on
a
recurring
item
of
the
legacy,
Docs
deprecation
plan-
you
know
we
just
this-
hasn't
really
changed.
We're
continuing
now
notes
as
we
go
along
in
the
process
of
implementing
the
the
beta
site.
That
is
all
being
tracked
in
issue
number
308.
So,
obviously,
if
you
have
things,
you
would
like
to
add
thoughts
on
that.
A
Let's
just
keep
track
of
them
in
the
comments
on
308
and
as
we
get
closer
to
launch,
will
organize
those
into
a
more
more
organized
way
of
tracking
our
deprecation
plan,
metrics
collection
and
definition
for
the
beta
site,
an
epic
2a
we
are
holding
off
on
this
until
you
get
settled
in
Johnny
and
we're
a
little
bit
further
on
the
pita
site
definition.
This
is
the
issue
about
just
trying
to
figure
out
what
metrics
we
want
to
be
tracking
out
of
the
box
when
we
ship
the
site
so
so
hold
on
to
that
space.
A
Recurring
item
betta
site
is
the
sound
full
feedback
mechanism.
This
is
pretty
much
in
the
exact
same
place
as
it
was
last
week.
Work
we're
ready
to
implement
this
as
soon
as
the
site's
a
little
bit
further
along
usability
testing.
No
new
testing.
This
week
we
have
implemented
all
of
the
ia
testing
results
from
the
beta
site
playground,
so
that
is
that
is
more
or
less
done
until
our
next
round
of
testing
we're
gonna
do
some
open-ended
usability
testing
with
PL
stuff
in
November.
So
that's
going
to
be
exciting
to
see
how
that
goes.
A
Watch
that
space,
obviously
any
community
feedback,
would
be
more
than
welcome
if
you
are
joining
us
from
the
community.
There
is
a
link
here
to
let
us
know
your
details
to
sort
of
step
up
as
a
beta
tester,
that's
just
so
that
we
can
be
in
touch
with
you
when
we
start
doing
this
more
detailed
testing
carrying
on
features
voting,
epic
2d.
We
have
the
public
facing
voting
page
again.
A
This
hasn't
changed
a
whole
lot,
but
I
realize
I
haven't
actually
showed
this
to
anybody
in
the
recent
meetings,
but
we
do
have
our
Canty
page
with
all
of
the
ranked
or
the
encouraging
folks
to
rank
the
features
that
they
were.
Our
own
internal
features,
prioritization
list,
the
ones
that
we
knew
we
were
going
to
do,
and
so
the
intent
is
at
launch
to.
Let
people
use
this
page
over
on
the
ones
that
they
would
like
to
see.
A
C
Gonna
say
quickly:
we
can
make
that
more
of
an
official
sort
of
roadmap
in
the
future
as
well.
So
you
can
flag
those.
So
once
something
gets
popular
or
it's
on
our
development
pipeline,
then
you
can
set
it
as
in
development
and
you
get
a
nice
little
planned
notification
on
the
county
board
as
well.
So
when
people
do
leave
feedback,
it's
a
bit
more
obvious
that
it's
coming
up
in
the
future.
Just.
A
A
C
A
C
A
Okay,
in
the
meantime,
so
Johnny
for
your
benefit,
the
changes
to
content
improvements
to
the
existing
doc
site.
We've
split
this
out
into
two
areas:
one
is
user,
driven
stuff
things
that
we've
been
proactively
reminded
by
users
in
since
taking
over
the
documents
project,
the
other
legacies
things
that
we
inherited
from
other
repos
or
just
past
issues
that
when
we
took
over
the
project
in
the
middle
of
the
year,
so
in
terms
of
user
driven
issues
which
we
try
to
prioritize
in
the
ice
box,
seven
in
soon
and
one
in
progress
since
last
week.
A
C
A
Issues
we've
got
23
of
them
in
the
ice
box
column.
Fourteen
women
scene,
we
haven't
changed
anything
since
last
week.
The
blockers
on
this
honestly
has
just
been
team
time
on
Docs
being
a
lunch
and
then
I'm
gonna
make
sure
Johnny
that
you
and
I
have
time
to
onboard
you
in
whatever
way,
is
necessary,
so
cool
cool.
Any
questions
on
that.
B
A
Yeah
there,
so
so
we
were
we're
using
we're
using
Zen
hub
internally
to
do
track.
Progress
on
things
and
I
can
walk
you
through
this.
After
this
call,
and
so
yeah
we've
just
been
using
an
icebox
column
for
things
that
we
we
know
that
we're
not
going
to
be
able
to
act
on
immediately
either
because
they're,
just
they're
too
large
or
because
we've
got
other
other
things
that
out
prioritize
them.
Okay
and
then
produce
cool
stuff,
guys
yeah.
F
You
know
until
we'll
build
a
lesson
and
I'll
proof
that
one
while
we
still
do
the
next
one
and
we
have
a
lot
of
feedback
that
we
just
incorporated
from
those
two
folks
so
we're
getting
close,
there's
a
little
bit
more
work
under
the
hood
on
validation
that
we
want
to
do
before
we
launch.
So
we
were
planning
on
today,
but
we've
decided
to
go
ahead
and
spend
the
time
now
to
take.
F
So
maybe
we
stay
on
track
and
then
the
other
thing
I
just
wanted
to
mention
here
is,
as
this
gets
out,
the
door
I
will
hopefully
dive
back
into
the
task
of
looking
at
the
IP
FS
camp
content
for
where
it
fits
in
proto,
school
and
Johnny.
The
link
that
I
just
posted
in
the
chat
is
the
issue
where
I'm
collecting,
like
as
I,
go
through
content
for
my
PFS
camp
I'm,
dropping
in
ideas
for
like
concepts
that
were
covered
in
different
lessons
and
where
they
might
fit
in
proto
school.
F
But
these
are
also
useful
materials
that
there's
a
different
okay,
art
I
think
it's
a
p2,
maybe
if
I'm
remembering
correctly
for
getting
those
things
into
documentation
if
they're
not
there.
So
that
will
just
be
a
good
one
for
you
to
watch
to
see
the
kinds
of
stuff
that
I'm
putting
in
there.
So
you
can
see
if
any
of
which
things
might
fit
well
in
the
documentation.
A
F
A
A
I
think
I
think
we're
I
think
we're
good.
Just
as
a
reminder.
We
will
not
have
this
meeting
next
week
if
there
are
notes
that
folks
want
to
share
with
the
broader
community.
Just
add
I'll,
add
another
I'll,
add
a
weekly
heading
for
next
week
for
the
11th
of
November
in
this
document,
and
we
can
we
can
update
as
needed,
just
as
as
a
as
a
second
point,
so
Molly.
E
I
believe
it
is
the
middle
of
the
quarter,
so
middle
quarter,
grading
time
is
upon
us.
I
was
just
looking
at
my
calendar
and
I.
Have
a
handy-dandy
need
eq
for
review
event
that
someone
has
added
for
me.
Thank
you
to
whoever
did
that,
but
this
is
a
reminder
for
us
to
all
check
back
in
on
the
okay
ours
that
we
said
Johnny.
E
E
This
is
an
opportunity
to
like
intentionally
set
some
things
down,
that
we
know
that
we're
not
going
to
get
to
or
refocus
some
of
our
energies
on
the
higher
priority
items
so
that
we
really
land
our
peasy
rows
instead
of
getting
even
coverage
over
P,
Jews
and
but
but
that
kind
of
lets
us
also
iterate
faster
on
our
estimates
for
ourselves,
like
you,
we
thought
we
were
gonna
get
one.
No!
No
on
this.
We
ended
up
getting
point
five.
You
full
feedback,
yeah.
E
A
A
Well,
yeah
and
good
point
are
equal
also.
What
will
also
update
that,
in
our
main
and
our
main
read
read
me
because
we
list
in
the
readme
for
the
docs
repo,
our
yeah,
it's
not
in
the
browser
that
I
shared
and
we
do
actually
track
she's
in
the
docs
repo
read
me
as
well,
so
we'll
update
those
there
as
well.
Alright,
awesome,
awesome,
well,
I
think
we
can
call
the
recording
good
for
now.