►
From YouTube: 2023-09-12 WG Platforms - General 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
C
B
D
C
D
B
H
C
A
F
F
C
I'm
Stuart
I
saw
the
talk
that
Abby
did
last
week,
so
I
thought
I'd
come
and
have
a
nosy
about
what
you're
up
to
so
I
run
a
platform
team
in
a
company
here
in
the
UK
called
Global,
so
small
team
always
too
much
to
do
and
as
much
as
anything
hard
to
get
investment
and
to
talk
about
what
we
do
and
why
it's
a
good
thing.
So,
potentially
some
of
what
you're
doing
sounds
interesting
to
help
with
that.
A
A
H
G
No
worries
noise
as
I
think
it's.
My
first
main
call
that
I
haven't
watched
on
YouTube,
so
hi
everybody,
Brian,
Liberty,
I,
I,
work
in
security,
but
specifically
container
and
Cloud
platform
management,
both
internal
and
external,
and
at
a
global
financial
services
company
that
I'll
keep
out
of
it.
So
I
don't
get
in
trouble
and
yeah.
So
like
like
some
of
the
others.
G
I,
you
know
saw
some
stuff
online
and
I've
been
following
cncf
and
what
you
guys
been
doing
for
a
while,
and
this
looked
like
a
great
opportunity
to
get
involved-
and
you
know
maybe
help
also
use
some
of
the
outcomes
of
this
to
as
a
as
a
stick
to
fix
some
of
our
internal
teams
and
what
we
don't
think
they're
doing
right
too.
So
I
appreciate
the
opportunity
to
help
out
where
I
can.
E
Thanks
Josh,
so
Oliver
who's
based
in
Sydney
and
I
have
been
working
on
a
draft
of
a
product
as
a
sorry
platform
as
a
product
paper,
it's
very
much
a
working
draft
that
we
just
opened
up
and
I'll
link
again
in
a
thread
below.
In
slack
that's
open
for
contribution.
The
idea
behind
it
is
to
be
primarily
focused
at
platform
leaders,
Business
Leaders
in
the
company
to
articulate
the
relationships
between
product
thinking,
what
it
means,
how
it's
operationalized
and
platform
outcomes,
the
idea
being
that
it
should
be
treated.
E
The
the
big
thing
with
this
paper,
though,
is
the
research
component.
We
want
to
get
real
world
examples
from
how
this
actually
plays
out
both
the
good
and
the
bad.
So
we
can
essentially
articulate
like
the
patterns.
The
anti-patterns
substantiate
the
relationship
between
you
know
treating
the
platform
as
a
product
and
better
platform
outcomes.
E
E
I
expect
that
it's
going
to
go
through
a
lot
of
kind
of
iterations
before
we
even
get
any
of
the
research
back
before
we
go
through
synthesis
before
we
incorporate
any
of
that
and
then
obviously,
once
that
happens,
there's
going
to
be
a
decent
amount
of
more
iteration.
The
goal
is
to
get
this
in
a
presentable
state
by
I.
E
Think
what
when
is
Paris
next
year,
March
or
March-
so
definitely
a
few
months
before
that
in
a
working
state
that
we
can
that
we
can
clean
up
so
any
kind
of
immediate
questions
before
I
get
into
the
kind
of
next
steps.
What
coordination
around
this
might
look
like?
What
are
the
kind
of
pieces
of
effort
around
this
paper.
H
I'm
super
excited
about
it
and
I'm
super
excited.
You
took
like
a
stab
at
it,
so
a
little
bit
of
context
for
that
we've
talked
about
on
and
off
at
group
meetings
is
around.
We
want
more
of
these
kind
of
deeper
dive
papers
to
come
like
to
hang
off
of
the
higher
level
papers,
so,
like
the
white
paper
being
the
highest
level,
the
maturity
model
being
an
example
of
something
that's
a
little
bit
more
detailed.
H
These
being
now
even
more
detailed,
because
they're
sort
of
like
implementations
of
things
we
discuss
in
short,
spurts
on
the
maturity
model,
so
yeah
super
excited
to
see
it
coming
in
in
and
being
in
this
state
I'm.
The
only
thing
I'm
hesitant
about
is
March
release
because
we
tend
to
need
to
release
them.
We
want
them
to
be
in
a
final
State
within
about
a
month
before
the
event
that
gives
us
time
to
get
it
publicized,
and
we
tend
to
go
into
formal
review
about
a
month
before
that.
H
So
that
would
put
us
in
like
we'd
want
to
be
in
sort
of
like
nearly
finalized
review
state
in
sort
of
mid-jan
and
I.
Think
what
we
learned
last
year,
trying
to
do
the
white
paper
is
just
how
hard
it
is
to
get
things
over
the
holidays,
so
I
just
just
something
to
think
about,
but
like
we
can
try
right,
we
can
set
dates
and
if
we
miss
dates,
we
move
dates.
But,
like
that's,
that's
my
only
concern
with
what
you've
suggested.
Otherwise
I'm
I'm
super
Keen
to
see
it
see
it
come
through.
So.
E
Thanks
Abby
yeah
one
thing
I'd
like
to
say
is:
you
know,
I'd
like
to
stay
creative
for
this
being
coordinated
like
the
original
platform
paper,
the
maturity
model,
and
then
this
like
nicely
working
together.
But
when
we
started
working
on
this
with
Oliver
I
didn't
even
know
there
was
a
maturity
model
paper,
but
they
work
really
well
together,
like
they
all
tie
into
each
other
at
different
levels.
E
This
one
is
going
to
be
the
first,
obviously,
research
driven
one
to
that
end
in
terms
of
timeline
yeah,
it's
a
little
bit
of
an
unknown
unknown
for
anybody
who's
done
any
research
driven
work,
there's
a
lot
within
our
control
in
terms
of
like
scoping
it,
giving
it
a
timeline
working
backwards.
But
in
terms
of
recruiting
companies
like
we
launched
a
survey,
I
think
we
only
got
16
responses
back,
it's
a
starting
point.
E
We
definitely
need
more
so
that
that
needs
some
dedicated
love
and
then
actually,
you
know
recruiting
folks
on
on
the
community
and
who
want
to
you
know
where
we
can
align
on
this
interview
scripts
to
go
out
and
conduct
them
in
a
pretty
consistent
way.
So
the
the
feedback
you
know
is
Meaningful
and
valuable
and
can
be
parsed
for
insights.
J
So
it
sounds
like
you
want
to
give
a
more
in-depth
review
of
like
different
perspectives
of
like
platform
as
a
product
across
Industries
or
across
like
a
stopper
engineering
industry,
but
across
different
organizations
and
how
it
looks,
and
you
want
to
add
some
like
research
findings.
It
sounds
like
interviews
within
that
process.
Is
that
a
good
summary
does
that
sound
right,
yeah.
E
We
want
to
establish
the
significance
of
treating
your
platform
as
a
product,
so
everybody
has
a
pretty
you
know
diverse
set
of
experiences
here
of
working
in
you
know,
consulting
or
or
you
know,
companies
on
the
platform
side
and
it's
a
mixed
bag
of
you
know.
Whack-A-Mole
to
this
is
a
I
mean
maturity
model
is
a
great.
You
know
a
great
way
to
frame
that
right.
The
industry
spends
the
Gambit
of
that.
E
So
we
want
to
explain
and
articulates
of
the
actual
decision
makers
in
the
company
kind
of
paint
by
numbers
of
why
this
is
important.
I
don't
want
to
go
into
like
super
detailed
version
of
it
now,
but
the
idea
isn't
to
be
to
be
incredibly
prescriptive
in
this
paper.
It's
to
outline
like
the
philosophy
and
the
principles
behind
this
way
of
thinking
and
then
painting
a
path
forward,
not
to
say
that
it's
the
only
path
and.
I
J
E
D
E
Yeah
we've
got
50
people
that
would
be
incredibly
ambitious,
I
would
say
and
broken
down
by.
You
know
consumers,
Builders
and
then
leaders
I,
don't
expect
we'll
get.
You
know
senior
leaders
coming
off
of
surveys,
that's
going
to
be
more
of
a
you
know.
That's
another
talking
point
like
that.
We
need
to
work
through
is
probably
recruiting
from
you
know.
Obviously,
Network
yeah.
D
D
E
E
A
We
talked
a
little
bit
about
that
Michael
about
like
putting
together
a
template
that
people
that
we
can
all
like
know.
This
is
the
process
we're
following
for
the
interview
so
yeah.
That
would
be
awesome
if
we
can
get
it
on
paper
and
you
know,
I'll
be
aligned,
it'll
help
us,
you
know,
run
them
too.
E
A
A
Is
our
I
I
kind
of
wanted
to
ask?
What
is
the
goal?
Is
the
goal
to
like
I
see
that
it
can
be
hard
to
go
from
engineering
to
PM
like
it's?
A
it's.
A
different
mindset
is:
is
our
goal
to
kind
of
help
your
typical
platform,
engineer
or
platform
team
become?
You
know,
adopt
that
product
mindset
learn
how
to
become
a
PM?
Is
it
to
tell
the
story
of
well,
you
should
go
and
figure
this
out
on
your
own,
how
to
become
a
PM.
E
E
That's
something
I
want
to
explore
on
this
as
well,
because
the
way
we
kind
of
wrote
it
was
slightly
disjointed,
which
I
am
aware
of
in
this
paper,
in
that
one
narrative
is
from
the
bottom
up
right,
because
so
often
the
power
you
have
to
change
these
things
and
those
ideas
come
from
engineering
teams
themselves
right.
The
reality
is
you,
don't
often
get
executive
sponsorship
and
like
we
get
it
you're
in
power,
go
do
amazing
things.
E
Yeah,
it's
the
bottom-up
story
of
like
how
do
you
kind
of
create
that
flywheel
like?
If
you
show
these
better
outcomes
at
a
level
that
you
can
control,
then
you
can
you
know,
then
it
can
go
beyond
your
team.
Your
org!
That's
one
story
that
we
can
tell
with
this
work.
The
other
story
that
I.
You
know
that,
no
matter
what
I
still
want
to
tell
is
that
top
down
the
connecting
the
dots
for
that
executive
or
that
business
leader
of
why
this
matters
right
like
why
doing
these
things?
E
Even
if
you
don't
understand
them
at
a
deep
technical
level
of
like
why
it
makes
sense
for
you
to
invest
some
of
your
political
Capital,
to
empower
teams
to
do
this
work
because
of
what
it
does
for
the
business
right.
You
can
respond
to
things
in
the
market
if
you
have
an
amazing
engine
behind
the
work,
but
it
takes
this
kind
of
thinking
to
build
that
engine.
Sorry
I,
think
saki
or
that's.
A
E
Yeah,
and
so
that's
one
way,
we
could
do
it,
we
can
one
one
way
we
can
do.
This
is
not
think
of
it
as
this
like
linear,
static
paper
that
you
know
is
red
top
to
bottom.
It's
this.
We
can.
We
can
package
up
multiple
narratives,
depending
on
who
the
reader
is
because
they're,
substantiated
by
the
same
insights
right,
it's
just
a
different
way
of
telling
the
story,
which
I
think
is
much
more
useful.
To
be
honest,.
C
B
I
I,
don't
know
how
to
raise
it.
Yeah
we
use
China,
so
is
it?
Is
it
like
like
it
is?
One
of
the
goals
is
to
have
like
some
sort
of
best
practices
or
like
those
kind
of
things,
because
other
than
collecting
users
stories
and
tell
them
in
a
linear
way
like
will
there
be
a
benefit
of
collecting
I,
don't
know
how
this
will
complement
to
the
maturity
model
but
exciting
users,
what
they
should
think
about,
whether
she
look
after
it
when
building
platforms
based
on
you
know,
if
and
when
we
have
advancesh.
B
E
That's
that's
so
that's
I'll
answer
these
questions
separately.
So
in
terms
of
kind
of
focus
on
the
work
in
being
prescriptive.
I
don't
have
the
answer
yet
I
think
as
we
go
through
this
iterative
process.
As
we
do
the
interviews
it
will
will
get
a
better
sense
of
exactly
where
we
want
to
tote
that
line.
E
We
want
to
see
how
this
plays
out
in
different
companies
under
different
conditions,
to
the
best
of
our
ability
and
see
which
patterns
emerge
right.
The
patterns
are
the
things
that
are
going
to
help
us
shape.
What
look
I
guess
the
prescriptive
side
of
it
right,
a
pattern
that
says
like
this
is
kind
of
a
thing
that
plays
out
well
in
a
bunch
of
companies
that
we
talk
to
is
probably
something
that
raises
to
the
level
of
it's
an
important
thing
for
you
to
consider,
maybe
not
entirely
prescriptive.
E
G
C
A
E
I,
could
it's
a
little
long,
I
would
say
if
everybody
can
kind
of
just
take
time
to
read
it
speed
read
it
read
the
headings.
At
least
that
would
inform
the
the
next
conversation
but
yeah.
The
paper
basically
follows:
you
know,
and
somebody
already
pointed
out,
like
I,
read
a
few
comments
and
like
just
switching
around
sections
for
readability,
there's
a
lot
of
work
that
needs
to
happen,
but
the
idea
is
that
you
know
why
product
thinking,
what
does
it
mean?
What
are
the
principles
of
it?
How
do
you
operationalize
it?
E
E
A
Yeah
it
almost
I
I'm,
almost
there's
three
work
items,
there's
no
three
tracks,
there's
the
paper
itself,
there's
running
the
interviews
and
then
I
saw
Matt.
You
brought
up
in
the
thing
we
the
the
survey
framework,
which
we
kind
of
rushed
out;
I
guess
around
kubecon
Amsterdam,
there's
room
to
to
iterate
on
that
too,
put
it
into
a
dock
and
and
think
about
how.
C
E
F
E
To
align
on
like
the
tracks
of
work,
who's
going
to
own
what
and
then
obviously
feedback
on
the
paper
is
just
open
to
everyone.
Whether
you
wanna
have
a
more
active
role
in
like
leading
a
track
of
work
but
yeah.
This
is
way
more
I
mean
you
know.
Two
of
us
started
this
with
the
help
of
Josh
and
Abby
to
get
what's
in
the
place
where
people
could
read
it,
and
it
has
some
some
Framing
and
structure,
but
obviously
that's
early
days
right.
There's
there's
a
ton
of
work
here.
F
That
doesn't
my
gen
I
I
haven't
made
it
through
the
whole
paper.
I
got
part
way
through,
but
the
the
two
things
that
jumped
out
at
me,
one
was
that
I
think
has
already
been
touched
on
here,
which
is
the
intersection
of
the
maturity
model,
like
these
things
reinforce
each
other
so
well
so
figuring
out
how
to
how
to
tie
those
things
together.
Super
great
opportunity
there
this.
The
second
piece
is
that
I
think
just
my
general
feedback
from
trying
to
get
my
my
bearings
in
the
document.
Is
that
like
what?
F
What
is
it
before
you
have
product
thinking
here,
right,
there's,
pre-product
thinking
and
there's
product
thinking
and
I?
Think
when
we've
talked
about
the
maturity
models
and
the
levels
like
to
me,
that's
like
the
levels,
one
and
two
are:
are
not
sustaining
they're,
not
they're,
not
in
the
they're,
not
platform
as
product.
Yet,
and
so
what
is?
What
are
the
kinds
of
things
we
see
in
those
different
stages?
F
What
is
required
to
get
from
one
stage
to
the
other,
and
then
you
know,
I
think
that
the
big
jump,
the
chasm
you're
trying
to
clear
here
is
the
levels
two
to
three,
where
you're
actually
now
incorporating
platform
as
product
and
and
I
wonder.
If
that
would
help
to
think
about
the
paper
and
how
you
structure
it
like
you
know,
because
I
saw
things
like
build
versus,
buy
or
or
what
is
your
strategy
for
your
platform
right?
F
E
We
don't
need
the
answer
right
now.
That's
a
that's
a
good
question
and
a
good
lens
on
this
right.
There
is
obviously
the
opportunity
you
know
the
maturity
model
was
was
running
on
its
own.
We
didn't
always
pay
the
best
attention
to
its
development,
but
certainly
it's
something
that
we
need
in
this
paper
right,
that
it
can't
be
disjointed
from
the
maturity
model
or
if
there
is
some
compelling
deviation
that
has
to
be
addressed
somehow.
H
A
A
H
Sure
so,
first
of
all,
a
really
big.
Thank
you.
I've
been
a
little
bit
M.I.A
for
a
few
days,
so
there's
probably
a
lot
of
comments
that
are
backed
up
I
apologize
if
anyone's
waiting
on
me,
I
have
some
time
set
aside
for
today
and
this
week
to
finally
or
to
get
back
into
some
of
them,
but
like
genuine
random
Applause
to
everyone
who
has
like
managed
to
get
an
awesome
set
of
details
in
to
each
of
these
sections.
H
So
for
those
that
haven't
been
as
deeply
into
it,
we
went
through
a
process
and
I
would
say
basically
June
where
we
tried
to
settle
on
the
model
itself,
the
like
progression,
the
names
of
the
levels,
the
progression
across
levels,
the
name
of
the
aspects,
those
kinds
of
things,
and
then
we
sort
of
divide
and
conquered
the
the
write-up
for
that
model.
So,
okay,
we
have
this
one
word
concept
of
investment
at
level,
three
scaled,
but
like
what
does
that
mean
to
people
in
a
consumable
way?
H
H
One
of
the
learnings
we
had
when
we
went
through
the
table
back
in
like
june-ish
time,
was
that
there's
sort
of
this
like
diverging
converge
situation,
that
we
have
to
do
where
we
get
everybody,
sort
of
all
the
ideas
out
and
Clarity
on
alignment
in
intention
and
then
there's
like
okay.
Now,
how
do
we
format
this
thing
in
a
way
that
has
Clarity
in,
like
our
consistency
in
ways
and
the
way
that
we
did,
that
on
the
table?
H
That
I
think
worked
well,
this
is
the
chance
to
give
feedback
if
it
didn't
was
that
I
sort
of
just
like
sat
down
with
everybody's
ideas
and
all
the
conversations
from
our
big
old,
like
readout
session
and
then
came
up
with
a
table
and
was
like
now.
This
is
a
like
clean
thing
to
comment
on
right:
it's
it's
taking
ideas
from
everybody's
different
things
and
from
our
conversations
and
putting
into
one
place
as
I
said
so.
H
A
H
F
It's
my
general
sense
that
the
sort
of
breakout
topics
are
at
different
levels
of
like
ready
to
to
go
into
GitHub
and
so
I
think
it
makes
sense
to
have
a
sort
of
check-in
before
you.
You
make
the
leap,
because,
if
there's
like,
certainly
being
in
a
gold
dock,
has
made
it
easier
for
us
to
collaborate
and
talk
and
it'll
that
we
will
lose
that
to
some
degree
when
we
shift
yeah.
H
Because,
possibly
there's
a
middle
ground
step
of
getting
it
us
doing
it
in
the
Google
Docs.
So
it's
visible
and
and
commentable
there
with
with
the
direct
intention
to
get
it
into
GitHub,
soon
like
ASAP,
but
doing
so
via
getting
Google
in
shape
to
enable
those
conversations
a
bit
better
across
the
across
the
detailed
sections.
Yeah
I
think
that
seems
like
a
good
point
for
sure.
A
H
H
People
are
aware
of
it,
because
it's
been
sort
of
deeply
in
the
working
group.
We
want
tag
people
to
be
aware
of
it
as
well
and
and
potentially
also
talk,
people
and
things
like
that.
So
that's
why
we
want
to
give
that
a
mouse
time
where
we're
confident
with
it,
but
we
want
to
get
the
reviews
from
a
wider
audience.
Basically,.
J
H
For
those
technical
reasons,
one
of
the
benefits
of
getting
it
into
GitHub
is
that
it
is
something
that
is
widely
used
at
the
cncf
for
these
kinds
of
documents.
And
so
we
can
start
tagging
people
in
to
be
like
please
review
and
it's,
and
that
is
something
that
they'd
be
like
familiar
and
expecting
right.
J
Okay,
that
makes
sense
so,
if
I'm
understanding
the
next
steps
properly,
it
sounds
like
it's
cleaning
up
the
detail,
sections
that
we
just
kind
of
recovering
and
then
figuring
out.
How
did
they
sync
up
with
like
one
another
as
well
and
doing
the
format
kind
of
similar
on
that
and
then
after
we
feel
good
about
all
of
that
I
should
we'll
probably
have
like
another
meeting
to
confirm.
We
feel
good
about
all
of
that,
then
we'll
push
into
GitHub,
something
like
that.
H
Yeah
I,
don't
have
a
yes,
so
that's
a
good
proposal.
I,
don't
think
I
knew
what
I
want
to
do
there.
Yet,
if
I'm,
honest
but
yeah,
I
think
that
the
proposal
from
both
Marsh
and
now
you
is
like
github's
really
helpful
for
I
mean
sorry.
Google
Docs
is
really
helpful
for,
like
the
iterations
and
the
understanding
of
things.
H
So
it
sounds
to
me
like
there's
an
ask
a
very
reasonable
ask
that
we
get
the
Google
Docs
in
the
into
where
we're
happy
for
them
to
go
to
GitHub
before
we
go
to
GitHub
and
then
it's
like
sort
of
a
a
thumbs
up
the
like.
We
could
put
like
a
little
thumbs,
upy
thing
in
our
our
slack
channel
for
if
everyone's
cool
and
then
look
to
make
that
move
and
I
do
I.
The
one
thing
I'll
call
out
is:
we
are
going
to
at
some
point
have
to
go.
H
So
what
we'll
be
looking
for
when
we
do
that
is
like
a
general
like
we,
we
talked
about
in
the
the
June
deep
Dives
like
General
travel
of
Direction
alignment
like
if
there's
something
that
you
want
to
edit
like
Google
going
to
GitHub
does
not
mean
final.
We
expect
there
to
still
be
pull
requests.
We
expect
there
to
still
be
discussions,
but
we
just
want
it
to
be
like
that
step
towards
finalization
and
I
think.
So
there
will
be
a
time
when
we
have
to
sort
of
say.
H
A
H
So
yes,
what
we'll
look
for
is
to
try
and
buy
early
next
week,
throw
a
vote
into
the
slack
Channel,
which
is
an
encouragement
to
go
and
read
the
compiled
version,
and
let
us
know
if
you
have
any
like
strong
reservations
about
moving
forward
with
the
review
cycle
so
by
the
end
of
next
week
and
have
a
look
at
we'll,
be
we'll
be
calling
with
questions
I'm
sure
over
the
course
of
the
next
week.
While
we
do
this.
A
Yeah,
in
fact,
I
have
been
I'll
share.
So
a
couple
things
first,
which
is
the
first
item
on
the
next
one,
the
other
item,
so
it
fits
in
here.
Abby
and
I
got
a
chance
to
present
I,
don't
know
if
you
all
know,
there's
a
there's,
a
group
in
cncf
the
end
user
groups
and
user
sigs
they're
forming
now
a
new
thing
of
them,
tab
that
technical
Advisory
board,
but
there's
an
existing
one
called
the
developer
experience
group.
So
we
went
and
shared
with
a
number
of
cncf
end
user
members.
The
original.
A
A
That
never
is
gonna
happen,
so
yeah
really
good
feedback
there
I
also
so
that's
exciting
I
also
wanted
to
share
even
internally
at
Red
Hat
we're
looking
at
this
maturity
model
to
do
some
to
do
some
research
and
learn
how
we
can
help
customers
so
already,
even
before
we've
published
it,
it's
been
helpful
for
folks.
So
thank
you.
Everyone.
K
K
A
I
personally
also,
this
is
a
great
segue,
because
one
of
the
things
is
like
we
don't
have
we
don't.
We
don't
have
to
be
stuck
to
any
exact
form
for
these
details
and
in
fact,
maybe
they'll
diverge
further
as
we
go,
but
I
think
we
should
be
open
to
like
in
the
details
section
for
measurement
like
if
we've
got
a
good
graphic.
A
A
A
J
A
A
H
It
just
changes
the
presentation
of
the
content,
but
then
there
may
also
be
questions
about
the
content
and
I
think
those
are
two
categories
of
information
right
or
of
change
and
I.
Think
yeah
we
want
to
I.
I
was
definitely
I.
Think
I
told
you,
please
don't
delete
that
mind.
Maps
I
think
it's
really
useful
there.
So
I
still
stand
by
that.
I!
Think
keeping
that
there
we'll
figure
out
what
the
format
looks
like,
whether
it's
a
graphic
or
bullet
points
or
whatever
I
think
that's
really
helpful
to
be
there.
So
yeah.
H
A
Need
to
kind
of
catch
up
and
and
I've
told
the
tag
leads
and
stuff,
but
I'll
just
tell
everybody,
because
we
gotta
it's
coming
up
soon.
Kubecon,
so
I
wanted
to
share
the
state.
The
tag
will
have
a
meeting
space
in
the
morning
on
Monday.
That
was
what
was
left
from
eight
to
twelve,
so
we'll
have
a
space
from
8
to
12
at
the
convention
center
here
in
Chicago
I.
Don't
think
you
all
for
coming
to
my
town
to
visit
yeah,
so
you
know
I.
A
That
might
be
a
tough
time
for
folks
to
come
or
you
might
be
coming
to
go
into
other
things,
but
we
particularly
like
to
go
over
work.
That's
going
on
in
the
working
groups
so
for
sure
talk
over.
You
know
the
state
of
the
platform
we'll
basically
have
a
meeting
like
this.
There-
probably
a
lot
shorter,
though
at
least
like
half
hour
update
for
each
group
yeah,
and
we
will
try
to
solicit
what
we've
done
in
the
past.
A
A
The
other
thing
is,
we
will
have
a
booth,
a
project
booth
in
the
project
Pavilion.
So
alongside
other
like
cncf
projects
and
tags
and
kubernetes
sigs,
and
all
that
we'll
have
to
put
up
a
schedule,
I
guess
for
people
to
volunteer
to
to
manage
to
to
person
it
and
yeah.
I.
Guess
we'll
talk
more
about
that,
but
it's
okay,
I
was
gonna,
say
even
if
you
don't
you're
not
in
charge,
it
is
still
it'll
be
fun
to
hang
out
there.
So
please
come
visit
us
there.
A
J
A
K
A
D
A
K
K
D
H
K
H
Thing,
that's
not
I,
don't
think
yet.
No
plans
I'll
get
a
comment
into
that
GitHub
issue
Josh,
but
is
there's
as
another
thing
that
people
may
want
to
do,
and
we
maybe
want
to
do
opposite
when
we
have
the
booth
or
when
we
have
the
booth
intentionally
near
the
booth.
I
don't
know,
but
it
ran
to
some
people
at
sivo
navigate
this
past
week
who
have
sort
of
topics
that
relate
to
tag
app
delivery
and
what
the
platforms
working
group
that
are
patterns.
H
So
last
in
Amsterdam
we
did
some
lightning
talks
at
the
booth.
That
I
think
were
amazing
and
we
can.
We
can
do
that
again,
one
of
the
things
about
those
those
they
turned
into
a
lot
of
people
talking
out
and
there
wasn't
as
much
of
an
opportunity
to
talk
like
as
a
group,
because
it
was
quite
loud
and
a
bit
packed
like
space,
wise
and
so
potentially,
what
we
could
do
is
try
and
like
once.
H
We
understand
the
layout
of
the
building
like
snag
a
lunch
table
at
a
certain
time
of
day
outside
of
the
core
lunch
hours
or
whatever,
and
try
and
set
times
that
we
can
have
like
different
talks.
So
the
examples
that
came
from
my
conversations
were
like
Secrets
management,
which
came
up
during
the
tag
meeting
last
in
Amsterdam
as
well
also
the
pattern
of
providing
Services
as
a
platform
and
the
patterns
of
like
working
with
custom
resource
definitions.
H
There
was
a
few
patterns
that
people
are
seeing
across
lots
of
different
products
and
lots
of
different,
like
company
needs
and
challenges
and
stuff.
So
yeah
I'll
make
a
comment
about
it
about
that
concept,
and
maybe
we
can
try
and
organize
that,
as
we
do
our
timings
of
other
things.
If
people
are
interested
in
that
and
if
you
have
more
topics
that
you're
interested
in,
we
can
try
and
organize
them.
A
A
Yeah,
the
rest
I,
it
says
website
and
prototype
platforms.
That
just
continues,
as
is
you
know,
look
at
the
issues.
Leanne
is
working
on
our
website.
So
if
you
have
suggestions
write
to
her,
we
still
think
we
still
want
to
do
prototype
platforms.
You
know
at
least
link
to
them
from
in
the
site
somewhere,
but
that's
still
just
a
work
in
progress.
So.
J
J
J
J
A
Let's
yeah
I
guess
we
gotta
look
at
that.
A
little
carefully
I
mean
most
actually
one
of
the
the
discussion
about
the
end
user
said
last
week.
That
was
the
first
piece
of
feedback.
I
think
they
gave
us
they
were
like
profit,
Center
yeah.
We
wish-
and
this
was
a
pretty
big
company
invested,
so
yeah.
Let's,
let's
think
about
that,
we
got
to
work
with
usra.
Is
it?
Are
there
more
folks
yeah?
Maybe
we
should
get
on
a
let's.