►
From YouTube: WG Platforms - Maturity Model Project Meeting
Description
TAG web site: https://tag-app-delivery.cncf.io/
TAG Slack channel: https://cloud-native.slack.com/archives/CL3SL0CP5
TAG git repo: https://github.com/cncf/tag-app-delivery
TAG meeting notes: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit
B
C
C
C
B
B
C
B
B
B
A
B
Cool
it's.
Basically,
it
was
a
thing
that
we
started
kicking
around
and
actually
got
a
ton
more
interest
than
we
thought
it
would
like.
It
was
sort
of
one
of
these
things
that
we
were
thinking
about
like
oh,
it's
a
model
that
we've
seen
go
evil
I
used
to
be
a
consultant
I'm,
fully
aware
of
where
this
can
go
badly.
C
B
But
at
the
same
time
like
there
are
I
think
opportunities
to
to
make
good.
For
you
know,
there's
a
set
set
up
that
model
for
success
in
a
way
that,
like
someone's
gonna,
do
it.
If
we
can
set
it
up
with
the
best
possible
intentions,
then
like,
hopefully
that
means
that
we
reduce
the
risk
of
evil.
So
we
started
kind
of
doing
that
and
the
the
conversations
in
with
like
the
original
reviewers
are
all
much
more
like
Nuance
than
like.
Stop
cancel.
B
Don't
do
this
kind
of
commentary,
but
there
were
some
big
questions
and
that's
sort
of
what
I'm
why
I
was
hoping
to
do
a
synchronous
call
like
in
general,
the
working
group
works
asynchronously.
We
can
do
it
through
comments
in
the
Google
Doc,
but
I
was
hoping
to
do
a
synchronous
call
because
there's
like
I,
think
anybody
who
hears
the
term
maturity
model
has
a
reaction
to
it
and
I.
B
If
you
and
we'll
give
it
a
few
more
minutes,
if
I'm
I,
I
can't
say,
I
have
High
Hopes
at
this
stage,
so
I'm
out
of
curiosity
was
there.
What
was
your
first
reaction
to
the
model
in
the
sense
of
the
the
chances
it
would
be
used
for
good
versus
the
chances
of
ease
for
evil,
and
if
it
was
the
right
structure-
and
you
know,
is
it
something
that
is
ready
to
be
iterated
on
or
is
there
some
big
questions
that
you
all
still
have
in
relation
to
it.
C
C
D
And
we
don't
have
to
describe
you
know
in
in
in
in
in
such
exhausting
detail
the
the
nuances
of
platform
engineering,
but
I
I
have
been
broken
down
the
categories
and
sort
of
simmered,
with
my
own
thoughts
about
gaps
that
there
might
be,
or
anything
like
that,
yet
so
I'm
kind
of
just
green
coming
into
it.
So.
B
B
You
really
should
be
doing
through
either
comments
on
a
GitHub
issue
or
comments
on
a
Google
doc,
because
that's
what
allows
for
the
like
collaboration
on
those
thoughts
and
like
the
deeper
response,
rather
than
it
just
being
the
loudest
person
who
happens
to
be
able
to
make
a
like
time
zone.
Specific
phone
call
right
like
that.
We
don't
want
to
be
the
like
deciding
factor
of
what
goes
into
this
paper.
B
A
A
Yeah
I
think
like
and
just
for
our
own
selfish
me
and
John,
specifically
our
use
case
like
had
we
had
something
like
this
like
if
you
were
on
the
clock,
what
was
it
like,
18
months
ago,
two
years
ago,
when
we
were
at
the
last
organization
that
you
know
we
got
to
adopt
Cooper
so
like
we
were,
that
was
our
full-time
job.
Taking
something
like
this
to
leadership.
To
be
like
look
we're.
A
We
were
preaching
all
of
these
same
bullet
items
to
them,
but
there
was
no
real
backing
aside
from
our
own
work
experience,
and
so
had
we
been
able
to
go
to
the
director
that
you
know
ended
up
giving
us
the
green
light
and
say
look
there's
like
a
whole
group.
That
literally
agrees
with
us.
This
isn't
just
like
us
walking
into
your
door
and
saying
hey.
We
should
go.
A
Do
this
Cavalier
initiative
because
kubernetes
is
great
like
they
were
trying
to
adopt
it
for
years
they
were
struggling,
they
didn't
have
the
right
paths
forward
and
having
this
type
of
thing,
I
think
would
have
really
helped
them
not
have
as
much
pushback
initially
because,
like
even
with
the
team
of
eight
that
we
were
on
like
John
and
I
basically
broke
off
and
they
were
like
okay.
Well,
you
two
show
us
what
you
can
do
for
a
little
bit
and
then
we'll
see
how
much
more
buy-in,
six
months
later,
they're
like
oh
wow.
A
E
E
B
C
B
I
was
I,
think
I,
don't
want
to
repeat
if
you've
heard,
but
basically
I
would
love
to
to
gain
confidence
that
we
can
work
asynchronously.
That's
the
goal
of
this
call,
so
the
goal
of
this
call
is
not
to
set
up
like
a
need
for
us
to
be
on
calls
every
week
for
us
to
make
this
better,
but
instead
for
us
to
be
able
to
raise
any
questions,
concerns
that
we
feel
like
would
be
better
sorted
like
upfront,
with
a
a
big
kind
of
discussion.
B
C
D
E
I'll
just
give
him
one
minute:
introduction
by
myself
I'm.
My
name
is
taffy
dwek
I'm
based
in
London
from
AWS
working
in
AWS
for
the
two
past
two
and
a
half
years
backgrounds,
the
devops
platform
engineer
a
developer,
even
Mainframe.
So
this
is
my
kind
of
background
today,
I'm
working
with
customers
around
containers,
so
in
my
job,
I'm
principal
Solutions,
architect
for
containers
and
I
I
see
those
customers,
like
you,
I,
think,
John
and
Jared.
E
E
B
Yeah
I
think
that's
a
good
point
setting
expectations
about
the
kind
of
goals
of
pace
of
movement
on
this.
So
we
my
plan,
so
my
background
is
that
I
helped
with
the
white
paper
as
like
just
similar
to
how
you
three
are
introducing
yourselves
like
I
sort
of
got
excited
about
things
about
when
I
was
in
Detroit
joined.
Some
calls
got
involved
right,
so
I
was
kind
of
there
as
a
attendee
and
a
participant,
but
not
as
a
leader.
B
This
is
going
to
be
the
first
thing,
I
attempt
to
try
and
Corral
and
and
I
mean
that
in
in
that
way,
it's
not
mine.
It's
not
mine,
to
write.
It's
not
mine
to
own
I
purely
want
to
try
and
encourage
the
right
humans
to
to
get
involved
and
to
feel
empowered
to
make
the
changes
and
all
that
so
as
for
like
get
time
scales
and
things
like
that,
I
witnessed
the
white
paper
go
from
a
similar
level
of
like
first
draft
through
to
publication
between
the
two
kubecons
and
I.
B
Think
I
have
a
soft
goal
of
that
happening
with
the
maturity
model.
It's
not
a
hard
goal.
If
we
find
ourselves
not
getting
the
right
level
of
participation,
because
summer
holidays
are
hard
or
because
whatever
then
we
then
we
hold
off,
and
we
make
sure
that
the
document
gets
the
right
level
of
participation,
but
so
we
were
kind
of
working
back.
B
That
sort
of
means
that
we
should
be
in
like
heavy
kind
of
asynchronous
comment,
based
kind
of
conversation
over
the
next
kind
of
two
months
or
so,
and
then
we
should
start
to
kind
of
narrow
in
on
some
of
those
comments,
make
some
decisions
as
a
group
and
get
to
the
point
where
we
can
do
final
reviews.
Ideally
I,
think
you've
gone
this
in
Chicago's
November
this
year,
so
we
need
to
be
done.
Sort
of
by
end
of
September,
so
kind
of
school
starts
back
up.
We
start
doing
the
narrow
in
kind
of
thing.
B
So
yes,
I
think
it's
also
worth
calling
out
that
like
I
think
we,
you
know,
you
all
have
mentioned
your
vendor
backgrounds,
either
vendor
background
as
well.
I
think
that
the
key
you've
also
mentioned
the
community
side
like
the
key
is,
is
that
this
is
a
Community
Driven
thing.
We
can
all
be
vendors.
We
can
all
have
our
tools
that
we
think
help
people
achieve
maturity
while
like
collaborating
and
getting
shared
language
on
what
maturity
means.
B
I
think
it
was
Alex
who's
part
of
the
tag
leadership,
yeah
Alex,
Jones
that
he
thought
there's
a
risk
that,
with
these
kinds
of
things
you
can
end
up
with
like
a
king
making
so
like
platform.
X
is
more
mature
than
y
and
I.
Think
that's
particularly
dangerous
when
there
are
vendors
selling
themselves
as
a
platform
versus
like
parts
of
your
platform
or
whatever
and
I.
Think
that's
something
that
we
need
to
like.
B
Just
be
aware
of
like
self-aware
as
well
as
like
aware
of
calling
each
other
out
like
I
did
like
definitely
as
a
part
of
the
white
paper.
One
of
the
conversations
was
everyone
tried
to
get
their
tool
to
be
like
the
top
of
the
list
and
and
the
images.
This
is
not
going
to
mention
tools,
there's
going
to
be
like
that's
one
thing
that
I
feel
like.
B
It
has
to
do
with
the
outcomes
you
achieve
and
there
should
be
multiple
tools
that
you
can
achieve
these
outcomes
with
and
if
there
aren't
that's
a
problem
with
maybe
how
we're
describing
it
and
and
so
forth,
so
yeah
so
I
think
that
that's
something
that
if
there's
other
concerns
or
other
ideas
there
and
then
I've
put
at
the
top
of
this
document
case.
It's
not
on
other
people's
screens.
C
B
One
question
that
we
need
to
answer
is
like
so
I'm
gonna
be
meeting
up
with
actually
since
Shashi
since
you're
in
London
I,
don't
know
if
you're
up
for
it
but
I'm
getting
a
pint
tomorrow
night
with
someone
else
in
London
Simon,
who
is
a
part
of
the
creation
of
the
cloud
cloud
native
maturity
model
and
we're
just
gonna
talk
about
his
experiences
and
how
he
wants
to
apply
it.
So
if
you're
ever
at
all
near
burrow,
I
can
ping
you
and
you
can
come,
join
us
and
yeah.
B
There
but
yeah
so
basically
there's
a
couple
different
formats.
People
have
used
I
defaulted
to
the
same
one
that
we
use
for
the
white
paper,
which
is
to
use
Google
Docs
to
start
with,
with
the
feeling
that,
like
it's,
probably
quite
up
for
flux
right
now,
and
we
kind
of
want
a
lot
of
people
to
be
able
to
make
comments
and
suggestions
and
and
things,
and
that
that
may
be
the
easiest
way
to
do.
That.
We've
also
been
suggested
that
the
git
Ops
paper
white
paper
operated
differently.
B
E
B
B
C
F
B
Yeah
I
don't
want
to
make
any
assumptions.
We've
basically
been
talking
about
how
we're
all
coming
in
this
with
enthusiasm,
but
not
a
lot
of
research
and
so
I.
Don't
think
it's
particularly
effective
to
have
a
conversation
about
like
the
different
model
structures
so
like
I
realize
I
should
probably
put
the
GitHub
issue
into
this
doc,
so
you
all
can
see
it,
but
it's
something
that
I
would
love
for
you
all
to
to
have
a
think
on.
B
As
I
say,
it's
get
issue
there
you
go
and
it's
in
there
in
that
GitHub
and
it
can
yeah.
You
can
see
what
some
of
the
big
big
questions
are
and
and
should
be
discussed.
But
what
is
your?
What
is
your
background?
What
makes
you
both
interested
and
also,
if
you
have
any
concerns
about
the
maturity
model,
wanna
work
on.
C
F
F
B
Not
I
think
look
what
I'm,
what
I'm
realizing
so
I
put
together.
This
call
just
to
reiterate,
I
put
this
call
in
order
to
give
a
forum
for
big
questions
that
may
be
hard
to
put
into
comments
and
I'm
going
to
continue
to
make
a
forum
available
whenever
those
those
arise,
because
I
think
that
there
are
reasons
to
do
synchronous
phone
calls
with
teams
I,
don't
think
that
every
piece
of
work
requires
it
and
that's
not
my
intention
to
introduce,
as
like,
a
a
lock
hold
on
the
way
we
work.
B
But
there
were
some
big
questions
that
I
wanted
to
give
a
forum
to
and
I,
and
that's
why
we're
here
it
doesn't
seem
like
the
group.
That's
here
is
particularly
concerned,
which
is
awesome
to
hear.
Like
you
know,
people
feel
like
there's
lots
of
things
we
want
to
talk
about,
but
nothing
that's
like
should
make
us
concerned
about
investing
time
into
this
process
right.
B
But
my
feeling
at
this
stage
is
that
we
have
a
draft
of
a
maturity
model
that
has
some
content
that
it
has
been
debated
and
and
kind
of.
A
a
version
has
been
cut
to
make
sure
that
we
go
as
wide
as
possible
with
input
and-
and
this
is
where
we're
at
and
I
would
love
to
encourage.
All
of
you
all
and
anyone
you
respect
and
and
work
with
in
the
industry
to
make
comments
and
make
suggestions
and
like
start
to
take
ownership
over
this
and
and
right
now,
I'm.
B
The
only
person
who
can
edit
the
documents
you'd
have
to
do
it
in
suggest
mode,
but
I'd
love
to.
If
you
all
have
a
think-
and
you
all
have
a
review-
and
you
feel
a
level
of
enthusiasm
about
this
I'd
love
to
make
more
people-
editors
I-
don't
think
we
can
do
open
edit
it'll
be
open,
suggest
right,
it's
globally
available
to
be
suggested
on
and
commented,
but
I
think
ownership
over
like
kind
of
keeping
awareness
over
where
the
changes
are
coming
from,
and
things
like
that
would
be
helpful.
B
So
but
I'd
love
to
open
that
to
wider
than
just
me
and
and
make
sure
that
there's
a
breath
of
people
there
so
yeah
so
I
guess
maybe
I'll
just
walk
through
really
quick.
It
will
probably
be
off
the
call
in
30
minutes
right,
there's
no
point
in
wasting
people's
time,
but
just
to
walk
through
some
of
the
big
questions.
As
I
said,
the
the
enthusiasm
for
this
document
is
to
be
able
to
help
people
be
more
tangible
about
the
things
that
are
in
the
white
paper.
B
There
are
pros
and
cons
to
this,
because
we
have
a
risk
of
this
King
maker
idea.
This
idea
that,
like
some
people,
are
bad
and
some
people
are
good,
which
is
not
the
intention
of
this
paper
at
all,
and
so
we
have
to
keep
an
eye
on
that.
Other
models
have
been
identified.
There's
links
to
them
capability,
fluency,
instead
of
the
maturity
model.
So
if
people
feel
like
they
feel
really
attracted
to
one
of
those
models,
better,
that's
a
thing.
We
can
evolve
this
towards
right.
B
I.
Think
one
of
the
big
questions
that
we
should
talk
about
is
so
one
of
the
very
big
pieces
of
feedback
was
that
one
of
the
dangers
of
maturity
models
is
that,
like
their
structure
and
you
kind
of
force,
the
content
into
that
structure
and
one
of
the
pieces
in
particular
where
some
one
of
the
reviewers
felt
like
we
were
doing,
that
is
having
four
levels
of
maturity
for
every
single
section
and
whether
or
not
those
four
levels
should
be
like
connected
in
some
way
across.
B
Is
that
we're
very
intentionally
just
to
reiterate
staying
one
level
more
tangible
than
the
white
paper,
but
not
to
the
point
of
solutionizing,
so
there
will
be
additional
work
done.
There
are
people
who
are
passionate
about
creating
there's
like
currently
work
being
done
on
reference
architectures
for
platforms.
There's
currently
work
people
being
passionate
about
working
on
things,
like
example,
like
workshops
to
run
about
your
platform
and
things
that
are
are
very,
like
here's
a
way
to
do
something.
B
B
D
I'll
just
comment
that
I'm
I
I
agree
with
the
format
of
having
sync
video
like
being
able
to
hop
in
a
zoom
and
talk
through
nuanced
details.
I
think
is
going
to
be
really
valuable.
I,
don't
know
how
regularly
we're
gonna
engage
deeply,
but
when
it'll
happen
have
having
the
ability
to
just
kind
of
chat
and
talk
through
nuanced
details
is
super
valuable
outside
of
comments.
D
So
I
really
encourage
that
to
keep
going.
I
I
showed
up,
like
I,
said
a
little
under
prepared
on
this
round,
but
I'm
looking
forward
to
diving
in
a
little
bit
deeper
and
having
some
more,
you
know
intelligent
thoughts
on
the
on
the
topic
by
the
by
the
time
we
Circle
background
so
and
also
wanted
to
call
out
that
I
think
the
choice
of
leaving
vendors
out
is
enormous
from
a
from
the
standpoint
of
we're
very
vendor
agnostic
in
our
heart.
D
B
B
If
we
can
all
be
speaking
the
same
language,
so
our
customers
can
genuinely
make
the
best
decision
for
themselves
across
vendors,
we're
in
a
really
good
spot,
plus
I
think
it'll
challenge
all
of
us
to
to
level
up
because
we're
no
longer
winning
on
marketing
we're
winning
on
like
actual
like
outcomes,
and
so
please
pull
in
other
like
this
is
not
when
I
say
vendor
agnostic.
It's
not
a
I'm,
not
shunning
people
for
being
vendors.
B
E
Question
from
my
side,
like
what
I've
seen,
seven
never
wrote
one,
but
since
I've
seen
several
maturity
models
like
do
we,
as
in
the
CNC
F1,
for
example,
like
the
the
the
general
one
which
goes
over
it,
haven't
really
dived
deep
into
that.
But,
like
you
know,
seen
the
the
four
like
four
pillars
like
you
know,
it
was
either
of
our
own,
for
example
the
world
architected
framework,
which
has
its
own
pillars,
and
we
know
when
we
write.
You
know
these
kind
of
documents.
E
B
B
The
other
question
about
the
format
is
I
think
something
that
this
is
where
I
think
we
have
the
opportunity
to
challenge
the
existing
format.
So
the
existing
format
has
a
bit
of
an
intro
as
well
as
a
set
of
characteristics,
and
this
juristics
are
then
drop
separated
into
four
different
levels
of
maturity
with
one
being
you
know,
a
level
which
is
you're
doing
something,
but
maybe
it's
a
bit
under
powered
and
all
the
way
up
to
four
being
that
you're
kind
of
at
the
the
like
most
mature
level.
B
We
know
of
you're
getting
the
most
value
from
your
platform
that
you
can
hope
for.
All
of
that
is
Up
For
Debate,
but
there
is
a
I
would
say
that
there
is
a
proposed
format
in
the
document,
and
so
you
can
see
that
document
that
Google
doc
is
in
the
git
is
in
the
GitHub
issue
and
I
will
add
it
here.
Current.
B
B
Yeah
here
I'll
add
it
to
the
zoom
as
well:
oops
I'll
end
the
zoom
as
well
the
I
just
added
to
the
Google
Doc.
That's
for
this
meeting.
It's
also
in
the
GitHub
issue.
Around
the
maturity
model.
There
is
a
basically
a
Google
doc
that
has
a
really
complete
like
draft
maturity
model.
The
idea
behind
it
is
that
it's
easier
to
Challenge
and
evolve
a
straw
man
than
to
trying
like
as
a
group
than
to
try
and
come
up
with
something
from
scratch.
B
E
So
going
forward,
we
we
like
looking
what
what
is
the
next
step
from
our
side
like
do
we
need
to
read
this
and
come
prepare
for
next
one?
Do
we
need
to
read
this
and
comment
on
this,
and
will
this
be
the
working
dog
or
you
will
you
create
like
another
one
where
we
can
comment
and
start
proposing
or
just
yeah.
B
So
yes,
so
this
is
the
document,
make
comments
and
don't
just
make
comments,
make
suggestions
so
one
of
the
most
effective
ways
I've
seen
people
work
with
this
with
the
white
paper,
is
to
make
a
suggestion
and
then
add
a
comment
as
to
why
they
were
doing
the
suggestion
similar
to
code
comments.
Don't
comment
what
you
did
comment?
B
Why
you
did
it
so
that
people
can
understand
like
the
intention
of
your
change,
because
sometimes
people
will
disagree
with
what
words
you
chose,
but
not
with
the
intention
of
your
change
and
then
you
can
talk
about
the
word
smithing
of
that
more
effectively,
so
yeah.
So
please.
This
is
the
the
document.
Please
make
comments.
Please
make
suggestions
there.
E
E
B
C
F
Yeah,
this
was
great
context.
I
appreciate
you
kind
of
just
like
bring
us
all
up
to
speed,
I
think
the
last
thing
that
would
help
as
I'm
kind
of
trying
to
understand.
So
it
seems
like
there's
a
compilation
of
white
papers
that
are
being
built,
obviously
the
one
that
we
seem
to
be
referencing.
Quite
a
bit
is
the
platform
white
paper
great
paper,
and
then
this
is
kind
of
adding
on
getting
more
context
of
for
that
other
white
paper
and
so
I'm
just
kind
of
curious.
F
B
Parts
than
I
can
I
could
keep
track
of,
but
the
platform
working
group
specifically
the
white
paper.
We
have
considered
a
little
bit
of
like
the
Cornerstone
of
the
group,
and
we
realize
that
that
is
aspirational
and
high
level,
and
now
the
goal
is
to
like
make
this
a
bit
more
tangible
and
and
and
and
a
bit
deeper
Dives
right.
It's
quite
a
broad
look
at
platform,
but
what
does
it
actually
mean
to
provide
the
capability
of
you
know
reliab
of
compute
right
like
what
does
that
like?
B
B
This
maturity
model
is
to
make
sure
that
the
language
builds
off
of
the
white
paper
or
intentionally
diverges,
but
right
now,
I
think
it's
unintentionally
diverged
and
I
think
what
we
want
to
do
is
create
is
to
build
off
of
that
shared
language,
sure
that
people
are
seeing
a
thread
from
the
highest
level
white
paper
down
through
the
more
tangible
maturity
model
down
through
the
more
tan,
even
more
tangible,
like
specific
exemplars.
So
but
yeah
I,
don't
know
if
that
quite
answers.
F
B
B
All
good
this
is
the
document
we're
talking
through
I
think
the
general
tone
on
the
call
is
that
of
interest
and
excitement
and
and
not
huge
amounts
of
of
issues
or
risks
being
raised
more
things
that
we
think
we
can
work
through
in
the
general
kind
of
review
process.
Not
in
like
a
you
know,
oh
hold
hold,
stop,
don't
don't
progress.
We
need
to
have
a
conversation
before
we
can
do
it
it's
more
like.
B
B
B
G
Yeah,
so
they
give
me
for
probably
coming
in
and
speaking
about
some
topics
you've
already
talked
about,
but
so
in
terms
of
the
collaboration
we
initially
did
a
lot
of
the
drafting.
Actually,
we
use
Google
Sheets
initially
for
a
tremendous
amount
of
the
drafting
that
we
did
with
the
the
cncf
maturity
model
early
on
that
that's
incredibly
helpful,
rather
than
relying
on
GitHub
issues
for
for
collaboration,
particularly
early
on.
B
Yeah
yeah
I
think
that's.
So
we
have
one
kind
of
I'll.
Add
that
up
into
my
I'll
just
leave
that
we
have
I
think
one
dissenting
experience
in
the
sense
that
there
was
a
success
using
GitHub
issues.
I
think
it
was
the
get
get
UPS
white
paper,
but
we're
getting
enough
interest
and
experience
and
success
with
GitHub
with
a
sorry
with
Google,
Docs
I
think
we're
going
to
start
there
and
and
solve
if
problems
appear
so
but
yeah
go.
G
G
Sorry,
oh
yeah,
probably
just
one
other
observation
as
well:
we
we
received
a
lot
of
a
very,
very
strong,
effectively
or
explicit,
almost
explicit
directive,
to
remain
to
around
or
challenges
around
King
making
and
try.
And
so
we
we
wrote
a
policy
around
included
Technologies
and
basically,
if
it
was,
if
it
was
graduated,
then
we
could
talk
about
it
incubating
to
a
degree,
but
it
might
be
worth
actually
considering
putting
in
a
policy
on
included
Technologies
as
well.
Yeah.
B
B
Current
policy
is
none
yeah,
like
I
think
that
sort
of
that
was
actually
one
of
the
things
we
were
talking
about.
Is
that,
like
we
are
going
the
target
so
I
think
one
thing
to
put
here
is
like
set
policy,
maybe
on
depth
of
like
story
or
whatever,
like
I.
Think
one
of
the
things
we're
talking
about
here
is
that
the
white
paper
is
very,
very
high
level
and
that's
been
awesome
and
it's
captured
people
so
deeply
like
it's
crazy.
B
How
many
places
I'm
seeing
it
pop
up
already,
even
though
it's
so
new.
So
it's
clearly
a
high
value
piece
of
document,
but
the
reality
is,
is
once
you've
read
through
it
once
and
you
go
and
you
try
and
implement
it.
There's
gonna
be
a
lot
of
questions
and
that's
why
we're
trying
to
follow
up
quickly
with
more
and
more
tangible
things
that
people
can
play
with
and
touch
and
actually
like
experience
at
their
companies.
This
is
meant
to
be
only
one
level
more
tangible.
B
It's
not
meant
to
go
down
to
the
level
of,
and
if
you
pick
these
Technologies
off
our
list,
you'll
be
a
level
four
mature
platform,
so
we
want.
We
want
other
documents
to
go
into
the
depths
of
like
well,
if
you're
trying
to
deliver
compute
on
your
platform
here
are
the
different
options
and
here's
why
you
might
choose
one
over
another
like
that?
Will
that
will
come,
but
from
a
different,
a
different
document
so
remember
it
might
come.
I
should
say
cool.
B
That's
that's
reassuring,
because
that
was
something
that
we
I
want
to
understand,
what
Alex
meant
by
King
making
and
he
wasn't
able
to
able
to
come
so
I
was
going
to
Ping
him,
but
that
makes
sense
if
what
the
issue
is
is
like.
You
know
mentioning
specific
projects
and,
having
those
be
elevated
to
a
level
we're
going
to
stay
away
from
that
for
sure,
correct.
B
B
I
would
propose
so
I
first
of
all
want
to
thank
you
all
for
taking
the
time.
Synchronous
meetings
are
always
hard
different
time
zones.
I
know,
we've
got
at
least
two
different
continents
so
like
at
three
different
cities
at
the
very
least
so
I
appreciate
y'all,
making
the
time
to
get
on
on
the
call.