►
From YouTube: IPFS All Hands Call - August 8th
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I'm
now
recording
okay,
hello,
everyone
welcome
to
the
IPS
All
Hands
meeting
Suites
little
using
Google
Hangouts
I'm
super
sorry,
Google
Hangouts
to
work
for
me
today.
There's
actually
a
lot
of
difficulty
in
that
process.
We've
been
switching
accounts
and
making
it
work
and
sometimes
doesn't
work.
They
was
one
of
those
days
we're
going
to
have
a
wider
discussion
before
we
switch
to
zoom.
If
we
switch
to
zoom
so
don't
feel
like
this
is
gonna
be
time
to
change.
Just
a
this
seems
to
work.
A
If
you
want
to
join
in
I'm
sorry,
because
you
can't
be
straining
this
room
so
I
might
about
that
today,
we're
gonna
start
a
different
type
of
call.
Normally
our
All
Hands
meeting
our
us
going
around
and
being
like
working
on
was
blocking
you.
What
can
you
get
help
on
we're
gonna?
Do
something
different
I,
don't
know
much
about
it,
so
I'm
gonna
switch
it
over
to
Matt.
Who
is
going
to
be
the
moderator
today
for
everyone
on
this
call
is
super
important
that
you
check
out
the
either
pad,
which
has
the
agenda.
A
B
You
think
so
all
right
well
yeah,
let's
start
with
the
roll
call
and
then
I'll
I'll,
give
an
explanation
of
the
structure.
I
am
proposing,
which
will
be
it
I
think
will
be
workable
until
we
come
up
with
something
better,
so
roll
call
by
you
do
it.
Oh
you
were
what
was?
How
have
you
guys
done?
Roll
calls.
A
B
So
maybe
Richard
could
you
do
as
a
note-taker
write
down
the
names
of
who's,
okay
and
then
I
will
proceed
with
usually
the
first
thing
we
would
do
after
roll
call
is
to
ask
for
more
agenda
items,
but
before
we
do
that
I'm
going
to
describe
the
call
format
that
I'm
proposing.
So
the
idea
for
this
All
Hands
call
is
to
be
a
brief
chicken
that
has
everyone
on
the
call
and
it's
the
opportunity
for
you
to
call
out
things
that
are
cross-cutting
topics
or
hey.
B
There's
this
important
thing
that
needs
discussion
who
wants
to
participate
in
that
discussion
so
like
top-level
brief
discussions
and
that
are
then
delegating
the
lengthier
discussions
or
the
detailed
discussions
of
tickets
to
project
specific
sprint,
calls
I
and
then
so.
We'll
try
to
keep
this
call
short.
Of
course,
the
first
couple
times
we
do
it.
It
might
be
a
little
bit
longer
because
part
of
the
discussion
will
be
figuring
out
the
process.
B
B
So
I
want
to
allow
a
little
bit
of
time
for
discussing
that
and
then
a
little
bit
of
time
for
discussing
the
temporary
format
we
can
use
for
those
project
specific
spring
calls,
while
we
figure
out
a
more
stable,
formal
sense
of
how
we
want
to
run
those
individual
project,
sprints
and
management,
so
any
discussion,
any
questions
about
this
format,
ideas,
misgivings
thoughts,
I
see
a
bunch
of
thumbs
up.
Okay,
all
right
all
right!
So
then
the
format
is
simple.
You
can
propose
any
agenda
item.
B
We
will
try
to
keep
the
discussion
of
any
agenda
item
down
to,
like
maybe
five
minutes
per
agenda
item
and
I.
The
moderator
is
something
we
should
rotate.
This
isn't
a
particularly
like
elaborate
task
of
moderating.
It's
just
mainly
time
teaching
and
the
main
thing
the
moderator
does
is
try
to
keep
the
discussion
on
track
and
ask
questions
like
seems
like
this.
Is
this
is
gonna?
Take
more
discussion?
Do
you
want
to
move
this
to
a
spring
called,
doesn't
need
its
own
in
spring?
B
B
D
D
A
E
One
engine
item
slash
gushing,
which
is
I'm
not
sure
if
we
are
still
doing
the
check-ins
through
github
issues,
I
mean
through
the
same
data,
be
sure,
so
if
I
can
be
in
one
of
the
items
just
confirm
if
we
are
still
supposed
to
write
down
what
we
achieved
in
the
week
before
and
and
if
so,
I
would
like
to
propose
something
related
with
that.
So,
yes,
we
can
do
it.
Yeah.
B
B
C
B
Items
so
there's
already
a
little
bit
of
a
history
there
in
previous
previous
polls.
We
have
pasted
right
shouldn't,
say
we,
it
looks
like
you
have
been
pasting.
The
nice
thing,
the
noticing,
the
notes
from
the
notes
from
you
meant
on
that
one
consolidated
issue,
which
means
that
you
can
go
to
that
issue
and
see
all
of
the
notes
there
all
the
calls
that
happens
on
that
week.
That
was
really
useful
for
me
as
someone
joining
on
I
think
we
should
keep
between.
That.
Is
that
what
you
were
talking
about
me?
E
So
I
was
asking
if
we
should
keep
doing
that
and
I
think
also
I
agree
I
really
like
to
have
that
information
like
it
takes.
Maybe
I
could
find
minutes
for
of
each
one
to
write
it
down
and
really
helps
others
know
what's
going
on
and
also
on
that,
I
would
like
to
propose,
because
we
have
been
always
saying
what
we
have
managed
to
accomplish,
and
we
typically
at
scale
like
the
things
that
we
didn't
to
accomplish
all
the
things
that
we
didn't
plan
to
do
that
week.
E
But
somehow
we
said
to
someone
that
we
were
going
to
do,
but
then
we
didn't
do
we
never
like
write
those
down
and
I
think
like
if
we
keep
doing
those
check-ins
to
be
very
important
weather
section
to
our
check-in.
Saying
hey
I
didn't
manage
to
do
this,
which
can
be
a
thing
that
you
had
planned
before
or
it
can
be
I
think
it
was
added
during
the
week.
But
at
least
like
what
the
team
know.
E
The
community
know
that
you
are
not
able
to
because
it
might
be
because
you're
blocked,
because
indeed
enough
time,
because
you
have
time,
was
questioned
by
some
other
thing
and
like
then
we
can
actively
proactively
fix
that,
like
we
can
keep
that
person
more
time.
We
can
like
bring
more
resources,
bring
more
people
to
help
with
those
tasks,
and
if
we
don't
write
those
down
like
then
weeks
fast,
and
then
we
don't
we,
we
don't
have
a
way
to
look
back
and
understand
which
items
were
dropped
on
the
way.
I.
D
Think
this
depends
a
lot
on
how
we
end
up
doing
the
project
management.
Stuff
I
also
would
love
to
have
a
listing
of
one
side
yeah
one
central
place
where
you
can
look
at
and
see
all
the
things
that
people
have
been
up
to,
and
you
know
what
was
achieved
and
also
certainly
what
was
dropped
so
that
we
can
make
sure
it
gets
handle
the
next
week
particular
for
very
pressing
things.
D
F
All
my
issues
would
be
tracked
through
that
word.
I
would
need
to
go
around
and
write
all
these
issue,
these
things
down
and
notes,
and
rather
once
a
week
when
the
sprint
half
this
sink
happens,
take
screenshots
whatever
some
way,
all
putting
down
the
current
state
of
the
Bob
wood
or
multiple
boards,
and
then
we
have
that
as
an
overview.
Yeah.
D
B
D
D
G
B
C
B
A
B
B
So
what
we're
trying
to
find
is
a
a
general
enough
process
that
the
projects
in
the
café's
community
can
opt
into
if
they
want
to
that's
something
to
to
underline
here,
nobody's
required
to
to
opt
into
the
IFS
project
management
format
if
they
don't
want
to.
But
I
think
at
this
point,
there's
quite
a
few
protocol
lapse
projects
that
we
would
like
to
use
this
approach.
B
So
we
have
a
good
way
of
starting
testing
different
ways
of
doing
that
and
then,
as
time
goes
by
and
other
projects
get
bigger,
we
can
have
something
for
them
as
a
guideline
to
basically
implement
a
project
management
project
process,
and
so
what
has
been
done
so
far
is
a
lot
of
discussion
regarding
what
it
is
and
how
we
do
it,
and
it
was
pointed
out
that
we
should
first
figure
out
the
model
so
kind
of
the
abstract
theory
around
it
and
I.
Think
one
put
it
in
a
nice
way.
B
The
goal
there
is
to
figure
out
the
description
for
the
process
so
that
you
can
implement
it
with
post-it
notes
if
needed.
So
that's
the
first
step,
there's
a
there's,
a
discussion
and
a
document
as
a
pull
request.
We'll
continue
working
on
that
document
based
on
your
feedback.
Thank
you,
Matt
and
one
and
dummy
Dan
Ellis
gave
some
feedback
on
that
and
I
think
after
one
more
iteration,
we
can
have
the
model
kind
of
as
a
baseline,
and
then
we
can
continue.
B
You
know
iterating
on
it
discussing
well,
is
this
good,
or
is
this
not
good
and
so
on,
and
then
we
can
go
to
the
discussion
of
the
mechanics,
so
I've
been
trying
to
defer
the
mechanics
discussion
since
last
week.
Is
it's
rightfully
pointed
out
in
the
issue
that
you
know
we
should
concentrate
on
the
abstract
stuff
first,
but
I
think
one
of
the
key
points
that
I
discussed
with
Jeremy
was
that
at
the
end
of
the
day,
we
would
like
to
have
something
where
the
tooling,
basically
automates
the
whole
process,
so
what's
described.
B
So
that's
kind
of
where
we
are
any
questions
comments.
One.
D
Yeah
that
also
has
also
recommended
first
question
on,
because
I
think
a
little
bit
of
this
iteration,
certainly
other
mechanics,
will
take
a
bit
of
time.
It
probably
is
one
of
the
most
important
things
to
spend
time
on
I
think
right
now
so
kind
of
like
a
requester
everyone
who
cares
about
this,
we
were,
like
you
know,
educate
some
time
to
it
like
up
front
this
week,
hopefully
can
like
land
this
as
soon
as
we
can
and
then
just
in
the
contingency
of
like
I.
D
Don't
know
how
long
that
my
cake,
whether
that's
planned
for
like
this
week
or
planned
for
next
week
or
something
when
they
want
to
like
just
figure
out
what
we
for
now
and
I,
like
you
know,
do
we
still
write
how
people
write
their
updates
and
decide
what
they're
pitching
what
they're
gonna
do
and
I
tell
people
what
they're
gonna
do
or
like
what
should
people
do
this
week?
Is
there
a
question
in
the
highlights.
F
Yeah,
but
if
we
had
like
something
I
do
like,
if
you
just
do
what
we
did
for
now
until
we
have
the
new
posters
figured
out
or
like
this
is
what
we
do
until
we
figure
things
out.
Ideally,
that's
tribute
as
simple
as
possible.
The
moment
I'm
chatting
over
the
intermediary
solution
as
much
as
possible.
A
So
I
think
like
that
would
be
great
if
what
we
were
doing
now
was
coherent
and
it
hasn't
been
the
last
months
of
stuff,
so
I
propose,
instead
of
doing
what
we
do
now
that
we
actually
go
back
to
a
previous
manner
of
just
writing
down
things
in
the
sprint
issue
just
having
for
this
week,
because
we
all
know
how
to
do
that.
Well,
it
might
take
some
time,
but
we
know
how
to
do
that.
A
B
B
B
D
And
yeah
sorry
yeah,
you
jumped
into
like
a
bike
show
that
has
been
going
on
for
a
while.
So
this
is
the
thought
here
is
we're
revamping
how
we
do
the
project
management
across
all
the
dozens
of
repos
that
we
have,
and
you
know
tons
of
contributors
and
so
on,
to
find
like
a
good
way
that
everyone
can
work
together,
and
so
people
end
up
wanting
different
kinds
of
tools
like
whether
to
represent
things,
issues
or
github
milestones
or
labels.
D
For
you
know
all,
and
we
we
think
of
those
or
the
point
there
was
to
think
of
those
as
mechanics
of
like
the
actual
ways
in
which
we
implement
some
process
and
to
instead,
at
the
beginning,
just
get
the
process
right
like
just
like
the
ideas
like
the
abstract
concept
of
like
hey
here's,
a
project.
The
project
has
a
road
and
I
have
any
road
that
has,
you
know
he's
like
milestones.
D
They
don't
need
to
be
didn't
have
mile,
so
necessarily
but
they're,
just
like
some
notion
of
like
a
batch
of
goals,
all
together
and
so
on.
So
a
good
focus
on
the
model
is
to
just
understand
clarity
on
the
process
itself.
First,
independent
of
all
the
mechanics
and
weekly
implement
to
a
find
agreement
of
that,
because
that's
way
easier,
then
and
then
see
we
can
enable
some
flexibility
and
then
they
can
act
so
that
different
people
on
different
projects
can
handle
things.
D
B
Then
that
discussion
at
this
point
has
gone
to
if
you
look
at
the
poor
quest
of
the
the
p.m.
and
document
p.m.
process
documents
that
basically
out
lee
that
the
model
came
together
very
smoothly.
If
it's
kind
of
obvious,
it's
basically
restating
things
that
we
were
already
doing
or
things
we
were
already
had
in
our
minds
and
now
the
discussion
that
will
be
happening
not
on
this
call
that
people
might
want
to
you
might
want
to
participate
in
or
might
want
to
have
nothing
to
do
with
is
is
figuring
out
the
mechanics.
B
How
do
we
make
this
work,
and
that
also
involves
a
discussion
of
scrum
versus
Kanban
or
some
mix
of
the
two,
and
all
of
that
definitely
I
and
Emily
and
Juan
and
smoothly
are
in
that
discussion.
Anyone
especially
won't
be
included
in
that
discussion,
and
then
otherwise
does
anyone
especially
want
to
get.
A
A
Would
like
to
get
updates.
I
haven't
been
involved
in
discussion
because
I
feel
like
there's.
A
lot
of
cooks
and
I
didn't
want
to
just
add
another
voice.
If
at
some
point
it
would
be
useful
to
have
another
voice.
Please
thing,
because
I
would
like
to
be
involved
I'm
just
waiting
for
you
guys
to
have
some
more
stuff
out
before
I
dive
in
and
spend
hours.
There.
B
F
F
B
B
A
B
So
then,
I
think
the
rest
of
this
discussion
can
happen
on
github
anon
on
IRC.
The
way
it's
been
happening.
That's
far.
Does
everyone
agree
with
that
and
if
there's
sort
of
my
calls
between
the
people
who
are
especially
interested
that
works
I,
don't
necessarily
need
to
plan
a
whole
week
in
advance.
Just
have
one
of
those
calls
to
be
say.
E
Definitely,
you
know
it's
always
the
best
way,
but
it's
it
sounded
to
me
that
we
are
pretty
close
to
having
the
final
version
ready.
So
if
we
can
like,
for
example,
agree
because
that's
who
and
said
like
if
you
are
interested
in
this
question,
please
like
allocate
some
time
during
this
week
to
review
it
like
maybe
like
Wednesday
like
everyone,
should
be
notified
to
hey
I,
could
review
decision
now
so
that,
like
next
week,
we
can
actually
go
into
implementation
and
not
like
previewing,
because
you
can
do
the
review
this
week.
B
Great
hey
all
right,
so
then
the
next
agenda
item
proposal
for
a
breakout
call
Hema,
fests
and
ipfs
files.
I
WI,
wasn't
sure
if
this
was
like.
Are
you
proposing
that
this
is
gonna,
need
a
whole
breakup
or
call
where
a
bunch
of
people
call
in,
or
is
this
like
this
just
needed
five
minutes
of
discussion?
That's
everyone!
Yeah.
E
We
have
talked
about
it
a
couple
of
times.
There
is
an
issue.
There
was
another
discussion
in
Lisbon
about
like
what
we
really
need
to
do
in
order
to
like
finish
a
lecture.
Now
we
completed
the
items
that
were
agreed
during
that
first
discussion
that
we
need
to
do
so
now,
it's
really
okay.
So
now
we
have
the
context
we
gave
time
to
people
to
like
present
their
feedback.
Should
we
move
forward
and
it
can
be
a
five-minute
discussion
or
if
someone
feels
very
strongly
against
it
can
be
a
thirty
minutes.
D
E
E
B
Sorry,
thank
you
hi
all
right,
so
I.
It
just
occurred
to
me
that
there
were
three
things
that
are
proposals
for
discussion
that
might
need
break
it
out.
So
I
rearranged
the
list,
so
we
can
those
first
and
then
and
then
we
can
actually
like
make
sure
that
the
next
item
is
to
talk
about
the
schedule
like
do
we
have
we
scheduled
all
the
calls
that
are
happening
today,
so
just
I'm
just
calling
out
that
I
rearranged
that
list
a
little
bit
so
the
next.
C
B
F
Was
my
son
came
the
room
so
I
just
wanted
to
mention
about
the
MF
s,
moving
to
github
I.
Think
that's
really
good,
but
I
think
this
needs
a
time
limit,
because
it
seems
to
me
that
this
is
an
issue.
That's
been
discussed
for
very
long
and
like
okay.
We
want
to
make
a
decision
in
four
weeks
or
something
like
that.
All.
B
D
A
B
A
Just
raising
hands
should
be
fine,
I
think.
As
a
way
of
saying
you
have
a
question
if
it's
relevant
since
we've
broken
up
the
discussion,
I
really
have
to
do
make
this
technical
point
so
technical
point,
actual
technical
point,
I
have
four
minutes
left
in
this
call,
because
I
hadn't
paid
for
zoom
I'm.
B
E
This
needs
a
call,
because
there
are
several
people
interested
in
discussing
this
topic.
First
of
all,
gravan
rejoin
us
today
to
get
into
the
pub/sub
discussion
that
we
have
been
having
since
the
IP
fest
workshop
and
seems
like
many
months
before,
and
there
is
already
a
bunch
of
nodes
on
get
up
and
we
need
to
figure
out
what
to
do
next.
What
should
we
be
doing
with
our
time
if
it's
like
containing
doing
a
research
start
like
doing
a
program
well
see
like
was
the
availability
to
do
that,
so
it
okay.
B
Alright,
well
then,
do
we
want
to
do
that
call
today
and
assuming
since
governs
here
today
today
we're
aiming
to
keep
this
small
at
least
under
an
hour.
So
so
do
you
won't?
That
means
we
have
a
half
hour
to
spare
before
the
JSI
PFS
call.
Do
you
want
to
do
it,
then?
That's.