►
From YouTube: Project Operations 2019-07-15
Description
Description:Group responsibilities: Core Implementations / Maintenance / Comms / Community / Collabs / Research
Notes: https://docs.google.com/document/d/1IZ8tyWKnuXKTMbYaZO_8FVUKJ1kxA4imgPaTBhXXbAc/edit#
A
B
B
C
B
Looks
very
cuddly
cool.
Well,
let's
we
don't
have
have
that
much
time.
So,
let's
take
let's
take
a
pass
through
all
right.
First
things:
first
I
advise
implementations.
Are
shipping
quality
releases
on
a
schedule?
There
were
a
couple
of
beatings
last
week,
I
think
Steven.
Do
you
want
to
give
a
quick
recap
of
the
two
meetings
you.
C
C
D
E
Yeah
so
I
will
represent.
Last
week
we
got
together
for
a
couple
of
days
or
kaleo's
in
San
Francisco,
and
we
camped
out
to
the
lab
space
in
the
final
days
and
hours
of
its
existence,
to
plan
how
to
systematize
collaborations
and
and
also
can
revitalize
the
user
registry
and
use
that
as
a
base
and
single
source
of
truth
for
how
we
track
the
people
we
know
they're
using
at
TFS
and
the
relationships
we
have
with
a
subset
of
those
people.
B
Guess
this
isn't
it
doesn't
quite
collaboration
since
we
didn't
work
with
these
folks,
but
attending
the
Mitchell
Park
Library
ipfs
exhibit
was
super
super
cool
and
definitely
like
if
anything
comes
of
it
in
terms
of
awesome,
cool
collaborations,
with
libraries
to
bring
workshops
or
anything
like
that,
I'll
I'll,
let
this
group
know-
and
hopefully
we
can.
Anyone
who
happens
to
be
in
town
could
could
come.
B
There
is
another
photo
which
I
do
not
have
yet
because
someone
from
the
library
ticket
would
of
like
you
know
the
people
who
actually
spend
all
of
the
time
creating
that
amazing
box,
including
doing
all
of
the
lettering
on
it,
which
is
mind-blowing,
including
aqm
hash,
with,
like
all
of
these
little
leather,
it's
crazy,
but
yeah
super
snazzy
cool
community
news.
B
B
B
Alrighty
maintenance,
tea
trick.
E
Yeah
we
had
a
web
browser
and
GUI
meeting
last
week
talked
a
little
bit
about
this
there's.
There
are
no
fires
at
this
point,
which
is
good,
but
I
think
that
the
next
step
is
going
to
be
kind
of
formalizing.
What
that,
with
the
delivery
and
metrics
around
the
maintenance
of
things
that
we
want
to
continue
moving
forward
yet
not
moving
forward
at
the
speed
of
the
most
important
thing.
E
If
you
have
thoughts
about
what
success
looks
like
for,
for
something
like
this,
you
know
feel
free
to
drop
them
in
it's.
It's
weird
that
success
isn't
negative
they're,
not
not
a
negative,
but
the
absence
of
effort,
so
some
effort
to
ensure
the
absence
of
effort,
but
I
think
you
know
as
long
as
the
the
products
are
still
functioning
I
think
that's
probably
the
biggest
risk
is
that
work
in
area
a
results
in
a
regression
in
low
priority
area,
B
that
we
don't
see.
E
B
Something
like
know,
regressions
or
if
there
are
regressions,
we
catch
them
and
fix
them
very
quickly.
So,
like
kind
of
the
combination
of
those
two
things
you
know,
if
we
are,
we
are
proactive
enough
about
paying
attention
to
and
addressing
any
issues
that
come
up
to
make
sure
that
the
web
UI
and
desktop,
and
these
things
that
our
users
and
we
rely
on
all
the
time
in
order
to
to
make
use
of
ipfs
continue.
Supporting
our
needs
really
effectively
is
the
place
I
notice.
Henry
could
couldn't
attend
this
call
today.
B
E
F
F
F
F
To
get
the
specs
into
mistake,
I
can
start
research
crusade,
but
I
get
something
that
supports
research,
as
in
we
will
be
able
to
have
a
forum
discussions
about
our
tickets
works
today
so
that
we
know
how
to
improve
it
and
there's
a
request
is
not
submitted
wrist
weights
and
like
review,
is
appreciated.
Then
there
is
a
meeting
up
in
English
Wednesday,
but
it
is
a
meeting
after
many
many
emails,
but
it's
basically
me
Evan
George.
F
B
All
right,
Mitchell,
I'm,
assuming
your
question-
was
that
a
about
a
previous
item
and
not
research,
okay,
cool
and
then
we'll
just
continue
onwards,
and
the
first
item
for
us
is
finalizing.
Q3,
okay,
ours
right
before
this
meeting
I
sent
out
a
note
about
having
a
in
all
hands
where
we
can
present
these
things
and
make
it
available
to
the
community
as
well.
This
explanation
of
the
things
that
we're
prioritizing
for
the
quarter
so
the
goal
there.
B
B
We
now
have
a
github
issue,
so
if
folks
want
to
kind
of
comment
back
and
forth
or
continue
refining
wording
on
these
things,
I
think
we
should
aim
to
have
this
in
the
spreadsheet
by
Wednesday,
so
that
we
have
any
any
time
necessary
to
do
any
final
things
before
before
I'm
meeting
on
Thursday
I
and
a
number
of
other
people
I
think
disappear
off
to
do
web
camp
midday
on
Thursday.
So
the
that's
kind
of
our
cutoff
for
making
sure
that
that
gets
done
this
week
as
well.
B
So
I
and
there's
been
some
progress
on
these
things,
but
I
think
we
could
work
on
making
them
more
precise
and
measurable,
and
you
know
we
having
some
initiatives
is
okay,
but
making
sure
we
have
metrics
that
are
going
to
tell
us
whether
or
not
those
initiatives
are
doing
what
we
care
about
and
whether
we're
being
successful
in
those
things,
it's
really
important.
So
there
are
dris
I,
think
for
each
area.
B
E
B
And
I
think
the
to
the
extent
that
we
can
have
fewer
items
in
our
okay,
ours,
the
better
having
too
many
things
makes
it
really
hard
to
prioritize
across.
So,
let's,
let's
really
focus
on
having
the
most
important
things
be,
what
we're
tracking
here
or
the
indicators
that
all
of
our
work
ends
up
being
successful
versus
the
lit
to
do
list
of
all
of
the
things
we
plan
to
do
this
quarter.
We
realize
we're
gonna
do
a
lot
of
stuff.
Okay,
it's
not
the
best
place
to
track.
B
B
E
And
so
I've
added
this
because
I
remember
things
being
on
that
on
the
boards
that
we
were
sketching
out
a
team
week,
but
that
night
review
the
photos
and
it's
actually
pretty
good.
The
hiring
is
represented
here
and
there,
but
not
wholly
as
a
cohesive
thing.
So
I
feel,
like
that's
one
area
where
there's
a
bunch
of
activity
that
it
may
be
necessarily
need
to
be
represented
in
okay,
iris
but
I,
but
that
was
I.
Think
you
added
that
there
or
somebody
else
did.
G
I'm
not
sure
if
you
should
be
tracked
here,
but
it
was
more
that
I
know
it
takes
up
a
lot
of
time.
So
it's
something
to
consider
as
we
you
know,
decide
what
we're
focusing
on
this
quarter.
It
will
take
it's
probably
some
of
the
people
on
this
call.
That
will
be
time
sucked
a
way
to
help
with
that.
So
we
should
acknowledge.
I
didn't
have
a
track
somewhere.
G
B
The
other
area
that
I
feel
reflecting
back
on
that
I
feel
like
we
could
use
some
more
definition.
Is
things
around
community
support
that
being
something
that
you
know?
B
There
are
already
people
who
are
doing
amazing
work
in
in
the
wider
ipfs
community
to
support
people,
onboarding
and
kind
of
run
local
chapters
and
and
also
be
super
engaged
in
in
the
ipfs
community
and
helping
people
and
so
figuring
out
how
we
can
continue
supporting
community
support
and
and
help
others
and
invest
in
this
and
make
IP
of
us
or
more
useful
for
people
who
are
on
board
of
Emmet
I.
Think
that
falls
within
this
group.
B
B
So
that's
the
direction
I've
been
going
in
my
head,
but
also
aware
that,
like
some
things
aren't
always
the
best,
the
best
fit
for
github
issues
or
arguably
better
attractive,
IP,
fest,
slash
blog
or
something
like
that,
which
I
think
he's
okay,
but
that
that's
been
my
top
level
like
the
default
of
tracking
these
things
in
IP
fest,
slash
project
was
where
my
head
was
going.
Does
anyone
have
other
other
ideas
or
ultimate
suggestions?
I.
E
Added
added
this
mostly
again
from
a
kind
of
measurement
standpoint,
so
when
we
get
to
the
end
of
the
quarter,
where
can
we
look
for
each
one
of
these
things?
What's
there
once
these
are
all
in
the
okay
are
sheets
and
finalized?
Maybe
we
can
add
links
back
to
issues
that
we
filed
or,
if
they're,
not
in
the
projects,
repo
at
a
link
to
where
we
would
check
for.
B
All
right
last
last
item
in
our
agenda,
so
I
have
more
agenda
items.
If
your
item
has
been
covered
and
the
blog
post
we
want
to
ship
this
quarter
and
I'll
find
implications,
capabilities,
ipfs,
I,
key
three
priorities:
more
camp
posts,
network
usage,
D
web
camp
yeah,
I
think
having
some
for
these.
These
events
that
we
expect
to
be
attending
makes
a
lot
of
sense,
I'm
kind
of
like
the
IP
of
us
camp
recap,
but,
with
you
know,
I
think
there
are
many
other
things
that
we
want
to
talk
about
from
my
PFS
camp.
B
There
was
so
much
great
discussion
and
content
there
that
yeah
I
imagine
having
or
helping
others
create.
These
recap
posts
for
IP
bus
camp
there's
a
lot
of
fodder
there,
whereas
for
some
of
the
events
we're
going
to
in
the
next
couple
months,
having
a
single
post
that
recaps,
both
kind
of
our
our
participation
and
our
top
takeaways
or
the
coolest
things
we
saw
or
stuff
like
that
could
be,
could
be
super
cool,
I'm,
so
I
think
signing
ourselves
up
for
for
each
of
these,
these
events
to
do
a
post
makes
sense.
B
What
three
is
another
one
that
falls
into
that
bucket,
which
is
end
of
August
and
the
last
web.
Three
also
had
some
really
cool
ipfs
related
discussions.
I
am
tentatively
planning
to
go,
but
I
haven't
thought
about
it
anymore
than
making
sure
that
I
am
not
otherwise
booked
to
that
particular
week
and
those
definitely
are
on
the
mind
and
other
people
want
to
comment
on
some
of
the
items
that
other
folks
wrote
down
here.
A
I'll
just
throw
out
in
response
to
your
your
mentioned.
I
was
like
how
much
we
can
get
out
of
my
PFS
camp
on
specific
topics.
The
model
that
we
use
for
offline
camp,
which
is,
admittedly,
a
very
different
beast,
and
this
is
an
extremely
time-consuming
effort,
but
we
actually
have
volunteers
who
are
at
each
right.
There
are
more,
there
are
more
kinds
of
content
at
ipfs
can
but
that
offline
camp,
for
example.
It's
like
the
discussions
that
happen
on
conference
discussions.
A
We
get
a
volunteer
from
each
of
those
who
take
the
written
summary
and
turns
it
into
a
blog
post.
So
a
structure
like
that,
maybe
it
doesn't
work
until
the
next
event,
but
a
structure
like
that
where
you
then
need
an
editor
to
be
pulling
from
different
people
and
editing
the
content,
but
having
volunteers
write
about
stuff
that
they
were
engaged
in
can
work.
Well,
it's
just
a
ton
of
work.
B
That's
something
that
comes
to
mind
based
on
what
you're
suggesting
is
also
having
area
dris
from
ipfs
camp
talk
about
the
area
that
they
were
DRI
for
because
they
tend
to
have
the
you
know
they
they
have
the
connections
who
kind
of
who
did
what?
So,
if
you
did
lightning
talks,
you
probably
have
the
information
for
most
of
the
people
who
are
doing
lightning
talks
and
most
of
their
presentation,
material
and
I
know.
B
That's
that's
like
again
distributing
load
for
writing
a
lot
of
posts
across
the
team,
but
that
definitely
will
be
better
than
trying
to
ask
one
person
to
write
eight
blog
posts,
all
about
various
content
happening
and
ifs,
camp
and
I
do
really
love
the
idea
of
getting
more
people
throughout
the
community.
Doing
this,
though,
I
think
that'd
be
really
awesome.
Yeah.
A
I
guess
another
thing
that
falls
in
this
bucket
of
well
I,
guess
not
specifically
blog
post,
but
like
communications
bucket
other
stuff,
we
want
to
communicate.
I
need
to
circle
back
what
Zach
on
this
to
get
an
estimate.
But
you
said
there
may
be
more
budget
checking
mid-quarter
as
to
whether
it
might
make
sense
to
do
interviews
at
offline
camp
of
people
who
are
on
that
bridging
that
border
line
of
offline
first
and
ipfs,
in
which
case
it
would
be
like
interview,
format,
video
about
offline
capabilities
of
ipfs.
B
Hercules
aqua
saying
that
some
of
the
video
content
from
ipfs
camp
was
gonna,
be
ready
like
within
the
first
two
weeks,
so
we're
probably
gonna
have
a
dump
of
that
getting
ready
soon,
and
we
should
make
sure
to
do
the
processing
and
get
it
out
to
people
quickly
so
that
they
can
also
share
it
and
link
to
it
and
all
of
their
we've
definitely
been
getting.
Pings
of,
like
I
would
like
to
include
the
video
of
my
lightning
talk
in
this
other
publication.
So
it's
definitely
thing.
B
The
last
last
quarter,
we
did
videos,
so
every
every
group
did
kind
of
a
video
walking
through
there,
okay,
our
section
of
the
sheet-
and
we
put
these
all
things
all
these
things
out.
His
videos
I
think
it'll
be
significantly
faster
to
do
as
a
blog
post
I
like
the
idea.
At
the
same
time,
it
also
feels
like
we're
just
gonna
take
what's
on
github
and
like
swish
it
around,
but
maybe
that's
still
really
useful
to
people
to
like
put
it
into
a
more
accessible,
readable,
blog
post
form.
B
B
Awesome
plan
to
do
it,
we
are,
we
are
not
out
of
time,
but
we
shall
continue
on
these
threads
async
and,
as
we
finish
finalize
our
okay
ours,
which
should
be
a
top
priority
for
all
of
us.
Let's
make
sure
that
we
have
github
issues
for
tracking
so
that
we
can
continue
onward.
With
all
of
these
awesome
tasks
who,
okay
I'm.