►
From YouTube: IPFS Project Operations Weekly 2019-12-16
Description
Sit in on a project operations team meeting with IPFS.
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
Hello,
it
is
Monday
December,
16th,
I,
don't
normally
say
at
the
time,
which
is
a
good
thing
because
time
time
changes
for
everybody,
and
this
is
the
project
operations
weekly,
sync
and
we're
gonna
run
through
the
stuff
in
our
our
updates,
and
our
agenda
is
pretty
light
and
if
we
underly,
we
underly
it's
not
good
cool,
so
I
I'm,
first
update
on
2020
planning.
We
made
a
ton
of
great
progress
this
weekend.
A
We
still
have
a
lot
of
follow-up
conversations
with
you
know,
folks,
everywhere,
synthesizing
all
of
the
lead
feedback
from
across
the
working
groups
from
people
who
are
are
owning
various
areas
but
I
think
we're
making
really
good
progress.
There's
definitely
going
to
be
an
email
out
to
everyone
and
then
we'll
also
be
talking
about
it
in
all
hands
on
Thursday
and
so
well.
We'll
have
good
communication
out
to
everyone
around
at
least
the
main
focus
area
for
three
to
six
months.
Bye
bye
end
a
week
so
not
quite
hitting
that.
A
Okay
are
that
okay
I
had
a
date
around
it,
which
was
I,
think
November
16th,
which
we
definitely
didn't
hit,
but
it's
December,
16th
and
and
her
we're
getting
pretty
good
definition
on
at
least
a
thing
to
really
focus
and
drive
ourselves
around,
which
will
allow
us
to
unblock
ourselves
as
well
and
and
hopefully
be
more
aligned
and
execute
faster.
So
that
feels
that
feels
really
good
and
I.
A
Think
everyone's
gonna,
yeah
I,
think
that'll
be
that'll,
be
a
good
unifying
moment
and
then
the
next
step
is
actually
also
synthesizing
decision-making
criteria
and
feedback
to
make
sure
that
everyone
in
the
whole
idea
us
community
is
like
really
aware
of
kind
of
how
how
structuring
that
decision,
synthesizing
feedback
from
a
ton
of
sources
and
putting
that
rhetoric
together
to
unify
our
our
plan
forward.
You
know
set
into
it
so
that's
kind
of
where
we're
at
and
any
questions
on
that
does
that
kind
of
resonate.
A
Cool
right
free
to
send
me
using
questions
or
in
sending
out
feedback.
Do
you
tell
me
if,
if
our
like,
our
logical
structured
thinking,
doesn't
make
sense
or
if
we
have
a
gap
in
our
thoughts?
That's
all
right
with
20/20
planning
collaborations,
there's
some
async
notes
in
here.
Arkady.
Do
you
want
to.
B
So
yes,
so
I
can
take
in
Fuhrer
and
grants.
So
we
had
a
nice
catch
up
call
was
in
para,
which
seemed
like
it
was
a
good
format
and
would
be
something
that
we
will
like
proactively
schedule
as
like.
A
quarterly
check-in
was
them
as
well
as
with
others.
They
have
the
usual
complaints
that
we're
too
slow
to
review.
Things
have
some
thoughts
on
making
them
better,
but
ultimately,
there's
not
that
much
we
can
do.
B
They
are
building
a
what
they
call
a
virtual
node,
which
is
essentially
kind
of
a
re,
our
key
texture
of
of
an
ipfs
node,
where
you
would
have
a
shared
storage
and
then
kind
of
like
my
cursors
for
each
of
their
users.
On
top
of
it,
I
think
there
were.
They
have
some
thoughts
on
reorganizing
other
parts
as
well,
but
we
didn't
get
too
deep.
So
that
is
their
big
projects.
B
The
other
thing
that
they
are
working
or
that
they
would
really
like
to
see
is
IP
NS
republishing,
which
is
something
that
I
need
to
catch
up
with
a
dino
in
this
to
whether
it
can
happen.
The
other
major
updates
is
grants.
So
we
have
soft
launched
the
ipfs
deaf
grants
plan
form.
So
it's
live
now
at
ipfs,
slash
dev
grants
on
github,
the
scaffolding
is,
is
all
up,
I
doesn't
have
many
grants,
and
it's
currently,
in
fact
it
has.
It
has
none.
B
So
the
task
now
is
to
both
internally
and
through
our
kind
of
close
collaborators
put
in
kind
of
a
pilot
set
of
grants
in
there
make
sure
that
all
the
systems
make
sense
I
and
also
that
we
set
a
good
precedent
for
others
that
are
seeking
to
use
it
as
well.
We've
already
reached
out
to
a
few
folks
we'll
be
doing
more
of
that
this
week,
a
little
you
want
to
take
the
browser
updates.
C
Yep,
so
on
the
bread
on
the
Opera
Franz,
they
provided
new
builds
of
the
mobile
version
we
has
protocol
handler,
so
they
addressed
our
previous
concerns
around
like
using
our
IP
first
console
start
in
fetching
sub
resources
like
images
and
videos.
They
addressed
those
those
work.
Fine.
So
then
we
started
digging
deeper
around
origin,
isolation
and
I've
added
some
small
tests
for
that
they
don't
isolation
because
they
effectively
use
the
infrared
gateway,
as
is,
and
if
your
is
only
providing
the
path
by
gateway.
C
So
everything
is
under
a
single
origin,
but
it's
like
ongoing
ongoing
discussion
and
we
are
growing
this
testitude
as
we
go
with
this
specific
collaboration.
So
when
we
live
then
talk
with
brave,
we
got
a
ready
test
to
test
like
compliance
against
our
needs
and
so
on.
The
bright
side,
I
think
last
Friday,
with
brian
tandy,
from
from
brave,
mostly
around
long
term
strategy,
how
to
deal
with
Chrome
Web
Store.
Well,
maybe
most
like
signaling
that
problem
they
not
like.
They
not
only
use
the
store
for
I
TFS
companion.
C
C
Think
that
that's
it
I
think
there
are
also
short
short
sync
with
metamath
guys
around
use
of
our
gateways.
So
they
were
asking
us
if
they
can
use
the
web
link.
We
suggested
maybe
don't
use
our
gateway
by
default,
but
then
I
realized
they
are
already
using
our
gateway,
so
just
kind
of
suggested
that
there's
no
change,
but
there
will
be
an
improved
security
for
users
if
they
switch
to
the
web
link.
C
So
they
switch
to
the
web
link,
but
they
will
be
looking
into
either
running
about
the
J's
like
the
first
node
or
work
in
question.
Shura
I
believe,
like
the
main
blocker,
was
ensure
enough
supporting
subdomain
gateways
and
that's
kind
of
enough,
because
we
need
to
make
that
easier.
It
should
work
out
of
the
box
from
with
go
IDF
s
so
that
something
will
start
off
in
the
beginning
of
2020.
A
D
D
So
basically,
it
was
a
complete
rewrite
of
this
TL
c
TL
was
a
pretty
old
package,
some
technical
debt
that
was
accumulated
there.
Some
old
things
were
not
as
necessary,
some
missing
stuff,
so
basically
I
needed
to
rewrite
everything.
To
allow
for
writing
improvements
in
the
tests
and
also
to
future
developments
that
are
now
are
now
possible
that
weren't.
So
one
of
the
big
big
things
was
that
now
we
have
almost
we
are.
We
only
have
three
tests
skipped
in
the
browser,
and
previously
we
had
a
bunch
of
them.
D
Basically,
all
of
the
tests
that
needed
two
or
more
connected
notes
were
skipped
in
the
browser,
and
now
they
are
all
enabled
and
no
passing
and
the
three
that
we
have
skipped
are
related
to
a
very
small
specific
issue.
It
only
happens
in
Firefox,
so
I
think
we
we
can
ignore
them,
ignore
issue
and
say
we
are
a
hundred
percent.
D
We
already
have
interrupt
repo
that
basically
does
runs
a
bunch
of
interrupt
tests
between
go
daemon
and
J&J
s
demon,
the
other
ripples
we
kind
of
only
do
one
type,
so
HTTP
client
is
basically
running
tests
in
with
the
go
daemon.
Jsi
BFS
does
a
little
bit
more,
but
we
don't.
We
don't
do
kind
of
the
whole
permutation
and
all
the
combinations
that
we
we
have.
D
We
can
predefined
the
options
we
want
for
all
these
types
of
demons
and
then
we
can
build
some
kind
of
orchestration,
so
the
tests
run
I
run
against
like
the
different
combinations
between
types
of
nodes,
and
this
wasn't
possible
at
all
previously-
and
this
is
really
important,
because,
while
doing
this,
as
I
said,
I
found
out
a
couple
of
issues
that
if
we
try
to
run
the
HTTP
client
tests
and
change
the
node
type
from
go
to
GS,
a
bunch
of
tests
just
break
fail
completely.
So
we
need
to
fix
that
and
also
in
jeaious.
D
D
Besides
tiny
bits
of
performance
improvement,
cleaner
codebase,
the
options
are
the
same
at
gsfs.
So
there's
no
is
no
need
for
a
new
developer
or
even
us
to
understand
the
CTL
options
and
then
understand
the
gfs
options
all
the
same
and
yeah.
That's.
Basically,
it
there's
a
couple
more
highlights,
but
you
can
read
the
release,
notes
and
also
I
think
Dietrich
links,
video
commentary
from
the
last
web
browsers
call
I
think
so
we
can
follow
up
on
that.
If
you
want
yeah
I
think
it's
basically
it.
C
Made
the
release
notes
with
pictures,
so
those
might
be
more
interesting
that
me
talking
about
it,
but
basically
what
I
would
I
put
in
notes.
It's
there's
a
better
integration
with
wet
your
eyes
for
importing
files
typify.
So,
finally,
someone
add
import
the
files
to
IDF
s.
We
if
I
keep
a
companion
either
with
that,
like
ad
hoc
upload
import.
We
also
changed
the
language
from
Apple's
to
imports
to
remove
this
idea
that
who
you
are
uploading
to
some
server
somewhere.
C
No,
you
are
importing
data
to
your
local
node
and
then
someone
made
requested
so
when
you
import
to
a
TFS
now
it
automatically
opens
in
web
UI
interface.
So
we
had
this
interface,
but
we
never
show
that
to
user.
Now
it's
we
do
that
and
the
like
small
u.s.
improvement
around
how
we
provide
context
actions
on
DNS,
linked
websites
and
the
smoke
on
more
control
about
activity
integrations,
but
overall,
like
all
those
differ,
differ.
Behaviors
we
had
other
calls
did
not
change.
C
The
main
improvement
is
UX
around
imports,
IDs
and
that's
mostly
for
Firefox
users
cause.
If
you
are
chromium
user
or
brace
user,
you
need
to
wait
for
our
extension
to
be
reserved,
because
now
we
are
at
the
Indus,
slow,
slow
queue
and
review
process
takes
about
a
week
on
average.
It
will
take
a
week
for
people
to
actually
get
this
update.
I
think,
hopefully.
A
All
right
so
I'm
stalling
Firefox
I
get
to
play
around
with
the
newest
stuff.
I
have
great,
you
know,
I
have
brave,
know
your
eight
companion,
a
chromium,
still
some
I'm
installing
firefox
to
get
to
play
with
this.
It's
just
every
browser.
Why
not?
That's
awesome?
I
love
the
pictures.
The
pictures
are
really
great.
They.
They
really
help
visualize
exactly
how
how
to
get
access
to
these
things.
So
thank
you
for
that.
Snazzy
release,
notes.
A
B
Yes,
so
this
is,
this
is
not
really
a
thing
to
report
yet,
but
we
are
meeting
tomorrow,
I
believe
to
do
kind
of
a
prototype
quarterly
slash
annual
in
this
case
collapse
reports.
So
this
will
be
kind
of
Li,
a
retro,
slash
analysis
for
for
the
rest
of
the
org
to
learn
about.
You
know
the
the
victories,
the
setbacks
and
what
looks
promising
for
the
upcoming
quarter.
B
Yeah,
absolutely
we
already
have
a
couple
conversations
going,
we're
like
porting
and
grant
application
from
any
type
we're
putting
that
over
from
the
file
coin
set
of
things
Brian.
So,
for
me,
simple,
is
writing
something
up,
as
we
speak,
I'm
reaching
out
to
like
three
or
four
other
people
this
today
tomorrow
and
then
we
are
also
trying
to
source
some
internal
things
as
well.
A
Cool
yeah
I
think
we
feel
free
to
to
ping
me
if
you
want
suggestions
and
who
to
talk
to,
but
I
think
probably
one-on-one
chats
with
people
of
like
you
know,
I'm
gonna
sit
down
with
you
for
15
minutes,
then
we're
gonna
like
walk
through
the
ideas,
and
then
you
know
make
sure
that
people
have
contacts
for
how
to
bang
it
out,
like
that
seems
pretty
good.
We
have
that,
like
brainstorm
list
to
see.
D
A
B
A
Sounds
good,
that's
exciting
cool
I.
Think
next
one
was
me,
which
is
the
word
we're
doing.
Q4
grading
this
week,
we're
gonna
hold
q1.
Okay,
our
drafting
to
the
beginning
of
January,
but
kind
of
the
two
things
here
are
to
go
into
the
spreadsheet
and
everyone
grade
the
K
ours
for
which
you're
responsible
and
if
it
involved,
measuring
something
measure.
A
The
thing
give
a
proposal
for
for
what
grade
seems
to
make
sense
and
use
the
the
notes
column
to
kind
of
update
the
rhetoric
refer
for
why
this
thing
or
document
the
what
the
metric
was
or
whatever
it
is,
and
we
also
want
to
do
kind
of
retrospectives
looking
back
over
the
quarter.
This
is
something
that's
been
kind
of
common
practice
in
the
past,
but
especially
kind
of
we're
at
the
end
of
the
year.
It's
a
touch
point.
A
I
know
that
Allen
has
a
draft
post
for
async/await
refactor,
a
blog
post
for
that
kind
of
talking
about
what
motivated
it.
What
learnt
lessons
learned
for
doing
larger
factors
of
of
repos
like
this
and
so
I
think
it
actually
item
here
for
me
to
check
in
probably
in
the
next,
in
the
core
implementations
meeting
about
whether
that's
on
track
and
there's
a
draft
blog
post
for
our
collab
around
bit
swap
improvements
and
it
needs
I.
Think
a
little
bit
more
finalization
Dirk
is.
A
We
have
Terry
in
here
on
the
I,
confess
community
tools
and
support
I,
think
you've.
You
I've
seen
you
poking
on
these
things
and
question
work
to
you
on
either
whether
you're
blocked,
whether
you
feel
like
this
makes
sense
and
to
push
forward
on
and
whether
it's
on
traffic
or
that's.
What
the
thing
is.
I
left
a
note
in
there
that
maybe
you
haven't
seen
yet
I
think
it
makes
more
sense
in
q1.
A
For
a
variety
of
reasons,
including
that
survey
that
I
just
sent
out
about
private
school
leadership
will
look
kind
of
affect
the
package.
So
if
we
can
wait
on
those
changes
and
bundle
it,
then
it
might
make
more
sense
but
feel
free
to
Amy
one
off.
If
you
disagree.
Okay,
well,
I
haven't
seen
your
comment
yet.
A
Not
senior
survey
either
so
I
think
I
think
that's
okay
and
make
sense.
I
also
don't
want
to
it's
the
end
of
the
year
and
where
we're
starting
to
stack
communications
that
we
wanted
to
do
this
week,
so
don't
want
to
overwhelm
ourselves
with
that
either
yeah.
That's
the
other
reason
is
I.
Think
there's
it
I
mean
this
week.
A
People
will
still
be
looking
at
things,
but
starting
next
week,
I,
don't
think
anyone's
going
to
be
paying
attention,
so
I
think
we'll
also
get
more
notice
if
we
give
it
a
little,
while
the
only
thing
on
the
community
front
that
hasn't
already
been
published
as
a
lot
of
things
you
wanted
to
blend
bill
are
things
that
we're
already
announced
another
post
like
the
camp
materials
or
whatever.
So
the
latest
thing
that
hasn't
been
announced
really
is
the
piece
you
put
together
in
the
community
repo
that
links
to
those
sessions.
A
I
think
they've
already
done
three
and
they
don't
even
have
the
full
test
all
the
way
running
yet,
but
I
don't
I.
Don't
think
that
before
this
timeline
is
obviously
we're
not
going
to
be
doing
a
launch
communication
today
on
December,
16th
and
I,
think
the
23rd
or
whatever
the
date
is
we
were
kind
of
trying
to
aim
for
is
still
very
optimistic
for
one
would
be
able
to
communicate
even
in
our
sea,
so
that
kind
of
feeds
into
also
what
we're.
What
we
need
to
prioritize
for
next
quarter.
A
In
terms
of
I'm
getting
getting
these
really
important
improvements
out,
yep
and
then
I
mentioned
communicating
out
to
I'm
kind
of
the
team
and
our
community
like
where
we're
focusing
next
quarter
and
definitely
still
in
the
plans
on
the
list.
We'll
have
some
of
that
on
Thursday
and
but
then
also,
you
know,
I
think
they'll
be
a
blog
post
or
two
out
of
that,
and
hopefully
one
of
those
which
lands
by
ended
here
or
at
least
the
very,
very
beginning
of
January.