►
From YouTube: CNCF Serverless Working Group Meeting - 2018-03-08
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
Barone
either
yep
okay,
Barham
yep.
Okay,
did
it
did
you,
let's
see
Chris
fortress.
A
A
C
B
Okay,
cool
Steve,
oh
hi,.
A
B
G
H
A
I
A
B
L
A
L
B
A
F
F
D
M
B
A
G
A
A
Kathy
did
not
get
a
chance
to
finish
her
quick
little
with
his
source
on
the
last
call,
because
there
was
so
many
questions,
so
I
agreed
to
give
her
another
5
minutes
just
to
quickly
finish
up
her
point
of
view,
and
then
we
can
quickly
move
on
to
the
other
agenda
items.
I
did
want
to
get
that
out
of
the
way,
because
I
feel
bad,
that
we
didn't
get
a
chance
for
all
four
people
to
finish
their
work.
So
Kathy,
do
you
want
to
go
ahead
and
share
your
screen
or
just
talk
to
it?
K
A
Let's
take
the
first
one
here
when
it's
111
this
one
there's
there's
a
link
to
in
the
chat
actually
hold
on
it
sure
my
screen
may
be
here
for
people,
okay,
so
on
this
one
in
terms
of
changes,
all
I
did
is
made
sort
of
a
an
index
list
of
material
that
we're
adding
for
people
to
share.
You
know,
presentations
and
stuff
like
that.
A
For
me,
the
meetings
or
conferences,
I
believe
on
last
week's
call
the
people
asked
for
that
if
for
index,
as
opposed
to
just
a
directory
for
things
to
be
put
in
that
way,
we
can
also
have
pointers
to
things
that
are
not
kept
in
our
directory
and
I.
Think
here's
a
good
example
from
Sarah
and
I
don't
believe
there
really
been
any
comments
on
this
one.
So
you
just
double
check.
You
know
no
real
comments.
So
are
there
any
questions
or
concerns
with
this
one?
L
A
A
O
C
A
O
A
Alright,
any
objection,
then,
to
approving
this
one
all
right
done.
Thank
you
guys,
all
right,
this
one
I'm
hoping
this
isn't
controversial.
Since
it's
been
saying
there
for
a
while
this
one
had
to
come
to
a
sec.
I,
don't
worry
what
initiated
this,
but
there
was
a
desire
to
make
the
what
is
it
the
goal
section
or
didn't
note
the
status
section
now
the
status
section
of
the
spec
basically
talked
about
what
our
current
or
what
we're
currently
doing,
which
is
basically
just
defining
the
abstract
definition
of
the
extra
metadata
or
for
an
event.
A
A
A
E
A
Okay,
it
sounds
like
this
walks
over
to
reasons
the
one
it
sounds
like.
There
is
some
discussion
around
your
comment
that
used
to
happen
and
then
Clemens
that
you
need
to
rebase
if
nothing
else.
So
perhaps
we
need
to
move
this
one
off
the
Z,
the
review
list
and
do
deal
with
that
later
and
in
particular
offline.
Is
that
fair?
Yes,.
A
O
A
A
K
Kyle,
how
do
I
see
my
site?
Yes,.
B
F
K
Okay,
I'm
sorry
I
mean
this
okay,
you
can
see
this
right
right,
okay,
so
this
is
example
on
a
trace.
The
same
example
I
presented
last
time.
So,
if
we're
like
you
know,
for
example,
on
this
use
case,
there
are
two
events
that
two
events
is
going
to
is
part
of
the
same
answer
for
this
application,
so
when
the
first
of
events
happened,
for
example,
if
for
the
window
open
and
also
the
motion
detection
event,
that
could
happen
at
many
different
houses
right.
K
So
when
the
when
the
service
platform
received
all
those
events
is
easy
way
to
know
to
correlate,
you
know
the
event,
a
and
event
B,
for
example,
no
motion
event
and
when
the
opening
event
or
door
opening
event
from
the
same
house,
basically
so
that
you
know
become
process,
you
know
it
correctly.
So
there
could
be
many
instances.
Execution
ins
function,
execution
instances
for
each
house,
there's
a
function,
execution
instance.
So
the
problem
is,
we
need
a
way
to
correct
those
events
correctly.
K
We
could
receive
multiple
motion,
detection
events,
a
multiple
door
or
window
opening
events.
So
how
do
we
correlate
them
together?
That's
a
problem!
This
is
a
it's
just
an
example.
There
are
many
other
use
cases
which
will
need
you
know
the
McMinn
to
correlate
them
together.
So
the
proposal
is
to
provide.
K
We
need
to
define
our
correlation
token
in
the
event
and
that
correlation
Coke
is
used
to
correct
all
the
events
associated
with
the
same
on
functional
application
instance
such
as
you
know
that
token
current
identifies
the
Oh
even
come
from,
for
example,
Cathy's,
house
or
whatever,
and
that
Tolkien
could
be
any
string
that
uniquely
identify
the
application
event
instance,
for
this
example
is
it
could
be.
You
know
a
house
address
or
whatever
other
unique
string,
but
for
other
examples
it
could
be,
for
example,
for
a
travel
request.
It
could
be
a
travel
request.
K
K
This
token
could
sit
in
different
location
of
the
event
data,
so
I
think
you
know
we
should
not
put
any
restriction
on
the
location
of
the
token
in
the
event
data
because,
because
that's
not
I
think
that's
not
feasible
or
it's
not
a
good
way,
because
there's
so
many
different
event
types
and
it's
measuring
IOT
scenarios,
all
those
device,
the
equipment's
are
manufactured
by
different
vendors,
so
I
think
you
know
one
way
to
do
this
is
the
token
view
can
be
identified
by
a
prism,
a
path
string
which
specify
the
location
a
token
in
the
event
date.
A
I'd
like
to
keep:
let's
let
Kathy
finish,
and
then
you
people
get
a
chance
to
ask
clarifying
questions
because
we
don't
really
have
time
to
go
back
and
forth
under
design
my
discussion,
so
let's
hold
off
on
the
Kathy.
Can
you
go
you're
basically
out
of
time,
so
you
can
just
finish
up
your
side
of
things
and
then.
K
K
Ok,
so
so
the
okay,
so
as
we
discussed
last
last
time
right
the
source,
no
could
be
storage
device
and
there
you
know-
and
then-
but
you
know
for
this
case
right
if
this
motion
detection
event,
if
we
did
find
the
source
as
that
picture.
If,
when
the
picture
is
saved
to
a
storage,
we
define
the
source
as
a
storage,
and
then
we
need
a
way
to
identify
the
you
know
the
correlation
token.
So
that
will
be
part
of
the
that
correlation
poker
should
be
in
the
data.
K
The
event
data,
then
I
think
we
need
a
way
to
do
that.
So
that's
why
I'm
suggesting
location
pass
will
be
the
way
to
do
that
that
in
that
way,
no
matter
where
that
path
is
where
that
no
correlation
cocaine
is
located
in
the
event
data,
no
matter
what
kind
of
event
source
we
have
a
generic
way
of
doing
that.
Yeah
I,
think
that's
all!
Okay,.
A
D
Have
a
question:
okay,
we
were
talking
earlier
about
the
source
being
a
URI
and
that
the
structure
that
URI
will
be
different
for
different
types
of
events
and
different
implementations
would
something
like
the
the
house
from
which
there
are
multiple
IOT
devices.
Wouldn't
that
be
a
portion
of
that
URI
in
order
to
get
like
from
all
the
way
from
the
most
generic
down
to
the
to
the
specific
device.
Can't
you
get
this
this
kind
of
correlation
for
something
like
that
from
a
component
of
the
source
as
the
URI?
Yes,.
K
Yes,
I
think
that's
that's!
That's
that
information
that
correlation
polka
information
will
be
in
that
URI,
but
we
need
a
way
to
say,
as
you
just
mentioned,
different
sources
in
the
different
event
types
that
could
be
in
different
they
that
URI
is
a
string
right
in
different
location
of
that
URI.
So
we
need
a
pass.
For
example,
here,
I
give
an
example:
if
it's
in
the
HTTP
header,
API
gateway
in
my
be
you
know,
Heather's
fall
day
and
then
something
you
know,
and
they
seem
not
like
a
storage.
K
It
could
be
like
some
records
and
then
some
whatever
make
a
date,
OBS
identified
question.
M
A
Guys
guys
I
got
the
cause
I'm
here,
because
I
feel
like
we're
getting
into
design
discussions
and
I.
Think
the
idea
of
the
abstract
idea
of
just
having
a
correlation
token
is
what
you
want
to
get
across,
and
we
can
talk
about
within
the
PR
itself.
The
best
way
to
represent
that
or
even
to
have
it
at
all.
So
at
this
time
I
mean
I'd
like
to
call
time
on
this
part
of
discussion,
because
I
just
like
to
get
Kathy
a
chance
to
present
review
and
Kathy
I.
A
E
I'm,
just
about
the
it's
that
it
seems
like
from
your
example
Kathy
that
there
may
be
some
time
to
be
like
multiple
multiple
pieces
of
data
right
think
somebody
could
want
to
correlate
right.
It
could
be
like
this
particular
house
and
windows
in
this
house,
or
something
so
I.
Just
wanted
to
I
was
curious,
whether
that's
something
you've
thought
through
and
and
just
really
maybe
I
could.
Just
if
you
didn't
speak
to
that
now
or
maybe
address
that
through
that
consideration
and
in
a
subsequent
publish
master
I'd.
K
Okay,
okay,
I'm,
not
very
sure,
I,
understand
the
question,
so
it
could
be
any
that
that's
so
let
me
just
express
my
view
so
that
correlation
token
could
be
anything
okay,
if
you
think
you
know,
I
need
to
go
to
the
you
know
that
granularity,
a
finer
granularity
level
yeah
just
specify
that
so
different
use
cases.
Different
application
could
have
different
Cartesian
token.
So
the
way
so
we
I
think
you
know
we,
the
correlation.
How
can
you
correct
these
events
but
how
to
defy
it?
K
K
O
Science
discipline
specifically
talked
about
is,
is
prior
art,
so
there's
their
messaging
systems,
whether
they
are
events
based
or
whether
they
are
carrying
messages.
Most
of
them
have
a
notion,
or
very
many
of
them,
have
a
notion
of
a
description
of
the
content
of
the
message
that
is
allows
for
broad
description
of
any
shape.
That
field
is
sometimes
called
subjects.
Sometimes
that
feel
is
called
title,
and
so
the
question
is
how
your
proposal-
your
differs
from
those
approaches.
O
O
A
A
Matt
Matt
Matt,
no,
no
I'm
gonna
have
to
call
time
era,
I'm,
sorry
to
be
a
little
bit
of
a
dictator,
but
we
really
need
to
get
on
to
other
subjects,
and
this
wasn't
meant
for
a
time
of
a
discussion.
I
think
she
made
her
point
clear
about
what
she's
looking
for
and
let's
save
the
discussion
of
the
design
and
how
our
release
other
feel
for
the
PR
itself.
This
isn't
time
to
dive
into
this.
A
C
What
this
is
more
of
a
proposal
for
how
we
like
handle
these
sorts
of
moments,
would
it
be
acceptable,
like
I,
don't
think
this
isn't
a
place
where
we
could
really
propose
a
PR?
Could
we
could?
We
have
like
a
place
where
we
just
continue
the
conversation
in
written
form
since
there's
still
a
lot
a
conversation.
People
want
to
have
well.
A
People
are
very
free
to
talk
about
these
things
offline,
but
I
would
my
preferred
approach
is
to
have
people
discuss
these
things
either
through
an
issue
or
a
poor
request,
because
I
think
that
that
helps
focus
the
discussions
and
people
can
have
offline
discussions,
but
on
this
call
right
now,
I'd
like
to
get
back
to
what
I
heard
from
everybody
for
the
most
part
of
the
most
important
issue
we
just
need
to
resolve,
which
is
the
scope
of
what
we're
doing.
That's
all
I'm,
trying
to
get
back
to
that
conversation.
So.
J
That's
the
only
observation
was
gonna
make
Doug
was
that
some
of
the
things
she
said
here
would
be
best
fitting
bodied
in
it
in
a
use
case
and
need
to
tease
out
what
people
are
seeing
in
terms
of
an
example,
as
she's
been
saying,
it's
it's
an
example
that
the
value
can
be
anything
so
people
aren't
referring
to
much.
So
we
need
to
capture
the
yeast
cake,
I.
A
Agree
so
Kathy,
please
take
the
action
item
to
write
up
your
use
case
and
potentially
a
PR
if
you
feel
comfortable
doing
that,
but
at
least
start
with
the
use
cases
and
get
the
discussion
going.
This
some
place,
whether
it's
an
issue,
you
know
or
PR.
That's
your
choice
in
terms
of
how
you
want
to
move
forward.
K
A
Agree
because
you
have
to
understand
the
point
of
this
part
of
the
discussion
was
not
super
forward,
a
proposal
to
have
a
discussion.
This
was
to
put
your
point
of
view
about
what
his
source
it
wasn't
to
have
a
deep
discussion
about
it:
okay,
I'm,
not
gonna,
shut
down
the
conversation
other
than
I
just
want
me
sure
you
have
the
chance
to
finish
up
your
five
minutes
and
we
gone
way
over
that.
I
A
A
There
are
quite
a
few
comments
in
the
PR
itself
for
things
that
I'll
consider
more
of
a
sink
tactical
change
more
than
anything
else
and
I'm
wondering
if
maybe
we
got,
we
can,
at
this
point
in
time
talk
about
some
of
the
higher
design
goals
of
what
you're
trying
to
get
here
or
design
their
design
cause
that
you
want
put
forward
here
and
get
those
discussions
going
right
now
that
make
sense.
Yes,.
E
In
fact,
there
and
thanks
everybody
for
the
feedback.
I
have
oops
I,
wanted
to
put
this
in
a
Google
Doc,
so
people
could
I'm
going
to
just
outdent
this.
We
can
delete
it
later
or
move
it,
but
I
sort
of
ripped
off
of
Clements
suggestion
that
we
do
this
with
like
user
stories
and
so
I'd
like
to
go
through
the
personas
and
user
stories.
E
E
A
E
Just
because
then
people
can
like
add
comments
and
I
think
there's
a
in
the
number
of
there's
a
lot
of
people
on
the
call.
So
if
people
have
like
wordsmithing
thing,
you
can
just
make
suggested
edits.
If
people
have
you
know
like
so,
then
they
can
do
some
more
dynamic
stuff
that
people
have
access
to.
E
We
have
somebody
who's
developing
an
event
source
right
that
that's
the
person
who
creates
the
code
that
is
going
to
emit
events,
there's
a
publisher
that
operates
the
event
source
and
then
there's
the
consumer
developer.
Who
creates
the
code
for
an
event
consumer
and
it's
useful.
We
can
also
have
the
publisher
of
that
and
then
I
came
up
with
these
three
stories.
Two
of
them
were
a
little
modified
from
what
Simmons
wrote,
but
basically
the
first
one
is
as
an
application
developer.
I
can
create
an
application
without
modifying.
E
Their
needs
to
be
some
more
words
there,
where
the
developer
may
not
have
access
code
access
to
modify
the
code
in
the
event
source
for
the
event
consumer,
so
I
think
there's
like
some
missing
words,
but
the
idea
is
we're
decoupling,
the
development
of
these
things,
and
that
could
be
because
we
have
two
teams
right,
that
we
want
to
be
couple
their
release
cycles
or
it
could
be
that
they're.
Actually,
a
third
party
event
sources,
event,
consumers,
and
there
were
some
question
I.
E
Think
a
lot
of
folks
in
the
group
are
coming
from
trying
to
figure
out
the
serverless
thing
and
I
wanted
to
point
out
that,
like
I
came
up
with
a
use
case.
That's
that
I
commented
on
this
morning,
where
you
can
imagine
that
in
the
future
we
could
have
consumers
that
are
prepackaged.
You
could
imagine
that
somebody
who
has
some
kind
of
SMS
service
right
or
like
pager
service
could
could
it
could
say,
like.
Oh
all,
the
you
know
there's
a
set
of
events
that
automatically
it
turned
into
natural
languages.
E
If
you
hook
up
my
SMS
service
to
your
to
these
ten
types
right,
then
so
that
you
could
have
event
sources
that
are
sort
of
prepackaged,
managed
services,
and
you
could
have
event,
consumers
and
actions
right
that
are
prepackaged
in
some
way
and
then
developers
can
then
like
string
these
together
and
then
maybe
eventually
end
users
and
stuff.
But
that
would
be
all
like
software
that
people
would
be
building
around
this
event
ecosystem.
E
So
then,
as
event,
publisher
I
want
to
make
the
event
available
in
a
way
that
it
can
be
distributed
to
other
software
services
and
that
other
software
can
get
at
some
particularly
interesting
subsets
with
minimal
effort,
meaning
like
there's,
probably
some
stuff
in
the
middle
that
they
can
delegate
to
right.
They
could
then
be
done
by
another
third-party
implemented
by
and
then
there's
the
event
consumer
as
an
event.
E
Consumer
I
want
to
have
enough
fidelity
in
the
event
metadata
so
that
there
might
be
generic
middleware
that
can
select
and
deliver
a
subset
of
events
for
and
for
there
to
be
enough
fidelity
and
that
metadata
for
local
dispatch
to
an
action
and
I
would
really
like
to
have
a
story
in
here
for
the
like,
the
the
people
developing
the
middleware,
but
I
didn't,
but
that
could
be
a
gateway.
I
didn't
know!
Quite
what
what
the
good
like?
What
is
the
persona
for
the
person
or
for
the
developer?
E
M
M
P
P
O
E
Action
term
that
we
talked
about
before
it's
not
an
accepted
PR,
but
we
did
do
the
talk
through
the
event,
concepts
and
I
bar
the
action
word
from
IBM,
open
wisk,
which
seems
to
have
like
the
most
well
thought
out.
In
my
mind,
like
just
like
naming
of
things
that
it,
you
know,
seems
clear
to
me,
and
so
because
not
everything
not
every
destination
would
be
a
function
necessarily
I
wanted
to
have
a
generic
church.
So
I'm.
O
Just
I'm
just
in
in
that
in
the
middleware
space
and
that's
kind
of
the
perspective
of
intaking
producer
and
consumer
are
the
those
generic
terms,
and
then
the
consumer
will
take
the
event
and
then
will
do
something
with
it
and
part
and
what
it
might
do
might
be
in
actually
that,
but
it's
not
necessarily
in
action.
That's
why
and
you
can,
if
slash,
is
fine
for
now
I'll.
O
No,
no!
That's
that.
So
that's
my
point.
So
there's
the
the
speaking
of
middleware
is.
There
is
some
piece
that
is
between
the
publisher
and
the
consumer
and,
and
it
doesn't
I,
don't
think.
There's
implication
here
that
that
piece
that
sits
between
those
two
is
a
networked.
Resources
might
just
be
a
framework,
and
you
have
an
event
publisher
and
an
event
consumer
that
live
peacefully
together
in
process
and
exchange
called
event.
Events
I
think
that
honestly
middleware
is
is
such
that
it
needs
to
be.
You
know
a
central
broker
thing,
but
it
is.
M
N
O
Of
this
I
think
of
this
in
a
very
generic
way,
and
that's
also
I,
don't
know
whether
you
have
the
I
put
an
issue
in
this
week.
At
the
beginning
of
the
week,
I
think
issue
112,
where
I
go
over
some
prior
art
than
I'm
referencing
and
when
I'm,
basically
going
through
some
of
the
topology
choices
that
are
being
made
by
some
by
existing
middleware
and
how
they
use
the
concepts
that
we
have
here
and.
B
O
Think
and
I
think
and
if
you
and
actually
sites
for
examples
for
IT
infrastructures,
that
being
AWS
IOT,
Watson
IOT
as
IOT
hub
and
called
IOT
core
from
Google
and
how
they
use
those
things
and
I
think
the
concept
that
we
have
right
now
and
also
those
definitions
that
we
have
have
here
also
fit.
Those
cases.
E
So
I
think
Clemens
you,
you
did
a
lot
of
I
read
your
your
request
and
I
think
I'm
your
pull
request
or
your
issued
whatever
it
was
and
I
think
I
think
Rachel's
done
some
work
if
I
don't
tease
it
apart
and
put
it
in
with
I.
Think
there's
like
a
set
of
meetings
where
we
talk
a
lot
about
prior
art
and
there's
been
some
work
on
the
repo
on
that.
So
I
think
you're
right
on
with
that
and
very
much
in
the
spirit
of
what
has
been
discussed
in
this
group.
E
So
so
I
think
the
question
is
I
just
drafted
here.
It
would
be
people
be
comfortable
with
calling
the
middleware
developer
like
inclusive
as
fun
and
suggest
so
it
could
be
an
API
API
gateway
or
a
router
or
software
framework.
It's
like
all
the
things
in
between
publisher
and
consumers.
That
is
it
reasonable
way
to.
F
I
I
B
E
E
E
D
O
O
The
middleware
can't
modify
them
at
all
and
they
have
to
do
with
you
know,
whatever
the
descriptive
information
for
the
message
body
the
system
put
in
there
like,
for
instance,
the
subject
is
unchangeable,
the
the
logical
destination
is
unchangeable
which
we
don't
have
here,
but
the
logical
source
of
information
is
unchangeable.
All
those
things
are
unchangeable
so
that
the
middleware
has
very
clear
rules
and
in
the
middle,
where
has
annotation
fields
that
it
can't
go
and
add
and
remove
and
do
things
with,
as
it
has
enhance
the
message
for
processing
two
different
places.
So.
E
So
I'd
love
to
so
I
think
that
that's
a
good
example
and
what
exactly
why
I
want
to
keep
this
like
really
high
level
about
our
intent
like
what?
What
are
the
goals
for
each
of
these
personas
and
then,
and
so
what
I'd
like
is
like
to
invite
folks
who
haven't
spoken
yet
to
comment
on
the
personas,
particularly
if
it
you
represent
one
of
those
personas
I.
K
K
So
how
we
decide
okay,
so
here
I,
think
we're
more
from
developer
point
of
view,
but
I
think
you
know
it
from
us
one
point
of
view
right:
uh-huh,
like
you
know
what
is
what
is
the
publisher?
What
is
a
action,
different
action,
so
just
you
know,
use
the
example.
I
gave
that
use
case
the
sensor
to
detect
the
motion,
and
then
there
will
be
that
picture
was
stored
in
the
storage.
So
what
is
the
event
source
in
that
case?
What
is
the
event
papi
sure
so.
E
I
think
at
this
point,
what
I'd
like
to
do
is
identify
the
actors
right.
So
the
idea
is
the
the
source.
Developer
is
the
thing
emitting
the
event,
the
thing
that
is,
and
it's
up
to
the
developer
to
say
and
I.
So
you
could
have
these
these
three
developers
right
so
I'm
going
to
move
the
the
publisher
out
of
the
way
a
little
bit.
E
The
operators
I
think
aren't
important
actors
as
well,
but
but
if
you
just
think
of
the
three
developers
right
in
terms
of
source,
whether
you
are
the
source
or
your,
the
middleware
totally
depends
on
the
code.
You
write
right
like
if
and
the
piece
of
software
I
write
leaves
the
meaning
intact,
then
I'm,
where,
if
the
piece
of
software
I
write
takes
in
information
and
then
changes
the
event
type,
then
I'm
a
source
right,
it
all
depends
on
whether
you're
emitting
your
own
events,
but.
A
E
Like
if
you
think
about
like,
like
in
normal
messaging,
like
actually
I,
think
it
is
completely
different
right.
So
it's
it's
I
think
that
we
need
language
to
discuss
the
parts
of
the
system
that
are
just
doing
transport,
where
they're
they're,
getting
something
from
source
to
destination
versus
the
things
that
are
like
I
am
omitting
events,
and
then
they
may
be
one
in
a
pipeline,
but
they
really
have
the
same
concern
as
the
original
source
of
the
event
to.
J
J
J
J
E
E
E
E
K
So
if
the
system
of
vice
that
modifies
the
event
does
it
become
the
new
source,
the
source,
if.
E
B
E
This
is
a
little
different
from
the
way
that
I've
heard
observer
used
before
that
image.
Server
could
actually
change
the
format
and
we
transmit
it.
But
if
people
are
like
that
term
and
and
have
more
experience
with
standards
bodies
in
this
area,
I'm,
like
you
know,
I
just
want
a
word
that
we
all
agree
on.
J
J
E
K
E
J
B
J
E
So
here
so
I'm,
adding
as
an
event
source
developer,
I
can
define
new
event
types
or
use
existing
tips,
then
types
that
are
meaningful
representations
of
my
system,
state
changes
or
something
like
that.
I.
J
A
Just
a
little
time
check
here,
so
we
have
less
than
nine
minutes
left
and
I
know
we're.
Making
lots
of
good
progress
here,
but
I'd
like
to
do
is
to
suggest
that
we
have
a
follow-on
meeting,
not
next
Thursday
but
before
then
and
Sarah
I
was
wondering
if
you
would
take
the
action
item
to
to
try
to
set
that
up,
because
I
think
I
think
we
need
some
more
discussions
here
and
this
one
hour
a
week
isn't
sufficient
for
that.
So.
E
A
Now,
without
getting
into
well
continue
the
discussion
of
the
design
itself
or
the
wording
here,
are
there
any
high-level
things
people
want
to
bring
that
relative
to
the
process?
We're
gonna,
follow
it
to
try
to
resolve
this
meaning
Sarah
is
gonna
set
up
the
Google
Doc
Sarah's
gonna
set
up
one
of
their
time
for
us
to
talk
during
the
week.
Is
there
anything
else
people
wanted
to
bring
up
from
a
process
perspective.
A
Okay,
in
that
case,
I
think
we
had
next
steps
on
that
one
and
before
we
run
out
of
time,
I
wanted
to
basically
have
almost
the
exact
same
conversation
or
process
question
or
discussion
around
was
the
source
but
I'm.
Sorry,
not
what
is
actually
so.
It's
interesting
Sarah's
your
discussion.
There
originally
started
out
talking
about
what
is
our
design
goals,
but
it
seems
like
you're
now
getting
into
discussing
what
is
the
source
I
might
eat
interpreting
that
correctly,
so
it
could
probably
merge
those
two
discussions.
Well.
E
I
actually
think
that
they
need
I'd
like
to
sequence
them,
because
I
think
there's
the
sort
of
like
at
a
high
level
what
it,
what
need
to
reach?
What
problem
are
we
trying
to
solve
with
defining
the
source
right
and
then
there's
like
okay,
let's,
let's
get
into
it
with
the
attributes
and
exactly
what
do
we
mean
and
so
I'm
trying
to
like
the
trying
to
use
this,
like
user
story,
language,
to
get
like
really
high-level,
okay,.
A
E
A
E
O
If
you're
someone
who
sends
a
message,
you
have
a
perspective
towards
the
middle,
where,
if
you
someone
who
consumes
the
message
for
the
perspective
towards
the
middle
word,
if
you're
writing
the
middle,
where
you
also
have
a
perspective
and
all
of
those
come
together
in
a
reasonable
term
and
there's
prior
art
for
that
that
people
have
been
coming
to
that
point.
But
we
should
go
and
arrive
at
a
conclusion
from
us
doing.
A
joint
analysis
and
I
think
this
is
a
good
good
place
to
do
this.
A
A
E
A
E
K
Sarah,
are
you
going
to
send
email
did
I
just
know
the
time
or
how
I
even
get.
E
E
A
Cool
in
that
case,
I,
don't
think
we
have
time
to
really
jump
into
anything
deeper.
So
let
me
just
go
through
the
list
of
attendees
and
make
sure
it's
on
roll
call.
You
can
see
who
doesn't
shriek.
Are
you
there.