►
From YouTube: WG Platforms - 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
A
So
yeah,
let's
go
ahead
and
get
started
yeah
we
like
to
start
out
there's
a
couple
new
folks
here
so
Kirsten
and
Rick,
if
you
guys
want
to
just
briefly
because
the
reason
why
is
we
want
to
know
what
you
do
and
kind
of
how
you
want
to
help
or
how
we
can.
You
know
refer
to
you
for
help.
So
that's
why
we
asked
for
the
quick
intros.
B
I'm
sure
I
can
go
first,
hi
everybody,
I'm
Kirsten
I'm,
a
technical
program
manager
at
datadog,
which
is
a
us-based
company
in
observability,
and
monitoring
I
work
in
out
of
New
York
City
on
their
API
platform
team
who's,
making
it
kind
of
easy
to
build
apis
internally
within
datadocs.
That's
an
alarm
and
yeah
I'm
just
trying
to
learn
all
things
platform:
engineering,
I've
spent
about
10
years
in
the
program
management,
space,
doing
all
kinds
of
things
and
platform.
Engineering
yeah
really
resonates
with
me.
B
So
how
I
want
to
help
yeah
I,
don't
know
still
just
just
kind
of
getting
started:
got
access,
yeah
to
the
git
repo
and
and
the
slack
Channel,
and
just
kind
of
observing.
First
everything
going
on
and
that's
me
it.
C
Owski
I'm,
a
principal
engineer
at
Seagate,
based
I'm,
based
in
the
suburbs
of
Chicago
I,
was
with
Josh
last
night
at
the
Meetup
downtown
I
I,
currently
work
under
our
live
Cloud
brand,
which
is
a
object,
storage,
service
or
storage
as
a
service,
and
it
all
runs
on
kubernetes,
so
I'm
very
interested
in
getting
the
ability
to
build
that
out
and
I'm
on
my
iPad
because
of
it.
Wouldn't
let
me
join
the
meeting
on
my
work
laptop,
so
I.
C
Don't
know
why
that's
Auto,
my
iPad
is
auto,
focusing
there,
but
the
hopefully
I'd
stop
soon
I'm
very
focused
on
helping
to
see
what
we
can
do
to
help
kind
of
evangelize
platforms
internally,
helping
to
get
past
the
a
lot
of
the
politics
of
of
what
that
means
for
that.
C
So
not
necessarily
the
technology
but
the
kind
of
the
people
side
of
it
and
then
how
we
can
help
to
build
that
out
and
grow
and
kind
of
show
some
of
the
value
very
early
on
so
I've
I've
been
in
in
communication
with
with
Abby
and
some
of
the
folks
at
craddocks
on
some
of
that.
C
But
in
the
meantime,
we've
just
been
battling
some
internal
reorgs
and
and
politics,
and
things
like
that
that
are
making
it
hard
to
actually
progress
forward
through
some
of
this
stuff,
so
hoping
to
help,
contribute
and
kind
of
be
a
use
case
or
a
sounding
board.
For
what
type
of
information
do
we
need
to
help
kind
of
move?
Some
of
this
forward.
A
A
Okay,
moving
on
one
thing:
I
wanted
to
bring
up
I've
been
thinking
about.
You
know
this
group.
We
are
trying
to
move
forward.
You
know
Cooperative
delivery
of
applications
and
infrastructure
and
move
forward
platforms.
A
You
know
we
put
out
the
paper
kind
of
as
a
strategic
motion.
Now
you
know
we're
looking
I
mean
we.
We
have
ideas
and
we're
pursuing
things,
but
I
wanna.
You
know
just
reiterate
like
if
other,
if
people
have
suggestions
like
to
improve
the
platform
practice
or
things
that
we
should
pursue
as
a
group
share
open
up
it
and
that's
what
I
was
getting
to
kind
of
the
the
GitHub
issue.
Thank
you
saying
for
opening
those
issues.
A
You
know
it's
also
fine,
if
you,
if
somebody
has
a
PR
to
add
straight
to
the
paper
on
a
topic,
you
know
we
can
discuss
it
that
way
too,
and
if
some
like
Abby's
maturity,
model
I
was
gonna
say,
like
I've,
been
hearing
so
much
the
past
couple
weeks
even
last
night
about
people
like
yeah,
we
love
the
strategy.
Now
help
us
implement
it.
A
That
kind
of
stuff
fits
in
really
well
yeah.
So
going
down
the
list,
somebody
added
kubecon,
cfps
I,
didn't
add
that
you
did.
Okay.
Did
you
wanna,
so
I
think
a
couple
of
these
are
your
side.
Do
you
want
to
share
with
us
what
you
wanted
to
talk
about
on
those.
D
Yes,
I
think
one
thing
I
need
to
discuss
here.
Let
me
know
if
my
voice
is
clear
Josh.
Is
it
good
enough,
yeah,
very
good?
Okay,
so
actually
I
think
after
a
few
months
of
later
this
year,
we're
mostly
in
the
Chicago
for
the
CF
cubecon
Chicago
and
in
November
I.
Think
on
that
time,
I
think
the
platform
paper
might
be
have
some
good
things
in
there
because
we're
working
on
it
on
a
weekly
or
the
monthly
basis.
D
So
this
means
we
have
to
be
in
the
visibility
Zone
in
the
cubecon,
so
I'm
thinking
here
like
we
should
consider
going
for
the
cfps.
That
is
very
important
for
this
group
to
have
some
participation
in
this
Cube
go
in
Chicago,
because
some
of
the
things
is
really
critical
in
the
in
this
platform.
Engineering
web.
As
for
months
to
come,
number
one
is
I'm
talking
to
a
lot
of
people
these
days
around
how
to
measure
the
success
of
the
platform
and
the
platform
team
is.
This
idea
is
new,
but
you
have
to
measure
it.
D
Otherwise,
things
already
to
understand
so
I
think
the
cfp
is
very
important
for
all
us
for
us.
I
think
Abby
Josh
or
anyone
on
the
call
today
I
think
we
have
to
be
friends
or
actually
team
up
with
some
some
of
the
cfp
as
well.
So
my
opportunity
collaboration
as
well
but
I,
think
this
group
should
go
for
the
cfps.
There
is
not
just
cubecon
Chicago.
This
is
app
delivery.
Conco
located
event
happening
is
well
in
the
cubecon
a
co-located
event,
so
I
have
to
live.
Yes,
so
I
think
these
are
the
Avenues.
D
We
have
to
write
it
up,
so
I
think
like
Josh
and
Abby
and
other
like
we
have
to
think
about
because
the
dates
is
now
is
very.
Very
less
18th
is
the
last
date
for
the
for
the
submission,
so
I
think
we
have
to
stress
this
more
like
we
have
to
write.
We
have
to
submit
few
of
the
topics.
Few
of
the
very,
very
important
topic.
I
heard
this
new
term
shift
down,
there's
another
term
being
public
over
the
Internet.
D
That's
called
self-service
infrastructure
platform
so
doing
going
down
the
road
we
already
did
Incorporated
those
changes.
Now
it's
telling
people
on
the
sh
on
the
cube
count.
We
have
some
group
coming
up,
so
they
have
some
visibility
to
access.
Visibility
is
important,
I
think
today's
my
focus
is
to
have
Team
upcoming
up,
so
we
can
go
for
some
submissions.
A
D
Because
I
think,
like
I,
think
like
some
of
us,
we
go
for
the
lightning
talk,
some
of
the
go
for
the
solo
talk,
some
of
the
girl
for
the
panel
talk
as
well
so
having
different
visibilities
on
inside
the
cfp,
so
I'm,
currently
looking
for
someone
to
team
up
with
for
some
of
the
loudest
topic
stuff
like
how
to
measure
the
success
of
the
platform
and
platform
clean.
Is
it
tougher?
I
need
someone
to
partner
with
for
this
cfp,
but
there
are
lightening
talk.
There
are
some
workshops.
D
There
are
so
much
things
you
can
talk
about,
so
I
think
having
different
talk
tracks.
We
have
to
submit
it.
That
is
very
important
because
I
believe
during
November
we
have
so
much
to
Showcase,
and
today
is
actually
we
are
closing
down
the
cfts.
So
if
you
miss
this
opportunity,
we
have
a
hard
time
of
telling
what
we
are
doing
in
the
cncr
platform
working
group.
D
E
A
Trying
to
think
how
to
support
you
there
same
so
I
mean
people
here
are
hearing,
and
you
know
we'll
share
the
update
on
the
thing.
Maybe
we
should
bump
on
the
on
our
channel
in
the
next
day
or
two
like
hey,
get
your
submissions
in
make
sure
and
and
yeah,
if
just
trying
to
think
just.
E
D
F
A
Oh
yeah
sounds
good,
sounds
very
good
and
also
I
just
got
a
call
out.
I
did
open
this
issue
number
408
and
we're
going
to
talk
about
the
next
tag
meeting.
If
anybody
is
interested,
the
tag
means
this
is
a
project
meeting
for
platforms,
but
on
the
21st
we
have
the
all-up
tag
meeting
and
there
we'll
discuss
the
pre-day
and
how
we
might
partner
I
I
think.
Certainly
the
get
Ops
folks
are
pretty
interested
in
how
we
can
streamline,
and
maybe
there
are
a
couple
others
also.
A
So,
if
you're
interested
in
that,
you
know
come
on
on
the
21st,
we
definitely
I
heard
same
worth
mentioning
also.
There
is
an
app
developer
day
being
planned
for
November
6th.
Also,
now
I
also
saw
backstage
conference
on
that
day.
So
e
already.
D
A
Okay,
let's
tip
forward
then
to
the
next
item:
yeah
thanks
for
bringing
that
upside,
which
is
maturity,
model
which
I
I
think
is
really
that's.
That
is
I'm,
so
happy
you're
working
on
that,
because
it's
definitely
what
we
need
to
be
focused
on
now.
So
can
you
tell
us
what's
up.
G
Yeah,
first
of
all,
it's
not
the
Abbey
maturity
model,
it's
just
the
maturity
model,
but
yes,
so
it
is
in
progress.
We've
been
making
some
progress,
I
know
Simon's
here,
which
is
awesome.
He
works
on
the
cloud
native
maturity
model,
which
is
one
of
the
documents.
We
want
to
make
sure
that
this
maturity
model
kind
of
speaks
to.
So
it's
not
that
it
has
to
be
the
same,
and
it's
not
that
it
has
to.
G
You
know
it's
it's
actively
a
more
detailed
level
than
the
cloud
native
one,
but
we
want
people
who
read
one
or
the
other
to
not
feel
lost
if
they
go
to
the
other
one
not
be
completely
different
language,
completely
different
structure
and
all
that
kind
of
stuff
and
actually
Simon
an
update
is
Michael
from
Michael
K
losing
the
last
name.
Someone
who's
been
working
with
you
for
the
last
few
weeks
or
months.
G
I
just
had
a
call
with
him
this
week
and
he's
Keen
to
get
involved
and
help
with
that
kind
of
making
sure
that
we
have
similar
voices
as
well
as
just
adding
to
it
General.
So
that's
great,
so
we'll
continue
to
have
more
kind
of
crossover.
There
sorry
you've
been
doing
an
awesome
job.
Making
comments
really
appreciate
all
of
that
and
yeah
anyone
else.
You
can
jump
in.
G
G
Where
I
wouldn't
say
we
have
a
ton
of
feedback
yet
is
on
like
does
it
to
the
to
the
categories
and
aspects
make
sense
so
I
don't
know
if
I'm
taking
that
as
a
really
good
sign
of
the
original
proposal
or
I,
think
it's
probably
more
so
either
a
fear
of
of
making
a
big
kind
of
statement
with
with
trying
to
change
one
of
the
aspects
or
maybe
just
not
enough
time
to
to
think
deeply
about
it.
G
G
Our
goal
is
to
keep
this
really
in
the
the
whip
stage
for
another
kind
of
month
or
two
at
least,
and
we're
looking
at
kind
of
into
September.
When
we
are
going
to
start
to
look
at
okay
are
we?
Are
we
prepared
to
say
that
cubecon
Chicago
is
a
target
release
date?
Yes,
that's
a
hope,
but
if
we're
coming
into
September
with
still
some
big
open
questions,
we're
not
going
to
push
it
like
this,
it's
important.
G
We
do
this
right
so,
but
that's
sort
of
our
Target
is
seeing
how
we
feel
in
September.
So
yeah.
A
A
A
A
A
G
G
The
working
backwards
math
that
I
did
based
on
your
your
leadership
for
the
white
paper
that
seemed
to
work
well,
so
I
figured
why
recreate
the
wheel
if
it
worked?
Okay
and
we'll
we'll
see,
you
know
we'll
we'll
evolve
with
this
group
of
people
that
are
working
on
this
piece
of
paper
to
see
if
that
changes.
But
it's
a
good
structure
to
at
least
start
with
so
yeah.
E
A
Any
have
any
has
anybody
else
heard
so
yeah
like
I,
was
saying
like
in
our
Meetup
last
night
and
another
time
that
you
know
we
had
Red,
Hat,
Summit
and
and
I
am
getting
a
lot
of
like
I
even
met
with
abhinav
Mishra.
If
you
all
recall,
he's
he's
part
of
our
group
too,
and
he
brought
this
up,
he
he
was
talking
about
Journeys
and
I
kind
of
said.
The
maturity
model
is,
could
facilitate
Journeys
I
I
feel
like
a
lot
of
people,
are
asking
for
this
like
next
step.
A
A
What
he
meant
was
if
I
am
today,
you
know
running
VMS
and
you
know
jars,
what
would
be
kind
of
my
Pathway
to
getting
to
This
Cloud
native
platform.
You
know
promise
like
what
are
the
steps
along
the
way.
Maybe
the
first
thing
is
I
containerize,
then
I
go
to
maybe
I
go
to
kubernetes
I,
don't
know
that
kind
of
a
journey,
and
so
it
actually
kind
of
like
he
thought
he
didn't
associate
with
the
maturity
model.
But
I
was
like
wait.
A
A
That
was
my
thought
on
what
Journeys
meant
and
abhinav
seemed
to
resonate
with
that
so
I'm
kind
of
tying
it
all
back
to
the
maturity
model
is.
Is
our
answer
to
the
this
ask
I.
G
Think
that
there
is
a
little
bit
of
a
a
race
to
get
the
next
level
of
detail
down
from
the
white
paper
solidified
or
at
least
provisionally
solidified,
because
I
think
a
lot
of
people
are
actually
what
I'm
hearing
is
a
lot
of
people
asking
for
like
blueprints
like
exempt
like
architectures,
like
things
like
that,
which
I
think
are
absolutely
reasonable,
asks
I,
also
think
those
without
a
little
bit
more
of
a
step
between
the
white
paper
and
use.
G
This
Tech
will
be
much
more
likely
to
cause
harm
than
than
good,
so,
like
I,
think
we're
talking
about
that
with
the
with
the
GitHub
issue
that
we
have
around
the
the
reference
architecture
and
like
trying
to
pair
with
the
work,
that's
already
being
done
a
step
one
step
above
right,
so
we're
sort
of
I
feel
like
we're
starting
to
create
this
little
hierarchy
of
detail
white
paper
at
the
top
maturity
model.
G
Maybe
next,
maybe
next
after
that,
some
like
principles
that
are
like
even
more
grounded
than
the
kind
of
higher
level
outcomes
that
you
get
from
the
maturity
model
and
then
from
the
principles.
G
You
can
then
start
to
say
here
is
a
a
working
prototype
or
a
reference
architecture
blueprint
whatever
the
phrasing
is
yeah,
so
I
think
that
that's
that's
things
that
I'm
I'm
thinking
about
is:
how
do
we
give
people
the
chance
to
ask
good
questions
rather
than
just
give
them
what
what
might
be
seen
as
an
answer,
because
I
don't
think
that's
going
to
work
quite
as
well.
C
Yeah
and
that's
I
was
going
to
mention
that,
because
of
my
experience
when
I
was
at
IBM
as
far
as
always
having
a
pre-canned
answer
for
every
problem,
and
it
was
kind
of
like
an
all
blue
stacker
now
with
some
of
the
stuff
that
was
being
done
with
with
open
openshift
as
far
as
an
all
red
stack
and
those
platforms
solve
a
lot
of
the
problems,
but
it's
you're
either
for
a
lot
of
it.
It's
either
you're
buying
all
in
or
not
or
it's
a
lot
harder
to
deviate.
C
And
so,
if
you
come
in
with
the
the
reference
architecture
to
begin
with,
you're
saying
all
these
decisions
have
already
been
made.
But
you
you're
not
kind
of
aware
of
all
of
those
decisions
so
having
that
almost
like
hierarchy
of
needs
for
coming
into
what
you
need
for
the
platform
and
how
you
navigate
and
kind
of
figuring
out.
What
is
there
I
think
that
the
structure
you
just
laid
out
Abby
is
really
good,
so
I'm
definitely
going
to
dive
into
the
maturity
model,
because
that
was
my
background.
C
That
IBM
was
reference
architectures
and
things
like
that
as
well,
and
so
the
breaking
down
at
some
point
like
a
case
study
of
what
the
openshift
platform
is
and
what
that
gives
you
and
how
those
decisions
were
made
and
how
you
kind
of
came
to
this.
C
This
point,
but
you're
solving
all
the
pieces
that
the
maturity
model
and
then
the
journeys
are
dictating,
but
that's
one
way
of
doing
it
and
obviously
you
could
arrive
at
a
different
end
state
if
you
made
different
decisions
or
you
did
it
at
a
different
time,
so
just
kind
of
bifurcating,
all
that
and
really
strictly
keeping
that
in
those
levels,
I
think
is,
is
very
valuable.
C
H
Yeah
so
I'm
still
relatively
new,
not
brand
new
to
the
to
the
open
to
the
kubernetes
cncs
community.
One
thing:
I
I've
been
going
through
the
older
kubernetes
earlier
design,
videos
and
Etc
I
find
that
it's,
it
will
be
interesting.
I
would
like
to
lead
those
discussions,
but
I
don't
have
them
another
experience
a
little
discussion
about
what
lead
to
the
current
design
of
kubernetes
and
then
what
is?
H
Is
there
any
gap,
for
example,
to,
for
example,
the
man
standing
like
security,
like
user
data
store,
typically
still,
not
part
of
a
kubernetes,
isn't
just
not
designed
that
way,
unless
my
understanding
so
in
order
to
actually
brought
it
up
a
couple
meetings
ago
is
like,
for
example,
if
we
use
openshift
as
a
platform
right
to
replace
public
Cloud
even
and
just
build
a
new
property
without
using
openshift.
What
is
the
gap
right?
What
is
the
remaining
seems
to
be
done
to
the
deal?
Is
it
even
possible?
H
You
know
if
there
is
such
a
thing,
is
it
possible
to
have
a
new
you
need
to
have
a
new
orchestrator
for
a
web
assembly,
so
I
think
that
would
be
all
interesting
platform
related
questions.
I
know
it's
not
simple
enough.
It's
a
but
I,
don't
know.
I
think
would
be
interesting
to
discuss
somewhere,
but
I
probably
can
be
a
listener,
because
I
don't
have
enough
knowledge
about
all
this.
A
I
think
that's
awesome,
I
think
what
kind
of
came
out
from
that
conversation
was
that
there
are
several
levels
going
down
like
we.
The
first
paper
was
strategic
high
level
North
Star.
This
is
how
it
should
look
at
the
end
of
the
day.
The
maturity
model,
Abby
I,
think
I
heard
from
you,
like
that's
still
a
little
bit
abstracted,
but
it
gives
more
guidance,
and
then
you
I
think
what
I
learned
from
this
conversation
is
the
journeys
that
kind
of
abhinav
was
brought
up
with
me
and
blueprints.
A
You
all
are
kind
of
thinking,
that's
a
step
after
the
maturity
model
and
then,
finally,
what
what
Victor
just
brought
up
like
very
detailed.
You
know
I'm
using
kubernetes
as
my
orchestrator.
What
are
the
ins
and
outs
of
that?
That's
that
feels
like
that's
the
very
lowest
it
might
be
in
some
of
our.
You
know,
prototypes
and
reference
implementations
at
some
point.
G
Yeah
I
think
absolutely
being
able
to
understand
where
you've
come
from
make
decisions,
as
you
go
down
and
always
be
able
to
pop
back
up
and
think
back
to
the
principles
of
the
level
above
is
is
really
cool
is
a
really
important
kind
of
piece
of
this
so
yeah.
We
should
always
be
thinking
about
like
how
did
someone
get
to
this
detail?
How
would
someone
have
made
this
decision?
Is
there
a
clear
path
from
the
white
paper
down
and
it
might
mean
making
updates
to
the
white
paper
in
learning
about
platforms?
A
Yeah,
maybe
we'll
maybe
I'll
figure
out
a
way
to
write
that
up
like
the
the
overall
path
that
we're
going
down
and
we
couldn't
pursue
some
of
those
things
in
parallel,
like
I
wanted
to
mention
to
Rick.
If
you
like,
building
reference
implementation,
you
know
the
way
for
us
to
finish
the
rest
of
the
stack,
I'm,
sorry
I
know:
I've
been
working
with
Mauricio,
salatino
and
Leanne
to
try
to
leverage
Potato,
Head
or
maybe
build
some
other.
A
You
know
reference
implementations,
so
yeah,
if
you're,
if
that's
where
people's
passions
are
I'm,
you
know
check
it
out.
Yeah.
F
And
I
think
it'd
even
be
wise
to
have
a
bit
more
organization
around
like
that
concept,
because
I
think
we're
I
think
Abby's
done
a
great
job
of
sort
of
like
really
kind
of
getting
people
on
the
same
page
with
just
the
maturity
model.
I
think
that
this
is
a
great
kind
of
progression,
next
step.
I
think
it
just
needs
some
like
coordination
of
like
okay
who's,
who
is
actually
going
to
do
what?
F
D
So
also
I,
think
Josh,
so
I
have
one
insight
into
it.
Like
I
have
also
created
a
one
issue
in
the
GitHub
repository
I
like
to
see
what
people
take
on
it,
because,
when
I'm
talking
to
public
currently
right
now
regarding
the
cncf
white
player
white
platform,
white
paper
with
several
different
companies
and
different
individual,
particularly
the
different
startup
as
well,
what
they
like,
what
did
intent
was
from
this
paper.
They
think
like
this
becomes
a
paper
that
become
a
shorter
in
the
loop
of
decision
making.
D
Like
you
know,
kubernetes
has
a
steep
learning
curve
associated
with
it
when
you
start
driving
into
the
kubernetes
there's,
not
just
one,
but
you
have
a
you
have
to
step
up
the
Larder
like
let's
say
if
you
want
to
use
kubernetes
and
deploy
apps
on
top
of
it,
you
need
to
install
Ingress
controller
for
then
logging
in
monitoring
their
Prometheus
and
grafana
for
service
meshes.
You
has
history
or
Linker
and
for
the
ketos
flux
and
Argo
CD
I'm
the
policy
engine
that
is
open,
I
ever
know.
D
So
currently,
when
I'm
speaking
to
about
giving
people,
gifts
and
resources
say
they
feel
like
that,
has
not
much
in-depth
information
regarding
what
is
the
next
step
for
me
because
I
doesn't
know
anything
about
Cloud,
native
or
kubernetes,
and
this
platform
give
me
the
paths
of
where
to
go
and
where
to
check
out
these
resources.
So,
currently,
people
see
we
have
well
I,
think
we
have
to
work
on
this
path
lines
like
I,
said
the
shortening
the
decision
making.
D
What
people
is
actually
frequently
asked
me
every
time
I
do
a
podcast
with
some
of
the
people,
so
I
hired
your
opinion
as
well,
when
how
other
people
think
about
this
domain,
because
I
can
see
like
for
me.
It's
for
a
development
point
of
view.
This
really
is
a
challenge
for
me
like
what
tool
is
next
for
me:
I,
never
able
to
figure
it
out
unless
I'm,
trying
and
testing
it.
A
Yeah
that
makes
a
lot
of
sense.
I
I
think
I
tried
to
capture
some
of
the
things
you
just
said
saying:
I
think
what
you're
saying
is
when
they,
when
people
read
the
paper,
they're
expecting
help
with
those
choices
and
it
the
paper
doesn't
really
make
the
choices.
It
says:
here's
12
capabilities.
You
know
we
think
you
should
think
about
and
here's
five
projects
on
each
one
to
evaluate,
but
it
kind
of
leaves
them
there.
A
D
Yes,
yes,
absolutely
absolutely!
That
is
really
a
challenge
for
me
right
now,
because
I'm
from
more
often
I
try
to
share
this
paper
Link
in
a
week
or
two
weeks
where
people
get
being
try
to
commenting
and
talking
on
the
internet,
about
these
people
and
that's
a
clear
intent
right
now,
because
they
see
like
cncf
platform
white
paper,
and
we
have
so
many
technology
stacked
and
it's
bombardment
of
the
technology
stack
it
existing.
So
they
feel
like
this
is
the
group
responsibility
to
let
everybody
own
board
like
here
are
the
choices.
D
This
is
a
use
case.
Let's
pick
that
juice,
then
I.
Try
to
talk
about
people
go
to
the
cloud
native
maturity
model.
This
is
discussing
the
same
dilemma,
so
this
is,
they
say,
like
is
good,
but
in
here
we
want
to
have
a
shortening.
The
decision
making
like
I
am
a
startup
I
want
to
build
a
platform.
I
doesn't
know
like
what
to
enter
in
integrate
into
my
platform,
so
this
one
paper
is
actually
give
me
the
shortest
possible
time
to
think
about
it.
What
is
the
mandatory
staff
for
me?
D
What
is
what
is
the
mandatory
tools
and
infrastructure,
or
things
or
Services
should
be
in
the
platform.
Currently
we
don't
see
this
how
much
on
this
part,
so
that
is
actually
what
I'm
expecting
might
be.
Some
people
hear
the
other
call.
They
have
some
different
opinions,
but
I'm
morally
on
the
public
side,
so
that
actually
I'm
right
now
facing
it.
C
The
the
white
paper
is
giving
us
a
general
shopping
list
of
what
we
could
go
out
there
and
consume,
but
now
we
need
some
help
in
saying.
Oh
well,
if
I
pick
this
one,
then
I
should
also
pick
this
one
or,
if
I'm,
coming
at
it
to
solve
this
problem.
You
should
really
go
with
this
one
and
then
you'll
you'll
have
less
issues
integrating
with
this
one.
C
So
having
like
the
the
I,
didn't
click
on
the
link
yet,
but
the
phrase
you
used
in
your
issue
as
far
as
fast
forward
decision
making
is
very
helpful
and
probably
about
six.
Seven
years
ago,
I
wrote
a
paper
on
that
for
just
microservices
in
general
for
IBM,
and
so
it's
very
used
to
that.
As
far
as
itemizing.
All
of
that
and
kind
of
saying
we
have
a
lot
of
the
capability
domains
inside
of
platforms,
but
now
saying
when
you
want
to
do
X,
you
can
choose
this.
C
Don't
think
we
have
to
do
that
as
long
as
we
elaborate
and
clarify
ourselves
as
far
as
why
decisions
are
being
made,
or
we
kind
of
back
that
up
with
data,
and
it's
it's
not
at
just
as
much
of
a
predisposed
notion
of
of
what's
there
because
I
think
we
all
kind
of
have
our
different
go-to
tools
as
far
as
what
we
do
and
personally
in
projects
but
I
think
coming
together
at
it
as
far
as
getting
just
more
Source
data
and
more
use
cases
can
help
clarify
that
and
kind
of
flatten
the
bell
curve
of
what
things
get
selected.
C
F
I'm,
a
bit
wary
of
I
think
the
trajectory
of
this
conversation
specifically
like
I,
like
the
ideas,
I,
think
they're
interesting
I,
think
they
make
sense
that
could
be
nice
to
have
I
think
it
can
be
tricky
when
you
start
to
prescribe
tools,
especially
with
the
rate
that
they
change
it
can
I,
don't
know
like
that's
just
a
that's
a
very
tough
path,
not
only
to
like
start,
but
also
to
maintain,
like
as
things
change
and
as
situations
change,
and
they
change
quickly.
We
all
know
that,
so
it's
I
think
it's
a
good
idea.
F
I
think
it's
something
that
would
have
to
be
thought
through
really
well
in
terms
of
like
what
it
would
be,
the
long-term
sustainability
of
starting
something
like
this.
So
it's
just
another
thing
to
think
about.
G
I
think
that's
one
of
the
challenges
around
the
open
issue
around
a
reference
architecture
that's
been
talked
about
right
is
that
that
is
a
reasonable
and
effect
like
really
helpful
thing
for
us
to
be
doing,
and
we're
really
far
on
that
path,
which
is
awesome.
But
how
do
we
make
it
so
that
that
is
sustainable
for
this
group
to
maintain
as
the
things
move
forward,
especially
when
there's
so
many
like
sandbox
level
projects
in
there
they're
gonna
be
updating,
releasing
weekly
right
like
more,
maybe
more
so,
there's
that
and
then
there's
also.
G
How
do
you
actually
do
comparisons?
What
are
you
actually
deciding
between
and
how
and
that's
why
that
whole
like
we
can't
jump
from
white
paper
down
to
reference
architecture.
We
also
can't
snap
our
fingers
and
have
you
know,
really
well
thought
out
and
written
documents
at
every
tier
of
depth
between
the
two
you
know
tomorrow,
but
that's
what
we
have
to
work
towards
is
give
people
that,
if
they're
looking
at
reference
architecture
they're
like,
but
that
seems
funny
to
see
that
technology
there
they
can
understand
where
it
came
from
what
the
decisions
were.
G
What
other
Technologies
play
in
that
space?
Etc
one
tier
up
in
in
detail,
ideally.
D
D
On
currently,
is
it
good
now,
Josh.
D
E
A
D
I'm
thinking
currently,
there
is
two
attended
audience
that
is
actually
taking
or
their
eyes
towards
us
number
one
is
that
actually,
the
users
of
the
cloud
native
technology
stack,
who
had
very
little
knowledge
and
they
want
to
accelerate
by
reading
the
paper.
That
is
the
one
areas,
and
that
is
audiences
views
you
can,
you
can
know
like
this.
Audience
is
80
to
90
percent
of
them.
D
Then
the
ten
percent
audience
is
actually
the
companies
and
the
vendors
and
other
public
sector,
and
they
actually
looking
at
us
that
we
can
make
some
coins
the
new
terminologies
that
eventually
become
a
standard
and
when
Android
actually
vendor
specified
their
tool,
then
they
Define
those
Technologies
according
to
what
we
actually
what
actually
we
actually
extended
eyes.
Let's
say
right
now:
people
talking
about
policy
and
the
governance
everybody
understands
is
what
the
policy
is.
D
This
thing
like
this,
that
subtle,
subtle
things
to
be
in
your
kubernetes
cluster
to
check
on
a
daily
basis,
so
that
is
another
audience
that
checking
toward
us
because
currently
for
the
platform
engineering.
If
you
look
at
the
platform
engineering,
we
have
20
different
definitions
on
the
internet
foreign.
If
you
look
at
the
self-service
how
people
actually
Define
self-service
is
not
just
a
one
definition,
it's
a
plethora
of
definition,
so
some
people
and
the
majority
of
the
vendors
looking
towards
this
group
to
standardize
those
definitions.
So
there
is
a
two
domains
into
it.
D
One
is
I'm,
actually
completely
agree,
I
think
with
Josh
and
me
we
have
a
so
much
debate
in
the
past,
like
we
never
tell
people
like
choose
Skywarn
over
Opa
or
Argo,
CD
or
flux,
but
General
opinion
was
to
actually
tell
people
your
cluster
has
to
be
a
policy
and
governance,
consistent
automation,
security
preparedness.
Those
are
the
world
that
have
some
vendor
specificity,
we're
not
letting
you
know,
like
usual
driver,
no
or
Opa,
but
we
tell
you.
D
There's
a
policy
pipelines
and
auditing
is
much
to
have
it
and
when
we
Define
the
term
platform
in
generating
it,
that
is
actually
a
picture
of
what
what
we're
actually
telling
the
people
so
I
think
we
had.
That
is
very
a
very
I
know.
This
is
a
very
complicated
like
very
sophisticated
way
to
think
about
it.
But
specifically,
these
are
the
two
audience
that
will
actually
the
whole
the
conversation
that
we're
talking
to
listening
to
Abby
and
other
people.
D
We
have
same
question
being
raised
to
all
of
us,
but
the
different
angles
like
abhinav
is
talking
about
the
journey
I'm
talking
about
the
decision
making
and
other
group
talking
about.
Let's
forget
about
it
flexity
or
Argo
CD.
So
the
question
is
say:
Still
Remains
the
Same.
So
we
need
to
figure
out
how
we
answer
this
in
a
consistent
manner.
A
G
A
Really
good
insights
I
feel
like
it
all
kind
of
for
me,
is
trending
into
something
we
kind
of
talked
about,
but
I
guess
we're
not
really
pursuing,
which
is
within
those
capability
domains,
kind
of
going
a
level
deeper.
Comparing
and
contrasting.
You
know
the
10
cncf
projects
for
governance
and
policy
or
something
and
then
I
guess
it
would
be
not
just
but
coming
out
with
the
common
language,
is
kind
of
what
you're
saying
right
so
like
if
I
I
put
this
down
as
a
possible
idea
like
that,
maybe
could
help
like.
A
Is
that
what
you're
getting
it
like?
Like,
let's
say,
databases
we
could
talk
with
a
storage
team
and
say
there's
10
different
cncf
projects
for
running
a
database
of
kubernetes.
Here's,
the
ups
and
downs
of
both
here's,
the
five
characteristics
that
are
most
important
or
that
you
might
want
to
think
about
is
that.
Does
that
I'm
trying
to
like,
based
on
this
I'm
solutioning
a
little
bit
but
like
is
this?
Where
you're
going
with
the
problem.
D
Yes,
actually,
absolutely
I
think
if
you
think
about
this
problem
is
currently
I.
Think
that
practical
way
to
think
about
it
like
in
a
platform,
you
have
these
five
six
things
visible
and
all
the.
If
you
look
at
the
internet,
everybody
is
talking
about
policy
and
governance,
everybody
is
talking
about
self-service
infrastructure,
everybody
is
talking
about
consistent
automation
or
provisioning,
and
deprovisioning
shift
left
shift
down.
These
are
the
terminologies
widely
accepted
and
nobody
has
different
opinion.
D
There
is
a
one
very
subtle
missing
piece
in
here.
They
are
defining
it
in
a
very,
very
different
way,
a
same
term
being
defined
with
14
different
ways
and
yes,
absolutely
and
the
problem
people
seen
is
like.
If
I'm
reading
the
platform
white
paper,
then
there's
a
one
terminology
that
in
future
might
become
everyone.
People
say
like
forget
about
you,
but
at
least
you
do
these
things
with
shift
left.
At
least
you
do
this
thing
we
shift
down.
D
D
While
reading
these
four
pillars
or
digesting
the
data
about
the
four
pillars-
okay,
people,
like
think
like
we
can
use
Sky,
Vernon
or
oppa,
they
can
make
fast
moving
decisions.
That's
why
I'm
actually
thinking
about
so
I
think
it's
tougher,
but
I
think
we
have
to
carry
forward
this
discussion
more
because
I
think
a
lot
of
people,
Mauricio,
George
Abby,
all
of
us
having
the
same
questions
with
different
angles,
and
she
talking
to
the
people
with
the
different
insights
they
might
become
like
they
are
all,
have
some
different
opinions.
G
I
just
think
it's
different
levels
of
abstraction,
so
I
think
it's
important
that
we
like
I,
don't
think
any
of
these
things
are
disagreements
and
like
that
they'd
be
valuable.
I
think
that
there's
different
speeds
of
feedback
loops
or
different,
like
abstraction
layers,
like
the
speed
at
which
you
need
to
be
moving.
G
If
you're
going
to
be
talking
about
specific
projects,
isn't
the
speed
my
brain
is
currently
working
on,
doesn't
mean
I
can't
in
the
future
and
like
it
doesn't
mean
I,
don't
think
it'd
be
fantastic
to
see
people
doing
that
work,
but,
like
I'm,
I,
think
the
white
paper
I'm
I'm
sort
of
chewing
my
way
down
the
stack
from
the
white
paper.
That's
the
way
my
brain
is
currently
working,
but
that's
why
we've
got
the
diverse
group
to
be
able
to
make
sure
that
we
we're
covering
the
different
angles
as
people
need
them.
So.
C
And
a
lot
of
it
is
as
far
as
going
back
to
the
one
comment
about
it:
kind
of
keeping
current
like
from
the
decision-making
point
of
view
like
the
decisions
you
have
to
make
generally
won't
change
like
the
decisions
are
going
to
be
pretty
static
or
the
the
decision
points
are
going
to
be
pretty
static.
What
solves
those
yes
are
going
to
rapidly
change
and
all
these
projects
are
going
to
change.
Some
of
them
will
merge.
C
Some
of
them
will
be
completely
gone,
so
the
kind
of
jumping
from
these
are
the
questions
I
have
to
solve,
and
this
product
at
this
point
in
time
will
solve
that
like.
That
is
a
specific
document
that
has
a
very
specific
shelf
life
versus
the
larger
Decision
Guide
of
we've
got
the
high
level
here
and
then
you
know
the
I
haven't
looked
at
it
yet,
but
the
maturity
Matrix,
you
know
the
next
level
down
and
then
below.
C
That
would
be
the
decision
points
for
how
do
I
navigate
some
of
the
the
structures
inside
of
the
maturity
Matrix,
and
then
you
can
have
a
current
like
this
is
for
summer.
2023
answers
for
our
decision
guide
and
then
keep
kind
of
occurring,
revisiting
that
and
so
again
having
that
level
of
abstraction
and
knowing
which
level
is
specific
for
which
purpose
is,
is
going
to
give
us
the
kind
of
the
best
longevity
there
and
applicability.
E
Yeah
I
was
just
thinking
as
well.
Just
a
couple
of
points
have
come
to
my
mind.
Just
through
this
conversation,
one
is
on
the
the
levels
of
abstraction
I,
see
that
as
well
and
agree
with
with
that
point.
E
Oh,
it's
just
a
couple
of
things
so
one
on
perhaps
on
the
language
side
and
on,
for
example,
the
definitions
perhaps
around,
for
example
policy
and
such
like
one
of
the
things
I
wonder,
is
just
thinking
about
the
wider
C
and
CS.
Is
they,
for
example,
there's
the
the
glossary
that
has
a
lot
of
definitions.
It's
been
populated
over
time
and
I
wonder
if
there
might
be
a
space
here
where
perhaps
some
of
the.
E
If
there
are
things
that
are
lacking
out
of
the
the
glossary
that
they
could
eventually
be
contributed
there,
and
vice
versa,
and
also
the
cloud
native
maturity
model
briefly
talks
about
things
like
policy
I'm,
just
using
that
as
an
easy
example
at
the
moment
and
then
just
I
wonder
as
in
a
discussion,
you
know,
you've
got
degrees
of
abstraction
and,
as
you
become
more
more
refined,
maybe
one
way
to
make
the
decision
easier
was
is
might
be
to
consider.
E
Well
if
there
is
going
to
be
discussion
of
tooling
things
that
are
graduated,
for
example,
are
really
great
candidates
to
be
discussed
because
they've,
they're
well
established
and
well
well,
understood,
and
maybe
part
of
the
job
starting
out
might
be
to
make
it
quite
easy
and
narrow
the
scope
and
don't
try
running
through
the
sandbox,
because
it's
changing
so
so
quickly
and
and
and
the
point
of
the
sandbox
is
that
some
of
those
may
not
ever
make
it
to
incubating
or
group
them
and
graduate
so
I'm.
F
I
think
what
you're
saying
makes
sense,
and
it
brings
up
even
more
questions
about
like
a
lot
of
these
tools
tie
into
cloud-specific
tools.
So
how
do
you
start
to
engage
in
even
like
those
like
dialogues
of
like
well?
What
is
kind
of
the
lines?
Stop
when
you're
sort
of
trying
to
talk
through
some
of
these
things?
It's
kind
of
those
are
some
of
the
conversations.
I
I
totally
agree
that
need
to
be
had.
A
So
I'm
kind
of
taking
away
from
both
of
these
conversations
that
it
might
help
to
have
a
bit
of
I
heard
from
Simon
like
saying
like
you
left,
placeholders
and
there's
things
to
be
filled
in.
Maybe
we
almost
create
a
matrix
and
I'm
kind
of
thinking
it
of
as
horizontal
things
like
the
paper
that
we
already
released
is
kind
of
the
Strategic
cross-cutting.
Even
the
maturity
model
is
kind
of
a
horizontal
cross-cutting.
A
There
may
be
even
another
layer
down,
that's
still
horizontal
cross-cutting,
but
at
the
same
time
the
capability
domains
and
decisions
within
those
they
almost
make
me
think
of
like
verticals
like
within
the
database
area.
You
know,
can
we
help
Define
choice,
choice,
decision
making
trees
within
those
verticals?
A
So
maybe,
if
like
I've,
almost
like
I,
don't
know,
maybe
in
the
website
structure
or
maybe
just
on
a
piece
of
paper
to
begin
with,
just
here's
the
things
we're
working
on
and
here's
where
you
can
fill
in,
like
maybe
there's
someone
really
passionate
about
observability.
That
wants
to
or
point
us
to
the
we.
You
know
the
tag,
observability
dock
on
it
or
something.
D
Yes,
for
the
gesture
and
I
think
the
one
thing
from
this
like
I,
think
when
the
kubernetes
started.
One
thing
I
really
like
about
this
notion
is
we
started
in
2014
2015.
when
there
is
so
much
containers
or
container
engine
being
popping
up
in
the
market
like
Joker
rocket
and
they're
they're,
so
much
what
cncf
does?
Is
they
actually
onboard
all
of
the
people?
D
Members
and
let
them
understand
how
you
define
the
container
engine
and
everybody
come
up
with
the
interface
like
there
should
be
an
interface,
irrespective
of
how
is
actually
being
implemented
by
the
local
low
level
abstract.
So
I
would
like
to
think
as
a
platform
Engineering.
In
the
same
way
like
we
can
like
we,
we
came
up
with
a
surveying
paper
with
some
of
the
folk
we
already
create
some
survey.
D
Google
talks
from
people
fill
in
survey
like
I
think
like
what
is
actually
really
interesting
to
understand,
like
we
have
the
full
knowledge
of
all
the
terminology
or
the
term
the
coins
being
termed
out
in
the
brighter
umbrella,
like
shift
left
shift
down
self-service
all
these
terminology
we
have
the
bigger
overview
of.
We
can
actually
add
the
document
or
the
talk
that
people
can
understand.
These
are
the
things
we
actually
need
to
think
about
it.
D
Then
we
have
some
definitions
if
that
visible
in
the
paper
that
has
a
great
reflection
on
the
reader
of
that
paper
as
well,
because
usually
what
people
think
about
white
paper
is
like
this
is
the
bigger
organic
bigger
user
group
that
Define
the
terminologies,
but
once
they
see,
some
terminology
is
being
coined
up
from
the
outer
side
like
they
feel
like
they
have
this.
There
are
two
notion
going
on
so
like
I,
think
like
like,
as
as
Josh
mentioned,
might
have
Matrix
of
different
I
see
their
internet.
D
There
are
some
metrics
available,
we're
going
to
use.
Those
metrics
like
here
are
the
different
terminologies
being
going
to
wind
up
in
the
marketplace,
but
like
I,
think
what
I'm
thinking
here
is
currently
in
this
moment
of
time
when
I've
been
trying
to
submit
a
PR
in
the
paper
is
like
platform.
White
paper
should
be
an
interface
to
the
people
who
think
about
the
platform.
So.
A
D
Light
I
think,
like
is
like
is,
is
a
thinking
prospectus
like
the
client
like
like
they
pursue
this,
to
be
an
interface
like
they're,
giving
us
a
knowledge
about
the
platform
engineering
and
we
have
full
opinion
of
agreed
or
desegreated,
like
that's
the
same
terminology
being
blind
up,
but
the
cloud
at
a
maturity
model
in
the
blast
like
they
said,
we
give
you
the
thinking
point
of
how
the
cloud
maturity
have
to
think
about
it.
It's
up
to
you.
D
But
this
group
has
to
do
challenge
so
that
is
actually
expectation
from
the
public
audience
for
us.
So
my
thinking
it
is
active
at
the
weight
the
communication
going.
You
have
to
think
about
like
what
the
cloud
at
a
maturity
model
does
when
the
one
of
the
there
are
several
meetings
like
think
about
us.
As
we're
giving
you
the
knowledge
of
how
you
think
about
Cloud
native
maturity
model
is
up
to
you,
agree
or
disagree,
make
some
assumption
about
it.
D
It's
totally
fine
and
if
you
find
some
adjustment
to
be
make
in
the
maturity
model,
suggestion
appreciation
feedback
is
always
welcoming.
So
that
is
where
we
actually
go
like
we.
We
develop
a
implementation,
mind
thinking
or
platform
thinking,
so
this
paper
is
giving
you
the
knowledge
about
how
you
think
about
the
platform,
so
I
think
that's
the
easier
road
to
go
through.
A
A
Cool
I
mean
I'm
taking
definitely
take
away.
Thank
you
for
your
seconding
Abby.
You
try
to
create
a
skeleton,
so
people
can
fall
in
and
do
the
things
that
they're
passionate
about,
because.
F
A
G
Of
people
we've
got
a
thing
around
updating
the
website
with
some
of
the
ongoing
projects
right
so
I
could
possibly
make
an
update
to
that
issue.
Just
to
I,
don't
know
who's
who's
kind
of
working
on
that,
but
I
can
at
least
make
an
update
to
what
we
chat
about
here.
To
make
sure
that
when
the
update
happens,
it's
thinking
in
this
structure
a
bit
so.
A
G
Thanks,
so
it's
a
restructuring
tag,
so
yeah,
yeah
and
I
think
Colin
yeah
responded
to
it
and
I
was
just
saying
that
I'd
been
recommended
to
do
that.
So
yes,
on
board,
so
yeah
I'll
make
an
update
as
to
like
yeah
just
seconding
and
that
it
was
and
possibly
introducing
this
kind
of
structure
of
Fidelity
or
detail
that
we're
talking
about
here
for
the
different
things
we're
working
on
cool.
A
Thank
you
Abby
stress
the
last
item
that
we,
the
last
two
I'm
gonna
skip,
but
there's
same
you
put
down
also
how
to
measure
successive
platforms.
Do
you
want
to
talk
about
I
think
we
have.
You
know
a
couple
more
minutes
here
if
everyone's
okay
with
that
is
there
anything
else,
we
want
to
talk
about
I'm,
fine,
with
talking
about
that
for
the
last
few
minutes,.
D
Yes,
I
think
like
I
I've
scrolled
through
I've
met
I
I
created
some
of
the
diagram
created
some
of
the
materials
in
there
for
the
mayor
with
the
platform.
I
think
that
is
where
I
see
a
challenge
in
the
ecosystem.
Is
that
I'll
read
about
all
the
content,
what
they
think
about
it?
Look
at
the
various
different
sources.
What
they
is
a
challenge
like
the
key
performance
indicator,
is
always
being
different
here.
D
That
is
a
big
pain
point
I'm
talking
to
the
coverage
or
my
podcast,
and
we
did
a
talk
on
the
same
title
had
he
mentioned,
like
user
friendliness,
developer
happiness
like
what
we
actually
mmgr
cffr
that
we
actually
think
about
it.
When
I
talked
to
another,
a
Rowdy
team
in
the
past,
they
have
completely
different
set
of
opinion
of
measuring
the
success
like
they
think
about
mostly
around
backstage.
Think,
and
then
you
talk
to
and
I
look
at
the
Go
poet
team
of
dear
thinking
point
of
how
they
measure
it.
D
It's
completely
different
right
now.
Currently,
what
I'm
doing
is
regardless
telling
like
everybody,
is
bad.
This
is
not
a
good
thing
of
my
hearing,
I'm
actually
congesting.
All
the
data
in
one
document
like
what
are
the
different
thinking
point
of
view
to
the
people.
So
when
we
have
all
these
document,
data
available,
I
will
share
with
the
team,
not
just
a
very
huge
200
of
people,
just
the
terminologies,
just
a
20
or
300
terms
that
people
think
about
it.
Then
we
actually
debate
on
like
from
300
words
or
400
words
or
400
terms.
D
What
to
concatenate
in
our
platform
white
paper,
because
it's
not
possible
to
add
300
terminologies,
it's
so
so
confusing
I've
actually
been
letting
people
know
like
tell
us
what
you
think
about
how
to
measure
it
even
include
all
that
data
So.
Currently,
my
planning
with
the
last
next
last
two
months
is
totally
around
concatenated.
D
All
then
I
data
in
one
place
and
think
about
it,
and
that's
why
I'm
thinking
like
this
is
the
topic
we
should
pursuing
the
cfp
and
submission
form,
because
that's
a
huge
number
of
audience
available
that
give
us
a
huge
visibility
like
according
to
what
we
actually
learned
from
this
group.
This
is
our
Matrix
for
the
measurements
platform
and
platform
thing,
and
that
from
that
we
can
actually
carry
this
behave
forward.
That
might
be
a
good
approach
to
think
about
it,
but
I'm
open
to
see
what
our
other
things
about
it.
A
I
mean
I
think
this
is
great
I
think
we
had
a
little.
This
was
a
struggle
for
us
in
the
paper
someone.
Actually,
we
didn't
really
have
very
much
measures
in
there
to
begin
with
and
the
feedback
was
you
need
to
have
something
around
us,
and
so
you
know
we
didn't
we.
We
did
put
the
door
up
metrics
in
there,
but
we
wanted
something
bigger
than
that,
and
so
we
developed
kind
of
a
thesis
of
our
of
our
own
I
think
to
some
degree.
So
we
we
definitely
want
feedback
I
posted
in
there.
A
You
know
how
to
measure
what
we
put
down.
I
think
you
know,
Mauricio
had
some
comments
there
and
you
know
stuff
like
that.
But
there's
a
lot
of
room
to
to
vet
that
and
make
sense
I
mean
we
saw
the
same
thing
that
you're
describing
saying
there
were
a
million
there
weren't
that
many
thoughts
actually
on
it,
which
is
the
same
thing
as
there
being
a
million
in
some
ways
like
everybody
was
trying
to
everyone's
still
trying
to
think
about
it.
So
that's
awesome
that
you're
doing
that.
A
A
Yeah
and
overwrote
down
the
feedback
is
key
yeah.
Exactly
that's.
You
know
we're
running
the
survey
and
like
if
people
are
passionate
about
that,
like
I
could
use
a
I
mean
Michael's
helping
on
the
survey
he's
not
here
on
this
call
now,
but
we
could
leverage
that
more
and
people
are
offering
to
talk
to
us,
but
we
need
to
follow
up
with
them.
We
kind
of
need
to
interview
framework
of
some
sort
if
anyone's
passionate
I
mean
I
I,
don't
want
to
say
I
gonna
do
that,
but
I'm
gonna
try
to
help
right
now.
G
G
People
working
on
the
community
side
of
things
that
maybe
would
be
good
people
to
get
involved
in
that
as
well
right
because,
if
they're,
the
ones
making
the
connections
with
people
also
doing
some
of
the
interviews
and
things
I
think
is
I
mean
don't
speak.
Four
people
are
saying:
that's
a
good
group
of
a
good
group
of
humans
to
talk
to
you
about.
If
we
need
need
more
support
on
the
kind
of
interview,
side
and.
A
D
I
actually
chatted
about
something
on
their
Twitter
and
I'm.
Encouraging.
Please
join
this
chapter
because
this
is
created
for
this
discussion.
So
we'll
have
it,
though
I'm
trying
very
hard
to
give
some
people
on
board,
but
we're
glad
language
connected
very
wonderful,
individual.
Every
new
week
some
new
faces
some
new
minds.
Yeah,
that's
a
great
thing.
A
Yeah
I
mean
I
think
that
one
of
our
I
think
that
is
actually
one
of
the
ways
people
can
contribute
to
our
group,
and
you
know
we
try
to
bring
this
up
a
little
around
kubecon,
it's
hard
to
say
that
but
like
if
somebody
has
a
story
from
their
own
organization
like
we
should
have
it
on
the
agenda,
and
we
will
I
mean
certainly
in
this
group,
we'll
give
them
10
or
15
minutes
and
want
to
learn
from
them
so
break
bring
them
in.
That's
the
I
forget
the
survey.
A
D
A
So
you
might
want
to
talk
with
Leanne
she's
kind
of
thinking
about
her
and
Jorge
about
some
sort
of
newsletter,
but
maybe
it's
not
a
newsletter.
Maybe
it's
a
blog
post
every
couple
weeks.
You
know
here's
the
topics,
we
talked
about.
Here's
a
couple
latest
trends
and
remember:
please,
come
and
share
with
us.
You
know
that's
how
we're
learning
or
something
like
that.
A
D
Absolutely
I'm
helping
to
see
what
this
did,
but
definitely
that's
a
wonderful
insight
as
well,
because
I'm
running
a
cube,
Weekly
Newsletter,
because
I
don't
have
anything
to
place
in
there
from
this
discussion.
So
having
blog,
is
very,
very
important,
because
now
we
have
a
website
available.
So
you
utilize
our
blog
on
that
posting
as
well.
We
can
do
some
like
because
it
can
be
automated,
like
everybody
can
write
a
blog
post
submitted
to
the
GitHub
repository
and
GitHub
action
triggering
and
that's
publicly
available.
That's
how
the
all
the
open
source
project
are
doing.
D
A
G
Should
say
I've
got
I've
got
to
pop
away,
so
I
was
just
gonna,
say,
I
didn't
know
if
you
need
the
time
the
time
check,
but
yeah
I
will
see
you
all
in
a
few
weeks,
hopefully
sooner
some
of
the
other
events.