►
From YouTube: IPFS Community WG Weekly Sync 2019-01-17
Description
To find meeting notes, video recordings and calendar invites for theweekly sync of the IPFS Community Working Group, start here: https://github.com/ipfs/community/issues/384
B
Alright,
welcome
to
the
ipfs
community
working
group
call
alright.
So
we'll
start
with
just
a
quick
check
in
with
everybody
here,
I'll
start
out
back
this
week,
which
is
nice
after
taking
a
week
off
jump
back
into
a
bunch
of
different
stuff.
The
big
one
is
some
metrics
work
that
is
really
actually
interesting,
I
think
the
whole
community
working
groups,
so
all
I'll
give
some
more
details
on
that
and
actually
go
through
some
of
the
day
that
we've
collected
later
after
the
state's
finish
Terry
you
wanna
go
next.
A
Sure
so
my
big
thing
this
week
has
been
launching
proto
school,
so
I.
Before
that
way,
now
I
did
some
pair
programming
with
Ollie,
which
was
great
to
get
the
mobile
nav
working
and
made
a
couple
of
last-minute
tweaks
to
get
things
as
good
as
we
could
before
that
Monday
I
gave
the
presentation
on
our
ipfs
weekly
call,
and
we
had
time
for
a
little
bit
of
Q&A
there.
A
Has
the
license
built-in
that
kind
of
thing,
and
then
upcoming
for
me,
includes
I,
need
to
figure
out
how
to
locate
and
invite
ipfs
meetup
organizers
to
see
if
they'd
like
to
lead
chapters.
I
think
some
of
the
people
who
have
reached
out
already
are
those
folks,
some
not
and
then
I
need
to
do
some
exploration,
myself
kind
of
find
the
resources
that
exist
right
now
to
teach
myself
the
ipfs
file
API
in
preparation
for
building
out
a
new
proto
school
tutorial.
That
covers
that.
So
that's
probably
what's
next
on
my
docket.
C
Hey
I've
been
working
on
the
communities
think
I
have
pare
programmed
with
Andre
in
working
with
the
Google
API,
and
also
like
building
a
command-line
interface
for
putting
in
a
PR
I
was
able
to
actually
get
our
notes
from
the
different
meetings
and
turn
into
markdown,
but
still
work
in
progress
or
work
in
progress,
which
is
closer
to
being
finished,
is
actually
making
a
feature
where
you
can
announce
your
meetings
during
as
a
github
issue.
So
I
worked
with
Michaels.
That
still
needs
some
more
work,
but
it's
definitely
coming
along.
C
So
oh
and
I
also
put
in
a
proposal
for
waffle,
Jas
to
speak
about
like
ipfs
and
how
people
can
get
started
to
contributing
to
ipfs.
So
I
hope
that
talk
is
accept.
It
next
on
the
list
is
to
continue
the
community
sync
tool
and
I'm,
not
sure
if
I
have
other
stuff
I'll
talk
to
Michael
about
in
terms
in
terms
of
five
coin.
So
that's
me.
C
B
Yeah,
that's
that's
a
I
have
a
tab
open
to
reply
to
that
yeah
yeah
I'll
be
kill
it
in
in
the
issue
for
kind
of
everyone's
benefit
who's
not
like
watching
the
call,
but
yeah
I
mean
we
should
consider
it.
But
there's
there's
also
a
lot
to
kind
of
take
away
from
what
node
school
did,
which
was
they
kind
of
forced
everything
people
into
github
when
they
had
issues
which
then
connected
them
with
this
sort
of
support,
structure
and
open
source
that
they
could.
B
D
F
B
B
Yeah,
let's,
let's
check
in
on
just
like
the
okay,
our
status,
real,
quick
I'll
share
my
screen
real
fast
just
so
that
everybody
can
see.
Well,
we
updated
with
priorities,
and
now
we
have
these
nice
that
is
everywhere
from
Mali,
Thank,
You,
Ollie
and
I
just
want
to
check
in
so
Terry.
Why
don't
you
tell
us
sort
of
where
we're
at
in
terms
of
getting
protocol
out
into
its
own
topical
project
in
the
future.
A
Well,
as
as
you
see
the
way
the
okay
ours
are
structured
here,
each
of
these
key
results
on
the
left
is
a
link.
So
there
is
a
link
to
roadmap
planning,
but
that
has
not
officially
started
yet.
So
we're
not.
We
read
about
a
zero
out
of
whatever
scale
goes
up
to
on
completion
of
that
one
in
terms
of
metrics.
A
C
B
B
C
B
C
B
F
B
Okay,
I'll
find
it
in
a
second
nope.
It's
not
on
protocol
some
protocol
labs
so
for
ipfs
we're
collecting
a
bunch
of
metrics
from
our
github
or
givenchy,
but
the
tool
itself
can
actually
pull
data
out
of
any
github
org,
so
it
like
all
of
the
other
top-level
projects
that
have
their
own
Oracle
be
able
to
use
the
same
tool
as
well
as
anybody
in
the
community.
That's
why
it's
open
source
so
right
now
using
the
github
migrations
API.
This
is
able
to
pull
out
tarballs
for
all
of
the
metadata
about
all
the
activities.
B
That's
ever
happened
in
the
entire
org,
and
then
we
can
generate
some
metrics
ESDS
and
so
I've
taken
those
CFPs
and
created
some
nice
charts
here
in
Google
sheets.
I'll
share
this
link
with
everybody,
so
you
can
pull
it
up.
It's
already
live.
Where
did
the
chat?
Go?
I,
don't
know
how
to
do
the
chat
here.
I
will
put
it
in
this
Google
Doc
and.
E
B
B
Actually,
the
reason
to
break
it
down
by
quarter
is
that
their
various,
so
in
open
source
generally
like
if
you're
looking
at
sort
of
like
that,
the
top
level
data
there
are
these
huge
variants
as
an
activity
between
weekdays
and
weekends
and
when,
on
average,
you're
only
having
like
maybe
a
two
to
five
percent
change
in
activity
every
month.
If
you
have
more
or
less
weekends
in
a
month,
it
greatly
impacts
the
head,
and
so
it's
not
actually
a
change
in
the
activity
of
the
project.
B
It's
just
like
a
variance
and
how
many
like
how
many
weekdays
versus
weekend,
if
you
break
things
down
by
quarter,
it
normalizes
a
lot
of
that
and
what
you
end
up.
Having
is
like,
you
have
a
fairly
light
q4,
usually
because
a
lot
of
people
kind
of
take
off
in
December,
and
you
usually
have
a
really
strong
q1,
because
everybody
comes
back
in
January
into
anywhere
in
February,
so
with
the
biggest
months
in
sort
of
all
can
have
activity
generally
anyway,
so
yeah.
So
we
we
have
sort
of
total
unique
users.
B
This
is
the
total
number
of
actions,
just
activity
broken
down
by
type
across
the
entire
org.
So
you
can
see
that
you
know
our
issues.
You
know
grew
and
grew
and
then
declined
a
ton
and
then
came
back
in
the
org.
But
issue
comments
are
relatively
flat,
which
is
like
an
interesting
thing.
What's
happened
and
you
can
see
the
like
pull
requests
have
actually
gone
up
like
tremendously
and
the
you
know
just
since
2017.
So
that's
really
cool
to
see.
B
You
always
use
a
little
slump
into
q4.
That's
totally
normal,
not
anything
we're
not,
then
these
numbers
are
really
noisy
and
there's
a
thread
about
sort
of
fixing
this,
but
like
this
is
the
growth
percentage
for
each
of
these,
both
in
total
actions
and
in
unique
people.
So,
looking
at
the
growth
that
as
a
percentage
growth
rate
quarter-over-quarter,
it's
an
interesting
way
to
look
at
this,
but
I
have
an
issue
here.
That
I
would
love
people
feedback
on
it's
issue.
B
One
in
this
repository
I'll
post
a
link
to
it
in
the
notes,
but
basically
there
are
lots
of
other
questions
that
we
can
ask
this
data
we
have
literally
all
of
the
activity
data
for
the
entire
org.
So
what
I
really
want
to
know
from
from
everybody
here
and
and
really
in
the
whole
project,
is
like
what
are
new
questions
that
we
want
to
ask
this
data.
What
are
new
insights
that
we'd
like
to
have
into
the
project
in
terms
of
how
we're
doing
and
what
kinds
of
metrics
were
collecting?
B
F
Well,
first
thing:
when
I'm
seeing
these
graphs
it
pops
in
my
mind,
is
I
would
like
to
see
like,
if
you
could
sort
of
you
know,
do
PL
contributors
versus
other
identifiable
groups
and
see
like.
Is
it
real,
organic
because
I
mean
like
we're
being
paid
to
work
on
this?
So
obviously,
if
there's
400
contributors
in
the
head
in
is
growing
a
hundred
people
and
we've
hired
a
hundred
people
in
the
past
year.
That
explains
most
of
the
that.
F
B
Some
new
people
I
think
that,
like,
though,
when
you
look
at
poor
request
right,
you
make
users
buy
pull
request.
We
see
like
an
increase
of
about
like
in
2018
from
the
beginning
of
the
year.
To
the
end
is
something
like
you
know
that
looks
like
about
60
or
70,
like
that,
that's
quite
a
bit
like
we
did
not
bring.
B
We
did
not
hire
that
many
people
that
work
on
ipfs
yeah
I,
don't
even
we
didn't
even
hire
70
new
people
at
TL
I
totally
agree
that
I
would
like
to
separate
out
the
peel
people
from
this.
It's
just
a
lot
harder
than
you
would
think,
like
very
few
people
at
PL
actually
put
protocol
ABS
like
in
their
github
profile
information.
B
So
if
it
were
there,
I
would
be
able
to
pull
them
put
them
out
pretty
easily,
but
also
we
hire
people
from
the
community
sometimes,
and
sometimes
people
like
we
actually
expect
that
occasionally
people
will
leave
PL
and
then
work
somewhere
else
where
they
still
contribute
and
so
like.
How
do
you
separate
that
activity?
Because
it's
actually
like
during
one
time
period
they
were
working
for
PL
during
another?
They
actually
work.
B
So
if
we,
if
you
really
want
to
drill
into
it,
it's
actually
kind
of
difficult
I
think
that
what
would
be
probably
easier
is
to
quantify
the
number
of
unique
people
that
we've
put
on
a
project
and
just
at
different
time
periods
and
then
subtract
that,
from
from
the
total,
no
I
think
something
that
everybody
that
we
hired
did
something
related
to
their
job.
In
that
quarter,
yeah.
F
B
F
Are
these
are
community
contributors,
then
you
can
like
begin
sort
of
like
all
the
github
user
names
into
particular
buckets,
but
then
realize
that
people
change
buckets
over
time.
So
then
they
get
sort
of
complicated.
But
then
you
consider
like
monitor
little
flows
between
the
difference,
but
is
it
much
more
complicated,
modeling
tasks?
It.
B
It
doesn't
really
tell
us
if
they're
they're
new
to
the
project
like
absolutely
and
once
we
start
tracking
that
data.
That
may
actually
be
more
interesting
and
it's
very
easy
to
quantify
how
many
people
that
we
add
in
a
recorder
like
we.
We
know
that
pretty
pretty
easily.
So
that
would
be
very
simple
and
then
you
only
need
to
knock
it
off
of
that
quarter,
because
once
you
see
them
once
they're
never
counted
again.
B
B
B
So
before
we
see
an
initial
pull
request,
we
see
just
issue
comments
and
we
do
we
see
them
first,
like
do
people
show
up
a
year
before
they
send
a
pull
request,
or
do
they
literally
show
up,
like
you
know,
on
average
month
before
so
the
information
like
that
is
really
interesting
to
look
at
as
well,
but
yeah,
it's
just
not
something
that
we
would
put
on
the
graph.
It's
just
like
a
single
number.
That
would
be
an
interesting
and.
F
I
would
also
say
like
if
you
start
getting
into
that
level.
Detail
like
the
numbers
aren't
that
large,
but
I
did
you'd
pair
some
quantitative
analysis
with
some
qualitative
analysis
like
actually
right
pick
some
people
out
of
at
random
and
then
actually
go
out
and
look
at
what
they
did,
but
then
also
just
like
maybe
contact
them
in
person
and
interview
them.
Yeah.
B
Okay
cool.
If
we
can
turn
these
into
sort
of
succinct
questions
into
that
issue,
that
would
be
awesome,
because
I
would
definitely
like
to
get
these
you
didn't
and
and
by
the
way,
we're
already
pulling
out
some
data
in
like
a
metric
JSON.
But
it's
literally
just
single
numbers,
they're,
not
CSV,
use
that
are
a
setter
meant
to
be
a
turn
into
line
graphs
like
this.
D
Might
have
one,
and
so
we're
talking
about
trying
to
bring
people
on
board
with
these
tutorials
and
I.
Think
it'd
be
really
interesting
to
see
where
we're
having
people
having
the
most
issues,
obviously
like
so
tracking,
which
tutorials
might
be
hardest,
but
also
is
there
a
turnover?
So
at
some
point,
do
people
start
going
from
just
like
having
issues
to
may
be
contributing,
so
is
there
a
particular
set
of
tutorials
that
actually
on
board
people
to
working
on
something
more
than
just
continuing
the
tutorial
set
so.
A
The
first
part
of
your
question
will
be
addressed
when
I
add
event
tracking,
so
hopefully
we'll
be
able
to
track
things
like
whether
you
submitted
the
correct
answer,
those
kinds
of
things
to
help
us
figure
out
which
lessons
are
the
hardest.
I
think
I
could
easily
identify
right
now,
which
lesson
will
have
the
most
incorrect
answers,
but
the
second
piece
in
terms
of
figuring
out
what
people
do
afterwards
I
know
less
about
Google
Analytics,
probably
than
Michael
does
so.
A
There
is
an
issue
open
right
now,
which
Michael
opened
after
some
Twitter
discussion
that
we
could
potentially
add
sort
of
a
next
steps
screen.
That
appears
at
the
end
of
each
of
our
lessons
that
could
have
some
links
out
to
different
things.
Like
other
resources,
for
learning
that
concept
or
places
you
could
apply
it
or
places
you
can
contribute
to.
So
that's
going
to
be
both.
A
You
know
both
there's
the
project
in
there
of
how
do
we
physically
set
that
up
like
creating
the
template
for
that,
but
also
than
recruiting
like
what
are
the
projects?
We
want
people
to
work
on
so
there's
gonna
be
some
work
in
alignment
there
and
I'm
not
sure,
like
I,
think
we
would
be
able
to
track
what
was
clicked
on
in
that
list,
whether
we
can
track
all
the
way
through
from
they
clicked
there
too.
They
actually
contributed
to
a
project,
I
presume
as
much
more
challenging.
What's
your
reaction,
Michael
yeah.
B
So
we
we
should
be
able,
either
already
or
very
shortly
in
Google
Analytics,
to
figure
out
where
people
fall
off.
You
know
like
if
they
start
out
and
then
they
don't
finish
a
lesson
or
they
do
finished
with
them.
It
was
hard
like
those
kinds
of
questions
we
should
be
able
to
answer.
You
know
in
really
self-contained
way.
B
We
don't
have
a
way
right
now
to
connect
a
user
profile
in
Google
Analytics,
though,
to
like
a
github
profile,
we
we've
talked
about
how
so
right
now
the
way
that
we
save
like
your
lessons
state
and
all
of
that
stuff
is
just
in
local
storage.
So
if
you
pull
up
a
new
browser,
it
just
like
won't
be
there
and
that's
not
always
ideal
for
everybody.
So
when
we
have
like
we
need,
we
want
to
add
some
features
that
would
require
some
kind
of
login
for
persistence.
B
This
is
a
really
good
argument
to
make
that
log
in
be
login
with
github,
because
then
we
would
be
able
to
associate
that
Google
Analytics
profile
with
that
particular
github
user
and
and
then
we
would
be
able
to
see
like
okay.
You
know
here
like
beginner
profiles
that
completed
particular
tutorials.
We
would
be
able
to
look
at
you
know:
do
they
have
new
repositories
that
depend
on
ITSs?
B
You
know:
are
they
engaged
in
the
fbms
project
in
other
places
like
we'd,
actually
be
able
to
connect
those
dots
at
that
point,
but
that
that's
you
know
at
least
another
quarter
out.
Probably
we
don't
plan
on
adding
that
feature
until
the
second
quarter.
Yeah.
Does
that
answer
your
question
did
I
think.
D
B
Yeah
we,
we
should
create
an
issue,
so
we
have
an
issue
right
now:
tracking
the
additional
metrics
just
in
Google
Analytics,
so
so
that
the
first
part
stuff
that
was
just
containing
Google
Analytics.
That
I
think
has
already
captured
there,
which
is
great,
and
we
are
working
on
that.
The
the
second
part
where
we
want
to
associated
github
profile
and
we
want
to
add
some
features
that
would
persist
over
time
based
on
your
sort
of
your
you're
logged
in
account.
I,
don't
know
if
we
have
an
issue
for
that.
B
B
Right.
Okay,
so
let's,
let's
let's
add
an
issue
for
that
feature
and
then
just
note
in
the
feature
that
like
we
also
want
to
set
a
flag
once
they
log
in
that
connects
their
analytics
user
session
to
their
github
profile,
and
then
that
would
connect
the
dots
once
that's
there.
We
can.
We
can
pull
out
all
the
rest
of
data.
B
A
B
Or
potentially,
we
would
actually,
you
know,
pull
in
something
like
maybe
actually
pouch,
DB
or
some
other
sort
of
like
on
top
of
local
storage,
ride,
EB
solution
that
stinks
well
between
different
browsers,
and
we
would
plug
that
in
or
potentially
we
could
just
store
all
the
state
data
in
EFS
if
we
can
properly
connect
their
account
back,
but
then
it
like
we'd
have
to
encrypt
it.
Okay,.
A
D
We
have
just
one
little
pitch
I
put
together
a
very
light
chapter
template
that
kind
of
mimics,
the
design
of
the
main
web
page
and
so
I
think
I
threw
an
issue.
So
it's
a
separate
repo
to
throw
that
repo
into
our
org
for
people
to
look
at
if
that's
something
of
value,
otherwise
I
can
just
use
it
for
Denver.
Let.
A
Me
I
saw
that
I
saw
you
post
that
Dan
I'm,
sorry
and
then
I
lost
track
of
the
thread.
So
I
haven't
looked
at
the
at
your
template
yet,
but
I'd
like
I
I.
Think
it's
a
great
idea
to
have
that
as
an
option
for
people
like
what
I
envision
that
going
back
to
what
Michael
said
earlier
about
the
reason
we
were
envisioning
using
github
as
the
place
for
a
discussion
is
that
we
could
have
sort
of
a
like.
A
We
could
have
organized
of
sharing
with
each
other
templates
and
things
like
that
and
some
of
them
we
might
want
to
host
within
within
the
organizing
site
or
it
could
just
be
people
saying
hey,
go
look
at
how
I
did
this
thing
for
Mumbai
I
think
it's
really
cool!
You
can
copy
it.
If
you
want
to,
or
they
could
be
some
things
that
are
more
formatted
with
fill
in
the
blanks
instead
of
already
having
Denver
filled
in
what
were
you
about
to
say,
Michael
I,.
B
Was
just
saying
like
so
our
onboarding
for
new
chapters
is
starting
to
include
like
quite
a
few
kind
of
manual
steps
and
so
at
some
point
we're
going
to
want
to
probably
automate
that-
and
you
know
if
we
have
this
like
great
template
for
getting
the
site
up.
That
could
be
like
a
checkbox
when
they
ask
for
a
new
chapter
like
hey
yeah,
you
know
like
add
this
template
and
then
the
automation
would
would
pull
that
as
well.
Well,.
A
There
are
things
that
I
am
ensuring
are
done
before
I
allow
the
site
to
be
listed
on
our
chapter
listings
on
our
website
and
having
a
websites
like
having
a
github
page
of
site
is
not
one
of
them
and
I
do
not
expect
that
every
chapter
will
want
to
do
that.
So
I
think
there
are
places
where
they'll
want
to
just
use
an
IP
of
us
meetup
or
whatever.
So
we
have
not
made
having
a
github
pages
website
at
requirement
and
therefore.
A
B
Yeah,
so
that
that
could
work
one
thing,
so
this
goes
back
to
when
I
when
I
started
the
it
was.
Actually,
the
IOT
is
internationalization
community,
like
localization
community,
but
now
it's
the
node.js
localization
community,
but
basically
it
was
this
sort
of
all
call
like
hey
like
it.
You
know,
if
you
want
to
set
out
the
localization
community,
for
particular
language,
tell
me
and
we'll
get
it
set
up
and
so
very
similar
to
note
school
like
you
know
they
get
a
repose,
they
get
added
to
it.
B
One
of
the
things
that
that
I
noticed
was
that,
like
their
engagement
with
the
repo
like,
they
didn't
feel
like
they
had
the
right
to
really
like
administrate
it,
even
though
they
were
added
as
admins
to
it
until
you
sort
of
gave
them
a
task
to
do
themselves
that
required
admin.
So
what
I
started
doing
was
like
every
time
that
I
would
set
up
a
repo.
I
would
I
had
an
issue
template,
and
that
would
be
the
first
issue
and
it
was
just
a
bunch
of
things
that
they
could
go
do
like.
B
You
know
how
to
read
me
to
it.
It
had
these
things,
so
if
we
have
some
documentation
for
like
hey,
here's
that
here's
a
template
for
a
website,
here's
how
here's
some
documentation
on
how
to
get
two
pages
works.
If
you
want
to
build
something
else,
you
could
also
just
link
to
your
meetup
like
if
we
just
document
that
and
put
it
in
an
issue
and
then
add
it,
it
would
give
all
new
organizers,
like
some
steps
to
take
on
themselves
and
then
actually
feel
like
they
own
the
repo
a
little
before
yeah,
totally
yeah.
B
There's
it's
like
it's
hard
to
make.
People
actually
feel
unable
to
like
make
decisions
into
things,
even
after
you
give
them
access.
This
could
be
like
one
of
those
nice
things
and
it's
not
something
like
like
the
license
that
we're
like
actually
kind
of
worried
about
a
little
bit
like
in
the
code
of
conduct
where
it's
like.
You
really
need
to
have
these,
like,
let's
just
add
them
when
we
on
board
them
yeah
yeah.
A
So
I
mean
what,
if
you
want
to
take
a
look
Michael
at
the
Seattle
and
DC
chapters
which
I
haven't
even
holds
those
organizers
that
they're
there.
Yet
those
ones
are
me
just
today
putting
in
putting
in
a
fully
complete
license
and
a
placeholder
code
of
conduct
and
some
placeholder
text
in
the
body
of
the
repo
that
includes
some
like
to
do
actually
write.
A
Something
here
write
something
here,
so
take
a
look
at
that
and
see
if
you
think
there
are
any
of
those
that
would
make
more
sense
as
issues
because
I
do
kind
of
like
the
idea
of
like
oh
I
should
be
using
the
issue
queue.
So
we
could
put
some
of
those
things
there
or
leave
it.
I,
don't
know
whatever
is
easiest
for
people
to
get
going
risk
yeah.
B
Another
thing,
too,
is
that
in
the
issue
template
that
we
have
for
them
requesting
a
new
chapter,
we
should
probably
add
in
that
try
to
capture
the
code
of
conduct
contact
so
that
by
the
time
that
we
add
the
repo
we
can
just
create
the
code
of
conduct
and
put
in
the
contact
that
they
that
they
gave
us
when
they
applied
for
the
chapter.
If
that
makes
it
so.
B
Along
with
my
contact
and
the
reason
I
like
the
the
ones
that
we've
done
with
the
Casa
code
of
conduct
for
in
person
and
the
contributor
covenant
for
code.
They
have
a
lot
of
translations
as
well.
So
one
thing
that
a
lot
of
these
places
may
do
is
actually
just
like
pull
out
the
link
that
we
have
to
be
to
the
default
page
and
put
like
the
specific
link
to
their
localization.
Like.
F
A
That's
happened
already.
Actually,
so
the
porno
chapter
is
organized
by
the
Opio
Network
folks
who
happen
to
be
I,
think
the
Moxie
folks
who
we
know
so
they
are
linking
to
their
Opio
code
of
conduct
as
the
code
of
conduct
for
their
chapter.
So
in
their
case
they
would
have
had
to
like
delete
out
the
file
that
we
had
etc.
If
we
did
that,
but
for.
C
A
C
A
A
B
Yeah
yeah
yeah
yeah
I
mean
just
having
them
deleted,
is
fine,
like
I,
think
that
you
know,
starting
out
with
something
to
set
the
expectation
that
way
you
need
to
have
something
as
good
and
then
yeah
if
they
pull
it
out
for
theirs,
because,
like
we
like,
especially
like
the
opioid
network,
the
Opio
network
thing
is
a
really
good
example,
where
they
don't
want
to
maintain
like
the
points
of
contact
changes
in
like
multiple
different
locations.
Like
you.