►
From YouTube: Project Operations 2019-07-08
Description
Description:Group responsibilities: Core Implementations / Maintenance / Comms / Community / Collabs / Research
Notes: https://docs.google.com/document/d/1IZ8tyWKnuXKTMbYaZO_8FVUKJ1kxA4imgPaTBhXXbAc/edit#
A
A
A
Well,
maybe
we'll
come
up
with
some
when
we
talk
about
what
it
is
we
do
in
this
meeting
and
we'll
come
up
with
some
new
ideas
that
they
see
one
talk
about
and
awesome
so
talking
about
what
it
is.
This
group
has
kind
of
signed
up
to
do
it's
a
little
bit
of
a
conglomeration
group
that
that
goes
across
a
couple
of
different
edges
and
the
the
things
that
we've
talked
about.
A
The
things
we
understood
is
we
needed
something
that
was
previously
kind
of
part
of
the
project
working
group
in
q2,
but
also
not
really
explicitly
part
of
the
project.
Working
group
was
thinking
about
things
like
community
and
communications
and
making
sure
that
the
project
is
effectively
messaging
for
itself
and
so
that
kind
of
from
a
interfacing
with
the
community
and
understanding
what
the
community
needs
of
us
and
being
a
feedback
loop
with
the
community
to
make
sure
that
we're
we're
understanding.
A
Communicating
if
anything
comes
up
on
the
internet
about
ipfs,
we
want
to
make
sure
that
we
are
aware
of
it
and
we
were
able
to
respond
to
it
and
respond
to
it
effectively
such
that
everyone
has
a
very
clear
idea
of
kind
of.
You
know
what
what
the
project
needs
from
them,
and
so
that's
kind
of
a
big
chunk,
something
that
blood
out
of
that
was
also
understanding
where
the
core
implementations
of
ipfs
are
going
and
making
sure
that
there's
kind
of
a
group.
That's
continuing
to
think
about
that.
A
We
also
have
now
an
hour-long
core
implementations
kind
of
engineering,
sync
that
the
hour
after
the
project
work.
Sorry,
the
weekly
IPS
call
every
week
and
so
I
think
will
actually
will
be.
Do
it
using
that,
for,
like
tactical
engineering
process
of
like
you
know,
do
we
want
to
add
this
feature
to
the
j/s
or
ipfs
or
both
implementations
or
protocol,
and
so
that
is
going
to
be
like
our
tactical
engineering
meeting
for
actually
doing
iterations
on
the
core
protocol.
A
But
here
we
might
use
this
meeting
for
kind
of
the
more
meta
like
hey,
I
need
help
writing
release
notes,
or
you
know
we
want
to
do
do
this
change
to
our
release
process
that
maybe
belongs
more
in
like
project
operations
than
actual
implementation,
iteration,
and
so
there's
that
trunk,
and
then
that
also
includes
maintenance
on
many
different
areas
of
the
core
protocol,
things
that
we're
not
actively
investing
in
right
now,
but
that
we
want
to
continue
on
in
the
future
very
effectively
and
so
that
stuff
like
like
either
desktop
or
other
UI's
or
other
features
that
we
have
put
out
in
the
past.
A
Where
we're
like.
We
want
them
to
be
great.
We
want
everyone
to
be
using
them,
but
we
don't
want
to
be
investing
a
whole
ton
in
them
right
now.
I
guess,
thinking
back
on.
That
collaborations
also
includes,
obviously,
all
of
the
great
work
that
that
Lydell
and
G
chicken
pox
have
been
doing
with
browsers.
Those
are
very
big
collaborators
that
we
absolutely
want
to
be
super
successful
and
then
finally,
there's
a
chunk
of
this.
That
is
planning
for
the
future
and
into
the
future
from
a
research
perspective.
A
So
this
is
not
like
a
cross
group
planning
meeting,
but
it
does
include
a
little
bit
of
kind
of
thinking
proactively
about
where,
where
we
need
to
be
heading
as
a
project
and
doing
the
pre
work
from
a
research
perspective
to
get
that
done.
So
there's
a
lot
of
different
things
in
this
meeting
and
we
should
find
a
a
structure
for
it
that
will
allow
us
to
knock
things
out
across
all
of
those
different
buckets
pretty
effectively
and
when
necessary,
split
groups
out
into
their
other
meetings.
B
Actually,
after
you
finished
talking,
maybe
I
should
wait
a
week
conceal
the
meetings.
Go
I'm,
not
super
clear
on
how
the
core
implementation
coordination
interacts
with
the
other
meeting
and
then
also
the
work
that
we're
doing
on
the
core.
I
mean
all
of
our
separate
meetings
are
work
on
the
court
so
but
I'm
happy
to
leave
that
for
a
week
from
now
or
two
weeks
from
now,
once
we
see
how
the
meetings
fall
out,
yeah.
A
My
kind
of
my
idea
for
this
is
that
this
would
be
a
meeting
where
folks,
like
Alan
and
Stephen
would
be
like
pulling
kind
of
us
as
members
of
this
project
operations.
Group
being
like
great,
we
need
help
iterating
on
this
part
of
the
court
protocol.
We
we
need
the
support
from
a
communications
perspective
from
a
community
support
perspective
so
that
we
can
be
spending
our
time.
You
know
actually
iterating
on
the
core
protocol
itself
and
like
making
sure
that
we
have
a
great
process,
and
so
that's
what
this
chunk
of
the
meeting
would
be.
A
Very
specifically
on
you
know,
package
manager,
needs
or
gateway
needs,
but
would
go
through
back
implementation
call
when
they
need
like
a
design
review,
or
we
need
to
get
like
top-level
agreement
on
the
direction
the
protocol.
The
core
protocol
is
heading
so
when
it
touches
like
protocol
design
and
stuff.
C
My
question
given
at
this
call
is
on
the
community
calendar
and
gets
recorded
to
I.
Guess
is
just
good
to
reiterate
for
group
like
we
should
focus
solely
on
action
items,
aspects,
questions
that
are
poor
like
because
project.
So
this
is
not
micro
collapse,
a
Peters
project
or
programs
FST
its
operational.
A
So
we
do
have
a
alternating
week
meeting
specifically
for
anything
that
kind
of
the
protocol
labs
contingent
of
the
team
needs,
and
the
aim
for
this
meeting
is
to
be
specifically
around
project
operations
for
the
ipfs
project,
globally.
The
community
open
and
all
of
that
stuff.
I'm
talking
about
things
like
collaborations
and
communications
and
such
that's
super
open.
A
And
then
there
is
another
alternating
meeting,
also
on
Tuesdays,
which
is
actually
a
new
meeting
which
is
gonna,
be
kind
of
a
cross
task
force,
update
meeting
and
so
where
this
one
is
gonna
be
really
focused
on
the
stuff
that
we
need
to
be
bringing
to
the
table
like
making
sure
that
there
is
great
community
interaction
and
we're
doing
the
job.
Communicating
and
we're.
A
Yeah
I
think
there's
gonna
be
we've
kind
of
split
it.
It's
like
there's
like
little
bits
of
both
like
previously
our
project.
We
call
had
the
communication
collaboration
stuff
and
then
it
also
kind
of
had
like
meta
project
stuff,
but
we
kept
having
less
and
less
time
for
meta
project
stuff
because
we
spend
all
of
our
time
doing
things
like
actually
planning
ipfs,
camp
and
other
stuff
like
that,
and
now
we've
kind
of
split
them
into
two
separate
meetings.
A
C
So
far,
thank
you
so
much
for
the
clarification
super
happy
to
kind
of
like
reset
my
brain
and
just
like
accept
the
new
calls.
I
guess.
The
reason
why
I
brought
up
this
question
is.
In
the
past,
there
was
like
some
confusion
about
like
what
is
internal,
what
is
external
like
what
what
should
be
communicating
outside
what
truly
be
inviting
people
to
join
us.
C
A
And
so
I
think
and
I
definitely
going
forward.
We
discuss
this
a
little
bit
last
week,
but
going
forward
definitely
inviting
people
to
this
call,
especially
folks
who
want
to
and
help
out
from
a
communication
perspective
or
things
like
that,
people
who
are
writing
blog
posts
or
books
or
whatever
about
IPS.
There
is
an
IP
FS
book
that
I
saw
a
very
early
draft
of
translated
from
Chinese
into
English,
which
is
really
awesome.
A
A
I
think
something's
that
I'd
like
to
check
in
on
are
kind
of
what's
what's
been
happening
from
kind
of
a
community
perspective.
Whether
that's
like
are
they're
known
like
is
there
any
communication,
that's
happening
in
the
community
that
we
we
want
to
be
escalating.
We
want
to
be
making
sure
we
respond
to
who's
kind
of
DRI
on
that,
if
there's
no
DRI
in
that,
we
should
figure
out
how
to
get
a
DRI
on
it
and
what
is
our
strategy
for
responding
to
it?
So
it's
like
you
know.
A
If
there's
you
know
a
post
up
a
new
article
that
we
kind
of
want
a
response
to
or
if
there's
something
happening
in
the
community,
that
we
think
that
we
should
be
communicating
on
about,
and
this
which
should
be
a
meeting
where
we
check
in
on
that
I.
Think
checking
in
on
a
kind
of
release
process
is
also
a
useful
thing
to
do
here.
A
A
Looking
forward
to
hearing
the
approach
I
think
when
there
are
updates
or
things
that
need
to
happen
from
a
research
or
maintenance
perspective,
I
would
I
want
this
to
be
a
forum
where
we,
like,
we
at
least
have
a
line
item
where
we're
like.
Is
there
any
anything
from
kind
of
an
update
perspective
like
either
an
update
on
research
that
we
want
all
to
be
reviewing
and
giving
feedback
on
of?
A
Even
though
this
is
not,
you
know
if
they're
maintenance
things
but
they're
important,
and
we
need
to
make
sure
that
we're
doing
a
good
job,
supporting
our
users
with
that,
and
so
those
are
kind
of
like
I
kind
of
imagine,
like
a
checklist
of
each
of
those
things
being
like
what
is
our
update
from
communications?
What
is
our
updates
from
implications?
Does
that
sound,
reasonable.
E
My
my
unmute
button
ended
up
right
where
my
hotkey
to
lock
my
screen
was
that
that
sounds
really
great.
Having
having
that
set
of
things
in
the
template,
for
this
meeting
will
probably
help
it
to
one
make
sure
we
hit
those
those
boxes
every
time
and
to
that
we
don't
you
know
me
and
or
all
around,
because
I
think,
with
the
amount
of
things
that
we
have,
it
will
be
keeping
this
meeting
at
least
making
sure
that
we
hit
those
high
priority
items
be
challenged.
There
always
be
something
coming
up,
especially
for
inviting
guests.
E
A
And
we'll
also
have
a
we
kind
of
have
a
hard
stop
to
this
meeting
so
that
we
can
all
go
too
quickly,
and
so,
if
we
have
other
things
to
talk
about
we're
not
going
to
have
a
good
time,
yeah
cool
on.
On
that
note,
let's
kind
of
consider
the
what
we
do
in
this
call
and
how
we
kind
of
think
we're
gonna,
run
it
going
forward
and
I'll
make
sure
that
the
template
for
next
week
has
those
line
items.
A
Alright,
alright,
do
we
want
to
take
a
pass
first
through
draft.
Ok,
ours,
I.
E
Started
last
week
before
disappeared
into
the
woods
to
kind
of
kr
ice,
the
set
of
things
that
were
in
the
q3
Team
document,
but
I
did
not
start
moving
them
over
into
the
okay.
Our
sheet
at
all,
so
it'd
be
great.
If
the
people
that
are
working
on
those
relevant
bits
did
it
passed
and
I'm
not
sure
they
did
it
Matt
I
think.
B
E
One
of
the
goals
that
we
talked
about
and
so
I
just
threw
that
number
out
there,
that's
how
you
start
throw
numbers
and
then
we
can
adjust
it
up
or
down
and
see
how
it
goes.
But
that
actually
came
out
of
a
specific
discussion
around
cadence
releases,
not
about
the
designing
a
release
as
much
as
creating
a
release
schemes
we're
releasing
on
a
regular
schedule
as
a
result
of
the
output
of
some
of
the
release
management
stuff
that
Steve
in
a
real
role
or
time.
A
Something
about
this
need
to
be
workshopped,
but
I
guess
maybe
Alan
and
Steven,
if
you
guys
want
to
kind
of
help,
continue
iterating
on
this
from
a
whatever
whatever
you
expect.
The
release
process
to
be
looking
like,
like
I,
agree
with
duties.
Point
that,
like
going
through
the
stages
having
a
release
that
go
is
helpfully
through
the
stages
that
we
design
in
a
release
process
like.
Maybe
this
is
just
a
healthy
release
or
something
like
that
and
I
know
that
we've
also
talked
about
making
sure
that
we
don't
put
out
releases
on.
A
We
go
through
this
healthy
release
process,
and
so
we
don't
other
than
like
patch
fixes
or
anything
like
that,
and
so
continuing
along
those
lines.
I
agree
that
we
shouldn't
be
counting
ourselves
on
number
of
releases,
but
on
the
the
quality
of
release
we
put
out
and
just
to
respond
to
Michelle's
point
really
quickly.
A
A
A
E
B
A
E
A
And
then
video
research,
all
right,
reasonable
folks
feel
confident
in
being
able
to
flush
these
out
over
the
next
couple
of
days
and
we
can
kind
of
check
in
a
sink
in
the
stock
and
try
and
move
to
the
spreadsheet.
By
end
of
week,
sound
reasonable
cool
I
see
nods
and
thumbs
huzzah
ivona
bah
I
will
stop
sharing
this
so
I
can
refine
the
notes.
A
C
We
just
need
to
kind
of
like
agree
and
I
can't
to
do
that
without
also
saying
like
these
are
our
favorites
and
like
like.
We
want
to
like
tell
the
community
that
there
are
some
that
are
even
more
attentively
exciting,
but
we
don't
know
each
other's
kind
of
creators
that
the
ones
that's
not
good,
the
ones
that
they
made
are
not
necessarily
especially
exciting.
All
them
are
really
good,
and
so
I
have
a
proposal
on
that
for
request
for
you
more
with
you,
but
other
than
that.
A
Okay,
I'll
take
a
pass
at
that
first
thing.
After
all
of
these
meetings,
and
hopefully
we
can
do
you
mind
if
I,
if
I
feel
100
percent
great
on
everything,
can
I
just
merge
it.
For
you
absolutely
sounds
good
collecting
community
posts.
I
know
that
a
number
of
these
have
already
started
happening,
who
kind
of
wants
from
a
like
organization
perspective?
A
Maybe
we
can
be
like
sending
them
all
to
the
PL
News
or
like
on
slack
or
on
IRC
or
somewhere,
where
folks
can
be
like
indexing
on
them
and
helping
retweet
them
and
generally
ensure
the
rest
of
the
communities
aware
of
them.
I
think
we
should
also
collect
them
so
that
we
can
make
a
master
blog
post
of
like
here
are
all
of
the
amazing
things
that
came
out
of
my
PFS
stamp
or
can
can
be
putting
them
somewhere
so
that
others
can
index
on
them
really
nicely
and
then
I.
Remember.
A
We
discussed
last
time
choking
in
also
being
excited
about
just
coordinating
the
back
and
forth
on
that,
and
so
I'm
gonna
ask
him
to
come
to
this
meeting
next
week.
Now
that
we
have
this
meeting
so
that
we
can
talk
about
kind
of
just
doing
that
at
top
level
according
to
get
even
more
people
talking
about
the
really
cool
stuff
they
presented
during
ipfs
camp
and
make
it
really
accessible
to
folks
who
weren't
able
to
attend
tissue
in
the
camper.
But
that's.
A
C
So
the
remiel
by
PFF,
slash
camp
is
becoming
this
kind
of
like
source
of
truth
like
this
index
for
everything.
Thank
you
all
then
help
like
push
the
tables
that
like
made
it
really
nice,
do
I
go
through
photos
of
the
people
who
created
the
content
with
the
titles.
We
are
waiting
on
back
to
publish
the
videos
like
that.
So
that's
like
publisher,
something
we
were
just
like
link
it
there
and
then
we
can
also
use
the
remade
to
list
all
the
articles.
I've
got
published,
spotlight
be
festive
I,
think
it'll
be
a
good
thing.
C
That
said,
I
still
think
that
we
as
a
project
really
need
like
a
better
media
in
a
big
page.
So
if
you
go
type
in
sarayaku
yeah
and
it
has
some
talks,
that's
like
a
long
list
of
like
musical
talks
like
no
Iowa
at
all,
so
like
we
as
a
team
as
a
community
produce
so
much
content
that,
like
I,
think
the
community
right
now
needs
some
help
from
us
on
directing
them
like
directing
their
attention.
So
maybe,
as
a
project
tiny
project
for
this
quarter,
he's
think.
C
A
F
Think
we
can
have
all
those
discussions
be
ours,
but
there's
a
lot
of
things
to
discuss
like
we
don't
even
know
what
type
of
release
postures
we
want
or
like
we
could
have
a
train
process.
We
could
have
with
the
car
passes,
which
is
a
really
psycho
process
and
we're
looking
anxious
cus
these
trade-offs,
so
it'll
be
a
while.
F
F
C
We
definitely
want
to
improve,
like
any
kind
of
automation
like
just
my
minion,
but
I
guess
like
maybe
Alan
can
speak
more
to
it
like
the
Jewish
process,
which
is
considerably
manual
with
the
exception
for
the
unit
test
and
actually
helps
not
only
communicate
to
the
community
like
what
is
going
on
what
is
coming,
but
also
helps
us
like
catch
bugs,
because
we
get
to
run
a
bunch
of
other
people
sex
with
into
it
as
it
costs.
It
has
like
time
costs
for
sure,
but
it
has
been
very
good
for
a
last
year
long,
the.
F
Point
is
whether
we
have
to
decide
what
the
the
basically
the
cutoff
is
for
cutting
release,
because
at
the
moment
we
have
to
maintain
two
copies
of
everything:
let's
get
two
branches,
and
this
will
work,
maybe
for
a
month
or
two.
But
after
that
we
start
getting
many
more
complex
and
just
nothing
work.
F
A
A
technical
point
we're
out
of
time.
Thank
you
all
very
much
for
a
great
first
call
and
I
will
restructure
the
agenda
next
time
to
make
sure
we
can
hit
on
these
things
all
real
fast
and
if
we
realize
we
need
to
well
make
sure
that
we
have
more
time
for
this
meeting,
because
there's
a
lot
of
different
things
to
cover
and
I
want
to
make
sure
we
don't
continually
run
up
against
the
the
next
meeting.
Alright,
thank
you
guys.
So
much
have
a
nice
rest
of
your
week.
Probably
see
you
all
very
shortly.