►
From YouTube: WG Platforms Project Meeting - 2023-01-18
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
D
A
Winter,
for
me
too,
although
not
too
bad
here,
I'm
in
Chicago,
so
now
we're
at
around
zero
healthiest
and
that's
actually.
D
D
D
Yeah
I
actually
I
finished
my
MBA
from
Kellogg
in
in
June.
So
it's
been
here
and
then
my
fiance
has
one
more
year
left
at
Kellogg,
so
I
guess
I'm
in
Evanston
congrats.
F
A
A
All
right
I'll
share
the
the
dock
here.
Oh
that
one
knows
where,
where
we're
taking
notes.
F
A
A
Is
it
first
kind
of
discuss
how
to
you
know
now
that
we've
got
the
the
paper
on
GitHub
and
stuff
talk
about
how
we
want
to
collaborate
there,
a
bit
of
a
change
from
the
Google
Doc
we've
started
to
pick
up
sections,
so
I'm
kind
of
thinking
after
we
talk
about
that,
we'll
go
through
each
section,
and
if
people
want
to
own
it
great,
if
there's
something
hot
that
we
need
to
talk
about
on
it,
we
can
and
then
maybe
set
some
dates.
You
know
just
to
give
ourselves.
A
You
know
where
we're
going
towards
light
a
fire.
Okay,
so
I'm,
just
gonna
yeah
I'm,
just
gonna.
Those
are
just
agenda
here.
So
the
first
thing
is
procedures
for
edits
Abby.
Now
that
I
were
discussing
oh
yeah.
G
No
sir,
sorry,
sorry
I
just
cross,
communicate
cross
conversation
here,
no
worries,
oh
okay,.
A
Yeah
just
feel
free
to
jump
in
and
stop
me
or
I'll.
Just
keep
on
going
procedures
for
added,
so
one
thing
abhinav
and
I
were
discussing
is
how
to
like.
If
we
have
a
chunky
edit
and
what
I
was
thinking,
is
we
submit
PRS
against
that
branch?
And
then
we
can
chat
in
those
I
was
thinking
like
meteor
topics,
or
you
know
we
can
talk
either
in
the
issues
that
are
per
section.
A
If
it's,
you
know
a
couple
things
or
we
could
open
other
issues
or
discussions
and
then
something
that
worked
for
me
in
node.js
a
long
time
ago
was
we
would
tag
if
there
was
a
hot
item
that
we
wanted
to
discuss
in
like
a
broader
meeting.
So
we
would
just
tag
that
and
then
we
would
just
have
a
list.
So
you
know
if
something
hot
comes
up
and
you
want
to.
A
E
A
E
A
That
would
maybe
that
would
help
to
do
that
next
I'll
move
it
up.
This
is
just
a
proposal
again
I,
just
yeah,
I,
better
or
worse,
I,
always
like
to
think
over
what
we're
going
to
discuss
before
we
come
in
so
I
kind
of
thought
over
like
if
we,
if
you
if
but
it's
relevant.
If
you
want
to
take
responsibility
for
a
section,
I'm
kind
of
thinking,
let's
get
them.
You
know
edit
ready
draft
ready,
Pub.
A
You
know
near
publish
ready
by
the
end
of
February,
March,
1st
and
then
take
you
know
that
gives
us
a
month
to
kind
of
make
sure
that
things
are
consistent.
Go
over
the
last
details,
get
like
a
real
copy
Editor
to
go
over
it.
A
I
did
open
a
thread
with
the
pr
Folks
at
cncf
and
they
basically
said
like
it's
up
to
us.
There's
no,
you
know
learn
from
other
folks.
If
we
want
yeah,
we
could
talk
about
that.
One
thing:
that's
really
cool
that
Colin
was
just
texting
me
is
that
at
least
I
think
it's
cool
is
what
the
the
cartoon
graphos
the
cloud
native
maturity
model
folks
did,
which
is
basically
create
a
small
website,
static
website,
I
guess,
yeah.
A
H
A
Go
cartographers
work
and
then
yeah,
okay,
so
yeah,
so
let's
jump
into
the
actual
content
and
I'll
just
work
from
these
milestones.
A
So
this
kind
of
lists,
the
sections
that
we
came
out
with
that
was
kind
of
one
of
the
top
goals
of
the
initial
dot-
was
to
kind
of
get
consensus
on
what
are
the
core
sections
here
so
now.
What
we
need
is
you
know,
keeping
in
mind
that
our
our
goal
for
this
first
paper
is
to
kind
of
build
the
market
for
platform
engineering
to
kind
of
help.
A
You
know
executive
leaders,
Enterprise
Architects
stuff,
like
that,
build
the
case
themselves
pitch
the
case
to
others
so
I,
just
eventually
that's
a
link
when
you
take
leadership
of
one
of
these
sections
like
well,
keep
that
in
mind
so
yeah.
Let's,
let's
go
through
and
talk
about
that
I
guess
the
first
one
is
what
is
a?
What
is
a
platform
which
kind
of
came
up
in
the
thread
with
Abby
from
from
the
Team
topology
Stokes
yeah?
A
What
this
is
more
of
an
intro,
because
we
do
get
it
to
like
attributes
to
the
platform,
because
this
is
more
I,
guess
generally
to
kind
of
set
the
stage,
and
you
know
the
first
layer
of
the
onion
I
know
you
had
volunteered
in
here.
I
did
not
get
a
chance
yet
to
read
over
what
Thomas
had
written
there,
we
could
have
more
than
one
owner
too
I
mean.
D
Yeah,
absolutely
you
should
definitely
be
you
know,
collaborative
right
and
yeah
I'm
sure
you
know
folks
will
want
to
contribute
to
multiple
sections
as
well,
so
I
think
we
should
definitely
have
that
I.
Think
no
in
the
what
is
a
platform
section
I
think
it
might
be
good
to
kind
of
have
like
some
parts
about
like
what
are
the
personas
involved
right
and
and
where
I
was
thinking.
There
is,
you
know,
I
think
I
definitely
think
they're.
You
know
when
we
think
about
the
platform.
D
D
Sure
access
is
secure,
like
a
bunch
of
things
that
they
need
to
figure
out
on
there
and
right
for
the
platform
to
scale
right
and
and
and
it's
like,
how
is
the
platform
consumable
by
the
platform
admin
or
by
whoever
is
managing
this
from
the
SRE
or
it
point
of
view
right
and
so
I
think
kind
of
ties
in
with
what
Thomas
was
commenting
right.
There
is
a
you
know.
Idp
is
definitely
one
part
of
it.
I
think
there
are
other
parts
of
it.
D
For
example,
maybe
you
know
you're
if
you're
using
kubernetes,
potentially
like
a
kubernetes
governance
layer?
Is
there
author
you
have
to
take
care
of
because,
if
you're
serving
multiple
personas
they're
running
on
the
same
infrastructure
or
on
the
same
platform,
then
there's
there's
different.
You
have
to
take
care
of
auth
as
well
to
make
sure
like
you
know,
certain
certain
users
might
have
different
responsibilities
on
the
platform
itself,
as
well.
So
I
think,
like
I,
think
from
that
stance,
probably
some
at
least
from
my
eyes.
D
There
could
be
a
way
we
could.
Maybe
you
know
talk
about
the
personas,
their
pain
points
a
little
bit
and
then
try
to
tie
it
into
like
and
I.
Don't
know
if
this
is
the
right
section
to
do
it,
but
it
was
just
kind
of
kind
of
my
two
cents
and
yeah
yeah.
E
I
think
the
one
concern
is
that
that
is
like
the.
What
I
hear
you
saying
is
exactly
what
the
whole
paper
is
trying
to
achieve,
and
this
is
like
the
intro
section.
So
how
do
we
set
the
stage
well
for
each
of
those
points
to
be
properly
covered
like
in
their
sections,
because
you're
right,
like
we,
don't
mention
some
of
those
things
in
here,
and
so
does
that
mean
that
they
get
kind
of
hidden
in
their
subsection?
So
how
do
we
like.
E
D
That's
that's
like
one
or
there's
no
self-service
model
right,
so
they
have
to
have
always
have
always
have
like
Ops
intervene
right,
that's
kind
of
like
a
higher
level
pain
point
that
facilitates
the
need
for
a
platform,
for
example
right
and
then
once
we
talk
about
like
what
is
a
platform,
then
there's
challenges
with
platforms,
attributes
of
platforms,
capabilities
of
platforms,
I.
Think,
then
that
could
line
up
well.
D
E
Think
to
your
point:
Josh
about
Matthew:
yes,
Matthew,
you
think
they
respond
to
me.
Somebody
respond
to
me
from
Team,
topologies
I
think
that's
their
concern
with
our
paper.
E
If
I'm
honest
is
that
we
are
saying
a
platform
is
only
a
platform
if
it
is
self-service
and
automated
and
doesn't
involve
Ops
and
has
all
sorts
of
and
and
covers
everything
to
do
with
the
cloud
and
all
that
and
I
think
so,
in
my
opinion,
like
a
platform,
it's
that
what
they're
trying
to
get
across
to
me,
I,
think
and
I'm
reading
in
between
the
lines
from
having
read
the
book
and
have
a
bit
of
a
sense
of
where
they're
coming
from.
But
I
could
verify
this
with
them.
E
But
I
think
what
they're
trying
to
say
is
a
platform
is
a
place
to
go
for
Solutions
that
place
to
go
for
Solutions
might
be
a
jira
project
with
templates
for
asking
for
things
to
start
with
right,
and
what
we're
saying
is
is
that
we've
seen
why
that
could
lead
to
bottlenecks
at
certain
scales
and
at
certain
requirements
and
things
and
and
we
are
providing
solutions
for
how
to
make
that
better.
But
I
think
so.
E
E
Do
we
want
to
go
with
the
hey
platform
as
a
single
place
to
go
and
by
the
way
you
if
these
are
the
things
you're
going
to
want
to
do
as
you
scale
that
platform
so
you're
going
to
make
it
self-service
and
all
these
things
or
do
we
want
to
jump
kind
of
straight
past?
That
sort
of
entry
level
point
and
go
to
like
a
platform
is
self-service
which
I
think
I
per?
E
Like
my
personal
opinion
on
that,
when
we're
talking
about
Enterprises,
which
Josh
you
know
reminded
us
that
that's
our
kind
of
target
audience
here
is
like
Enterprise
Architects
and
things
like
that,
I
think
it's
it's
I
see
both
sides
because
a
lot
of
those
Enterprises
they
can't
just
stop
on
a
dime
and
pivot
to
like
100,
automated
shiny,
new,
perfect
platform.
So
talking
about
the
fact
that
a
platform
is
about
collating
all
of
the
like
offerings
that
you
have
and
some
of
them
are
going
to
be
a
bit
more
self-service
than
others.
E
Maybe,
but
it's
like
a
a
place
where
you
can
go
to
to
look
for
help,
might
land
quite
well
with
Enterprises,
but
at
the
same
time
we
don't
want
to
feel
too
too
comfortable
in
their
world
of
large
tickets
and
large
queues
and
all
that
kind
of
stuff.
So
it's
sort
of
a
I,
don't
know
I,
see,
I,
see,
I,
see
both
sides
a
bit.
D
The
more
important
metric
is.
How
do
you
reduce
the
time
it
takes
for
developers?
You
know
to
ultimately
get
to
their
end
goal,
whether
that's
you
know,
spinning
up
environments
or
testing
application
changes
whatever
that
thing
is
right
and
so
I
think
the
pain
points
at
the
top
would
be
great
to
have
those
a
little
bit
kind
of
higher
level
and
as
you're
saying
Abby
like
very
Enterprise
oriented.
D
So
it's
kind
of
it's
not
diving
too
deep
into
like
here's,
the
exact
model
that
you
have
to
fit
as
a
company
right,
because
every
every
company
and
every
industry
is
going
to
be
so
different
at
the
end
of
the
day
and
like
we're
here
to
provide
recommendations.
It's
my
guess,
but
probably
like
in
some
example.
Like
you
know,
best
practices,
but
not
like
have
them
say
that
hey
self-service
is
the
requirement
necessarily
right.
A
So
so
I
want
to
just
just
kind
of
go
through
I
I
hear
what
you're
saying
I
mean
I
have
a
lot
of
the
you
know,
it's
good
to
call
out
what
the
motivations
are,
I,
guess
or
why
people
would
want
to
platform.
I
kind
of
thought
you
know.
A
Maybe
it
would
help
to
like
look
through
these
holistically
and
that's
why
I
brought
up
my
screen
here
and
kind
of
the
story
that
we're
we're
telling
because
I
also
am
kind
of
thinking
like
some
of
those
things
would
fit
well
into
some
of
these
upcoming
sections.
So
what
is
the
platform?
Is
kind
of
you
know,
laying
the
foundation
but
like,
for
example,
why
platforms
is
really
talking
about
the
the
things
that
it's
all
you
know.
The
platform
is
also
going
to
answer
the
problems
that
people
are
hitting
reduce
risk
of
security.
A
F
A
I
mean
this:
this
person
was
gonna,
reflect
everything
kind
of
so
I
kind
of
thinking.
Maybe
like
your,
why
platforms
you
might
be
able
to
put
in
like,
in
fact
we
might
even
retitle
this
to
you
know,
motivations
for
platforms,
platform,
attributes
also
kind
of
has
these
these
eight
qualities.
You
know
things
like
self-service,
consistent
interfaces,
documented,
automatable,
I'm
kind
of
thinking
that
you
know,
maybe
maybe
we
should
explore
those
first
rather
than
putting
them
into
the
into
the
top.
A
Maybe
let's
keep
going
down
the
rest
of
them
and
see
how
this
goes.
So,
let's
go
to
Y
platforms
like
so
this
one
yeah
I'll,
just
open
it
here
is,
is
motivation.
This
is
you
know
what
motivates
what.
A
F
A
Whether
it's
you
know
security
or
regulation,
whether
it's
saving
money,
faster,
Innovation,
that's
kind
of
the
stuff
that
goes
in
here,
I
think
in
particular
here
use
cases
like
I
feel,
like
I'm,
I'm
short
of
my
use.
Cases
are,
you
know,
put
up
a
development
environment,
do
some
observation,
but
but
maybe
there's
something
more
specific
or
we
can
elaborate.
There.
A
G
Rob
I,
wonder
I,
wonder
if
this
is
the
area
to
include
include
the
section
about
the
or
or
maybe
Frame
It
From
perspective
of
developers
wanting
to
use
things,
because
the
use
case,
because,
like
because
I
think
for
this
first
point
one,
maybe
a
reduction
is
very
simple
way
of
saying
this
could
be
that,
like
developers
need
need
thing
to
use
the
like,
they
want
to
use
capabilities
of
the
platform,
but
they
think
about
these
as
features
because
they
like
when
a
developer
wants
to
like
wants
to
run
their
workload
like
they
think
like
I
need.
G
Postgres
database
like
I
need
a
database
they're,
not
thinking
about
the
the
totality
of
the
complexity
involved
in
making
sure
that
the
the
database
exists
or
how
this
comes
to
existence
or
like
what
is
the.
What
are
all
the
pieces
that
it's
wired
into?
What
they
appreciate
from
the
platform
when
consuming
their
platform
is
that
I
can
just
use
a
database
and
the
platform
takes
care
of
the
complexity
of
that
like
that
is
the
the
ease
of
use
of
that
of
being
able
to
use.
G
It
is
the
value
that
the
users
get
and
I
wonder
if
there's
a
like,
if
there's
a
way
to
maybe
maybe
this
is
the
section
where
to
kind
of
include
that
I'm
not
sure
what
your
thoughts
are
about.
This.
C
F
A
G
Yeah
that
that's
that's
the
value
that
that
developers
are
looking
to
get
from
the
platform
like
they
they
want
to.
They
want
to
play
with
the
rules.
They
want
to
get
their
work
done.
They
don't
like
they
wanted
to
work
easily
for
them.
They
don't
necessarily
have
an
opinion
of
how
the
platform
team
gets.
That
done.
G
I
think
that
that
separation
between
the
desire
to
just
use
the
platform
versus
the
complexity
of
fulfilling
those
that
the
ability
to
to
think
about
the
platform
in
that
way
is
actually
what
the
platform
provides.
G
That's
actually
a
benefit
of
the
platform
as
a
developer
can
think
about
the
platform
this
way,
because
the
flip
side
to
that
is
what
we
see
with
some
of
our
clients,
where
the
platform
exposes
terraform
as
a
way
of
provisioning
and
now
to
get
anything
done,
they're
getting
into
like
the
networking
layer
of
how
the
how
the
database
becomes
available
to
their
workload
and
they're,
just
like
I,
I,
I,
I
I
didn't
come
here
for
this.
You
know
so
it's
I,
don't
know.
G
If
that's,
if
there's
a
way
to
kind
of
highlight
that
that
quality
of
the
platform
being
something
a
developer,
can
use
without
having
to
think
about
the
details,.
H
I
wonder
if
it
just
means
expanding
a
little
bit
on
the
cognitive
load
piece
there
in
the
first
Hub.
It's
exactly
what
you
guys
are
saying
like
it
gives
us
a
framework
to
operate
within.
It
gives
us
kind
of
a
rule
book.
H
It
tells
us
how
we
need
to
do
things
and
gives
us
the
tools
to
do
those
things,
and
so
then
I
don't
have
to
think
about
it,
like
sometimes
developers
just
want
to
be
told
what
to
do
or
how
they
should
do
something,
and
the
platform
gives
me
a
framework
to
do
that
with
them,
and
I
can
follow
the
rules
and
get
what
I
need
right.
H
So
maybe
cognitive
load
is
just
a
little
bit
too.
You
know
Petty,
but,
however,
you
want
to
say
that.
F
E
If
I'm
right,
you
were
trying
to
aim
to
get
like
people
who
could
help
Shepherd
those
kind
of
either
a
person
or
a
pair
of
people
to
help
with
each
of
those
like
eight
sections.
Is
that
what
the
kind
of
goal
of
this
I
don't
know
if
we
want
to
try
and
workshop
the
the
stuff
in
this
meeting
or
if
we're
trying
to
get
like
figure
out
who's
going
to
be
able
to
Workshop
them
in
this
meeting?
What's
your.
A
A
You
know
against
that
section
of
the
paper,
and
you
know
elaborate
on
this
if
we
feel
it's
appropriate,
but
but
folks
I'm
looking
here
so
I'm,
looking
to
kind
of
figure
out
how
we're
going
to
go
forward,
but
also
yes,
I
would
like
someone
to
that
feels
passionate
about
defining
that
I'm.
Making
sure
this
is
the
right.
Yeah
just
drop
your
name
in
here,
we'll
put
you
down
as
a
sign.
D
D
Sir
and
I
think
what
we
can
do
is
we
can,
you
know
folks,
want
to
contribute
to
a
specific
section
Abby,
if
you're,
okay
with
it,
what
maybe
they
could
just
comment
in
that
specific
thing
saying,
like
you
know,
I'd,
you
know
I'd
like
to
contribute
to
this
thing,
and
then
we
can
kind
of
have
like
a
joint
working
sessions
over
over
Zoom.
D
Just
you
know,
kind
of
you
know
kind
of
on
the
side
just
to
just
to
kind
of
work
on
these
things
together
as
a
as
a
team,
I
think
that'd
be
a
nice
kind
of
collaborative
way
to
do
it
as
well.
Absolutely.
E
Like
I
I
think
might
be
best
to
try
and
get
as
much
as
we
can
and
in
like
kind
of
the
collaboration
in
GitHub
rather
than
requiring
video
calls
just
because
of
time
zones
and-
and
things
would
be
personally
that
would
work
out
a
little
bit
better
for
me
and
also
allow
you
to
kind
of
be
informed
about
more
than
one
section,
rather
than
needing
to
be
like
kind
of
all
in
on
a
section
to
like
understand
how
it's
evolving
a
bit
but
I
think
that's
sort
of
the
like.
E
If
there's
someone
who's
helping
Shepherd
something
along
that
that's
like
sort
of
part
of
what
they
can,
they
can
help
do
I.
Think
from
my
perspective,
Josh
I'm
happy
to
help
with
any
or
any
of
these.
So
like
I,
don't
I'm
not
going
to
throw
my
name
into
any
one
of
the
sections
as
like
I
I,
absolutely
feel
like
that's
the
section
I
most
want
to
to
help
make
sure
wraps
up
nicely.
E
B
So
Josh
I'm,
just
thinking
about
like
I,
think
I
believe
when
you
start
working
on
the
papers
like
this.
What
we
are
working
on
there
are
some
of
the
stuff
that
is
actually
make
available
in
the
different
places,
but
the
sequence
of
words
and
the
sequence
of
how
you
define
and
how
you
portray
is
change.
So
what
I
feel
like
there's
some
of
the
stuff
is
our
lie
between
some
of
this
so
watch.
Let's
say
we
talk
about
why
the
platform
which
talk
about
the
wider
platform,
but
some
of
the
stuff
is
actually
correlate
with.
B
Let's
say,
platform
team
attributes
and
those
stuff
might
be
added
into
the
why
the
platform
section
is
but
I
think
some
of
the
sections,
if
only
let's
say
the
wire
platform
section
is
owned
by
one
person,
so
it's
mean
he's
only
working
on
that
part,
so
in
moving
forward
anybody
else
can
make
changes
into
it.
So
if
we
have,
if
team
members
try
to
add
on
different
places,
so
we
might
wind
up
end
up
having
same
thinking
on
the
different
section
of
the
paper.
So
I
think
that
we
need
to
figure
out
is
well.
I
And
may
I
add
something
as
well:
I
I
just
wanted
to
make
a
comment
about
what
we're
discussing
right
now,
which
is
I
I,
think
we
we
can
all
work
on
every
part
of
the
document.
I
think
we
should
just
like
make
sure
that
we
keep
the
same
tone
throughout
the
entire
document,
but
I
feel
like
the
idea
of
having
one
person
responsible
or
one
or
two
people
is
just
to
make
sure
that
you
know
the
suggestions
that
get
in
there
edited
correctly.
I
You
know
like
just
just
like
it's
more
administrative
work
that
is
about
you
know,
curating
the
content
of
it
I
think
that
is
more
like
a
like
a
team
effort,
but
I
I
do
feel
like
if
we
just
say
like
oh
everyone's
just
doing
everything,
then
there
will
be
sections
that
maybe
someone's
just
like.
Maybe
that
are
just
not
as
interesting
to
all
of
us.
That
just
will
be
neglected.
So
I
do
think,
like
one
person
to
be
responsible
for
a
section
is,
is
important.
I
think
that's
a
better
way
to
go.
B
Yes,
absolutely
absolutely
that's
some!
That's
why
I'm
that's
my
concern
was
absolutely
like
somebody
owned
the
correct
order
of
the
suggestion
being
made
to
this
paper
and
they
will
make
sure
like
what
the
previous
history
and
what
the
next
history
was
to
make
sure
the
changes
are
reflected
appropriately.
F
A
Is
not
the
only
person
thinking
about
the
content
and
their
first
responsibility
is
make
sure
that
we
Gather
in
the
feedback,
integrate
it
and
that
we're
ready
to
go
I
guess
at
the
end
of
February.
A
You
know
so
on
that
point.
Maybe
it
would
help.
There
are
two
I
know
in
particular,
which
could
use
some
work
platform.
These
were
added
later
platform
challenges
which
are
you
know
the
summarized
list
right
now
of
things
that
you
know,
platform
adopters
might
run
into
I.
Think
we're,
including
that,
because
we,
you
know,
our
goal
is
to
support.
You
know
Enterprise,
Architects
and
adopters,
and
when
they
hit
these
challenges
best
to
know
in
advance
that
they're
going
to
hit
them
or
try
to
avoid
them.
A
So
they're
not
discouraged
could
use
some
leadership.
There
say
measuring
success.
This
one
is
particularly
weak.
It's
mostly
links-
and
you
know
some
known
things
like
doordome
metrics.
But
if
somebody
has
you
know,
I
don't
know.
I'd
almost
want
to
put
a
case
study
or
you.
A
For
are
these
the
right
things?
Are
we
capturing
there's
tons
of
Articles
out
there,
but.
A
And
then
metrics
too,
and
this
one
you
know,
I'll
bring
it
up
right
here
we
had
some
suggestions,
things
like
time
for
a
new
contributor
to
get
to
their
10th
PR.
That's
a
Spotify
metric.
Here's,
the
Dora
metrics
a
couple,
people
reach
out
and
I.
Could
you
know
if,
if
so,
the
goal
of
this
is
also
to
again
inform
those
architects
of
leaders
like
okay,
so
they
want
to
do
platforms,
but
they're
not
going
to
go
into
it
blindly.
A
What
are
the
things
they
should
be
looking
for
to
show,
there's
some
feeding
or
or
the
opposite
I
actually
had.
There
was
somebody
on
there's
a
couple
people
doing
research
into
you,
know,
developer
experience
and
how
to
measure
developer
success.
You
put
people
in
contact
like
the
Microsoft
folks
that
did
the
space
framework.
D
So
I
think
here
as
well
in
the
metric
section,
be
happy
to
take
a
look.
I
think
that
the
thing
is
there's
there's
kind
of
some
metrics
for
your
developers,
as
well
as
as
a
platform
team
like
continuously
improving
right,
so
I'm
sure,
there's
some
kpis
that
we
can
come
up
with
here
and
also
in
terms
of
the
challenges
to
one
one
big
one
that
I
was
I
was
thinking
about
is
you
know
we
mentioned
a
lot
of
the
capabilities
and
Source
tooling,
which
is
great
right.
D
I,
think
you
know
we
want
to
make
it
as
open
as
possible.
There
is
a
challenge
on
the
platform
teams
to
stitch,
all
of
that
together,
right
and
and
continuously.
You
know
enforce
that
upgrade
scale
like
all
of
those
kind
of
challenges
that
you
know,
a
platform
team
will
have
to
deal
with
at
some
point
right,
especially
as
they
introduce
more
and
more
capabilities
onto
the
platform
and
so
I
think
there's
some
way.
We
could
probably
tie
those
two
together
like
hey
here's,
a
challenge
when.
D
To
those
you
know
a
lot
of
these
open
source-
tooling,
here's
some!
You
know
success
metrics
that
can
allow
you
to
and
adhere
the
kind
of
things
you
need,
as
you
scale
further
out,
or
integrate
more
or
more
capabilities
into
your
platform,
potentially
potent.
This
is
some
just
you
know
to
my
two
cents,
but
something
we
can
think
about.
There.
A
D
F
I
G
I
would
like
to
support
whoever
is
going
to
be
leading
the
work
on
the.
Why
platform
is
available,
how
it
supports
one
on
that
I.
Don't
I,
don't
know
if
I
can
commit
to
driving
it,
though,
or
or
like
overseeing
its
correctness.
I
think
it's
gonna
that
am
I
able
to
do
that,
but
I
can
support
for
sure.
F
A
And
folks
put
their
name
in
a
would
you
mind
replying
in
there
because
I
don't
necessarily
don't
want
to
GitHub
handled
and
then
I
can
just
interview
as
a
sign,
then
yeah
is
there
any
other?
We
want
to
discuss
any
other
topics
here,
yeah
platform,
attributes
platform,
team
attributes.
This
might
be
what
this
might
be
the
place
where
we
talk
with
the
the
team.
Topology
spoke
capabilities,
I
put
myself
down
for
I'm.
This
is
actually
my
favorite
part
of
the
whole
thing.
A
Kind
of
working
out
what
those
rationalizing
those
you
know,
this
isn't
the
main
place
for
it,
but
I'll.
You
know
it's
just
a
concise
summary
I,
I
kind
of
wanted
this
to
be
a
jumping
off
point
for
for
the
technical
standards
and
kind
of
work.
So
I
put
myself
down
here
and
we
started
some
discussion.
D
Yeah
on
the
capability
section,
so
if
you
find
with
also
some
more
comments,
there
will
probably
I
think
it
looks
really
great
Josh
and
it's
really
comprehensive.
So
I
think
there
was
just
a
couple
of
minor
things
that
we
we
just
wanted
to
ask
about
as
well.
So
we'll
we'll
probably
say
them
or
or
I
will
probably
comment
on
that
at
some
point
as
well.
H
What
an
quick
question
on
content
platform
capability
providers
does,
that
is,
that
a
subsection
of
what
is
a
platform
that
is,
that
belongs
somewhere
else.
A
I
put
that
there,
when
we
had
the
discussion
about
a
month
ago
about
you,
know
the
layers
layers
of
a
of
a
of
a
platform
and
we
needed,
because
we
were
talking
about
you
know
who
the
people
that
actually
run
the
database.
Who
are
they
like?
What
do
we
call
that
team?
Is
it
an
infrastructure
team?
What
is
it
so?
We
we
came
up
with
that
generic
term
platform
capability
provider,
a
provider.
A
They
felt
like
I
needed
to
Define
that
or
we
felt
like
we
needed
to
find
it
there,
but
you
know
if
it
if
we
can
get
that
point
across
or
if
that's
not
necessary,
we
can
you
know
we
that's
that's
motivation
at
the
moment.
For
being
there.
E
H
E
Your
name
under
the
why
I'm
I
put
my
hand
up
but
I
as
I
said,
I'm
happy
to
take
on
any
of
them.
The
only
one
I'm
hesitant
about
taking
on
both
due
to
the
commitment
of
time,
and
also
my
experience,
is
the
measuring
one,
but
otherwise
Josh.
If
you
find
that
we're
overloaded
on
a
section
feel
free
to
move
my
name
around
like
yeah.
Thank.
C
F
C
Yeah
and
probably
like
comment
on
different
issues
and
then,
like
Ian,
said
more,
like
the
administrative
part
on
the
this
section,
I
think
it's
important
to
have
the
the
whole
picture,
because
there
are
like
it's
all
the
same
topics,
but
the
depth
of
each
part
of
it
will
be
different
based
on
the
section.
So
it's
important
to
have
the
same
flow
and
the
same
like
yeah.
A
good
flow
of
reading.
G
I'd
like
to
add
to
whoever
is
going
to
be
doing
the
work
on
attributes
of
platform
teams
I'd
like
to
add
comments
about
GX
teams,
because
I
think
it's
a
that's
like
I.
Have
we
have
a
lot
of
experience
with
that
because
that's
primarily
a
customer
that
we
work
with
and
they
interface
with.
G
You
know
what
would
be
a
more
typical
platform
team
but
they're
all,
but
we're
also
seeing
other
kinds
of
teams
emerging
like
API
registry
teams,
so
I'd
like
to
add
whoever's,
gonna
be
working
on
the
attributes
of
platform
teams.
I
could
I
could
provide
some
additional
information
for
that
section.
A
G
Yeah
I'll
so
I'll,
add
myself
to
that.
The
other
thing
I
wanted
to
mention
is
that
challenges
of
platforms
is
that
one
thing
we're
seeing
is
that
there
isn't
a
consistent
understanding
of
what
the
platform
is
across
a
different
platform
teams
which
in
itself
could
be
a
challenge,
because
it's
like
a
bunch
of
com,
a
bunch
of
different
teams
talking
about
building
platforms
but
they're,
not
actually
they
don't
have
the
same
conception
of
what
a
platform
is.
So
that
might
be
something
to
call
out
so
a
lot.
That
is
a
comment.
A
D
A
So
we
actually
have
and
Colin
I
think
Colin
I'll
put
you
on
I,
don't
know.
Let's
we
got
a
lot
of
people
to
help
on
the.
What
is
the
platform
section
I
think
there'll
be
a
lot
of
involvement
there,
the
only
one
that
so
yeah
so
yeah,
we'll
figure
out
how
to
add
people.
You
could
be
more
than
one
on
each
one.
A
F
D
Maybe
maybe
Sam
you
you
can
if
you're,
okay
with
it,
we
can
start
there
and
but
I
think
we'll
definitely
need
a
little
bit
of
it'd
definitely
be
good
to
have,
maybe
maybe
even
Terrace
I,
don't
know
if,
like
you're
working
a
lot
with
platform
teams,
so
kind
of
you
know
what,
if
you've
seen
as
success
criteria,
it'd
be
great
to
get
your
input
there
right,
based
on
the
projects
you're
working
on
like
what
is
there?
D
What
is
kind
of
the
success
criteria
that
you
define
going
into
these
projects
would
I
think
that
would
be
super
helpful
from
a
mattress
point.
G
And
I
think
in
general,
but
I
think
part
of
the
challenge
here
is
that
it's
this
is
actually
something
that's
being
actively
developed
like
it's.
Not
there
it's
hard
to
it's
kind
of
early.
You
know
so
they're,
not
there
aren't
really
good
references
yet,
but
I'll
do
my
best
to
try
to
find
things
that
I
can
but
I
actually
have
access
to
a
bunch
of
platforming
some
platform
design
docs,
so
I
could
see
what
if
I
could
find
something
yeah.
D
Exactly
those
would
be
great
I
think
I
was
thinking
of
taking
a
look
at
some
of
the
I
know.
Some
sometimes
human
attack
will,
in
their
in
their
blog
posts,
will
address
certain
things
from
a
that
they're
trying
to
solve,
for
maybe
maybe
we
take
a
look
at
those
and
convert
those
into
you
know
measurable,
metrics
and
everything,
but
I'm
happy
to
kind
of
take
an
initial
stab
as
well
on
that.
H
Yeah
one
thing
Josh
had
talked
about
before
a
few
weeks
ago
or
a
month
ago
was
just
was
actually
interviewing.
Some
companies,
I
think
and
getting
companies
involved,
I'd
like
to
continue
to
help
work
toward
that
some,
and
that
seems
like
it
feeds
well
into
metrics,
because
maybe
even
if
there
aren't
some
clear,
hard,
obvious
metrics
in
place,
maybe
there's
at
least
some.
What
are
companies
doing
and
what
are
companies
measuring
that
could
come
out
of
that.
D
Yeah,
like
that
blog
post,
that
it
sent
out
this,
the
the
remation
and
and
Palo
Alto
right,
so
I
was
planning
on
reaching
out
to
him
at
some
point
soon.
So
so
we
because
I
think
he
he
kind
of
likes
showing
thought
leadership
in
this
area
as
well.
So
I'm
sure
he
you
know,
want
to
be
involved
and
kind
of
share
his
stories
and
everything
and
I.
D
Really
good
thing
to
that's
been
helping
me.
A
little
bit
is
on
LinkedIn
I,
followed
one
of
the
PMS
for
backstage,
so
then
they're
kind
of
talking
about
hey
these
are
new
adopter,
backstage
it's
a
new
adopter
backstage,
so
that
we
can
kind
of
use
that
as
well
to
expand
our
our
Network
into
kind
of
different
platform.
Success
stories-
or
you
know
folks,
who
are
building
platforms
and
kind
of
the
pain,
points
and
and
success
criteria
that
they're
measuring.
A
That
would
be
amazing,
like
like
we
were
saying
we
do
want
to
get
closer
to
project
users
and
if
you're
passionate
about
that
abhinava
I
would
love
some
help.
I
dropped
in
you
know
we
started
a
long
time
ago
and
we
need
to
iterate
on
this.
But
there's
this
this,
like
almost
like
survey
framework,
but
you
got
a
couple
people
to
contribute
to,
but
maybe.
F
A
D
Absolutely
I
mean
we
did
a
recent
survey
actually
just
for
it's
it's
more
along
the
lines
of
like
more
along
the
lines
of
provisioning
environments
and
that
kind
of
stuff,
but
it
does
tie
into
like
developer
pain
points.
So
if
there's
something,
if
there's
some
data,
that
I
need
to
talk
with
my
marketing
team,
of
course
first.
But
if
there's
some
data
that
from
there
that's
relevant,
you
know
would
be
happy
to
share
that
as
well.
So.
G
If
we
can
make,
if
we
could
put
together
a
kind
of
a
script
of
things
that
we
could
talk
to,
then
I
could
probably
get
using
working
with
Francesco
could
probably
get
a
bunch
of
like
product
Managers
from
company
from
teams
that
are
leading
backstage
projects.
To
give
us
like
to
answer
those
questions
for
us.
So
we
can.
We
can
work
on
that
together.
Yeah.
H
Yeah,
do
you
think
we
could
start
like
a
slack
conversation
or
something
yeah
I.
H
I'm
sure
there's
some
some
sort
of
thing
that
we
need
to
follow
too
to
make
sure
like
if
we're
asking
on
behalf
of
cncf
or
like
I,
don't
know
what
the
rules
are.
I
want
to
make
sure
I
follow
the
rules
I
wish
there
was
a
platform
for
this.
A
Yeah
I
know
there
have
been
a
couple
of
the
other
groups
have
done
things
like
this
I'll
try
to
take
a
look
around
I
did
share.
You
know
in
the
in
the
chat
where
you
know
we
could
iterate
on
this
template
thing
in
GitHub,
and
you
know
make
that
use
that
as
like
the
foundation,
if
you
all
want
to
not
everybody,
we
have
to
determine
whoever
wants
their
stuff
published
here,
but.
A
F
A
H
Yeah
and
I,
don't
I,
probably
don't
need
to
really
screen
share,
but
I
can
kind
of
walk
people
through
what
we've
talked
about
a
little
bit.
So
I've
been
hanging
out
in
the
cartographers
group
a
little
bit
as
well,
and
one
thing
that
came
up
and
they're
called
following
the
platforms
call
last
week
was
they
have
a
website
that
was
just
published
or
was
getting
published
at
the
time
on
the
cncf
site
and
what
they're
actually
doing
is
they're
using
the
the
website
as
a
part
of
their
publishing
workflow.
H
It
seems
like
they're
using
it
as
like
the
final
draft
right,
so
they
have
the
internal
workings
in
GitHub
and
their
reference
papers.
They
have
a
folder
called
reference,
and
then
they
have
another
folder
called
website
and
they
update
website
with
the
latest
to
create
a
bond
definitions,
maturity
model
whatever's
there.
H
It
sounds
like
I
talked
to
Chris
Abraham,
who
put
together
the
site
there,
and
it
said
that
the
contribute
page
and
the
glossary
page
at
the
same
CF
are
using
the
same
framework,
and
we
could
probably
just
follow
the
same
pattern
to
be
honest
and
just
publish
what
we
think
is
like
that
version.
But
as
the
website-
and
it
sounds
like
there's
some
prior
art
in
the
cncf
for
getting
it
actually
listed.
As
part
of
the
you
know
publicly
available
resources
which
would
be
really
cool.
H
But
it
seems
like
a
really
straightforward
way
to
enforce
some
good
workflow
for
us
in
a
publishing
workflow
as
well
and
I'm,
happy
to
kind
of
take
the
ball
on
on
getting
at
least
that
example
framework
in
there
and
a
self-hosted
version,
and
they
even
have
the
dev
flow
of.
If
you
want
to
get
involved
with
the
project
clone
the
website
right
and
then
here's
how
you
get
the
website
running.
So
some
cool
stuff.
There.
B
Cncf
glossary
side
as
well,
so
basically
it's
a
Docker,
it's
all
the
docker
container.
You
run
it
and
both
the
maturity
model
and
this
glossary
is
using
the
same
analogy.
So
we
can
use
that
as
well.
But
if
you
look
at
the
cloud
energy
maturity
model,
if
you
look
at
the
left
panel,
there's
a
heading
section
and
you
click
on
that
and
then
it's
going
to
be
give
that
to
that
section
as
well.
For
the
platform
for
from
the
platform
side.
B
A
H
E
C
A
Yeah,
if
somebody
wants
to
work
on
that,
I,
like
you
know,
put
it
feel
free
I,
just
posted
the
issue
where,
where
I
get
people
kind
of,
we
could
talk
about
this,
how
we're
going
to
publish
it.
So
we
there's
a
couple
links
in
there
and
yeah
I'm.
Not
I.
Don't
need
someone
to
sign
up
right
this
second,
but
somebody's
wants
to
give
it
a
try.
F
A
F
A
All
right
so
yeah
I
think
I
need
to
create
the
tag
or
tagging,
so
you
can.
Let
us
know
if
you
want
to
discuss
something
in
the
next
meeting
and
otherwise
yeah
we'll
we'll
work,
asynchronously
and
GitHub
and
slack
and
don't
be
a
stranger.
Thank
you.
Everyone
for
your
contribution,
good
stuff.