►
From YouTube: libp2p Bi-Weekly Meeting - 09 24 2018
Description
Bi-weekly meeting, focusing on Q4 OKRs.
B
B
B
If
we
have
time,
let's
come
back
to
the
end,
but
I
just
want
to
make
sure
we
can
finalize
the
okay
ours.
Basically,
you
know
today
or
tomorrow.
So
so
here's
here's
where
we
are
on
okay,
ours.
So,
first
up,
if
you're
not
aware,
there's
a
calendar
link
in
the
doc
there's
a
two-hour
block,
it's
not
entirely
lit
p2p,
but
I
think
most
of
it
is
lit.
P2P
I'll
be
presenting
for
the
project.
Overall,
then
Cole
will
be
presenting
for
goal
it
p2p.
Then
sorry
I
forgot
who's
presenting
for
joyously
to
be
it's
divvied.
No.
B
B
Okay,
okay,
I'll
sort
that
out
with
you
every
male
but
otherwise
I
can
present
for
us
and
then
yeah.
That's
that
that's
the
plan
so
for
q3
scoring
I've
pinned
a
couple.
People
Cole
Cole
isn't
on
this
call,
but
he
has
a
score.
He
needs
to
get
in
I.
Think
there's
a
couple
other
people,
if
I.
Basically,
if
you
received
an
email
or
notification
from
me
this
morning,
then
I'm
still
waiting
for
a
score
from
you,
I
wasn't
planning
to
go
over
the
scoring
on.
This
call
will
do
that
on
Thursday.
B
But
if,
if
you
got
a
thing
for
me,
I'm
hoping
you
can
respond,
so
here's
where
I
want
to
focus
the
bulk
of
our
time
this
week,
oops
that
was
q3.
Okay.
So
this
this
document
is
the
q4
okay
ours.
So
let
me
just
try
to
start
it
so
as
you
struggle
with
the
zoom
controls
and
everything.
So
let
me
just
try
to
explain
the
sort
of
the
premise
of
this
document.
A
bunch
of
us
got
together
last
week
and
talked
about
this
on
Thursday,
but
not
everyone
was
there.
B
We
have
I'm
trying
to
radically
simplify
things
compared
to
last
quarter.
I
got
a
lot
of
feedback
that
last
quarter
spurred
she
was
like
so
complex
people
couldn't
understand
it
and
even
I
was
having
trouble
understanding
hit
by
the
end
of
the
quarter.
So
there
are
four:
there
are
four
real
tabs
and
then
one
kind
of
backburner
tab.
The
this
first
tab.
The
one
you're
looking
at
right
now
is
for
overall
project
objectives
and
key
results
for
q4.
B
B
B
So
let
me
just
talk
quickly
about
the
project,
one
and
then
we'll
say:
okay,
so
basically
I'm
trying
to
condense
this
down
to
the
other
mistake,
I
think
we
made
last
quarter
to
back
up
for
a
second
is
we
had
a
very,
very
large
number
of
k,
RS
and
then
we
said
well
we're
only
gonna
grade
ourselves
on
the
p0
s
and
in
hindsight
I
think
that
was
a
mistake.
I
think
what
we
should
have
done
is
have
a
an
achievable
number
of
K
ours.
B
You
know
a
stretch
but
but
basically
possible
and
then
say
we're
gonna
grade
ourselves
on
everything,
because
the
way
it
worked
out
last
quarter,
it's
sort
of
like
anything
that
wasn't
p0.
It
became
an
excuse
to
just
just
ignore
it,
and
a
few
of
them
actually
got
worked
on
anyway,
but
then
they
don't
count
toward
the
toward
the
final
scoring.
So
it
just
seemed
that
that
whole
system
seemed
well-intentioned
to
a
mess
up
to
me.
So
what
I
want
to
do
this
quarter
is
put
in
chaos.
B
Have
every
kr
be
something
we
honestly
believe
we're
gonna
do
and
it
doesn't
obviously
were
you
know
we
target
about
a
point.
Seven.
So
three
out
of
ten
of
the
chaos
aren't
gonna
get
get
done
or
get
fully
done
or
whatever,
but
I
think
we
should
try
to
set
goals
that
we
believe
are
challenging
but
achievable,
and
rather
than
just
put
everything
put
everything
in
the
sheet
first.
So
for
the
overall
project.
B
Let
me
let
me
just
talk
about
this
quickly
and
then
we
go
to
language
ones,
and
we
still
have
this
kr
about
lid
p2p
being
a
first
class
project.
I
think
the
biggest
thing
that
we
need
is
a
roadmap
and
and
then
once
we
have
that
we
need
to
develop
a
KPI,
a
key
performance
indicator,
which
is
a
quantitative
number
that
we
track
every
quarter
year
and
you're
out
of
showing
how
the
project
is
doing.
So
for
us,
it's
that
that's
gonna,
be
percentage
of
features
on
the
roadmap
completed.
B
So
you
can
see
how
that
depends
on
the
one
before
it
then.
The
second
objective
is
quality
and
dependability.
This
is
what
we
spend
most
of
the
call
on
last
week.
You
can
watch
the
video
it's
on
it's
on
the
YouTube
channel,
but
basically
a
lot
of
people,
I
think
felt.
I
think
there's
a
very
strong
consensus
on
the
call
that
we
don't
have
enough
documentation
and
it's
reaching
like
a
tipping
point
and
we've
got
to
just
do
more
documentation
work.
B
The
third
one
is
about
attracting
outside
contributors,
I'm
I'm
planning,
to
delete
this.
We,
you
can
give
me
feedback
in
a
second,
but
basically
the
language
specific
tabs
have
Kay
ours
around
hiring,
X
number
of
developers
or
X
number
of
dev
shops.
So
I,
don't
think
this
I,
don't
think
it
makes
sense
to
duplicate
it
here.
So
this
one
will
probably
go
away.
B
Three
is
closely
related
to
five,
which
is
about
event
organizing.
So
just
the
context
on
this
is
that
last
quarter,
we
spent
a
lot
of
time,
organizing
events
and
we
had
not
planned
for
that
and
so
I
had
a
chat
with
with
Juan
and
I
said:
hey
a
lot
of
lit
PDP's
time
is
going
into
event
organizing
and
it's
not
actually
a
kr
for
us
and
she'd
point
out
to
me
that
that's
probably
that's
more
likely
a
deficiency
in
the
que
ours
than
his
a
deficiency
in
the
the
system.
B
So
this
time
around
I
want
a
budget
time
in
advance
on
the
assumption
that
they're
going
to
be
little
events
like
lab
day
that
come
up
that
we
weren't,
anticipating
so
I
just
want
it.
I'll
probably
take
ownership
on
those,
but
I
just
want
to
budget
time
for
those
and
then
jumping
back
to
number
four.
We
want
to
do
more
to
support
downstream
users,
particularly
in
the
blockchain
community.
There's
a
lot
of
interest
in
this
I'll.
B
A
In
there,
yeah
just
forget
kind
of
like
an
update
of
where
we
moving
so,
if
you're
into
point
O
in
the
last,
they
had
them,
I
really
hit
on
Interscope
and
in
the
last
poll
two
weeks
ago
there
was
there
was
an
agenda.
There
wasn't
really
an
agenda
topic
of
this
one
book.
Somebody
brought
it
up
in
the
poll.
We
are
they
going
to
use
Libby
to
be
you
know,
and
it
was
basically
the
there's
a
very
high
confidence
right
now
that
you
say
you
need
to
be.
A
A
It
would
be
awesome
if
you
could
add
issues
for
everything
that
we
plan
to
work
on
kind
of
like
a
feature
list
right.
I
know
that
we've
had
a
number
of
discussions,
but
given
that
the
demon
is
gonna
take
a
prominence
and
important,
it's
gonna
be
okay
people.
It
won't
be
super
useful
if
I
could
go
into
that
call.
I
basically
speak
about
everything.
Are
we
gonna
build?
Well,
that's
on
the
roadmap
for
us
and
then
the
next
week
is
this
possible,
maybe
still
alien,
bezel
Biggs's,
not
in
the
poll.
I
can
contribute
to
that.
A
B
B
A
Exactly
so,
what's
in
my
mind,
is
sort
of
like
a
like
a
short-term
medium-term
roadmap
of
what
we
have
generally
agreed
to
work
on,
so
that
others,
so
that
we
are
prepared
for
others
to
pitch
in
as
well,
but
they
would
like
us
to
work
on
what
it
would
like
to
contribute.
So
I
need
ideally
something
that
we
have
already
agreed
on.
As
I
know,
we
have
some
great
discussion
there,
but
we
don't
we're
not.
We
haven't,
really
landed.
It.
B
E
B
A
B
Yeah
I
mean
I,
don't
know
if
this
cause
the
right
time
to
do
it,
but
it
seems
to
me
that
all
of
the
people
who
are
either
involved
in
the
demon
or
planned
to
consume
the
demon
need
to
kind
of
sync
with
each
other.
On
this
I,
don't
know
I,
guess
Raoul.
Can
you
try
to
put
push
for
a
discussion
of
this?
It
can
be
on
get.
E
B
B
Okay,
so
I'm
gonna
take
that
as
a
no
I'm
gonna
try
to
prioritize
these
p0
p1
and
then
I'm
gonna
post.
What
I've
done
on
the
so
each
of
each
of
these
tabs
has
a
corresponding
issue
on
some
github
repo
for
this
one.
It's
in
lid,
p2p,
/,
lid
p2p,
it's
like
if
you
go
to
issues
I,
think
it's
the
top
issue
or
something
it's
okay,
ours
for
q4,
so
I'm
gonna
try
to
make
a
pass
on
priorities
and
then
I'm
gonna
ask
for
people's
feedback
and
I'm
hoping
we
can
do.
B
We
can
do
this
a
sink
so
from
with
that
said,
so,
you'll
get
you'll,
get
a
github,
King
and
you're
free
to
ignore
it.
If
you're
not
interested
or
you
agree
with
it
with
all
the
priorities
I
said,
but
if
you
don't
agree
absolutely
like,
like
speak
up,
I'm,
not
trying
to
be
the
you
know,
dictator
of
this
or
something
I'm
just
trying
to
drive
it
forward.
Okay,
so
I
want
to
go
to
go
now.
Unfortunately,
Cole
can't
make
it
to
this
call.
Today.
B
B
A
A
So
these
are
some
of
the
things
that
I
would
like
to
basically
set
them
in
to
respect
that
everybody
can
contribute
to
and
provide
an
implementation
and
another
thing
that
I'm
interested
in
researching
and
kind
of
get
it
going
a
little
bit
is
an
eternity
tell
structures
for
the
teenaged.
So,
ideally,
this
is
between
awkward
we
basically
implement,
and
there
are
no
changes
to
the
awkward
protocol.
A
We
still
do
Athenian
interfacing
mauryans,
with
the
same
behavior
as
yeah
as
we
are
right
now,
but
internally
we're
able
to
keep
to
make
better
use
of
the
peers
that
encounter
and
index
them
in
a
way
that
we
can
access
their
portions
of
the
network
tree
in
a
quick
manner
and
requiring
less
khadiyah
search.
Iterations.
A
B
Yeah,
okay,
no
yeah,
no
I,
think
I
think
on
these
kind
of
caused
us
a
silence
is
a
sign
that
nobody
has
anything
to
say
right
now,
but
they
may
they
may
have
an
opinion
in
the
in
the
future
out
in
the
ether,
so
that
which
is
great
so
I,
there's
only
one
other
objective,
so
so
right
now,
I,
just
I
don't
want
to
spend
the
whole
call
on
go
because
we
can
do
our
own
meeting
on
that.
This
feels
pretty
sparse
right
now.
B
B
We
had
talked
about
some
a
couple
of
things
you
were
gonna
add.
Maybe,
let's
just
sync
offline
I
think
we're
gonna
talk
later:
yeah,
okay,
yeah,
okay,
but
so
I
think
this
is
gonna,
get
filled
in
with
more
more
features.
Hopefully,
then,
for
Jas
they're
having
a
discussion.
So
it's
the
reason
it's
blank
is
because
they're
having
their
discussion,
it's
like
everybody
else,
and
the
github
issue
and
I
thought
I
pulled
up.
Oh
sorry,
this
is
goes
AHA,
space-suited.
B
C
I
think,
like
we,
we've
kind
of
got
it
pinned
down.
I
think
the
next
thing
we're
gonna
look
at
because
it's
just
me
in
Bochco.
It's
a
lot
of
work.
I!
Think
we've
got
the
priorities,
nailed
down
what
we're
gonna!
Do
it's
really
about
laying
it
out
so
that
we
can
accomplish
it
by
the
end
of
the
quarter.
I'm
imagining
a
couple
things:
you're,
gonna
fall
off
and
I've
commented
in
the
PR
about
that.
I.
C
Think
one
of
the
biggest
things
that
we're
taking
on
is
trying
to
get
a
testbed
of
up
to
50,000,
nodes,
running
and
I.
Think
that's
gonna
have
a
lot
of
dependencies
on
what
we're
looking
at
with
like
go.
Interoperability
and
the
daemon
will
work
and
so
making
sure
I
mentioned
in
the
the
pull
request.
It
would
be
awesome
if
we
took
some
time
at
team
week
to
sit
down
and
talk
through
like
what
do
we
need
to
get
a
testbed
running?
C
Who
do
we
need
from
infrastructure
to
make
sure
we
have
what
we
need
to
spin
of
that
many
nodes
to
make
sure
that
we're
able
to
test
things
like
like
DHT
and
IP
NS?
Have
repulsive
within
rock
with
go,
be
able
spin
up
browser
nodes,
and
all
of
that,
so
that's
going
to
be
a
huge
blocker.
That
I
is
that's
going
to
require
more
than
just
the
Jas
team
to
be
able
to
do
I'm.
B
Yeah,
hey
I'm
glad
you
mentioned
items
for
the
discussion
in
team
week.
I
created
this
repo
I'm,
the
only
person
who's
contributed
to
it
so
far,
because
I
don't
think
many
people
know
about
it,
but
it's.
This
is
what
I'm
hoping
we
can
plan
once
we
get
this
okay,
our
cept,
on
next
week.
I
want
I,
want
to
be
all
about
planning
Glasgow
so
that
we
can
go
in
organize
know
what
we
want
to
accomplish
and
so
forth.
B
But
if
you
can,
oh
I,
don't
care
how
people
use
this
open
and
issue
open
a
PR
like
we,
you
know:
I
I
have
a
couple
PRS
I'm
going
to
open
for
things.
We
want
to
talk
about
and
I'll
paste
this
in
the
chat,
since
this
meeting
only
happens
every
two
weeks.
So
what
you
might
what
might
happen
on
planning
for
Glasgow?
Is
you
you
hear
from
me
over
email,
a
little
more
vocally
once
the
okay?
B
C
B
Yeah,
okay,
so
I'll.
Let
you
up
openness
you
over
there,
but
but
I'm
glad
you
brought
up
so
under
remind
people.
The
other
thing
that
your
what
you
said,
Jacob
sparked
in
my
mind,
is
it
q4
is
actually
quite
short.
Basically,
the
first
week
of
q4
or
the
like
that,
like
team
week,
is
going
to
be
occupy
the
first
half
of
October
and
then
some
a
subset
of
people
that
go
core
devs
are
even
gonna
do
an
additional
week
beyond
that.
B
So
then
it's
gonna,
that's
ipfs,
an
Olympia
peak,
so
we're
cutting
out
like
three
weeks
of
October
and
then
at
the
other
end.
December
is
the
holidays,
so
you
know
like
nothing's,
going
to
happen
after,
like
December
15
I
mean
just
realistically.
So
keep
that
in
mind
as
we're
setting
okay,
ours
like
I,
don't
want
it!
I,
don't
want
it
to
be
like
last
quarter,
where
we
set
far
more
chaos
than
we
can
possibly
achieve,
because
then
it
just
feels
it
doesn't
feel
like
something.
B
B
Okay,
okay,
okay,
well,
I
didn't
also
I'll
speak
to
rust
and
I
can
talk
to
Pierre
offline
too,
so
so,
basically,
I
think
that
the
biggest
two
things
we
could
do
for
for
us.
This
quarter
are
for
wolf.
One
is
just
to
lock
down
this
agreement
with
parody
that
parent
or
offer
maintainer
there's
mainly
it's
just
a
business
thing.
We
have
an
agreement
in
principle,
it's
just
about
PL
and
and
parity-check
agreeing
on
a
price
which
I
think
it's
like
a
I,
don't
think!
There's
any
gonna
be
any
issue
there.
B
Then
the
next
thing
I'd
like
to
do
is
hire
a
dev
shop
I'm
having
a
really
promising
discussion
over
email.
Going
with
these
folks
called
integer.
32
and
I
won't
go
into
the
details
right
now,
but
I
think
that
that's
the
promising
one
for
us.
We
can
also
go
to
parody
Tech
and
see
if
they
wanna
start
a
new
engagement
with
additional
people
beyond
here
and
tore
off.
B
So,
anyway,
that's
there's
a
kind
of
the
goals
there
peer
put
in
an
awesome
one
which
is
a
non
advanced
trust
user
should
be
able
to
understand
how
lippies
architected
in
less
than
an
hour.
So
this
is
like
a
doc
skull
and
he
wants
to
take
this
on
and
so
I'm.
A
hundred
percent
like
in
favor
of
this,
then
beyond
that
Interop
is
an
issue.
I'll
take
responsibility
for
flushing
this
out,
but
I,
don't
know.
There's
a
broader
discussion
about
interoperability,
testing
that
we
need
to
do
I.
B
Think
maybe
team
makes
the
place
to
do
it
across
all
of
the
languages,
and
it
also
ties
into
better
specs
because
we're
going
to
start
having
Java
a
Java
implementation
ease
could
just
be
bindings
to
the
go
demon,
but
they
also
could
be.
They
could
be
language
bindings,
but
they
also
could
be
full
implementation,
so
we're
gonna
have
at
least
Java
and
Python
in
your
future,
and
we
can't
continue
to
like
centrally
manage
every
every
language
implementation.
B
It's
just
gonna
be
impossible,
so
we're
gonna
need
some
kind
of
conformance
tests
that
cross
it
can
be
written
in
any
language
and
and
validated
that
way.
So
maybe
that's
time
you
talked
about
in
Glasgow
all
right,
and
so
then,
just
as
I
mentioned,
I
moved
a
bunch
of
things
to
the
backlog.
If
you
want
to
resurrect
any
of
these
feel
free.
B
Sorry,
that's
the
structures,
a
little
confusing,
but
project.
The
green
row
means
that's
what
tab
I
deleted
it
from
and
then
you
know
so
the
underneath
go
green.
It
means
I
deleted
it
from
here
and
then
I
haven't
believed
anything
from
Jason
Ross.
But
this
is
just
like
a
way
to
put
stuff
on
the
back
burner
so
that
the
primary
tabs
are
things
that
we
actually
are
going
to
achieve
any
any
thoughts
or
comments
or
questions.
B
I
can't
see
okay,
yeah
I,
don't
see
anybody
raising
their
hand,
so
are
people
feeling,
okay
about
this?
We're
gonna
present
this
on
Thursday
and
it's
a
commitment
from
basically
the
kr
owners
to
the
community
that
this
is
what
we're
gonna
do,
or
people
feeling
comfortable
with
generally
how
this
is
playing
out.
C
C
We're
pretty
locked
in
I
don't
think,
there's
a
whole
lot
of
feedback.
It's
really
just
about
making
sure
that
we
come
together
as
a
group
and
are
able
to
create,
like
the
sub
milestones
over
the
course
of
the
quarter.
To
make
sure
we
have
things
like
the
the
daemon
in
the
test
bed
infrastructure
in
place
to
complete
by
the
end
of
the
year.
A
D
B
Here's
the
issue
rows
talking
about
I,
just
pasted
it
in
the
chat.
So
so
Cole
knows
about
this.
He
he
what
he
was
out
of.
He
was
you
know
in
vacation
or
whatever
for
Thursday
Friday
over
the
weekend.
I
think
that's
why
he
hasn't
turned
in
maybe
a
step
alien.
You
might
want
to
take
a
look
at
this
and
see.
B
B
John
I'll
talk
to
you
later
later.
In
the
day,
we
follow
up
yeah,
okay,
okay
cool,
so
this
is.
This
is
how
it's
shaping
up.
I
will
see
all
of
you
on
the
github
issues.
If
I'm
not
I'm,
not
responding,
it
means
I,
agree
or
I'm.
Not
I,
don't
disagree!
So
that's
why
I
don't
respond
on
the
the
json'
from
for
most
things,
but
I
am
following
that
discussion
and
same
for
the
go
on
yeah.
That's
that's
what
I
had
for
this
week
we're
one
minute
over
so
I'm
going
to
call
it.