►
From YouTube: libp2p Q1 2019 OKR discussion
Description
This was our Q4 OKR discussion. We will present these OKRs publicly on Thursday 12/18. The finalized OKRs will live here: https://docs.google.com/spreadsheets/d/11GKG1DBRIIAiQnHvLD7_IqWxDGsVdaZFpxJM6NWtXe8/edit
A
A
Okay,
let's
yeah,
let's
just
see
how
this
goes.
I
just
want
to
see
if
at
the
end
of
the
meeting
I
can
I
can
get
the
YouTube
livestream
saved
without
having
to
reload
it
so
anyway,
this
will
just
be
an
experiment,
but
it's
not.
This
isn't
well
actually
I
guess
this
is
public
in
YouTube,
but
I,
don't
think
anyone,
but
us
is
gonna
watch
it.
A
A
A
A
I
think,
okay,
maybe
yeah
calm
pitches
counter
something:
okay.
Well
anyway,
hey
guys!
Oh
sorry,
about
that.
I
switched
to
the
link
at
the
last
minute
to
test
our
live
streaming
capabilities
for
next
next
lid
p2p
all
hands
so
you're
you're
live
on
on
YouTube
I
doubt
anyone
is
watching
this,
but
you're
live
on
YouTube.
The
reason
I
want
to
record
this.
This
format
Joyner
in
Australia,
because
these
morning
meetings
are
like
always
the
middle
of
the
night
for
him.
So
we
got
to
get
better
about
making
recordings
at
least
like
internally.
A
A
Okay,
so
here's
what
I
wanted
to
do
so
this
was
my
thing
on
this
call.
I
think
that
jeaious
Luke
PAP
is
in
good
shape,
like
okay,
our
sink
pretty
clear
to
me
overall
project.
I
think
this
is
what
I
think
we
should
do
as
a
theme
for
the
year
is
like
try
to
grow
the
user
base
to
1
million
users.
This
is
the
goal
suggested
by
Juan
and
daveed,
obviously
is
ambitious,
but
I
think
it's
like
the
right
I
think
I
feel
like
the
right
direction
for
us
to
go.
A
So,
as
we
think
about
these,
you
know
the
actual.
Like
engineering
work
items,
we
should
keep
in
mind
that
our
goal
is
to
kind
of
grow,
grow
the
user
base
for
the
pp.
So,
but
the
purpose
of
this
call,
though,
was
to
talk
about
go
since
I've
talked
to
people
individually,
I'll
just
run
through
this
really
quickly,
and
then
we
just
start
open
discussion,
basically
on
dhg
2.0.
Most
of
this
came
out
of
me
and
John
Heisey
discussing
socio
Johnson.
A
Let's
call
I,
guess:
Stevens,
not
that's
unfortunate,
but
yeah
me
and
John
discussing
this
with
information
that
had
been
fed
in
into
the
process
by
Steven,
as
well
as
John's
own
thoughts,
so
I'll.
Let
him
talk
more
about
that.
Multistream,
2.0,
I.
Think
Stevens
gonna
do
this
in
q1.
We
think
it's
high
priority
because
once
well,
just
as
let
Pete
if
he
gains
more
and
more
adopters,
it's
gonna
get
harder
to
change
these
really
fundamental
things
like
how
the
connection
and
shake
works.
So
Stevens
thinking
is
like
let's
charge
us
as
soon
as
possible.
A
The
swarm
host,
refactor
I
think
it's
language
to
talk
about.
Is
that?
Should
that
be
a
goal
for
q1
and
has
all
these
things
like
service
brokering
and
I?
Don't
know
I
put
dialer
update
under
there,
although
I
don't
know,
if
that's
quite
the
right
place
to
categorize
it.
So
we
let's
talk
more
about
that
one
testing
in
the
demon.
This
is
like
continuing
the
test.
You
know
get
to
50,000
nodes.
A
We
actually
put
the
50,000
no
thing
on
the
on
the
overall
project
tab
because
it's
cross
language,
but
each
language
is
going
to
have
to
do
some
additional
work
to
get
to
to
get
to
that
point,
and
Jas
also
has
this
reflection,
I
think
and
then
five
was
like.
This
is
for
you,
visa,
like
the
testing
or
whatever.
That
needs
to
be
done
on
relay
nodes
and
then
I
have
a
another
bucket
called
other.
C
E
C
Aggregation
signature
aggregation
scheme
that
relies
on
UDP.
Unfortunately,
we
don't
support
UDP
and
a
word
where
API
is
are
not
even
message-oriented,
so
we
haven't
like
that's
on
the
roadmap.
It's
a
different
topic,
but
for
now
we're
advising
them
to
be
an
early
adopter
of
quick,
so
yeah
everything
that
that
is
necessary
to
make
quick,
finally
deploy
a
ball
in
the
world.
I
guess
would
be.
You
know
my
ask
for
for
Martin.
A
C
That's
Martin
also
said
in
one
issue
that
there
is
a
really
nice
extension
that's
coming
through
in
quake
and
the
quick
community
for
unreliable
for
unreliable
unity
like
semantics
on
top
of
quake,
so
it
comes.
It
goes
like
back
up
to
Greg
and
young
too,
like
the
udb
semantic
support
and
reliable
messages,
and
this
would
be
pretty
interesting
to
like
ten
using
or
implement
in.
Let
me
to
be
kind
of
like
as
as
a
testbed
for
for
that.
You
know.
Emerging
technology,
yeah.
F
C
Maybe
that's
like
a
larger
goal
here
that
we
could
start
looking
at,
which
is
packet
or
a
packet
oriented
communication
in
general
right
and
there
are
some
small
steps
that
the
community
I
know
that
somebody
I
remember
whom
had
created
a
mult
I
think
a
multi
gram
protocol
for
negotiating
protocols
over
UDP
and
stuff
like
that.
So
there
is
some.
You
know
some
I
guess
offshoots
for
this,
but
yeah.
Basically
a
logical
would
be
welcome
here.
You.
A
C
C
A
A
A
B
A
This
is
a
huge
topic.
I
was
gonna.
Try
to
address
this
a
little
bit
on
in
kind
of
introducing
things
on
the
call
I
fretted,
but
basically
there's
like
two
parallel
processes
that
are
going
on
right
now.
One
is
this
longer
term
Road
mapping
thing
where
I
think
we
probably
after
this
quarter
I
think
we
want
to
stop
having
this
division
by
languages
and
try
to
focus
on
overall
project
goals,
but
in
the
meantime
we
need
to
deliver
q1,
ok,
ours
like
so
that
people
know
what
we're
doing
so.
A
So
then
I
thought.
Okay,
basically,
we'll
use
the
old
process
to
just
get
goals
for
q1,
so
that
people
know
what
to
do.
You
know
at
9
a.m.
on
January
2
and
then
we'll
try
to
shake
things
up
and
align
better
with
the
roadmap
and
finalize
that
in
in
January.
So
so
that's
what
you're
seeing
kind
of
so
yeah,
but
there's
a
lot
of
issues
around.
A
So
if
you
go
to
the
overall
project,
tab,
there's
a
lot
of
stuff
around
documents,
so,
first
the
so
the
first
issue
with
more
downstream
users
is
we
need
to
document
things
better,
there's
a
huge.
It
is
like
the
number
one
ask
we
hear
from
everyone
is
about
documentation,
and
then
we
also
have
yeah
these
collaborative
items
where
some
of
some
of
these
are
specs,
which
is
another
facet
of
documentation.
You
need
to
improve,
as
well
as
the
large
scale
testing.
A
If
anyone's
missing
the
link
to
this
document,
I'll
paste
it
in
the
chat
but
but
just
on,
go
itself.
I.
D
A
A
D
F
A
F
C
We
don't
I
think
in
the
in
the
Latin
lab
week
we
talked
about
specialized
Libby
to
be
nodes
in
the
sense
that
you
know
you
could
run
in
a
very
easy
manner,
a
DHT
booster
or
you
could
run
a
relay
node
and
so
on.
This
would
be
it
right,
it's
kind
of
like
exactly
there's
a
special
node
in
a
simple
binary
that
you
can
just
draw.
A
F
Yep
I,
it's
really
kind
of
just
a
detail:
I
guess
that
the
idea
leveraged
the
daemon
but
I
think
it's
just
a
good
way
of
like
dogfooding
and
keeping
that,
like
that's
like
a
project,
that's
actually
getting
use
because
it
is
it
like
very
generally
useful
and
running
it
in
the
environment.
This
will
force
us
to
make
it
more
usable
and
more
stable
and
stuff
like
that.
What.
F
A
F
A
A
Okay,
all
right,
okay,
so
we've
covered
four
and
five
we've
talked
a
little
bit
about,
but
in
the
two
sevens
seven
and
eight
hey
John.
Do
you
want
to
talk
a
little
bit
about
DHT?
Because
we
had
this
long
conversation
yesterday,
but
I
don't
know
that
anyone
else
is
aware
of
it.
Yeah.
G
So
this
is
just
the
home
with
what
I've
been
talking
to
Steven
about
I
mean
mostly
inspired
by
by
his
goals
originally,
but
I
think
we
mostly
agree
on
this,
so
we
want
a
DHT.
That
is,
we
want
to
split
it
up
into
smaller
components
that
are
easy
to
easier
to
change
individually
than
what
we
have
now,
and
we
also
want
to
get
some
so
that's
sort
of
for
the
larger
goal
later
of
of
of
experimenting
with
lookup
algorithms
and
such
to
see
how
we
can
we
can
make
it
more
robust.
G
A
Okay,
so
maybe
the
privacy
row,
we
keep
us
a
low
priority,
relatively
sure.
Yeah
yeah
p3
is
pretty
lit.
P4
means
this
is
not
gonna
happen
teacher,
but
it's
there's
like
a
10
percent
chance.
That
will
happen.
Okay,
so,
but
on
Stephens,
original
refactor
issue
I
mean.
Is
it?
Is
it
fair
to
say
that
this
is
like
sort
of
this
starting
point
from
which
we
have
to?
We
have
to
do
this
first
or
do
you
think
we
have
to
do
this?
One
first,
the
sorry
it's
not
top
aligned,
but
the
I.
G
G
G
A
G
A
A
Okay,
cool,
so
I'm
gonna
delete
these
rows.
We
should
talk
to
Matt
joiner,
though
about
what,
like
I,
think
he
can
contribute
a
lot
here
yeah.
We
can't
talk
to
him
right
now,
but
I
think
that
if
it's
possible
to
break
up
row
with
what
is
now
row,
five
into
multiple
things
like
I
think
he
could
own
some
of
those
and
okay.
G
A
A
E
A
Works:
okay,
I'm,
pretty
sure
Stevens
gonna
do
number
two
I'll
double-check
with
him,
but
I'm
pretty
sure
like
he
like
he'll.
Do
it
I,
don't
know
what
to
say
about
swarm
host,
refactor
or
Steven
thinks
we
should
do
this
step
by
step,
but
I
don't
really
I,
don't
know
how
to
break
it
down,
and
oh
these
oak
or
coal
or
bees.
Oh,
can
you
explain
this
services
thing
a
little
bit
more
yeah.
F
So
we
have
had
kind
of
two
or
three
discussions
about
like
what
that
would
look
like
I
think
where
we
left
it
off
was
I.
Think
these,
oh
you
correct
me
here
if
I'm
wrong,
but
you
you
seemed
like
you
were
interested
in
taking
like
a
first
stab
at
sketching
out
what
that
would
look
like.
F
We
had
talked
about,
maybe
forking
dig,
which
is
ubers
dependency,
injection
library
and
yeah,
and
that
would
be
kind
of
factoring
like
I
guess
the
nice
thing
is
it's
it's
not
even
though
it's
a
pretty
big
change,
it
doesn't
necessarily
have
to
be
like
a
hugely
breaking
one.
At
first
like
we
could
theoretically
move
services
that
don't
depend
on
other
stuff
over
to
this
framework,
well
piece
by
piece
but
say.
D
D
Medium
gray
already,
because
we
do
because
we
have
a
little
bit
of
a
mess
and
the
internals
wrapping
and
everything
and
we
kind
of
want
to
be
able
to
access
the
battery
services.
Time
skating
like
identify
and
now
or
not,
and
so
there
does
give
some
priority.
But
it's
not.
You
know
like
on
the
critical
path,
because
it
could.
It
doesn't
effect
right
now.
Our
external
visibility
at
all.
A
A
C
F
I
think
that's
a
good
title,
I
think
that
describes
it
well.
Okay,.
A
C
D
D
F
F
A
C
A
A
C
A
C
A
A
F
G
G
Not
really
I'm
not
sure
if
Stephen
has
a
particular
use
case
in
mind,
or
if
this
is
more
of
just
a
a
high-level
goal.
I
mean,
from
my
perspective,
the
goal
of
refactoring.
It
is
that
the
the
peer
routing
and
content
routing
systems
that
we
have
now
it
sort
of
each
be
their
own
module,
but
potentially
with
the
goal
that
that
would
be
easily
extensible
and
you
can
add
more
later,
but
I
don't
know
if
that's
aI,
don't
know.
If
that's
you
know
well
justified.
C
G
C
G
D
D
Another
thing
that
is
not
in
the
rider
right
now,
but
I
think
might
be
important,
is
that
there
was
a
discussion
about
learning
the
changing
the
d8
steam
to
face
the
provider
interface
to
use
multi
classes
instead
of
see
IDs
or
even
put
into
the
swings
I.
Don't
know
what
it
started
with
that,
because
you
know
kind
of
like
ties
together
with
C
ad
overhaul
work
in
ipfs,
so
I
don't
know,
what's
the
status
with
that,
but
man
we
might
have
a
night
where
this
will
have
an
item
for
each.
A
D
Lessons
right,
you
know,
we
don't
even
know
whether
we
actually
want
to
do
this
taste
and
whatever
usual
teahouse
is
whether
or
whether
to
use
for
things,
because
it's
kind
of
like
backwards
breaking
chains
and
it's
gonna
be
a
bear
to
deploy
this
one.
So
I
don't
know.
We
really
need
Stephens
name
put
on
that.
One
cuz
he's
the
one
driving
for
the
change.
Okay,.
D
There
is
an
open
issue:
you
can
just
read
it
there:
okay,
so
basically
they're
the
TLDR
is
that
those
are
changing.
The
multi
base,
40
IDs
and
the
all
Shady's
are
raised
58,
and
they
will
change
it
later
to
do,
which
is
gonna,
break
the
keys
when
they
make
the
chain
so
they're
going
to
make
it
so
that
it
takes.
The
movie
passes
the
reacquaint
set
of
the
CDs
or
its
base
independent,
okay,.
B
A
I'm
just
looking
at
what
we
have
okay,
so
okay,
so
you
seem
pretty
committed
to
these
two
rolled
you
so
should
we
just
leave
these
others
and
you'll
work
on?
Okay,
all
right,
I,
don't
know
what
to
do
about
packet.
Switching
honestly,
it's
really
big.
It's
really
big
endeavor
I
mean
I.
Think
it's
important,
but
are
we
gonna
really
get
to
a
key
one.
C
We
definitely
I,
don't
think
that
goal
would
be
to
implement
I,
guess
anything
related
to
that.
But
I
think
that
we
need
to
start
thinking
about
it,
and
maybe
we
can
have
some
goals
in
there
that
are
related
to
like
potential
designs,
which
are
discussions
even
if
it's
just
to
like
identify.
You
know
and
breakdown
rate,
this
further
down
into
actionable.
You.
F
Know
I
think,
like
some
design
and
interface
sketching
would
be
great.
Some
general
progress,
I
would
say
yeah.
C
A
No
I'm
I'm,
considering
that
but
I
hate
to
do
that.
Well,
no
I
think
he
actually
would
would
be
on
board
for
it.
But
I
thought
I,
don't
want
to
speak
for
him.
He
could
come
back
after
his
vacation
with
a
totally
different
mindset.
So
we
don't
know
he
said.
Would
anyone
be
willing
to
be
an
interim
owner
of
this
I
suppose
I
could
be?
If
no
one
else
will
do
it,
but
does
anyone
want
to.
A
I,
don't
I
can't
see
you
guys,
but
I
don't
hear
anyone.
Volunteering
right
here
right
here,
I'll
own
the
driving
some
discussion
on
this
and
that's
cool
I,
would
like
to
participate
on
some
level.
Yeah
yeah
I
mean
every
everybody'll
participate.
I
think
like
Porto
would
be
a
good
place.
I
did
invite
him
before
I
haven't
heard
nothing
that
I'm
hoping
he'll
come
yeah,
but
but
we
can
also
discuss
some.
You
know
their
channels
as
well.
A
C
We
shouldn't
be
pushing
it
any
further.
There
is
so
there's
some
interesting
discussion
that
is,
that
is
taking
place
in
the
ipfs
community
that
relates
as
well
to
go.
Mod
GX
and
different
people
are
taking
different
positions
and
voicing
out
like
different.
You
know
very
valid
points,
so
I
think
when
we
watch
that
for
now
see
you
know
what
the
different
opinions
in
in
PL
are
regarding
to
that
and
then
we'll
add
to
core
degree.
C
I
think
Steve
Allen
was
also
interested
and
he
had
been
sketching
out
a
proof
of
concept
for
Sri
centralizing
into
for
centralizing
interfaces
across
all
these
repositories
in
a
single
one.
So
that
is
definitely
something
to
keep
an
eye
on,
and
maybe
you
can
I'd
that
add
that
there
as
a
proof
of
concept
as
as
a
task
within
other,
as
well
so
below
Gomory
Factory
in
a
new
line
yeah,
maybe
a
proof-of-concept
would
be
like,
rather
than
go.
C
C
A
Cool
all
right,
are
you,
okay,
owning
that
I,
don't
know
yeah
you
did
you
make
yourself
on
earth?
Did
you
know
I've
made
some
noise
regarding
that,
so
it's.
C
A
E
C
Yeah
so
right
now
we
have
all
like
each
and
the
interfaces
behind
each
component
of
let
p2p
it
lives
in
a
repo
of
its
own,
and
this
is
makes
it
really
hard
for
a
newcomer
to
the
project
to
actually,
you
know
explore
what
is
over.
The
p2p
are
are
all
about,
because
they're
spread
across
number
of
rebels
and
if
you
look
at
the
history
of
those
reckless,
it
doesn't
really
like.
C
They
haven't
really
evolved
independently
as
much
as
one
would
have
expected
at
the
beginning,
and
that
would
have
justified
putting
them
in
a
separate
red
book
right.
So
that
makes
a
lot
of
sense.
So
what
so,
as
a
kind
of
like?
Ideally,
we
have
been
some.
There
has
been
some
discussion
about
potentially
having
you
know,
putting
the
p2p
all
together
into
a
mono
repo.
C
Know
where
that
is
gonna
be
headed.
This
is
like
very
you,
know,
initial
discussion,
but
as
a
like,
as
a
proof
of
concept,
step
Ali
wanted
to
wanted
to
at
least
try
centralizing
and
grouping
all
the
interfaces
in
a
single
report.
So
that
way,
we'll
have
I
call
the
abstractions
in
a
single
place
and
then
the
different
modules,
the
different
implementations
and
alternative
implementations
for
transport
for
network
for
DHT
and
so
on
would
be
was
still
live
in
separate
rebels.
Okay,.
G
E
C
B
F
B
So
one
of
the
ones
that's
on
the
road
on
the
roadmap
is
something
about
like
offline
message
queuing
and
we,
the
dynamic
data
capabilities
group
and
Steven,
and
some
other
folks
spoke
with
the
textile
people
and
they
have
their
own
version
of
some
of
these
things,
and
it
may
be
worth
putting
in
some
time
whether
it's
you
know
it's
someone
like
me
or
someone
like
slightly
outside
that
can
help
you.
You
guys
have
a
little
more
bandwidth
or
internally.
B
You
know
it's,
it's
I
think
that
one's
like
more
apparent
than
the
or
more
more
obvious
in
a
sense
than
the
you
know,
message
passing
our
PC
kind
of
thing,
which
is
just
helpful
to
get
people
involved
and
get
moving
or
is
off.
My
message,
cueing,
is
something
people
are
already
doing
in
a
sense
or
want
to
be
doing.
B
A
C
D
D
A
D
I
mean
what
is
written
in
the
spec
right
now.
It
has
already
been
implemented.
That's
like
pretty
much
ready.
So
there
are
some
things:
I
want
to
do,
improve
the
client.
You
provide
a
seamless
interface,
so
they
have
a
stateful
client
bunch
of
other
things
and
also
we
need
to
split
the
service
out
out
of
there
and
the
women
who
addition
to
have
separate
repos
for
the
service
and
during
the
client
itself.
But
this
can
happen
after
them
when
they
should
be
I
registered
some
it's
an
incidental,
but
really
ought
to
do.
Okay,.
A
I'm
sure
I
decided
whether
to
put
what
you
just
said
in
the
notes
or
just
leave
it
the
way
it
is
now
I
think
I'm
just
gonna
leave
it
like
this
I
think
we
should
do
better
Kay,
ours
and
future
quarters,
but
I'm
not
as
worried
about
it
right
for
q1
I
think
we
should
just
get
something
done
so
by
better
cars.
I
mean
like
really
specific
about
what
we're
gonna
deliver
or
not,
but
I
think
it's
ok
crap.
A
C
D
C
B
D
Because
there's
also
another
issue,
there
was
discussion
about
having
you
know
the
host
support,
multiple
choice
and
multiple
deities.
This
is
something
that
we
really
need
for
the
demon,
because,
right
now
we
don't
have
an
any
mechanism
for
having
Fergus
accident
with
many
multi-tenancy
other
than
implementing
differently
p2p
cause
at
which
fine.
You
know
there
isn't
much
gain
over
using
no
like
a
single
demon
per
liberty,
big
house.
A
A
A
H
A
A
A
A
Yes,
so
this
one
well,
these
are
P
threes,
I.
Think
then
the
near
form
guys
might
be
able
to
work
on
the
network
visualization
tool.
They
would
need
some
input
from
us
if
Roley
yeah,
but
I
think
that
I
think
I
was
going
to
reach
out
to
them
about
that.
So
let
me
put
this
as
like
and
sort
of
brackets,
like
at
your
formal
question
mark.
A
Alright,
that's
a
pretty
big
one,
but
but
alright
well
anyway,
I'm
totally
yet
for
having
help.
Okay,
okay,
okay!
Well,
we
can
leave
like
this
for
now.
Were
there
any
other
ones,
passcode
that
I
missed
it's.
A
B
H
B
C
So,
let's
for
me,
can
you
make
the
piece
the
ps4
TTL
stuff,
a
p1
that
is
working
and
it's
not
at
the
moment
causing
like
major
problem,
so
that
could
be
a
p1
for
me,
then
the
POC
for
go
want
refactoring,
I,
think
that
that
should
be
a
p0.
That's
super
important
as
we
discussed
Nick
had
a
droid
that
was
already
part
of
q4
in
a
way,
so
I
think
it
should
stay
on
as
a
PZ
over
here.
I
think.
E
C
A
C
C
C
D
D
C
Others
have
been
helping,
like
we've,
been
in
constant
communication
over
Gitter
as
well
and
yeah
I'm,
pretty
happy
that
you
didn't
get
slashed
by
the
state
as
dansgame,
because
he's
doing
some
pretty
good
work
and
stages
also
like
had
had
a
few
layoffs
and
so
on
that
they
announced
previous
week.
So
it's
great
that
he's
still
on
board.
A
A
Let's
hit
by
the
end
of
tomorrow,
I
think
we
should
yeah
cool
okay,
and
maybe
we
can
just
kick
kick
take
discussion
over
to
IRC
or
whatever.
If
there's
you
know
more
questions
about
what
are
the
parties
or
something
like
that?
Cool?
Okay,
all
right!
Well,
thanks
everyone,
I'm
gonna,
stop
the
meeting.