►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2020-01-27
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
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
Yeah
I
do
that
it
should
be
like
a
pop
up
coming
on.
Your
screens
now
see:
okay,
hi.
Everyone
thanks
for
joining
us
today
is
Monday
the
27th
of
John
2020.
This
is
the
IFS
docs
weekly
sync
up
call.
Today:
we've
got
myself
Johnny,
we
got
Jessica
and
we've
got
Leon
from
the
community
joining
us,
which
is
really
cool,
he's
popped
over
to
say
hi,
so
we
just
quickly
run
through
what
we've
got
going
on
for
the
next
few
weeks.
A
What
we've
got
done
in
the
past
week
and
anything
else,
anyone
used
to
bring
up
really
so
I
guess
the
number
one
thing
to
bring
up
would
be
that
we
actually
got
a
goalie,
a
search
function.
So
that's
not
running
on
the
new
bear
doc
site,
which
is
excellent
instead
of
the
old
search
function
where
it
just
it
collected
information
from
the
the
h1
headers
of
each
post
and
each
page,
it
actually
goes
through
and
I
indexes
the
entire
site
now,
which
is
really
cool.
A
So
you
can
search
for
very
unique
and
strange
terms,
and
it
should
find
what
you're
looking
for,
which
is
excellent
and
again
that's
hosted
or
doesn't
manage
by
a
go
Lea,
which
is
really
cool,
Chris
wiring
who's,
not
on
the
call
I
was
the
the
leading
driver
for
that.
So
it's
really
cool
a
lot
of
work
playing
from
him
to
get
that
up
and
running.
So
that's
fun,
I
mean
fact:
I
might
just
be
able
to
bring
it
up.
A
So
you
can
see
things
now:
cool,
okay,
cool
I'm,
so
you
guys
are
in
the
way
over
here.
So
let's
just
search
for
something:
let's
just
go
hashing,
so
this
is
really
cool.
You
got
like
a
context-sensitive
things
here,
so
you
actually
got
what's
in
the
page
as
well,
not
just
like
the
actual
header
of
the
content
you're
looking
for
so,
let's
look
on.
Let's
move
down,
yeah
I!
Guess
it
just
takes
us
to
it.
It's
just
a
load.
It's
just
a
little
more
easier
to
actually
find
the
things
you're.
A
A
Maybe
you
should
write
an
article
that
includes
brexit.
We
definitely
shouldn't
write
an
article.
The
includes
breaks
it,
but
you
know
it
was
a
laser
throwing,
but
yeah,
that's
really
cool.
So
it's
definitely
helped
us
figure
out
the
content
that
we
need
to
be
right.
The
things
that
people
are
looking
for-
and
this
is
also
really
cool,
because
this
still
power
of
really
well
with
when
other
sort
of
ipfs
projects
making
releases.
We
can
kind
of
look
at
those
releases
and
go
Oh.
A
A
C
A
A
Excellent,
okay,
cool,
so
I
guess
the
next
thing
that
we
can
guess
we
can
discuss.
Stop
sharing.
Now
is
over
the
next
couple
of
weeks.
We're
gonna
have
a
few
different
people
contributing
to
the
to
the
doc.
So
we've
got
a
few
different
people.
Picking
up
a
lot
of
the
grants
that
we
have
our
available
I
think
there's
about
seven
or
eight
grants
available
now
and
I
think
at
least
half
of
them
are
filled
up
all
they
have
yeah.
C
I
will
note
what
hasn't
been
attached
to
it
was
arbitrarily
chosen
by
me.
Oh
there
may
be.
You
know
if
something,
if
something
feels
here,
this
is
for
Leon,
for
whoever
might
be
reading
this
out
in
the
ledger
world.
If
something
feels
like
it
ought
to
be
that
it
is
valuable
enough
that
that
we
should
throw
about
the
other
to
accelerate
its
development.
Please
let
us
know.
A
Yeah
definitely
so
over
the
next
pretty
much
the
rest
of
today
really
I'm
going
to
be
going
through
and
finding
more
stuff
that
we
can
be
throwing
bounties
on
there's
a
priority.
Listening
of
that,
so
there's
like
a
priority
of
p0
all
the
way
through
2
P,
3,
P,
0
being
the
most
like
highest
priority,
freeze,
pre
3,
being
the
lowest,
which
is
probably
not
the
way
I
should
have
done
it
because
it
doesn't
make
sense
semantically
anyway,
but
yes,
I'll
just
go
through
and
then
like
throw
bounties
on
some
of
the
big
things
Leon.
A
D
A
A
Point
so
we're
kind
of
in
a
way
limbo
stage
at
the
moment.
Well,
we've
like
you've
noticed.
We've
got
the
two
repositories,
so
we've
got
ipfs,
slash,
docs
and
then
ipfs
slash,
ipfs
dogs
v2.
So
the
actual
content
should
go
into
the
v2
stuff.
So
when
you're,
making
piles
and
things
like
that,
make
them
into
the
v2
version,
but
then
all
the
issues
themselves,
they're
staying
in
ipfs,
slash
dogs.
A
There
is
an
intention
to
merge
those
two
together,
it's
just
because
while
we
still
have
the
old
silent
before
we
Capra
cater,
we
need
to
keep
that
repository
alive
with
all
the
same
content
and
things
like
that.
But
yes,
so
actual
content
changes
when
you're
writing
are
down.
I
goes
into
ipfs,
slash,
ipfs,
dot,
me
too,
but
then
the
issues
you're
addressing
or
in
the
old
ipfs
slash
dogs,
repo.
Does
that
make
sense,
cool
yeah,
it's
a
bit!
It's
it's
very
strange.
A
A
You
ever
if
you
get
stuck
or
anything
just
ping,
an
issue
in
one
of
the
two
places
and
we'll
help
you
up
yeah.
C
I
think
we
actually
for
right
now,
we've
got
I,
keep
us
Doxey
to
the
the
fetus
site
repo.
You
can't
even
open
an
issue
in
that
repo.
Basically,
that's
just
a
holding
pen
for
the
new
code
base
until
is
Johnny
said
we
deprecate
the
legacy
code
base.
We
had
intended
to
do
it
sooner
rather
than
later,
but
there's
some
extenuating
circumstances
with
an
IP
FS
world,
large
and
bandwidth.
That
mean
we're
probably
going
to
wait
until
the
end
of
the
quarter.
C
If
we
end
up
with
more
bandwidth,
we
will
accelerate
that,
but
the
deprecation
plan,
once
we
all
got
it
on
paper,
got
real
real,
lengthy
and
the
decision
was
made
just
like,
rather
than
rather
than
rush
through
this
and
potentially
botch
some
stuff,
because
there's
a
lot
of
opportunities
to
break
outside
linking
from
other
people's
tutorials
and
whatever
like
Lissa's
to
it.
Let's,
let's
delay,
make
sure
we
can
do
and
when
we
know
that
we've
got
the
resources
to
do
it
like
perfectly
well.
C
So
what
that
does
mean
is
that
all
the
issues
live
in
Docs
all
the
code
lives
in
ipfs
docks
beats
you,
which
is
sort
of
pain
in
the
butt.
That
said
any
issue,
that's
got
a
bounty
put
on
it.
We've
explicitly
noted
the
document
like
the
markdown
document
in
the
new
repo
that
you
should
see,
are
your
changes
against.
So
if
you
want
to
grab
a
mounting
issue,
this
those
examples
will
be
real
real
explicit
if
you
want
to
grab
something
that
isn't
about
any
issue
hit.