►
From YouTube: IPFS Sprint - 06-02-2016
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
While
you're
restarting
the
scream-
because
this
is
the
stream
because
there's
a
Marva
on
an
announcement-
a
rope,
perfect
perfect,
so
I
sprint
planning
closed.
So
this
week
is
the
second
week
of
the
current
sprints,
meaning
that
they
end
this
friday
and
they'll
be
doing
demos
next
Monday.
That
also
means
that
starting
next
Monday's
new
sprints,
the
big
one
being
the
IPF
s
in
the
browser,
I'm,
not
sure
which
other
sprint
so
we've
scheduled
for
that
time.
A
I
don't
of
the
road
meadow
map
up,
but
I
try
to
be
if
you're
leading
a
sprint
next
week,
try
to
be
scheduling
your
read
or
sprint
planning
call
for
this
coming
Thursday.
So
that's
when
your
whole
team
will
look
through
all
the
stories
of
what
you're
doing
and
figure
get
a
clear
sense
of
what
you're
going
to
work
on
over
the
next
two
weeks
and
discuss
estimates
of
how
hard
the
work
is
going
to
be
all
of
that,
so
that
most,
how
that
impacts.
A
A
So
that's
more
of
a
heads
up
I'll!
Do
it
and
then
similarly
sprint
retrospective
call.
So
if
you
were
working
on
a
sprint
this
past
weekend
this
week,
then
on
Friday
we
will
be
doing
the
Sprint
retrospective
and
that
will
probably
be
on
friday
at
the
time
that
this
call
happens
so
whatever
that
is
UTC
or
in
your
local
timezone.
So
it's
noon
eastern
time,
I'm,
not
sure
what
it
is
in
UTC
is
that
so
be
17,
UTC
well,
Victor
a.
A
No
I'm
going
to
post
a
proposal
for
an
alternative
format,
I
synopsis
version,
though
we
will
all
be
on
the
call
all
together.
Basically,
each
team
will
spend
20
minutes
doing
their
retrospective
and
everyone
else
is
just
listening,
and
so
it's
like
for
20
minutes
your
team
discuss
amongst
yourselves
like
how
did
things
go?
What
worked
what
didn't
work?
What
should
we
continue?
What
needs
to
change
action
items?
A
That's
it
ready,
like
so
you're
sort
of
like
on
the
stage
being
watched
by
everyone
else,
so
everyone
can
witness
how
your
process
is
going
and
witness
how
you're
deciding
how
to
improve
it,
but
it
won't
be
like
the
last
one
where
it
ended
up
being
more.
The
leads
from
each
project,
basically
doing
a
showcase,
and
you
didn't
get
much
of
that
sort
of
internal
like
introspection
of
how
is
our
process
going?
A
So
I'm
going
to
write
up
a
proposal
of
how
we
structure
that,
but
that's
the
basic
idea
and
it
will
include
if
you
were
on
a
sprint,
eno
working
alone,
you
should
plan
to
join
in
and
you
you
won't
necessarily
take
a
full
20
minutes
that
you
will
also
have
time
to
sort
of
retrospect
on
how
your
work
process
is
going
with
the
people
who
you
ended
up
interesting.
It.
A
Will
be
on
friday
at
five
p.m.
UTC,
okay,
which
is
noon
eastern?
It's
the
time
that
this
call
starts
on
Mondays,
but
it
will
be
on
Friday
and,
and
that
will
be
for
people
who
participated
in
a
sprint
or
a
sprint.
Ino.
A
Yeah
well,
how
do
people
feel
about
that
I
guess
I
wish
there
were
more
people
on
here,
I
hesitate
to
say
yes,
because
I
want
people
to
speak
freely
about
what
is
not
working
so
that
it
can
be
acknowledged
and
things
can
change
and
if
you
have
a
bunch
of
strangers
or
the
wide
unknown
watching
that
might
prevent
people
from
actually
saying
this
thing.
Didn't
work
and
I
want
it
to
change
so
yeah
mixing
thoughts
on
that.
Should
we
should
we
open
it
up
or
keep
it.
A
E
A
E
F
A
G
A
Down
and
let's
keep
in
mind,
so
this
is
why
it's
partially
important
the
showcase
of
what
we
worked
on,
what
we
got
done,
what
we
didn't
get
done
and
like
a
demo
of
all
that
stuff
that
happens
on
Monday
on
the
public
hall.
This
is
just
for
the
team
who
immediately
collaborated
to
have
a
conversation
about
process.
What
worked
and
didn't
work,
and
so
that's
less
about
the
content
of
the
work
itself
and
much
more
about
process
of
the
teeth.
The
people
who
are
collaborating.
G
E
D
A
Well,
that's
where
we
will
all
be
on
the
call
together
and
we'll
just
take
turns
being
like
on
the
stage
being
the
ones
who
are
having
our
retrospective
with
everyone
else.
Listening
in.
Oh,
ok,
so
there
are
something
if
your
team
is
working
on
sensitive
stuff,
that
the
other
teams
can't
hear
then
yeah,
you
could
do
it
on
your
own,
but
this
is
more
still.
A
E
A
A
E
A
Might
think,
and
especially
since
you
guys
are
sort
of
on
you-
are
a
stable
team-
that's
not
getting
a
lot
of
people
rotating
on
and
off!
So
if
you
need
to
do
it
on
your
own
I
give
it
cool.
A
This
is
a
big
one.
Almost
everybody
is
working
on
this,
so
starting
next
Monday.
So
this
thursday
will
do
the
planning
call
and
then
starting
on
Monday,
we'll
be
doing
two
weeks,
I'm
working
on
it's
78,
the
title,
kinda
misleading
its
or
it's
the
title
is
confusing.
The
focus
of
this
print
is
saying
if
our
ultimate
long-term
goal
here
is
that
we
want
I
PFS
to
be
natively
supported
in
all
web
browsers.
A
What
do
we
need
to
do
now
in
order
to
set
things
in
that
direction
like
what
is
that?
What
are
the
things
that
need
to
be
cleaned
up?
What
are
the
tools
that
need
to
be
built?
What's
the
stuff
that
needs
to
be
documented
I,
so
that's
sort
of
we're
not
going
to
achieve
all
of
those
goals
in
those
two
weeks,
it's
more
like.
Let's
we're
spending
two
weeks
really
focusing
on
getting
the
house
in
order
in
that
domain
and
and
so
so
I'm
I'm
leading
that
project.
A
So
what
I'm
doing
over
the
next
three
days
is
gathering
all
the
use
cases
around
that
of
like
what
could
we
be
working
on
and
how
are
we
thinking
about?
The
things
that
need
to
be
worked
on
so
people
have
input
on
that.
Please,
let
me
know:
I
also
have
a
question
of
which
repo
are
we
going
to
track
this
work
in
because
that's
where
people?
If
people
have
suggestions,
they
should
be
creating
issues
in
that
repo,
but
I,
don't
know
which
repo
we
should
use
on
a
free,
pillow
Jeremy,
a
victory.
E
A
All
right,
I,
don't
think
notes
fits
like
this
is
those
of
you
who
followed
the
IPF
s
archives
spring.
The
data
cup
sprint
know
that
I
create
a
lot
of
issues.
I
create
a
lot
of
issues
and
I
document
them
very
thoroughly
and
I
think
that's
important
for
having
a
good
waffle
board
and
tracking
your
project
well
and
making
a
transparent
for
the
external
world.
So
if
you
did,
that
notes
notes
would
be
flooded
with.
That
is
specific
to
this
scrim.
Sorry.
A
Saying
knows
where
we
normally
put
it:
let's
not
do
that.
Let's
make
a
new
one,
yeah
and
and
two
Victor's
and
then
we'll
get
soloist
victories
question
of.
Should
we
create
a
one-off.
The
reason
why
I
hesitate
there
is
that
we
already
have
so
many
repos
and
creating
one
that
doesn't
even
contain
any
code.
It's
just
there
really
to
track
this.
D
You
made
it
yeah,
I
just
clicked
on
the
leaf
button
accidentally
and
then
I
didn't
yeah.
Anyhow,
the
whole
browser
thing
is
not
really
just
a
one-off
thing
has
been
work
done
in
that
direction
for
a
long
time
and
collaborations
with
others.
There's
the
browser
add-ons
for
Firefox,
which
is
pretty
far
and
the
one
for
Chrome,
which
is
a
bit
more
or
less
unmaintained
at
the
moment.
I
think
I
think
it
would
make
sense
to
have
one
place
where
we
can
gather
all
this
information
and
lids
I.
A
D
A
D
Yeah,
because
there's
so
many
aspects
to
this
ASAP
affairs
there's
the
add-ons
there's
keeping
track
of
what
the
pen
points
in
the
browser
are
like
ap
is
that
are
missing,
that
we
would
like
to
have
things
that
are
just
a
big
headache,
like
origins
and
content.
Security
policy,
for
example,
is
just
completely
at
odds
with
how
I
did
this
work
and
specs
for
the
e4.
The
your
ice
cream
other
kind
of
stuff
would
benefit,
I
think,
from
one
from
one
entry
point
where
we
can
crack
all
that.
F
Hey
I
think
I
agree
with
large
here.
I
would
love
to
have
a
repo
I,
don't
know
his
I
PFS
in
the
browser
yet
which
effectively
tracks
all
these
endeavors,
because
a
new
response
cross
a
lot
of
areas
as
lives
mentioned,
for
example,
d.
Your
I
SPECT
doesn't
have
a
good
home
currently,
and
things
like
that.
I'm
tracking
cross
orange
policy
in
various
places
on
this
way
could
actually
have
a
place
where
we
can
aggregate
all
that
data.
F
We
can
link
to
the
various
loans
and
the
various
states
in
the
readme
I
think
it's
fine.
We
have
a
couple
of
Rico's
that
already
are
not
code
repos
butter.
Just
for
discussion
of
like
notes,
for
example,
this
would
be
effectively
notes
for
AP
of
us
in
the
browser.
Okay,.
A
F
I'm
unsure,
if
it
works,
I'm,
just
afraid
of
people
coming
in
and
being
confused,
just
ask
them
like.
Isn't
this
just
a
sigh
PFS
I,
don't
know?
Oh
that's.
Why,
and
this
is
not
so
JSI
PFS
go
I,
PFS,
etc
is
is
about
a
complete
implementation
of
a
PS?
This
is
not
about
implementing
I
PFS
again.
This
is
about
tooling,
to
use
existing
implementations.
D
What
is
it
like?
In
the
end,
the
browser
is,
is
a
completely
different
environment
than
what
Jessica
Vess
outside
of
the
browser
would
run.
In
fact,
you
or
what
go
I
PFS
with
runnin,
you
don't
get
the
same
transports.
You
don't
get
the
same.
You
don't
get
the
file
system,
you
don't
get
direct
access
to
to
to
the
networking
layer
right.
F
A
I'll
kick
this
off
to
a
good
hub
issue,
then
for
deciding
what
we
should
call
it,
and
but
thanks
because
I
yeah,
so
I
wasn't
I,
wasn't
wrong
and
being
like.
This
is
hard
to
choose
this
name,
so
I'll
make
an
issue
and
will
well
sort
it
out.
So
as
far
as
this
announcement
goes
watch
that
issue
and
once
we've
named
it,
you
can
put
issues.
You
can
put
comments
into
the
new
repo.
A
C
C
C
A
A
A
During
the
planning
call
but
I've
needed
to
exist,
so
I
can
start
doing
the
pre-planning
work.
So
choose
name
for
browser.
A
C
B
Victor
Victor
me
so,
let's
see
I
just
wanted
to
share
a
bit
about
our
progress
right.
So
far,
wait
I
see
we
have
a
call
after
this
the
spins
sink.
Maybe
that
would
make
for
samsung
demos.
B
Whatever
them
so,
let's
see
share
the
screen.
There
we
go
so
now
you
should
be
able
to
see
much
screens.
We
have
Jenkins
running
here,
so
this
is
kinda
like
worrying
looking,
so
we
also
have
a
plugin
thoughts,
cow
bees,
I
think
the
recall
we
working
called
blue
ocean
that
adds
like
a
much
nicer.
You
are
into
projections
so
right
now
we
haven't.
We
haven't,
talked
to
for
we're
currently
working
on
the
kivati
of
us
and
the
jail's
aquifers
and
chase
I
PFS
API.
B
And
then
we
have
a
nicely
pipeline
view
and
you
can
see
some
of
the
things
running
in
parallel
as
well,
so
yeah,
that's
where
the
current
status
on,
if
you
still
like
the
old
you
are,
is
still
gonna,
be
running
exactly
like
normal
and
it
has
a
fresh
little
tub
log
in
as
well
as
when
I
press
on
login
I
already
authenticated,
with
which
guitar
so
is
just
gonna
use.
My
my
github
account
and
send
some
in
the
IPF
s
organization.
Everything
is
solved
for
us.
Basically,
so
yeah
take
questions.
Demo.
A
B
J
J
Cool,
let's
see,
I
gave
I,
give
a
talk.
Last
night
an
etherion
meet
up.
J
All
right
here,
the
talkative
you
meet
up
about
the
Zika
Explorer
yeah.
It
was
great
alright,
so
at
PLD
it's
really
cool
and
really
easy.
So
I
have
let's
say:
I.
Have
this
JSON
witches
and
I
feel
the
object
super
easy
to
just
put
it
into
I
PFS.
Let's
hope
it
I.
Have
it
working
cool
at
work
all
right
and
you
can
get
it
back
out,
Wow
fantastic!
You
can
also,
you
know,
do
things
like
get
foo,
oh
my
god,
not
like
it
giving
Pat
what
did
I
break?
J
Oh
I'm,
not
on
the
right
branch.
That's
embarrassing,
yeah!
So
one
other
thing
up.
I
did
last
night.
Let's
see
if
this
works
because
I'm
not
on
the
right
branch,
you
can
just
get
files
out
right
and
it
follows
these
internal
pads
inside
this
JSON
structure,
and
so
it's
great
because
you
can,
you
know
design
your
own
schema
/
structure
to
that.
A
Have
a
question
before
you
move
to
the
next
one:
so
with
that
the
that
JSON
is
just
stored
as
JSON
that
you
added
I
PFS
right.
No.
J
So
that
JSON
the
store
to
see,
bore
okay,
oh.
A
J
I
were
to
do
I
give
this
block
get
this.
It's
pretty
gnarly
right,
so
it
actually,
it
gets
converted
to
see,
bore
and
then
we
just
didn't
see
boards
along
the
one
mapping
with
JSON.
It
goes
back
and
forth
clearly
because
I
have
written
some
members.
Well,
I
mean
this
is
this.
Is.
F
A
Jeremy
the
reason
why
nots
never
missing
the
the
reason
why
I
asked
that
question
was
that
last
week
to
be
was
talking
about
the
idea
that
there's
no
such
thing
as
a
I
pld
object
that
you're
not
converting
your
JSON
to
I
pld
objects,
you're,
just
adding
JSON
die
PFS
and
then
parsing
it
as
I
PLT
content,
you're
using
sort
of
the
IPL
d
structures
to
interact
with
the
data
is
that
right,
no.
J
There
is
I
pld
like
there
is
a
Seeb
or
IP
LD,
which
is
like
the
so
like.
Initially,
we've
had
a
bunch
of
confusion
around
this
because
11
first
started
talking
about
IPL
d.
He
really
meant
the
Seaboard
data
structure
with
links.
We
sense
kind
of
expanded,
I
pld
to
really
just
mean
linked
data
and
the
the
Seaboard
stuff
still
definitely
exists,
and
you
know
you
can
use
it.
Whatever
I
got
the
right
banner,
you
know,
but
the
yeah
the
defaults,
their
default.
Ip
LD
is
the
C
bore
stuff.
J
But
then
you
can
do
other
things
like
this
object
right
here
and
if
we
look
at
this
one,
we
can
see
that
it's
a
normal,
so
this
one's
a
Seeb
or
object,
but
inside
it
has
a
link
to
something
called
Z
cash.
And
then
I
can
grab
that,
and
this
object
is
jason
right
now,
but
it's
actually
stored
as
a
rosy
cache
block
like
in
the
native
format.
J
All
we
did
is
literally
essentially
just
move
it
into
the
correct
place
in
blocks
directory
piped
it
directly
from
the
daemon
to
z
cash
payment
through
to
IP
of
us.
Without
anything,
and
then
you
can
do
fun.
Things
like
you
know,
walk
along
it.
It
the
difficulty
and
it
works.
Great
I
have
a
question.
Yes,
gonna
drizzle
of
through
links,
yeah,
thats,
encinas
parent
thing.
Those
are
links,
TX,
I!
J
J
So
there's
no
like
the
inputs
is
a
blank
thing
and
then
the
outputs
is
1010
z.
Cash
to
one
address
and
2.5
to
the
founders
reward
is
really
fun
and
I
have
the
Bitcoin
stuff
working
I
just
haven't
synced
Bitcoin
box,
you
into
my
laptop
because
I
that's
120,
gigs
of
space.
That
I
don't
feel
like
using
right
now.
C
G
So
that's
a
small
weekend
thing:
I
just
took
a
well
basically,
the
idea
is
to
have
liquid
ttp
be
able
to
send
and
receive
HTTP
and
use.
Go
stand
our
stuff
to
do
work
with
it.
So
this
is
kelly,
p2p
HTTP
and
it
should
just
yeah
pretty
easily
like
you
doing
any
other
go
server
and
client.
You
should
be
able
to
just
expose
your
HTTP.
Ip
is
only
TTP
I,
don't
know
if
this
is
super
useful,
probably
not,
but
looked
fun
to
do
it
actually.
G
D
G
Yeah,
it's
pretty
much
so
it
just
you
can
on
one
side
you
can
just
HTTP
serve
something
that
is
served
via
a
stream
ali
p2p
string,
I'm
from
the
other
side.
You
can
get
or
do
any
client
operations
on
something
that
is
read
and
written
from
a
stream
so
basically
consists
intriguing
going
to
sink
in
the
streams.
I
connections.
G
Right
everything
is
a
standard
Ingo.
You
just
rub
the
streams
as
standard
connections
and
then
just
like
go
do
everything,
and
so,
if
you
want
to
expose
something
on
HTTP,
only
p2p
which
it
happens
to
be
an
HTTP
rest
api
and
you
want
to
read
it
from
the
other
side,
it
is
possible
with
minimal
modifications.
C
A
G
Not
really
this
is,
you
may
just
expose
up
website
directly
through
liquid
to
be
and
be
able
to
read
it
from
the
other
side.
So,
instead
of
using
regular
connection
so
get
non,
ETP
thing
you
might
just
do
a
get
request
and
throughly.
It
will
be
be
able
to
obtain
the
content
from
the
other
side.
Okay,.
G
Cool
cool
I
think
I'll,
think
of
it
more
practically.
If
I
PFS
has
an
HTTP
idea,
if
it
exposed
ditch
these
api
through
the
radar
little
bit
channel,
I
wouldn't
have
to
and
I'm
already
talking
to
I
DFS,
for
whatever
other
reason
and
I
want
to
use.
The
idea
of
si
di
I
would
not
have
to
just
establish
a
separate
connection
using
a
standard
network
connection.
Tcp
I
could
just
make
my
request
through
the
already
existing
the
p2p
connection
and
use
the
API
through
that.
But
as
I
say
it
not
sure
it's
super
useful.
A
F
A
It
like
we
might.
This
was
super
relevant
two
weeks
ago
when
it
was
art
for
we
had
just
on
our
first
week
ever
of
doing
sprints.
So
it
was
like
let
everyone
thought
about
how
that's
going
and
so
we'll
see,
we'll
see
what
comes
up
like
we
might
just
talk
for
ten
minutes
and
be
like
seems
like
it's
working,
fine,
bye,
y'all
but
yeah
like
that's
what
that's!
What
the
focus
of
this
next
section
is
about.
A
B
A
K
A
H
A
A
C
A
Look
hi
all
right
I,
so
the
the
point
of
this
time
slot
made
a
lot
of
sense
two
weeks
ago.
Oh,
it
was
the
sort
of
midpoint
through
our
Springs
it
as
a
chance
for
the
people
and
the
different
Sprint's
to
sort
of
sync
up
about
what
are
we
doing?
How
is
it
going?
It
was
like
almost
a
midpoint
retrospective
now
that
we're
in
our
second
round
of
sprints
and
also
there's
no
one
from
at
least
one
of
the
Sprint's
on
there
might
not
be
that
much
to
discuss.
A
But
the
point
here
is
a
week
from
now.
This
prints
are
going
to
be
showcasing
so
there's
less
time
for
the
the
discussion
just
about
like
on
the
fly
discussing
what's
going
on,
because
you
spend
more
time
showcasing
what
you've
done.
So
you
people
have
anything
to
flag
of
how
things
are
going
or
yeah
stuff
to
discuss.
B
H
B
A
Victor
for
your
spring,
are
you
do
you
basically
just
have
a
long
list
of
things
that
need
to
get
done
and
you're
all
just
sort
of
picking
them
up
and
getting
them
up
really
good
to
frame
so.
B
B
Really
we
color.
Like
simply
estimation
part,
we
try
to
split
up
the
stories,
so
they
were
kind
of
like
equal,
but
then
we
ended
up
in
our
planning
call
with
like
one
Capshaw
issue
which
was
figure
before,
but
then
we
spit
it
out
and
then
it
got
bigger
and
always
clear
it
out,
and
we
did
the
same
with
the
monitoring
we're
trying
to
make
it
the
same
size.
But
then
some
other
things
popped
up
with
monitoring
swiss
figured
out
into
its
own
storage.
A
Consider,
instead
of
using
a
sprint
label,
which
we've
done
in
other
repos,
been
using
to
like
say,
this
issue
represents
a
whole
sprint
of
two
weeks.
You
might
instead
want
to
use
like
story
and
that
one
you
just
opened
like
in
a
scrum
context.
You
would
call
an
epic
right,
like
this
is
sort
of
bigger
story
that
involves
a
bunch
of
some
stories
so.
B
Basically,
like
all
these
stories
you
see
out
here
is
actually
epics
and
the
actual
tasks
are
inside
the
issue,
so
you
could
say
that
the
issues
around
here
or
epics
and
they
are
just
tagged
with
the
springs-
to
be
able
to
filter
to
your
desk.
The
time
we
have
been
my
stone
as
well,
which
one
cannot
wrinkle.
A
So
this
is
where
we
did
the
same
thing
on
the
data.gov
one,
and
this
was
having
this
page
was
super
useful.
The
problem
is,
if
your
issues
that
the
work
is
spread
across
multiple
repos,
then
there's
no
way
with
github
just
should
to
get
this
page
with
that.
That
has
here's
the
milestone
in
here
all
day,
truth
up
along
to
the
milestone.
If
the
milestone
involves
work
that
spread
across
multiple
Rico's
and
that's
what
labels
and
milestones
this
floor
and
starters.
A
The
reason
why
the
bead
is
always
asking
for
labels
and
milestones
is
because
everything
that
they
do
on
on
everything
that
he's
sort
of
directly
involved
in
is
cut
across
many
resources
yeah.
He
doesn't
have
this
page
and
can't
have
this
page
without
labels
and
last
names
without
that
tool,
all
right.
So
this
is
helpful
to
see.
A
J
Yeah
daveed
and
I
heard
working
somewhat
independently.
It's
kind
of
I've
been
working
on
a
lot
of
the
block
chain,
integration
stuff
and
then
he's
been
working
on
Jess
I,
PFS,
dag
API
stuff.
We
did
sit
down
and
hash
out
some
general
api's
on
that,
but
I
mean
that
he's
coming
here
today,
ish
so
we'll
be
able
to
work
more
closely
on
that
are.
J
E
G
A
And
your
captain's
logs
include
this
sort
of
here's.
What
we'll
be
working
on
next,
here's
the
functionality
will
be
moving
towards
next
entrant.
I
think
so.
I
thought
I
only
have
to
increase
in
soon.
Well,
I'm
just
wondering
how
you're
sending
out
the
message
of
it.
If
someone
is
following
cluster,
how
do
they
know
like
what
stuff
you're
aiming
at
and
what
the
like
anticipated
timeline
is
for
which
things
get
attention
when
and
I
think
that's
mainly
you're
doing
that
with
the
captain's
lockrey
yeah.
A
E
D
B
E
D
A
It's
a
start,
I
guess:
there's
the
update
from
the
data.gov
stuff
that
is
fiom
other
people
using
our
stuff
that
there
is
a
work
of
actually
replicating
all
of
those
datasets
between
a
bunch
of
blank
mirrors
using
IP
FS
is
probably
happening
over
the
next
week
like
by
this
Friday.
It
will
probably
be
done
and
or
at
the
very
least
they
will
have
started
the
replicating,
and
so
that's
that's
exciting,
but
there's
nothing
there's
nothing
really
to
report.
A
Yet
it's
more
that
like
they're
finally
ready
to
try
it
and
our
code
is
ready
for
them
will
try
and
so
we'll
see
what
what
happens
I'll
have
more
of
an
update
next
week,
probably
maybe
a
demo
of
reading
it
datacom
data
set
awful
I
PFS.
Oh
so
I
think
we
just
did
our
whole
Monday
sprint.
In
an
hour,
our
whole
Monday
calls
and
everything
in
an
hour
is
there
anything
else
that
we
needed
to
cover.