►
From YouTube: CNCF Storage WG Meeting - 2018-10-24
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
Alex
I'm
just
looking
at
the
they
get
attendees
right
now
because
I
know
about
you,
know:
half
the
call
was
involved
in
the
paper
and
the
other
half
was
another
Clinton
asked
earlier.
If
folks
in
to
take
a
look
at
it,
but
maybe
we
can
probably
turn
it
out
that
way
again
because
I
think
it's
Saad
and
T
Nelson.
Sorry,
what's
your
first
name:
okay,
I'm
you
Toni,
Nelson,
hey
Tony,
hey
glad
you're,
seeing
you
yeah
and
John
great
kind
of
have.
You
guys
had
a
chance
to
look
at
that.
The
way
I
took.
C
C
D
You
know:
block
storage
file,
system,
object,
storage
and
key
value
stores.
Specifically,
we
decided
to
defer
databases
in
general
to
a
later
version
of
the
documents,
primarily
because
databases
was
a
really
large
scope
and
you
know,
could
even
be
a
might
even
marry
the
document
of
its
own
and
also
partly
just
from
a
pragmatic
point
of
view.
From
a
timing
point
of
view
we
just
it
was
it
was
a
bit
of
the
pilot-
was
too
big
to
bite
off
and
just
now,
and
so
so
very
quickly.
D
We
talk
about
the
attributes,
so
we
have
a
section
here
and
the
attributes
we
talk
about
things
like
availability,
scalability,
performance,
consistency,
durability.
Are
we
put
in
a
small
section
near
about
at
instantiation
and
finally
deployment?
We
talk
about
the
layers.
There
are
a
couple
of
small
sections
and
layers
which
which
needs
to
be
fleshed
out
with
the
identified
and
the
province.
D
We
cover
things
like
the
topology
of
the
storage
system
and
the
data
protection
capability,
and
we
talk
about
data
services
like
replication
and
snapshots
and
encryption,
for
example,
and
we
have
a
section
on
the
data
access
interface
so
talking
about
our
how
workloads
actually
interface
with
the
with
the
store
system
and
how
they
actually
consume
storage
active
after
the
storage
system-
and
we
gather
you
know,
block
file
system,
shared
file
system
and
also
object
stores,
key
value
stores.
As
we
said,
theta
betas
were
the
third.
D
We
are
building
at
a
comparison
table
and
trying
to
do
some
work
to
make
this
to
a
pretty
diagram
rather
than
just
stuff
than
just
a
table.
Probably
do
that
in
the
next
couple
of
days,
and
then
we
have
some
further
detail
on
each
of
the
store
types.
So
we
have
a
section
on
block
stores,
another
one
on
file
systems
and
object
stores
and
another
one
on
key
value
stores.
D
We
then
also
talked
about
how
the
storage
is
orchestrated,
so
talking
about
the
different
control
interfaces
between
the
generators
and
the
controlling
of
the
of
a
storage
system,
and
we
discuss
list
some
of
the
interfaces
there,
like
the
main
two
drivers
and
it's
photography
only
blocking
the
Flex
for
human,
obviously
CSI,
and
we
also
trying
to
put
in
some.
We
also
tried
to
cover
orchestration
up
interfaces
for
the
API
component,
so
you
know
how
you
orchestrate
an
object,
store
or
a
database
or
key
value
store,
for
example.
D
Obviously
you
know
the
volume
orchestration
is
probably
more
mature
at
this
stage,
so
so
dr.
Haas,
that
has
more
detail
and
the
API
section
and
then
finally,
we
have
the
appendix
which
has
a
little
blurb
parents
and
the
history
for
the
documents,
mostly
for
just
informational
verses,
and
we
talked
to
parents
coming
here.
Can
we
have
coverage
around
things
that
consensus
protocols
and
consistency
we
which
are
fairly
complex
concepts
which
are
again
poorly
understood
but
often
referred
to
inconsistently
in
different
documentation?
E
A
Yeah
obviously
I'm
somewhat
biased,
because
I
was
kind
of
involved
in
this,
but
but
I
must
say,
I
read
through
you
know,
took
a
long
time
to
piece
all
the
bits
together
and
there
were
multiple
authors
and
a
lot
of
document
restructuring
at
the
last
minute.
But
reading
the
final
draft
I
must
say
it
really
comes
across
as
super
valuable
to
me.
I
I
think
it
I
hope
it
will
be
very
well
received.
A
I
think
it
gives
a
very
good
balanced
view
of
everything
from
a
virtual
point
of
view
and
congratulate
everyone
who
was
involved
because
I
think
the
end
result
is
very
impressive.
Indeed,
I
had
one
question.
Actually
that
only
occurred
to
me
after
I
read
the
final
draft,
which
is
one
thing
we
don't
talk
about,
and
it
is
obviously
a
bit
of
a
contentious
one.
A
So
maybe
we
want
to
avoid
it,
but
I
think
cost
and
pricing
is
a
is
a
pretty
salient
property
of
storage
that
people
take
into
account
when
they
choose
what
to
use
and
I
wonder
I,
don't
think
we
talked
about
it
much.
We
have
that
section
at
the
beginning
about
what
would
we
call
it
provisioning
and
something
but
but
I
think
there's,
maybe
a
bit
more
to
say
around
you
know:
service
storage
services,
like
s3,
are
typically
priced.
A
You
know
with
this
sort
of
structure
per
gigabyte
or
I/o
or
whatever
it
happens
to
be,
whereas
you
know
different
storage
devices
like
storage
servers
and
whatever
are
priced
typically,
this
other
way
and
that
may
play
into
which
of
the
two
you
choose
in
addition
to
you,
know,
performance
and
all
the
other
things
and,
and
some
of
them
are
sort
of
some
of
them
are
more
capex
focused
and
others
are
more
optics
focused.
You
know,
pay
as
you
use
versus
pay
for
a
big
box
and
use
it
anywhere.
D
I
think
having
you
know,
adding
a
little
bit
to
the
deployment
options
section
where
we,
you
know,
we
say
we
discuss
the
differences
between
hardware,
software
and
cloud
services
where
exact
like
I,
think
it's
you
know
it's
it's
worth
pointing
out
across
desert
as
a
factor
there,
because
you
know
hardware
typically
implies
Catholics
on
the
other
end
of
the
spectrum.
Craft
services
typically
provides
a
typically
implying
subscription.
However,
it
is
you
know
it
is.
D
D
B
I
was
kind
of
thinking
about
that,
the
same
way
to
maybe
you
can
generalize
it,
and
you
can
say
you
know
most
expensive
and
structured
data,
storage
for
databases,
media
most
blocks
or
and
tea
vistas
object
or
something
like
that.
But
you
know
we
never
want
anyone
picks
out
a
part
like
it's,
not
all
mysterious,
so
I
think
it's
tough
to
really
get
in
those
details,
and
then
the
other
thing
I
was
thinking
about
is
like.
A
Yeah,
those
are
those
are
definitely
valid
points
just
to
be
clear.
I
wasn't
necessarily
suggesting
that
you
know
we
say:
block
stores
are
cheap,
filesystems
or
anything
like
that.
But
more
is
probably
more
to
do
with
the
software
based
stuff
built
on
off-the-shelf.
Hardware
has
certain
pricing
properties
that
are
different
than
proprietary
handmade.
A
You
know
enterprise
storage
systems
now
I
know
this
is
gonna
get
controversial,
but-
and
maybe
you
know
I-
don't
have
that
the
pricing
details
at
least
off
the
top
of
my
head.
You
know
right
here,
but
but
it
might
be
worth
saying,
they're,
either
comparable
in
price
or
different
in
US
or
you
know
whatever
you
know,
oh
it's,
it's
not
a
technical
decision.
I
think
it
sort
of
inevitably
plays
into
decisions.
A
F
This
is
the
forum
for
that
I'll
call
it
it's
almost
kind
of
a
sales
pitch
right,
I,
think
I,
think
it'd
be
really
valuable
to
you
know,
call
out
the
different
options,
but
it
doesn't
like
trying
to
associate
a
cost
of
each
one
is
is
really
something
that
you
can
actually
do
and
I
don't
think.
It's
necessarily
overly
useful
because
you,
you
don't
know
what
existing
hardware
folks
have
you
don't
know
what
kind
of
contracts
they
have
with
vendors.
F
B
I
could
definitely
like
just
a
job
playing
like
the
devil's
advocate
here
for
sure
and
he's
my
background
from
that
out
the
background
from
EMC
on
my
side
and
I
I
agree
like
from-from,
emcs
perspective
or
even
I.
Think
then
I'll
just
want
I
can't
speak
for
doctor
I
work
for
them
in
this
one,
but
I
think
that
you
know
an
open
source
solution.
B
You
know
you've
added
up
with
the
hardware
and
the
people
it
takes
to
actually
run
it
because
you're
not
getting
it
supported
by
an
enterprise
company
like
the
kasam
that
being
similar,
so
so
the
cost
savings
is
very
much
a
subjective
thing
that
just
like
John
said
you
can
write
a
paper
about
what
that
translates
to
an
organization
depending
on
your
structure.
So.
D
So
how
about
this
I
I
kind
of
agree
with
all
of
those
comments
there
and
I
think
that
trying
to
compare
ranges
or
pluses
and
minuses
imprison
cons
is
probably
not
suitable
for
documents.
However,
on
the
other
hand,
I
think
it's
worth
working
ads
through
developer
who's.
D
Looking
to
compare
costs,
just
maybe
some
basic
things
like
the
differences
between
purchasing
stuff
up
front
versus
fishing
services
and
subscriptions
of
the
client
is
one
of
this
one
and
I
think
it's
probably
also
worth
pointing
out
to
people
that
products
are
generally
priced
according
to
the
attributes
that
they
support.
So,
for
example,
you
know
if
a
product
is
focused
on
capacity
attributes
like
like
an
object's
floor.
D
B
I,
like
that
I
think
generalizing
at
that
levels
will
be
useful
like
if
the
audience
is
the
developer
and
it's
a
nation
I
think
that
makes
sense,
and
you
know
the
the
common
unite
before
you
know.
How
can
we
break
it
up?
We
could
say
you
know,
there's
a
traditional
mode
of
you
know
the
capex
purchases.
You
buy
everything
upfront,
you
know,
you
run
it
yourself,
you
get
it
supported.
B
There's
the
the
other
model,
which
is
the
service
based
model,
and
you
know
that's
different,
corrects
reasons
and
then
maybe
you
can
even
do
something
in
the
future
for
the
next
white
paper,
which
is
and
there's
a
leveraging
cloud
main
attack
to
run
something
services,
and
maybe
that's
a
better
place
to
be.
You
notice,
but
maybe
there's
three
models
that
we
we
talked
about.
There.
A
Yeah
I
I'm
I,
like
what
you
say
that
looks
as
well
and-
and
I
think
I
think
not
mentioning
cost
as
a
consideration
when
comparing
storage
alternatives
is
not
the
right
thing
to
do
so,
yeah
just
adding.
But
what
is
a
factor,
and
these
are
the
kinds
of
things
you
probably
want
to
think
about:
capex
versus
of
x
per
gigabyte
versus
their
I
off,
etc,
and
leave
it
at
that.
D
Now,
just
in
terms
of
logistics
and
timing,
so
there
are,
there
are
a
couple
of
sessions
that
I
mean
to
be
filled
in.
We
have
people
nominated
for
them,
but
of
course
we
are
also
going
to
have
to
take
on
board
any
feedback.
That's
presented.
We
were
tentatively
looking
to
Zen's
I
believe
next.
Is
it
next
Tuesday.
A
Through
the
EOC,
I
actually
dropped
the
TSE,
an
email
yesterday
to
ask
them
if
they
want
us
to
present
the
stuff
or
if
they
just
want
to
read
the
document
and
I
haven't
looked
at
my
inbox
yet,
but
I
have
I'm
not
aware
of
any
replies
to
that.
Yet
I
think,
let's
give
it
a
while
there's,
certainly
no
urgency
to
talk
about
there.
People
have
not
been
handing
me,
so,
let's
see
what
they
think.
I
think.
A
What
we
do
need
to
do
is
talk
about
it
at
the
at
the
Q,
chronic
China
event,
three
weeks
time:
I
guess
it
is
so
as
long
as
as
long
as
by
the
time
you
stand
up
there,
there
are
no,
you
know
violent
objections
to
our
documents.
I
think
we're
good
for
that
and
I
have
as
I
searched
the
document
to
the
TRC.
They
can
read
it
if
they
want
to.
They
can
reply
to
my
email
if
they
want
us
to
present
it
to
them
in
a
summarised
form.
A
So,
let's
just
give
it
a
few
days.
I
think
what
I
would
like
to
do
is
make
sure
that
that
at
least
some
significant
number
of
people
outside
of
the
authors
of
this
paper
show
visible
evidence
of
actually
having
read
it
to
end
and
provided
see
feedback.
So
Johnny
thanks
for
yours
here
and
if
we
can
get
more
I,
think
that
would
be
great
I
wouldn't
wanted
to
feel
like
this
document
was
purely
the
opinion
of
the
five
authors
and
not
an
opinion
shared
by
anyone
else.
A
I
personally,
I
would
give
it
another
few
days
for
people
to
see
your
email
that
you
sent
out
and
we've
got
this
forum.
I've
announced
it.
We
have
a
TAC
meeting
next
Tuesday
Wednesday
I
believe
Monday
may
be
so
I
can
I
can
verbally
tell
everyone
on
that
call.
So
I
want
to
open
it
up
to
two
broad
feedback
just
yet
until
we
had
let
the
working
group,
you
know,
look
at
it
and
comment
just
because
you
can
become
a
mess
in
become
inundated
with
too
much
feedback
and
not
be
able
to
process
it.
A
But
if,
by
next
week
we
are
not
overwhelmed
with
feedback
from
the
working
group
itself,
then
I
can
announce
it
at
the
TOC
meeting,
which
just
to
be
clear,
includes
TRC
members,
but
also
typically
around
fifty
to
a
hundred
other
people,
and
so
I
think
that'll
be
an
effective
way
of
getting
more
reviewers.
If
we
want
more
okay.
D
A
Good
and
then,
hopefully
again,
cube
Khan
will
add
yet
more
interested
parties
we're
on
the
agenda
and
people
will
probably
sign
up
to
come
to
that.
So
come
three
to
four
weeks
time:
I'm
guessing
you'll
have
more
than
enough
feedback,
and
then
we
can,
as
I
think
the
plan
was
to
sort
of
declare
it
published
and
final
by
cube
con
Seattle,
which
is
about
a
month
after
you
come
yeah
I,
think
that
sounds
reasonable.
They
say
what
about
this.
D
A
I
think
I
think
the
conference
is
on
the
13th
of
November.
If
I
remember
correctly,
yeah
I
mean
within
a
week
I
think
the
slides
are
probably
supposed
to
be
uploaded
already,
and
we
can.
We
can
put
a
wireframe
slide
upload
there
I,
don't
think
they
get
made
public
I
think
they're
just
trying
to
encourage
people
to
make
sure
they
have
actually
prepared.
This
live
their
presentations
more
than
the
night
before,
but
we
can
sit
me
amend
the
slides
up
until
not
long
before
the
13th.
Let's
maybe
have
a
draft
in
the
next
week.
A
Think
I
stand
corrected,
but
I
think
I
sent
you
that
a
couple
of
weeks
ago,
but
I
can
take
it
out
again.
I,
don't
think
there
is
a
template,
but
there
is
a
CN
CF
github
repo,
that's
got
all
the
logos
and
it's
got
some
example
slide
decks
and
stuff
like
that.
I
think
that's
his
closest.
We
get
actual
coupon
template
today.
A
G
A
D
A
B
D
G
D
G
A
You
know
one
thing:
I've
learned
from
the
cube
cons
is
that
the
audience
every
year,
the
actual
people
attending
is
growing
so
fast
that
the
percentage
of
people
who've
never
been
to
a
cube
come
before
is
pretty
high,
and
this
one
being
the
first
one
in
China
is
gonna,
be
even
more
than
even
more
so
than
usual.
So
yeah
don't
be
too
shy
to
present
material.
That
is
quite
similar
to
what's
happened
in
the
past.
A
A
Clinton
only
really
got
involved
in
this
group
in
the
last
few
months
and
I
don't
have
full
visibility
into
what
other
things
this
group
has
done
before
I
joined.
So
we
might,
you
know,
we've
been
kind
of
heads
down
getting
this
document
published
recently,
but
we
may
want
to
reincorporate
some
of
the
other
things
that
this
group
was
doing
before
we
dived
into
the
dock.
I
know
you
were
you
had
some
presentations
from
various
technology
groups
and
vendors
and
whatever
I
don't
know
how
well
received
that
was
if
it
was
use
useful
use
of
time.
A
If
we
want
to
get
that
going
again
and
with
any
projects
that
we
you
know,
if
we
identify,
you
know
holes
in
the
landscape
that
we
think
we
want
to
tackle.
I,
don't
know
if
those
kind
of
discussions
have
happened
before
with
scoping.
Do
we
actually
have
a
like
a
charter
for
this
working
group?
This
is
what
we
do,
and
this
is
what
we
don't
do.
I
think.
B
B
When
we
look
at
that
deck
that
was
posted
by
Alex,
we
do
have
on
there
slide
number
six,
which
is
what
can
we
kind
of
interpreted
as
our
mandate
and
the
three
things
were:
data
clarify
terminology
landscape
to
look
at
how
the
components
are
used
in
clouds
and
compare
and
contrast
properties
of
storage
such
as
availability,
durability,
performance,
etc
and
I
think
that
kind
of
covers
like
building
the
white
paper,
but
I'm
definitely
all
ears
to
hear
from
folks.
You
know
what
what
they
will
see
is
I.
D
So
quickly,
just
just
for
context,
one
of
the
one
of
the
things
the
societal
I
think
there
was
a
lot
of
debate
at
the
tail
end
of
last
year
and
one
of
the
things
I
recall
on
one
of
the
talk
meetings
was
that
there
was
kind
of
a
general
consensus
that
working
groups
shouldn't
exist
for
the
sake
of
existing,
but
there
exist
because
they're
tasked
to
do
things
by
the
book,
but
the
TOC,
and
you
know
whether
that's,
for
example,
reviewing
a
project
or
writing
content.
Or
you
know
what
whatever
that
thing
might
be.
D
A
I
think
I
think
there's
a
sort
of
a
bi-directional
aspect
to
this,
so
I
think.
On
the
one
hand,
the
tools
me
wants
to
know
what's
going
on
in
storage
world
and
find
out
where
the
problems
are
and
find
out,
you
know
all
that
kind
of
stuff
and
when
I
say
the
tears,
I
think
I'm
making
a
requirements
of
the
tears
yeah
I'm,
not
aware
of
anyone
having
anyone
else.
Having
said,
we
want
the
storage
working
group
to
do
this.
A
I
believe
this
working
group
was
kind
of
spawned
of
its
own
accord,
so
I'm
not
sure
that
the
TLC
actually
requested
that
a
storage
working
group
be
put
together
an
answer:
question
XYZ
it's
more
than
it
itself
formed
and
then
the
TRC
was
saying
well.
What
is
this
working
group
actually
doing?
What
is
their
scope?
A
What
are
they
planned
to
do
and
that's
where
that's
where
the
conversation
started,
so
I'm
I
think
we
can
propose
what
we
want
to
do
and
what
we
want
to
provide
to
the
TRC
and
to
the
CN
CF
in
general,
and
as
long
as
the
TF
that
CN
CF
does
not
object
to
that.
I.
Think
we're
good
well
tip
off
the
top
of
my
head.
He
means
that
I
would
imagine
that
would
be
very
well
received,
or
so
the
department
is
a
good
starting
point.
A
The
other
thing
that
I
the
leaves
or
people
are
very
interested
in
and
which
we
didn't
actually
cover
very
well
in
this
document
in
any
detail,
is
because
how
are
these
things
actually
used?
So
one
thing
we
could
do
is
publish
case.
Studies
of
you
know
the
details
of
how
particular
use
cases
of
youth
get
guessed
I'm,
just
thinking
of
someone
like
gitlab
just
to
take
something
off
the
top
of
my
head.
So
how
does
get
lab
do
their
storage
behind
the
scenes
and
what
are
the
problems?
They've
had
and
I
know.
A
A
Now
that
could
be
somewhat
contentious
clearly
would
not
want
the
user
to
stand
up
and
say
we
hate
cloud
provider,
X
Z
and
we
love
cloud
provider
a
while,
but
I
think
this
is
a
genuine
interest
in
understanding
how
some
of
these
things
are
actually
done
behind
the
scenes
and
some
companies
will
be
prepared
to
you
know
talk
about
that.
I
would
imagine.
Netflix
is
another
example,
which
is
a
big,
high-profile
thing,
where
people
must
wonder
like
how
the
hell
did
they
stall
these
movies
and
metadata,
and
are
they
prepared
to
tell
us?
B
I'm
wondering
if
you
know
what
we
I
think
we've
got
a
good
outcome
of.
You
know
the
working
group
for
creating
this
document
and
Quinta
to
rewind
Lee.
The
TOC
did
ask
to
form
it
and
that's
what
been
kind
of
stuffed
up
and
said.
Okay,
you
know
I'll
leave
it
for
the
TSE
report
pack,
so
I
do
believe
it
was
like
okay,
but
you
know
I
think
the
the
tangible
outcome
of
it
has
been
wild,
like
you
know,
bringing
folks
together
at
one
point
we
had
30
or
30
people
are
so
like
that
were
joining.
B
Think
we've
got
a
little
bit
of
tailing
off
of
attendance
at
this
point,
but
my
my
my
thoughts
are
kind
of
like
in
terms
of
timing
and
where
we're
at,
like
within
the
conference
season
in
the
year
like
this
seems
like
a
house
I'm
a
working
group,
and
it's
something
that
I'm
kind
of
just
see
like
how
it
goes
like.
What's
the
feedback
from
it,
does
the
CNC
go
from
TOC
find
this
really
useful?
It
was
this
good
use
of
our
time,
and
maybe
it's
in
considering.
We
have
coupons
coming
up
and
cetera.
B
A
Yeah,
that
sounds
like
a
perfectly
reasonable
approach,
so
I'll
tell
the
TOC
we're
basically
calling
this
task
done
and
based
on
the
hub,
based
on
the
feedback
to
the
document.
We
will
decide
whether
we
want
to
reconstitute
in
the
new
year
for
the
next
step,
when
I
would
propose
that
in
the
next
step
we
come
forward
and
say
these
based
on
the
feedback
we've
received.
We
think
this.
A
These
three
things
would
be
the
next
logical
steps
for
this
working
group
and
we're
essentially
reforming
to
do
item
number
one
on
that
group
list,
or
maybe
two
or
three
in
parallel
I'm,
not
sure
that
depends
how
it
works
out.
I
think
that
totally
reasonable
I
think
the
TOC
would
welcome
proposals
from
us
as
to
what
we
think
we
should
do.
You
know,
rather
than
us
saying
what
do
you
want
us
to
do,
because
I
think
we're
less
likely
to
get
useful
feedback
from
that
right
instructions?
Oh.
D
D
About
that
we
will
talk
to
practicing,
and
one
thing
that
might
actually
be
really
useful
is
to
actually
you
know
called
the
audience
when
we
do
these
sessions
of
keep
done
assume
what
I
don't
know
if
we're
gonna
be
good
or
not,
I
don't
know
if
we're
gonna
be
ready
enough
to
give
them
a
couple
of
options,
but
maybe
ask
them
what
they
wanted
to
see.
Next,
what
they
see
their
pain
points
are
or
what
their
decision
points
or
issues.
You
know
they
might
say
actually
well.
B
D
So
so
maybe
we
maybe
we
ask
and
see
this
thing
would
comes
back
and
but
I'm
hoping
that
there
will
be
a
few
things
that
might
be.
You
know
immediate
follow-up
directly
from
this
document,
so
so
somebody
might
say:
well,
okay,
this
is
grains,
but
actually
I.
Don't
think
you
captured
this
area
and
we
might
have
a
separate
document
or
we
might
have
a
separate
discussion
or
some
other
project
presentations
or
whatever
very
related
to
that,
for
example,
hey.
E
D
E
A
This
forum
would
be
an
alternative,
so
so
they're
welcome
to
come
to
this
meeting
and
and
provide
I
mean
first
prize
is
written
comments
in
the
document,
but
sometimes
comments
are
more
usefully
presented
verbally
to
people.
Saying
look.
The
thing
I
didn't
quite
know
where
to
put
this,
but
my
feeling
is
XYZ
and
that's
also
fine.
Okay,.
B
We
should
make
that
no
I'm,
like
in
terms
of
the
other,
if
you
said
that
your
email
I'll,
absolutely
think,
we've
got
three
of
these
sessions
leading
up
to
cubic
on,
and
you
know,
if
you
have
your
comments
to
come
to
these
sessions,
to
verbalize
them.
I
totally
agree.
I,
think
that
that's
probably
a
better
forum
for
some
skills.
A
A
Solicit
audience
input
as
to
what
so,
first
of
all
make
them
aware
of
the
document
and
tell
them.
This
is
basically
certainly
by
Seattle.
This
is
kind
of
delivered
and
then
solicit
feedback
on
whether
and
if
and
what
sort
of
next
steps
they
would
like
to
working
you
to
take
and
have
in
the
wings
a
set
of
proposals,
just
I
mean,
rather
than
we
end
up
with
a
roomful
of
goldfish,
not
able
to.