►
From YouTube: 2023-09-26 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
A
B
D
A
D
E
E
D
D
E
A
A
Just
walk
through
here,
please
consider
putting
your
name
in
the
list
of
attendees
with
this,
so
we
track
ow
I
like
to
start
off
reading
new
folks,
people
that
do
faces
that
haven't
joined
before.
If
you
wanna
just
introduce
yourself
real,
quick,
tell
us,
you
know
something
you
specialize
in,
and
so
we
could
keep
an
eye
on
when
to
call
on
you
here
and
I
want
to
ask
you
to
contribute.
B
I
yeah
I
can
go.
My
name
is
Bob
Hong
and
I'm,
an
architect
and
working
on
platforms
at
Rockwell,
Automation
and
just
recently
found
out
about
the
working
group
and
the
maturity
model,
and
you
know
really
pretty
excited
because
it
fits
exactly
with
the
types
of
things
that
I
want
to
do
that
were
actively
pursuing
to
mature
our
platforms
and
to
make
them
more
available
to
a
broader
audience
across
the
organization.
B
A
A
All
right
well,
one
of
the
things
that
we
that
we
also
offer
or
ask
is:
if
you
have
a
story
from
an
end
user
company
or
your
own
company,
and
you
want
to
share
with
us,
we
really
like
to
hear
them.
We
can
give
you
we're
going
to
give
Matt
he's
gonna
present
to
us
today,
I
told
him
he
could
have
five
to
seven
minutes,
although
we
usually
try
to
keep
it
down
until
three
to
five
minutes.
So,
as
you
know,
if
whatever
you
want
to
share
with
us
Matt
that.
G
G
We
are
a
SAS
company
that
I'm
still
kind
of
struggling
on
like
the
one
sentence,
what
we
do,
but
we
build
a
platform
that
allows
constituents
of
government
to
interact
with
the
government
agencies
in
a
way,
that's
better
for
everybody,
so
this
could
mean
paying
personal
property
tax.
This
could
mean
we're
doing
a
motor
vehicle
registration.
This
could
be
paying
a
court
ticket
requesting
a
copy
of
a
professional
certificate
applying
for
temporary
assistance.
G
So
things
like
authentication
things
like
some
key
user
experiences,
things
like
some
key
platform:
functionalities
like
service
creation,
pipelines,
cueing
processes,
background
cues,
things
like
that
and
as
we've
grown
and
we've
invested
in
product
teams,
some
of
these
things
have
kind
of
ceased
to
be
maintained,
and
so
there's
opportunities
there
and
I.
As
of
recently
as
of
April
and
over
our
platform,
engineering
function
and
I'm
kind
of
charged
with
taking
us
in
a
more
modern
direction.
G
Of
like
an
infrastructure
operations,
team,
right
care
and
feeding
of
kubernetes
clusters
and
some
key
managed
services
like
mongodb
and
some
observability,
tooling
and
I'm
interested
to
to
try
to
push
their
scope
of
ownership
a
little
bit
to
include
like
a
useful
layer
of
abstraction
on
top
of
those
offerings
right
and
to
actually
kind
of
measure.
Success
of
the
team
in
terms.
G
Enabling
other
teams
to
do
whether
that's
stand
up
a
new
application
quickly
or
own
an
application
in
production
more
effectively
or
have
better
alerting
on
applications.
So
it's
very
early
but
I've
been
meeting
with
the
team
and
doing
a
lot
of
planning,
and
hopefully
this
this
Q4
we're
really
going
to
start
to
to
push
things
in
the
in
the
right
direction.
So.
G
Yeah,
it's
it's
an
exciting
time
for
me,
I'm,
getting
to
address
a
lot
of
the
frustrations
that
I've
begun
to
feel
about
our
stack,
so
I
think
it's
it'll
be
interesting.
I
have
a
meeting
actually
with
our
SVP
of
product
this
week
to
talk
about
platform
as
a
product,
so
I'm
excited
I'm,
hoping
I
can
share
something
again
in
a
year
talk
about
where
we've
been.
A
G
I
G
F
One
of
the
challenges
I
think
I've
heard
others
mention.
That
sounds
like
it's
a
part
of
your
journey
that
I'm
excited
to
learn
more
about,
as
you
experience
it,
the
challenges
of
trying
to
both
manage
the
infrastructure
and
that
higher
level
abstraction
within
one
kind
of
group
of
humans
and
yeah.
Where
are
you
where
you
evolve
that
you
know
how
you
support
that
group
of
humans
to
be
successful
with
both
areas
as
well
as,
if
you
end
up
splitting
like
responsibilities
in
some
way?
F
G
Yeah
one
of
one
of
the
things
that
makes
it
really
hard
right
now
is
this:
this
particular
platform
engineering
team
really
owns
like
dollar
costs
of
a
lot
of
the
infrastructure,
and
so
I
think
that
we
really
need
to
be
strategic
about
what
we
invest
in
in
terms
of
head
count
versus
what
we
invest
in.
In
terms
of
like
operational
expenditures,
we
have
a
lot
of
big
decisions
coming
up
with
things
like
do.
We
continue
to
self-manage
mongodb,
or
do
we
move
to
a
hosted
solution
like
Atlas
or
documentdb
like
and.
D
G
Right,
like
I
know,
the
in
the
consensus,
I
think
seems
to
be
favoring
like
use,
managed,
Solutions
and
keep
your
kind
of
capacity
spent
on
what
is
business
specific
for
your
for
your
business
and
I?
Think
that's
the
direction
I'd
like
to
go,
but
introducing
a
new
operational
expenses
is
a
challenge
so.
F
It's
an
interesting.
There
was
a
talk
at
devops
days,
London
this
past
week
by
someone
around
like
kind
of
green
Ops
and
and
Eco
oriented
things,
and
they
made
a
really
interesting
point
of
how
using
managed
services
are
also
eco-friendly,
because
bin
packing
as
a
single
organization
versus
bin
packing
as
an
entire
cloud
provider,
is,
is
different
right.
G
And
that's
very
interesting
having
a
long
tenure
here
in
dealing
with
you
know:
people
leaving
and
people
joining
and
the
training
costs
and
the
operational
knowledge
walking
out
the
door
like
investing
in
managed,
Services
I
think
makes
a
lot
of
sense
from
that
perspective
as
well,
and
so
it's
the
question
of
like
can
I?
Could
we
appropriately
communicate
the
long-term
concerns
and
not
just
the
short-term,
like
operational
costs,
so
we'll
see?
But
it's
it's.
A
All
right
well,
thank
you,
so
much
Matt
and
and
other
folks
that
are
willing
to
share
stories
like
that
with
us.
Just
take
five
minutes
and
tell
us
your
journey,
you
know
help
us
learn
what
it's
like,
or
confirm
some
of
the
hypothesis
in
the
paper.
Just
just
let
us
know
or
drop
your
name
into
the
agenda.
A
A
So
if
folks
from
the
group
want
to
meet
there,
then
at
any
time
during
that
morning,
let's
talk
about
it,
we
haven't
really
made
any
concrete
plans,
but
we
have
the
space.
I
know.
Abby
also
wants
to
perhaps
run
some
other
like
meet
up
Times
birds
of
a
feather
so
check
out
the
issue.
If
you
want
to
work
on
that,
we
will
also
have
a
booth
in
the
project
Pavilion,
where
all
the
other
cncf
projects
go.
A
We
just
have
a
PM
Booth,
so
like
three
o'clock
each
day
and
then
like
we
have
it
during
the
booth
crawl
that
I
thought
was
nice,
so
you
we
could
come,
you
could
come
hang
out
there.
We
could
have
people
do
presentations
there.
We
could
even
let
projects
take
take
over
the
booth
for
10
minutes
and
do
a
presentation.
A
We
could
do
lightning
talks.
We
did
in
the
past.
We
we
had
some
light
Network
session.
So
that's
something
we
could
think
about,
and
then
the
last
thing
is
that
we
are
having
a
session
on
panels.
Sorry
session
on
platforms,
a
panel
session
on
platforms,
Abby
and
I
are
leading
it
with
Colin
and
a
couple
end
users
that
we
have
asked
to
join
us
that
have
some
significant
platforms
so
come
and
join
us
that'll,
be
great
yeah
I.
Think
I
just
wanted
to
share
that.
A
D
J
It
thanks
so
just
sharing
like
in
a
cubecon,
cubecon,
Chicago,
there's
a
event
I'm
actually
organizing
with
the
cncf
called
multi-tenancycon
and
I
wanted
to
invite
some
of
the
folks
who
are
actually
attending
the
cubecon
in
person
will
be
there
at
the
multi-tenancy.
Con
I
will
share
the
link
in
the
chat
in
a
minute,
so
basically
I
wanted
to
actually
highlight
some
of
the
work
that
actually
we
are
doing
here
for
that
conference
as
well.
A
Thank
you,
Sam.
That
is
a
really
good
point.
There's
like
10
co-located
events,
there's
a
backstage
con,
which
some
of
us
are
probably
interested
in
argocon
multi-tenancy
con
app
developer
con
yeah,
it's
a
little.
That's
been
tricky
how
to
balance
this
so
yeah.
If
people
are
going
to
those
yeah,
that's
great
too
here's
the
schedule.
I
should
post
that.
H
A
Mostly
yeah
just
just
being
present,
probably
at
the
booth,
you
know
able
to
talk
about
some
of
the
initiatives
and
projects
that
were
involved
with
we.
We
did
do
a
lightning
talk
and
we
could
do
that
again.
We
did
do
a
call
for
presentations
where
we
asked
people
to
just
present
a
night,
a
new
idea
for
five
minutes
or
an
open
source
project
related
to
app
delivery.
H
A
F
Comment
and
yeah,
as
Josh
said
it's
it's
super
exciting
where
it's
come
from
I
think
we've
had
something
like
40
different
people
review
respond
to
add
to
improve
the
model
over
the
last
almost
six
months.
I'd
say
that
it's
been
there,
so
that's
it
gives
me
a
lot
of
confidence
that
we
are
addressing
a
lot
of
people's
challenges
and
needs,
and
all
that
and
the
people
have
ranged
from
startup
to
large
Enterprise
and
from
vendor
to
consultant,
to
you
know,
platform,
team,
member
and
that
kind
of
thing.
F
So
again
seeing
a
lot
of
that.
It's
the
I
think
somebody
summed
up
perfectly
that
did
a
review
of
it
today,
in
their
kind
of
comment
back
to
me
is
like
there's
always
going
to
be
things
you
can
do
better,
there's
always
going
to
be
changes
that
people
will
recommend,
but
at
some
level
the
only
way
you
really
refine
and
improve.
Something
like
this
is
is
getting
it
published.
F
So
with
that
I
mean
the
tag
people
who
are
in
leadership
of
the
Tag
app
delivery,
as
well
as
our
Representatives,
on
the
talk
as
being
the
technical
oversight
committee,
which
is
above
tags
as
well
as
our
peer
tags.
So
people
like
the
cartographers
who
are
I
always
say
it
wrong
who
are
working
on
the
overarching,
Cloud
native
maturity
model.
F
We
want
them
to
have
time
and
to
review
and
things
and
and
I
think
all
these
people
were
asking
for
these
tangential
reviews
from
we've
been
we've,
we've
been
keeping
them
abreast
of
how
we've
been
going
all
along,
but
look
everyone
has
their
own
focuses
and
so
being
able
to
go
to
them
with
hey
we're,
really
feeling
confident.
Now.
This
is
like
you
allocating
your
time
and
energy
to
reviewing.
F
This
makes
sense
now,
because
we're
not
gonna
kind
of
table
flip
and
completely
restart
unless
something
major
comes
up,
and
so
that's
sort
of
where
we're
at
so
with
that
it
does
not
mean
that
we're
finalized.
If
you're
like
concerned-
because
there
are
things
you
want
to
think
on
more
deeply
or
or
propose
PR's
changes
to
the
GitHub
are
still
more
than
welcome.
These
are
not
you
know.
The
door
has
not
yet
closed,
but
just
yeah,
that's
I,
guess
where
we're
at
in
the
way
of
confidence
in
it.
F
Yeah
and
and
just
to
say,
I
get
that
it
might
be
a
not
everyone
can
make
these
meetings
and
B.
It
might
be
scary
to
to
jump
on
a
call
and
say
yes,
I
think
we
should
red
button
stop
this
thing.
There
are
major
concerns.
I
have
with
going
to
V1
release
on
a
call
like
this,
and
so
you
you're
welcome
to
ping
me
in
a
back
Channel
you're
welcome
to
Ping
On
the
cncs
slack,
either
in
the
group
Channel
or
directly.
F
F
Yeah,
let's
I,
think
there's
maybe
I
was
trying
to
do
one
final
review
and
I
got
a
little
bit
running
out
of
time.
You
know
life,
but
I
think
maybe
one
thing
that
I
saw.
That
would
be
a
useful
group
chat.
So
this
is
the
document
if
people
wanna
play
along
at
home,
it's
in
the
notes
document,
but
now
just
add
it
to
chat
as
well.
F
I.
Think
one
of
the
questions
that
I
thought
was
has
been
sort
of
I
think
it
was
called
a
nitpick,
but
I
don't
actually
think
it's
a
nitpick.
It
was
bothering
me
for
a
long
time,
as
well
as
like
I,
really
like
I,
think
we've
narrowed
in
on
something
like
provisional,
operational,
scalable
and
optimized,
but
there
is
like
a
difference
in
kind
of
tone
to
each
of
those
words
or
function
to
those
words.
F
So
I
guess
there's
been
a
suggestion
of
provisional
operational
scalable
and
up
optimal
or
optimizable,
as
one
kind
of
if
we
were
to
align
in
one
way
of
saying
those
words,
a
different
way
of
saying
those
words
could
be
provisioned
operated,
scaled
and
optimized.
So
one
is
like
maybe
more
capable
of
this
kind
of
behavior
or
this
kind
of
characteristic
and
the
other
one
is
more
like
done
been
there
done,
that
ticked,
the
Box
like
got
the
tattoo.
G
Like
there's
similar
to
the
comment
about
kind
of
organization,
size,
there's,
like
the
whole,
like
company
positioning
part
of
this
right,
like
as
as
a
startup
who
maybe
will
need
to
Pivot
your
concerns
very
different
from
a
mature
organization.
Who's
like
established
a
position
in
the
market
and
like
not
not.
I
I
have
mixed
thoughts
about
this.
Have
you
know
seen
have
having
worked
on
the
interface
document.
I
do
realize
that
you
know.
While
we
were
working
on
it,
we
had
thoughts
that
at
every
particular
level
the
platform
would
have
achieved
a
certain
level
of
you
know
functionality.
So
keeping
that
in
mind
it
it.
It
sounds
correct
when
we
say
it's
provisioned
or
operationalized
or
you
know,
sorry
operated
scaled
optimized
on
that
way.
I
But
I
think
Matt
also
pointed
one
thing,
especially
on
the
optimized
level
that
you
know
mentioning
optimized
would
convey
in
a
way
that
okay
are
we
done
there,
but
then,
actually,
no,
that's
not
you
know,
I
mean
the
word.
The
evolution
of
platform
shouldn't
stop,
so
I
think
that
message
goes
really
well
when
we
have
optimal
or
optimizable,
so
that
you
know
that
there
is
always
a
room.
You
know
room
for
improvement,
sort
of
so
mixed
thoughts,
but
then
both
I'm
fine
with
both
of
them.
E
Yeah
I,
don't
know
I'm
with
you
I'm
with
you
most
of
the
way
there
until
the
end,
I
think
when
you
say
the
word
optimal.
That
sounds
like
to
me
that
this
is
the
optimal
Solution.
That's
what
you
have
gotten
to
is
like
any
arrived
State
and
obviously
the
difference
between
the
optimizing.
The
rest,
the
rest
are
just
straight
adjectives
of
just
describing
something.
E
Well
optimized,
there's
there's
like
a
verb,
that's
kind
of
being
used
their
past
tense
verb,
so
I'm
not
necessarily
upset
that
we're
using
a
verb
for
the
last
one
I
think,
maybe
maybe
a
different
approach.
You
could
say
because,
like
optimizing,
that's
a
present
tense
verb.
That's
like
connotating
that
there's
there's!
This
is
something
that
you're
actively
continuing
to
do,
and
so
it
kind
of
hits
on
like
what
is
actually
going
on
while
still
giving
respect
to
the
others.
E
That's
just
another
path,
I
know,
there's
a
lot
of
paths,
but
I
also
want
to
be
cognizant
of
like
if
we
change
words
entirely.
That's
also
something
to
think
about
that
modifies,
like
the
rest
of
the
paper
of
like
there's
a
lot
of
other
things
that
need
to
be
changed.
That
may
be
like
a
nice
like
Middle
Ground,.
G
I
have
I
have
a
question
actually
now
that
we're
getting
into
the
Weeds
on
this
a
little
bit
is:
are
these
terms
intended
to
be
descriptive
of
the
platform
as
like
a
thing
or
of
like
our
platform
engineering
practices
as
an
organization,
because
I
feel
like
that,
maybe
adds
a
little
bit
of
difference
to
how
I
feel
about
some
of
these
things?
If
it's,
you
know,
our
platform
is
never
going
to
be
optimal
right,
there's
always
going
to
be
new,
tooling,
and
things
like
that.
But
like
can
our
practices
be
optimal?
G
F
F
This
is
this
is
the
conversations
from
doing
the
white
paper
that
I
feel
like
everyone
who
just
read
it
missed
out
on,
and
so
we
all
are
all
here
doing
that
getting
that
benefit
for
this
model
and,
like
we'll
all
be
able
to
look
at
all
the
people
who
read
it,
read
it
and
get
value
and
be
like
you.
You
have
no
idea.
F
So,
yes,
so
to
your
point
to
your
question
Matt,
we
are
explicitly
saying
that
like
you're,
it
is.
This
is
not
a
model
for
the
platform,
because
a
I've
gone
through
and
specifically
I
have
removed
all
references
to
singular
platforms,
because,
while
an
organization
might
have
a
singular
platform,
it
is
at
scale.
That
is
something
that
would
limit
this
model
to
this
model's
Effectiveness
for
larger
scale
organizations
where
they
more
likely
have
capabilities
which
are
delivered
in
in
many
different
ways
or
across
potentially
many
different
platforms
and
platform
teams
right.
F
So
yes,
so
to
answer
your
question,
this
is
not
about
the
platform
and
it
is
also
not
that
any
one
ASP
like
anyone.
You
are
not
one
level
you
are
not
optimized
or
scaled
or
provisioned.
You
are
evaluating
the
ways
of
working
that
you're
doing
and
they
may
be
at
different
levels,
and
we
call
out
that,
like
sometimes
there
will
be
tight.
Coupling
of
you
can't
achieve
a
certain
level
within
one
aspect
without
leveling
up
another
aspect
at
least
a
little
bit,
but
they
they
are
relatively
independent.
In
that
you
can
have.
F
F
F
G
F
That's
an
appreciated
confirmation
on
that,
because
I
think
we
talked
about
a
little
bit
with
the
platform
white
paper
and
we
didn't
end
up
doing
the
edit
for
that
paper.
So
we
talk
about
the
platform
in
that
paper,
but
it
was
something
that
was
being
talked
about
right
around
publishing
time
so
similar
to
right.
Now
we're
having
these
discussions
and
we're
like
do.
We
include
it
in
V1,
or
do
we
not
for
this
paper
and
we've
seen
that
kind
of
that
idea
come
through
and
affect
this
paper?
F
I'm
sure
we'll
see
something
like
that
as
well.
Where
we'll
see
some
of
these
later
conversations
affect
other
papers
that
we
release
and
yeah
okay.
So
what
I'm?
Taking
from
this
is
I'm
going
to
have
a
we
are
going
to
do
an
update
on
these
levels
to
match
the
vocabulary
of
this
paper,
with
the
understanding
that
this
more
product,
startup
vocabulary
is
possibly
like
something.
We
want
to
introduce
and
and
encourage
in
the
platform
as
a
product
paper,
because
that
has
the
opportunity
to
go
more
in
depth
into
what
that
means.
F
For
you,
I'm
going
to
have
a
look
at
whether
or
not
this
diagram
fits
best
where
it
is
or
if
it's
best
under
adoption,
so
as
to
yeah,
be
be
the
least
surprising
for
where,
where
you
might
find
it
and
where
you
might
look
at
it
and
I'm
going
to
have
a
bit
of
a
think
around
whether
or
not
we
go
with
the
achieved
state.
For
these
words,
the
a
characteristic
that
ability
state
for
these
words
and
whether
or
not
sustained
or
sustainable
or
sustaining
or
whatever,
is.
F
Cool,
so
that's
so,
then,
let's
call
that,
as
like
the
de
facto,
unless
something
comes
up
and
again
we'll
do
the
you
know
as
people
sleep
on
it,
we
can
have
reviews
in
GitHub
and
all
that
awesome
is
that
about
the
amount
of
time
Josh,
I
I,
don't
know
if
there's
anything
else,
the
only
other
one
that
people
maybe
want
to
think
about
over
time
is
I.
Think
that
that
leaves
any
level
of
kind
of
question
mark.
F
F
When
you
get
to
optimizing
we're
looking
at
that,
as
that
it
is
bringing
specialists,
skill
sets
into
all
the
things
that
you're
delivering.
So
you
know
making
sure
that
security
in
fin
Ops
and
compliance
and
performance-
and
you
know,
user
testing
and
all
these
things
are
things
that
are
built
into
the
platforms
and
yeah
we're
trying
to
think
of
what
the
right
word
is
for
that.
F
J
Yes,
so
I
just
have
one
question
in
here,
so
I
was
actually
chatting
with
Josh
on
the
previous
week
as
well,
so
we
use
a
term
capabilities
very
heavily,
and
thankfully
just
Josh
has
pointed
me
out,
like
we
have
capability
section
in
the
previous
platform
white
paper.
So
now
the
thing
is
like.
If
somebody
came
into
this
paper
directly
and
start
reading
it-
and
he
comes
to
have
so
many
terms
like
capabilities
in
every
place,
and
we
have
a
no,
we
excluded
it
because
of
our
previous
work.
J
J
What
do
we
meant
to
buy
capabilities
so
in
order
so
that
people
don't
read
jump
into
the
previous
paper
and
read
about
it,
because
that's
where
a
harder
lays
for
the
previous
paper
as
well
like
sometimes
you
have
to
have
described
some
places
in
the
this
version,
and
usually
people
don't
go
on
that
place-
is
to
understand
it.
But
people
have
to
go
there,
but
sometimes
people
won't
go
there
and
just
trying
to
understand
what
the
capabilities
are.
J
A
A
So
that's
kind
of
we've
defined
capability
in
that
way,
as
opposed
to
like,
in
my
mind,
it's
like,
as
opposed
to
an
application
or
a
service
which
is
the
actual
value
stream
that
gets
delivered
to
a
customer,
but
yeah
I
guess
like
what
do
do
folks
feel
comfortable
with
that
term.
Like
yeah
I,
don't
know
you
know,
I
guess
we
could
put
a
little
more
definition
of
it
here.
Maybe
in
the
water
platform
section
or
something.
C
C
F
That
might
be
very
powerful
because
then,
all
of
a
sudden
in
this
website,
you've
got
your
platform
working
group
and
you've
got
like
platform
glossary
or
like
whatever
glossary
here
and
then
you've
got
your
white
paper.
You've
got
your
maturity
model.
You've
got
your
platform
as
a
product
paper.
All
these
things
that
can
all
point
back
to
that
glossary.
Just
like
we
do
and
again
we
are.
We
are
independent
of
the
larger
cncf,
but
that
would
be.
F
F
Oh
sorry,
Cloud
native
glossary
right
so
like
yeah,
they
have
a
whole
site
for
it,
so
that
pattern
of
having
like
a
global
place
to
point
to
right
and
that,
like
the
first
time,
what
I
was
looking
at
the
reason
I
did
a
control.
Fine
for
capabilities
in
here
was
the
first
time
that
we
use
it.
You
know,
could
we
link
out
to
the
glossary
item
the
first
time
we
use
it
so
that,
like
someone,
goes
what
the
heck
is.
F
B
B
It
was
pretty
clear
but
and
I
I
did
go
back
after
I,
went
through
the
maturity
model
and
and
read
the
the
platform
white
paper
so
that,
provided
you
know
more
context,
but
I
I
do
like
the
idea
of
having
a
hyperlunk
out
to
the
glossary
and
where
you,
throughout
the
maturity
model,
where
you
have
links
to
other
terms
like
some
of
the
some
of
the
other
models
like
the
score
model.
I
wasn't
familiar
with.
F
F
Yeah
yeah
nice
that
that
clocks,
then,
because
I
haven't
actually
gotten
as
far
deep
into
that.
So
I
was
like
wait,
a
second.
What
am
I
where
have
I
lost
the
plot,
but
yeah?
No,
that
that
makes
perfect
sense.
It
makes
perfect
sense,
cool
all
right,
I'm
gonna,
stop
sharing
so
as
to
stop
hogging
the
the
meeting,
but
this
is
all
really
really
helpful.
A
F
F
F
I,
don't
know
it's
a
great
question:
I
think
that
there's
a
lot
of
opportunity
for
that.
So
that's
one
of
those
things
where
we
can
create
a
PR,
that's
maybe
low
Lo-Fi
in
the
sense
of
like
a
single
page
and
then
and
then
look
to
to
make
it
a
bit
fancier,
and
that
can
be
the
type
of
thing
that
PR's
come
in
for
or
we
can
start
there.
F
If
you
have
a
vision
for
it,
I
think
I
think
what
we
have,
which
is
really
nice
for
the
white
paper
is
we
have
the
website
and
then
we
have
a
printable
version,
a
PDF
and
I.
Think
we'll
want
the
same
thing.
We
will
want
this
to
be
pdfable
like
printable,
but
also
the
website
doesn't
have
to
be
a
PDF
right.
It
doesn't
have
to
be
like
in
the
shape
of
a
PDF.
It
can
be
links
so.
A
A
C
C
C
Michael
and
me
are
currently
working
on
the
first
draft
for
getting
a
research
goal,
and
you
know
a
general
script
we
want
to
achieve
with
the
research
and
who
we
wanted
to
reach
with
it
and
how
we
can
potentially
do
that.
We're
working
on
getting
this
done
this
week
and
then
show
it
off
in
the
next
meeting
sometime
next
week,
depending
on
when
he
schedules
the
meeting.
A
F
Let's
make
sure
Josh
between
you
and
I
and
and
Dominic.
You
can
help
with
sharing
making
sure
Michael's
aware
we
can
that
both
of
us
can
create
the
invites
on
like
the
cncf
calendars
and
we've
gotten
feedback
before
that.
There's
there's
two
processes,
so
one
is
if
people
are
signed
up
to
the
working
group.
Well,
it's
to
the
tag.
Actually,
they
will
get
like
alerted
to
new
events
being
created
so
that
so,
if
we
create
an
event
for
this,
people
will
be
like.
F
F
Maybe
one
of
us
can
reach
out
to
Michael
and
figure
out
the
time
and
see
if
we
can
get
into
the
into
those
different
mechanisms
so,
but
also
just
I.
Think
that
the
reason
I
took
the
time
to
say
that
out
loud
in
this
call
is
because
what
these
calls
are
really
good
for,
is
awareness
of,
what's
possible
and
and
about
like
working
practices
of
the
working
group
so
FYI
to
everyone.
F
If
anyone
ever
wants
to
have
a
face-to-face,
a
zoom
call
or
whatever
that's
relating
to
the
working
group
and
would
like
that
to
be
something
that's
broadcasted
and
more
available
to
people.
Please
reach
out
to
one
of
the
working
group
or
tag
leads.
We
all
have
capabilities
of
getting
that
onto
the
right
kind
of
calendars,
and
things
like
that.
So,
yes,.
J
F
I
think
the
big
thing
is
just
a
caveat:
it's
going
to
be,
you
know
it's
still
privy
one
and
that
version
One's
Gonna
be
coming
out
shortly.
I
think
that
way,
you're
sort
of
safe
to
share
it
in
its
current
state,
there's
been
no
hiding
the
state
of
the
paper
along
the
way
people
can
see
where
it
came
from
and
where
it's
going
to
so
yeah
I
think
that's
really
exciting
and
thank
you
for
wanting
to
include
it
I'm
glad
that
it's
helpful
so.
A
Cool
deal
the
one
other
thing
I
was
going
to,
let
folks
know
I
know
there
was
interest
for
some
folks
in
this
group.
A
while
back
is
that
we
are
talking
with
a
group
that
wants
to
form
a
working
group
around
API
conventions
and
standards
based
on
a
collection
of
proposals
that
they
have
based
on
some
of
the
Frameworks
that
we
have
and
addressing
some
of
the
kubernetes
I
guess
apis
and
infrastructure
apis,
it's
kind
of
nascent,
but
but
I'm
trying
to
find
out.