►
From YouTube: TAG 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
A
B
C
A
C
D
Yeah,
let's
type
in,
if
you
have
the
running
notes,
you
can
add
agenda
items
there
too.
If
you
want
just
paste
them
into
the
chat.
E
D
I
almost
want
to
bring
up
while
we're
waiting
about
Mike
rocks
and
just
because
I
noticed
that
kcp,
the
team
behind
it
is
proposed
it
to
sandbox
now,
and
that
reinvigorated
me
at
least
to
think
about
the
API
shapes
that
different
kubernetes
based.
You
know,
providers
capability
providers
might
use
like
you
know,
across
planes,
xrm
and
critics
as
promises
and
stuff
like
that,
and
then
we've
had
a
number
of
API
standards
projects
coming
through
recently
AIP
presented
to
us
a
couple
weeks
ago.
Yes,
seen.
D
Of
course,
Mike
rocks
has
been
coming
through
and
they've
been
wondering
if
there's
a
Synergy
there
to
you
know
like
let's
say
k-native
duct
types
where
they
choose
certain
attributes
to
go
into
the
apis
that
they
Expose
and
they
Define
them
a
certain
way.
Is
there
a
testing
framework
that
we
could
use
to
establish
conventions
around
those
kinds
of
API
shapes,
and
could
we
leverage
some
of
these
API
projects
to
Define?
You
know
higher
level
API
conventions,
or
you
know
second
level
kubernetes
apis
for
lack
of
a
better
term.
So.
E
Because
you
know,
cdk
case
is
a
is
an
attempt
to
give
a
second
order
level
of
abstractions
through
an
API
and
I.
Think
it's
a
really
interesting
effort
and
I
think
just
to
maybe
expand
on.
Perhaps
what
you
were
alluding
to
is.
We
could
definitely
do
some
research
into
that
area,
because
it's
beneficial
to
a
lot
of
folks.
B
I
I
I
propose
to
add
cdks
to
the
to
the
white
paper
and
then
Abby
responded
to
create,
like
a
more
open
discussion
around
how
we
want
to
structure
the
tooling
around
that
and
I.
Think
like
I
responded
to
her
like
it
really
it
really.
B
In
my
view,
it's
really
interesting
to
talk
about
like
this
distinction
about
how
you
can
extend
or
create
some
sort
of
API,
because
the
difference
between,
in
my
view,
between
cross
plane
and
in
silicate,
is
this
cross
plane,
unlike
syndicates
and
helm,
not
only
create
the
high
level
obstruction
or
API.
It's
also
extend
the
kubernetes
API,
where
cdks
doesn't
like
syndicates
create
syndicates
can
create
an
abstraction
there
on
top
of
and
and
basically
double
down
like
beneath
it.
They
create
all
these
kind
of
objects
whether
there
are
extension
of
the
kubernetes
ABR
or
nothing.
B
D
My
of
like
the
two
or
three
things
that
the
the
tag
and
the
working
group
might
do:
Gathering
up
the
cdk8a,
okay,
that's
and
cross
plane
and
I.
Think
of
critics
because
I
work
with
Abby
a
lot,
that's
her.
They
have
promises
too,
which
do
some
of
that
kind
of
stuff.
So
yeah,
that's
good!
Thank
you
for
the
tip
on
cdk.
It
has
to
include
that
in
there
I
need
to
look
at
your
at
that
issue
too.
Exactly
I
know
I'm
a
little
behind
okay,
it's
1006!
D
So
maybe
we
should
get
to
our
agenda
here,
so
I
pasted
into
the
notes
they
paste
it
in
a
potential
agenda.
Do
we
have
anyone
new
today?
I,
don't
think
so
we
all
we're
all
familiar
faces
here,
so
we
were
I
put
in
just
to
briefly
give
you
all
an
update
on
what's
happening
in
the
working
groups,
cuecon
plans
we
can
bring
up
again.
We
talked
a
little
bit
about
that
last
time.
D
There's
not
a
ton
honestly
on
there.
Oh
website
restructuring.
Maybe
we
should
move
that
up
to
the
top,
because
somebody
put
that
on
is
that
you
Leanne
I.
A
Put
that
on
yeah,
so
I
just
wanted
to,
because.
B
A
Think
we
up
until
now
only
discuss
the
website
restructuring
in
the
platforms
working
group,
but
it's
gonna
be
touching
the
website
for
the
entire
tag,
and
the
idea,
just
to
summarize
kind
of
what
we
were
discussing
before
is
just
to
surface
kind
of
the
the
work
in
progress
stuff
more
so
it
will
be
easier
for
people
to
immediately
see
how
they
can
contribute.
What
are
we
working
on
and
where
do
we
still
look
for
feedback,
or
you
know
just
people
generally
giving
us
some
pointers,
and
there
is
a
GitHub
issue
for
that.
A
I
will
share
that
in
the
zoom
right
now.
Oh
wait.
You
already
shared
it.
Wait
and
I've
just
started
playing
around
a
little
bit
with
Hugo,
so
I
can
also,
if
I
may,
share
my
screen
really
quickly.
So
there's
a
doc
that
basically
in
which
we
are
discussing
just
the
general
structure
and
hierarchy
and
then
I've
started
on
building
the
or
just
changing
the
page.
So
it
would
look
like
this,
where
we
have
like
a
main
page
with
some
information
about
the
tag
as
such.
A
Then
there
would
be
a
section
working
group,
so
we
can
put
all
the
working
groups
in
so
far.
I've
only
put
the
platform
surfing
group
and
then
every
working
group
can
decide
for
themselves
how
they
want
to
structure
their
own
section
here
and
then
there
will
be
a
contribute
section
where
we
will
add
stuff
like
projects
that
are
looking
for
participants.
So
anything
that's
not
really
a
working
group,
but
just
a
little
bit
smaller,
maybe
and
then
stuff
that
we
are
looking
for
feedback.
A
So
really
this
is
about
getting
people
involved,
who
don't
want
to
commit
a
lot
of
time.
So
maybe
not
people
who
wouldn't
want
to
come
to
these
meetings
regularly.
But
then
we
have
like
different
levels
of
participation.
So
here
you
can
just
like
look
at
something
give
quick
feedback
and
then
you're
done.
These
would
be
more
like
longer
running
projects
and
then
the
working
groups.
So
what
I
would
ask
everyone,
if
you're
interested
in
how
to
change
the
website
to
restructure
it?
Take
a
look
at
the
stock
leave
some
comments.
A
You
can
also
just
edit
the
doc
there's
no
restrictions
on
it
and
yeah
I
will
also
post
this
branch
that
I'm
working
on
right
now
in
slack
later,
so
you
can
also
just
commit
to
it
yeah
that
is
it.
E
This
is
really
cool
yeah.
One
of
the
questions
I
have
I
guess
and
it's
really
great
to
have
it
from
a
fresh
pair
of
eyes.
It's
like
I'm
am
I
wrong
to
think.
If
I
go
to
the
website,
it's
kind
of
confusing
what
we
do,
I
think
that
might
be
one
of
the
things
I
think
people
find
really
hard
like.
Would
you.
A
Agree
with
that
or
is
yeah
100
I
think
also
from
like
this
is
after
kubecon
EU.
When
we
had
that
booth
and
people
came
to
us,
I
really
realized
most
people
don't
even
know
what
a
tag
is
like.
What
are
we
actually
doing,
and
what
value
are
we
providing
either
for
the
cncf
or
for
the
community?
A
So
even
that
I
think
we
need
to
clarify
a
bit
more
and
then
it's
just
very
difficult
to
realize
how
to
contribute
like
even
for
me,
like
I,
had
to
reach
out
to
you
Alex-
and
you
said,
oh
just
hang
out
on
the
slack
Channel
and
then
I
just
kind
of
started
like
doing
small
things,
but
like
most
people,
don't
have
the
time
to
just
hang
out
in
a
slack
Channel
and
wait
for
a
task
to
fall
into
their
lap.
So
it's
really
about
you
know
putting
everything
kind
of
right
on
the
silver
platter.
E
Handy
Maybe,
what's
really
cool
is
like
I
I
think
we
should
really
get
some
focus
groups
on
this
I
don't
mean
it
in
kind
of
a
silly
way,
but
like
get
some
students
or
new
people
to
Cloud
native
and
say
hey
what
do
you
think
of
this
preview?
Because
I
can
imagine
that
people
understand
Concepts
like
get
Ops
yeah
I
understand
that
or
I've
heard
of
v-cluster
I've
heard
of
these
things.
Maybe
we
need
kind
of
some
really
catchy
front
page.
E
You
know,
but
I
love,
what
you're
doing
and
I'm
gonna
mute
myself
now
and
actually
just
read
this
Doc
and
suggest
some
stuff
on
it.
So
thank
you.
A
Yeah
I
think
all
ideas
that
you
have
put
them
in
the
dock-
a
colonists
not
here
right
now,
but
Colin
and
Abby
and
Josh
myself.
We
already
started
discussing
kind
of
like
what
we
would
like
to
see
and
how
we'd
structure
it
so
yeah.
The
discussion
is
happening
in
there.
C
D
E
There's
a
differentiation
isn't
that
it's
kind
of
do
you
want
to
get
involved
in
the
framework
of
Open
Source
versus?
Do
you
want
to
get
involved
in
an
open
source
project
and
I?
Think
even
that
is
worth
explaining
kind
of
Simply?
We
are
a
community
of
people
who
don't
necessarily
build
tools
and
things
you
use,
but
we
build
the
governance
and
structure
and
all
these
good
things
around
that
so
that
we
make
it
more
accessible.
A
Yeah,
so
if,
since
you
asked
about
like
the
fresh
set
of
eyes-
and
my
eyes
are
not
that
fresh
anymore
but
I
think
they're
all
intents
and
purposes,
if
you
go
to,
if
you
want
to
find
out
anything
about
the
app
delivery
tag,
maybe
you
will
even
go
to
the
website.
I
I've
found
the
GitHub
repository
first
and
then
it
says
it
supports.
Projects
produces
guidance,
gathers
feedback,
but
it's
like
it's
very
vague.
Still,
it's
not!
Then
you
read
through
the
charter
and
it's
very
much
like.
A
Oh,
these
are
the
things
that
we
care
about.
These
are
the
things
that
are
not
in
school,
but
I'm
still
left
with
the
question
like
what
is
it
that
you're
actually
doing
right
and
then
you
have
to
dig
into
okay.
You
have
these
working
groups.
You
produce
white
papers
like
this
just
needs
to
be
the
first
sentence
like
if
it's
buried
you
lost
me
until
then
right.
It
needs
to
be
like
the
first
two
sentences
we
provide
like.
We
have
these
three
levels
of
contribution
right.
You
can
just
like
provide
feedback
on
individual
stuff.
A
You
can
join
projects
like
I,
don't
know
Potato
Head
or
something
or
you
can
really
like,
join
a
long-running
working
group
or
maybe
even
level
four.
You
can
like
be
a
chair
or
something
like
that
like
just
put
that
front
and
center,
so
people
know
exactly
immediately
and
then
all
the
charter
and
everything
that's
like
for
later.
That's
when
you
really
want
to
get
very
deep
into
governance
and
stuff
like
that.
E
Just
reminded
me,
anecdotally,
I
opened
an
issue,
I
think
or
a
suggestion
a
while
ago
to
revisit
our
Charter,
because
I
think
some
of
the
wording
that
we
use
in
it
and
some
of
the
concepts
we
have
are
a
little
bit
out
of
date.
I
mean
this
was
this
was
really
conceived
many
years
ago
now.
So
perhaps
some
of
our
wording
could
be
part
of
your
website
reimagining,
because
I'm
just
looking
at
the
current
website-
and
it's
as
you
say,
it's
like
super
glossy
brochure
vague.
E
Maybe
it
could
be
a
little
bit
more
relatable.
A
Yeah,
so
if
the
the
goal
of
this
issue
is
really
just
to
create
the
basic
structure
of
it
and
then
have
all
the
working
groups
like
put
the
stuff
in
there
that
they
wanna
that
they
want
that,
that
will
be
our
store
like
a
storefront,
more
or
less.
The
only
thing
is
right
now,
I,
don't
think
we're
doing
a
lot
with
the
website,
so
everything
is
linked,
so
we're
linking
to
the
Charter
and
the
charter
is
in
the
repository
once
we
start
moving
this
to
the
website.
A
We
need
to
like
make
sure
that
we're
keeping
stuff
up
to
date
so
yeah
in
the
long
run.
You
probably
need
to
think
about.
Do
we
want
to
copy
the
charter
in
here
and
then
we
need
to
make
sure
that
they're
always
kept
up
to
date
on
the
website.
Do
we
want
to
commit
that
much
time
and
effort
into
the
website
and
keeping
it
up
to
date?
A
I
think
we
should
because
I
think
the
website
is
a
much
better
way
to
get
to
funnel
people
into
the
group
than
git
repository
it's
just
not
as
attractive
but
yeah.
These
are
all
things
that
we
need
to
think
about
in
the
long
run,
but
maybe
not
like
right
now.
It's
not
super
important.
C
Do
you
have
statistics
on
the
website
on
how
much
traffic
it
gets.
D
We
can
get
those
either.
The
website
was
fresh
in
April,
but
I
the
what's
his
name,
Chris
Abraham
that
was
working
with
us,
sent
me
the
stats
because
he
wanted
to
show
how
the
platforms
paper
was
getting
like
some
good
traffic.
So
that
was
nice.
So
we
can
get
those
yeah
that
might
be
helpful
for
you,
Leanne
for
all
of
us
in
planning.
You
want
me
to
try
to
find.
A
Out
I,
don't
know
if
it's
super
helpful
right
now.
It
would
be
helpful
later
if
you
want
to
know
like
what.
What
are
the
paths
that
users
take
to
know
which
information
maybe
needs
to
be
more
upfront,
but
right
now,
since
we're
starting
from
pretty
much
nothing
before
I,
don't
think
the
traffic
is.
The
previous
traffic
is
super
Illuminating
at
the
moment,
but.
E
A
Think
so,
there's
a
separate
netlify
config
for
the
website.
E
D
If
you
yeah-
and
if
you
make
progress
here-
okay,
so
I'm
I'm
on
I,
have
your
back
talking
to
Chris
Abraham
and
getting
more
stats
and
like
he
put
basically
Colin
started
this
because
they
made
the
thing
for
cartographers
the
cloud
native
maturity
model.
Then
he
was
like.
Let's
use
that
for
the
paper
too,
and
then
we
were
like-
let's
not
just
use
it
for
the
paper,
let's
use
it
for
the
whole
tag
site
and
then
we
were
like
wait.
Every
tag
wants
a
site,
and
so
they
applied
it
to
every
tag.
D
C
We
go,
I
am
I,
mention
it
too,
because
thinking
ahead,
there's
a
lot
of
excitement
now
and
then,
as
people
get
busier,
especially
people
who
are
involved
in
multiple
projects.
And
you
know
you
have
to
keep
up
on
slack
and
GitHub
and
website,
and
then
we
don't
want
the
website
to
become
stale,
as
people
have
to
move
off
or
move
on.
So
just
wanted
to
put
that
out
there,
but
that's
great
work.
Leon.
A
D
One
thing
this
is
really
interesting.
Conversation
is
what
exactly
is
the
tags
role
like
I've
thought
about
this?
A
lot
and
I,
sometimes
think
of
us
as
PMS
governance
over
the
project,
especially
PM,
sometimes
I.
Think
cncf
is
the
PM
to
kubernetes
engineering
but
like
we
are
bringing
these
products
like.
There's
no
standards
bodies
in
Cloud.
So
how
do
you
get
10
different,
API
Builders
to
get
in
a
room
and
talk
to
each
other
and
pursue
conventions,
we'll
call
them
standards?
D
I
like
to
work
with
lots
of
projects,
but
so
I
think
that's
part
of
it,
but
okay
I
just
wanted
to
share
that
a
lot.
If
anyone
else
has
any
thoughts
on
you
know
what
is
our
job.
E
I
think
just
to
maybe
expand
or
lend
additional
thought
there.
You
know
I
I,
see
it
somewhat
differently.
I,
don't
think.
Standardization
is
necessarily
part
of
the
role
here
and
it's
to
be
a
focal
point
for
Community
right.
That's
that's!
First
and
foremost,
the
chief
goal
is
to
bring
people
of
like
Minds
into
a
safe,
shared
and
constructive
environment,
to
which
they
can
not
only
find
but
be
connected
to
projects
for
collaboration
and
contribution,
and
also
to
use
and
users.
So
maybe
it's
more
like
we're
we're
guides.
E
D
E
C
A
The
what
sorry
I
had
a
conversation
at
kubecon,
which
really
stuck
with
me,
which
was
a
person
who
wanted
basically
us
to
be
the
people
he
can
point
to
to
tell
his
manager.
This
is
the
way
that
you
need
to
do
it
because
the
cncf
says
so
right
and
he
basically
wanted
to
use
our
authority
to
make
a
political
Point
more
or
less
and
like
even
that
whether
we
are
the
right
people
to
do
that
or
not
we
could
like.
That
is
also
important
to
communicate.
A
C
I'm
I'm
trying
to
remember
the
point:
I
was
going
to
make
going
going
back
to
community
and
so
like
I,
think
many
of
us
here,
I'm
involved
in
multiple
communities,
but
then
also
multiple
tags
and
in
cigs
and
then
so
on.
So
as
a
focal
point,
there's
a
lot
of
projects
that
overlap
multiple
tags
right.
C
C
So
end
users
as
well
as
Josh,
was
mentioning
you
know,
projects
Etc,
so
there's
a
balance
across
the
board,
but
I'm
trying
to
understand
I'm
sure
each
of
us
has
a
different
expectation
of
the
tag
so
back
to
Leon's
point
of
capturing.
You
know
what
you
know:
what
you're
trying
to
do?
Why
you
know
and
then
how
so
yeah.
E
One
of
the
things
Justin
answer
a
little
part
of
that
question,
perhaps,
is
that
when
the
tags
first
created,
they
already
focused
a
lot
around
building
the
initial
inertia
behind
Community
right
setting
office
hours,
email
lists,
all
the
trappings
of
something
that's
reproducible,
and
so
that
initial
momentum
has
gotten
wider
and
has
now
become
leadership
in
these
categories.
Right
so
having
people
who
have
significant
amount
of
Industry
knowledge,
you
can
sort
of
put
other
people
together
within
the
cncf
now.
E
The
way
I
think
it's
started
to
change
is
that
really
the
new
emphasis
is
on
end
user
education
is
that
that
is
now
the
primary,
or
at
least
one
of
the
primary
functions
of
the
technical
advisor
groups.
E
It's
you
know,
Gathering,
all
the
input
around
what
the
industry's
standards
what's
being
used,
not
necessarily
what's
best
and
providing
high
quality
education
and
high
quality
information
for
for
our
community
I
think
that
we
can
strive
to
do
even
50
of
that
and
we
will
be
doing
an
excellent
job
because
that's
a
really
a
really
Broad
and
quite
a
I'm
a
hard
mandate
to
hit.
But
you
know
that's
my
interpretation
and
I.
D
Thank
you
yeah.
That
was
that
was
helpful
to
chat
about
that.
I
think
that
this
kind
of
leans
into
the
next
couple
things
so
I
reordered
the
agenda
site
I'm,
always
refactoring
as
I
go
so
just
bear
with
me,
but
the
next
couple
things
are
cue,
comp
plans
and
project
reviews.
D
Maybe
I
should
maybe
almost
switch
that
up
project
reviews,
because
we're
talking
about
what
the
what
the
group
does
sandbox
are
an
easy
one
to
help
with.
But
of
course,
there's
also
incubating
and
graduated
here
are
some
like.
Are
there
ones
here
that
we
should
proactively
reach
out
to
and
ask
to
come
talk
to
us
or
or
support
them
like
we
like,
we
tried
to
do
with
Yasin
with
with
Mike
rocks.
You
know,
like
that's,
also
leads
into
I.
D
Put
it
here
process
refinements
like
could
we
provide
some
standard
templates
to
guide
people
coming
to
present?
What
do
we
want
from
them?
You
know
what
kinds
of
questions
might
we
ask
and
then
guide
us
like
okay,
they
presented
now?
What
do
we
do?
Do
we
write
a
a
a
post
in
the
sandbox
issue?
Do
we
create
a
a
permanent
dock
in
some
repo?
You
know
sorry
I'm
going
a
long
term.
There.
G
D
I
wanted
to
know
if
you
know
how
people
think
we
might
interact
with
projects
if
we
should
proactively
pick
some
up,
whether
from
sandbox
or
from
existing.
E
You
know
Showcase
of
delivery
right
so
taking
something
in
get
Ops
taking
something
that
facilitates
the
build
process,
something
else
that
doesn't
really
some
day
two
operations
pieces
and
putting
those
all
together
and
inviting
some
of
the
maintainers
and
contributors
of
those
projects
to
speak
a
little
to
them
at
the
at
the
booth
and
at
qcom,
because
I
think
that
would
really
be
enough
because
remember
we're
on
the
bleeding
age
and
we're
thinking
about
all
these
second
order
problems,
and
all
this
really
advanced
stuff,
but
really
A
lot
of
people
just
want
things
that
are
kind
of
encapsulated
and
easy
to
understand
knowledge,
and
that
could
be
a
good
start.
D
Yeah
actually
Alex,
we
one
of
the
proposals
and
it
comes
up
pretty
frequently.
Actually
the
platforms
meeting
is
we
want
to
create
what
we
call
the
Prototype
platform,
basically
doing
what
you
just
kind
of
described
like
coming
up
with
some
use
cases.
That's
what
has
been
the
every
time
we
talk
about
we're
like
we
got
to
define
the
use
case.
First,
you
can't
just
build
a
platform
in
a
vacuum
but
yeah
defining
some
use
cases
and
then
bringing
in
the
relevant
projects.
B
E
It'd
be
really
interesting
to
hear
back
from
some
of
you
folks,
like
Leanne,
Thomas
and
Justin
I'm.
Sorry
Josh
yourself,
like
around
what
people
are
asking
on
the
booth
last
kubecon
and
looking
to
see
whether
we
can
kind
of
capitalize
on
some
of
those
questions
to
really
bring
something
that
will
you
know
excite
and
and
evoke
reaction
from
the
new.
The
next
audience
that
attends.
D
E
I
think
one
of
the
things-
that's
probably
quite
wise
about
showing
a
couple
of
projects
in
a
real
world
situation
is
that
you
know
these
projects
have
their
own
booths
right
like
we
don't
just
want
to
be
a
booth
for
a
project.
E
That's
already
got
people
maintain
us
there
like
it's
very
little
value-add
for
us,
whereas
if
we
show
it
in
a
more
cohesive
environment
of
like
hey,
fictitious
Bank,
a
wanted
to
increase
their
velocity
by
going
to
Cloud
native
here's,
this
kind
of
story
and
we'll
hear
all
the
tools
that
tag,
delivery
and
delivery
has,
you
know,
helped
to
create
and
cares
about.
That
could
be
interesting.
D
That
was
yeah
that
that's
kind
of
what
we
did
I
think
in
EU
like
we
had
Potato
Head,
but
we
want
to
do
more,
so
yeah
I
think
you're
right
on
the
same
part.
E
Time
is
it's
pretty
simple
right:
it
is
a
micro
service
that
deploys
into
kubernetes
with
15
different
ways
right
that
doesn't
really
solve
business
problems,
whereas
if
you
are
focusing
more
on
personas
of
Alex's,
Alex
owns
a
startup
and
wants
to
be
able
to
move
to
Cloud
native,
but
he
only
has
three
Engineers
or
Leanne
owns
a
50
million
dollar
business
and
she's
looking
to
move
from
a
traditional
data
centers
into
the
cloud
you
know
like
actually
focusing
on
these
kind
of
use
cases
and
then
mapping
that
to
how
app
delivery
projects
meet
those
needs.
A
Yeah
I'm
working
on
the
platforms
working
group
because
I
don't
know
what
to
do
with
my
money,
I
think
if
we're
talking
a
little
bit
about
the
kubecon
plans
it.
This
is
what
I
was
already
working
on
a
little
bit
last
time
and
we're
discussing
like
what
should
we
do
at
the
booth
and
what
would
we
need
for
in
case
of
like
marketing
material?
So
it
was
super
helpful
that
we
just
republished
the
white
paper,
because
already
we
had
something
that
we
could
just
talk
to
people
about.
A
What
I
also
liked
was
the
lightning
talks
that
we
had
at
the
booth,
because
that
was
less
us
explaining
to
you
how
you're
supposed
to
do
things
or
like
this
is
how
we're
more
like
bringing
people
together
in
the
community
right.
It
was
more
like
we're
providing
a
platform
and
a
space
for
people
to
just
exchange
ideas
around
the
topic
of
app
delivery.
So
I
do
I
did
like
that.
We
created
that
space
But,
then
maybe
we
need
a
bit
more
just
stuff
that
we
can
tell
people
when
they
come
right.
A
As
you
said
like
this,
is
this
is
case.
Study
of
company
XYZ
I
think
that
that
was
maybe
missing
a
little
bit,
which
is
why
a
lot
of
our
conversations
were
just
a
bit
General.
Either
they
were
about
the
platforms,
white
people
or
they
were
just
very,
very
general,
about
app
delivery.
What
is
a
tag?
What
do
we
do
so,
if,
like
for
the
next
one,
we
could
have
more
specific
stuff
like
even,
for
example,
the
maturity
model.
A
The
platform
maturity
model
would
be
great
anything
where
we
now
know
where
we
now
know
we.
We
want
some
feedback
from
people.
The
platform
I
mean
there's
a
lot
of
platform
stuff
that
I'm
looking
at
right
now,
because
I'm
looking
at
the
docs,
but
again
we
could
ask
all
the
working
groups
to
provide
some
some.
E
Time
just
a
question
I
mean
before
we
even
get
that
far
I
think
a
really
simple
activity
to
be
very
useful
is
to
identify
which
projects
actually
are
right.
I've
grown
up
through
Tag,
app
delivery
right
and
what
I
mean
by
is
you
know
their
problem
area?
Does
it?
Is
it
in
our
scope
and
have
they
consulted?
You
know,
have
they
worked
with
us,
perhaps
because
anyone
I
can
think
of
that's
actually
graduated
as
Harbor
and
that's
quite
some
time
ago.
E
So
if
we
want
to
make
something
with
some
project
logos
to
say,
you
know,
let's
take
these
and
connect
the
dots
and
build
a
solution.
We've
got
to
start
with
that
right.
We've
got
to
understand
which
projects
in
the
cncf
landscape
actually
relate
back
to
Target
delivery,
because
that
will
you
know,
that's
just
a
useful
activity
for
us
to
do
anyway,
right,
like
a
state
of
the
union.
D
It's
so
yeah,
actually
there's
a
bit
of
a
start
on
that,
like
so
take
take
a
look
at
what
Leo
palke
has
been
saying
and
they're
working
on
tag
being
able
to
tag
tags,
sorry
in
the
in
the
landscape
items,
so
that
might
be
a
start,
even
just
making
sure
everything
that
should
be
tagged.
Tag
app
delivery
is
tagged
and
and
yeah
bring
bring.
Those
together.
D
D
I
mean
I
really
like
the
stuff,
you're
saying
Alex,
I,
think
I.
Think
a
lot
of
us
have
have
kind
of
similar
ideas
like
let's
bring
these
projects
together,
build
some
prototype
platforms.
Define
the
use
cases
write.
Adrs
has
been
the
thing.
That's
come
up
like.
Why
did
we
decide
X?
Why
did
we
decide
why
it's
kind
of
the
the
resources
to
do
it
is
kind
of?
What's.
E
The
key
challenge
with
these
kind
of
death
by
committee
approaches
is
that
it's
a
lot
of
conversation
very
little
doing
I
am
happy
to
be
somewhat
proactive,
but
I
would
need
definitely
to
know
more
around
which
projects
are
in
our
tag
and
not
overlapping
with
others.
So
maybe
that
I'll
read
through
this
issue,
you've
mentioned
that
it's
gone
up
that
could
be
yeah.
Maybe
maybe
we
need
to
have
a
working
group
for
kubecon.
You
know
it
could
be
something
as
practical
as
that.
D
Yeah
that
probably
makes
sense
that
we
might
need
a
separate
meeting
just
to
talk
about
that,
but
I'm
thinking
for
this
like
to
get
a
prototype
platform
like
to
me.
What
I
kind
of
see
is.
We
need
someone
to
just
spike
it.
We
need
someone
that
has
the
time
to
spend
a
week
and
you
know:
use
Cube
spray
set
up.
Kubernetes
set
up
a
standard,
cni
set
up
a
standard.
You
know
10
controller
managers,
that
people
need
like
flux
and
Argo
and
whatnot.
D
You
know
backstage
or
something
you
know
there
too,
and
then
just
share
it
with
this
group
and
let's
party
on
like
I,
don't
know
it
feels
like.
If
we
get
something
that's
like
60
70
percent
done,
then
we
can
move
forward
till
we
can
get
that.
E
D
B
B
D
D
So
we
kind
of
we
talked
a
little
bit
about
sandbox
and
how
we
approached
sandwich.
We
don't
really
say
too
much,
but
at
least
we
we've
brought
up
I
guess
we
did
because
Alex
you
brought
up
like
how
we
could
tag
the
ones
that
are
relevant
to
our
tag
and
start
to
get
a
little
focused
around
those.
D
We
talked
a
little
about
so
that
that
was
helpful.
We
talked
a
little
bit
about
kubecon
plans.
D
C
We
talked
about
maybe
meeting
on
Friday,
there's,
13,
colos
and
then
other
vendor
events.
So
meeting
on
Monday
I
think
you
wouldn't
get
a
lot
of
people
so
I
like
the
idea
of
meeting
on
Friday,
but
we
didn't
really
get
a
consensus
and
I
know
people
will
have
to
start
making
travel
plans
even
though
it
is
July,
but.
D
B
D
The
other
project
meetings
so
so
I
think
that's
what
you're
getting
I
can
run
out,
that
we've
run
a
project
meeting
of
our
own.
The
past
couple
coupons
maybe
once
before
that,
where
we
tried
to
bring
together
the
working
groups,
projects
that
are
related
to
app
delivery.
D
You
know
new
ideas
and
and
have
us
all
share
with
each
other
kind
of
to
advance.
You
know
the
maintainer
group
there
were
like
20
last
time
on
the
pre-day
now,
in
addition
to
those,
we
also
have
the
13
Colo
event,
so
we
were
talking
about.
D
Should
we
have
project
meetings
on
Friday,
so
I
guess
there's
that
and
then
there's,
but
the
kind
of
tied
into
that
is
like
do
we
want
to
have
them
all
together
in
like
have
an
organized
like
maintainer
day
or
project
meeting
day
on
Friday
am
I
taking
it
too
far
like
we
need
to
I
kind
of
want
to
know
what
the
other
tags
are
doing
in
the
other
projects.
Are
they
going
to
have
a
bunch
of
meetings
on
Monday,
in
which
case
maybe
we
just
go
along
with
the
crowd
or
we
say
hey?
C
C
E
Don't
we
not
orientate
to
what
other
people
are
doing
and
align
to
what
is
going
to
be
the
best
end
user
experience,
probably
a
single
day
of
just
like
I,
can
drop
in
and
understand
what
Art
Delivery
is
doing
and
making
it
super
simple
that
they
can
just
understand.
This
is
the
track
for
our
maintainer
day,
and
this
is
the
stuff
that
I
care
about.
E
A
I
would
I
would
maybe
make
an
argument
against
the
Friday,
but
I'm
not
even
going
to
Chicago
this
year,
but
it
is
the
last
day
and
I'm,
usually
on
the
third
day
of
cubecono
I'm.
Just
done
I'm
completely
fried
I
will
not
be
able
to
work
on
anything
really
productively,
so
I
will
probably
say
Monday
or
Tuesday
would,
for
maybe
your
preferred
day,
but
I'm
not
good.
D
All
right,
I
guess
next
steps
are
to
find
out
what
the
other
tags
are
doing.
I
know
tag
security
was
particularly
interested
in
talking,
so
I'm
gonna
ask
them
because
they
had
a
whole
Booth.
Last
time,
I
mean
sorry,
not
a
whole.
The
whole
like
sub-conference.
D
In
in
Amsterdam,
there
was
a
like
a
separate
room
which
was
like
the
security,
something
so
I
I
don't
know,
I
talked
to
some
of
them
and
they
were
like
well.
Why
didn't
we
do
like
tag
up
delivery?
Just
have
the
booth
at
the
solution,
showcase,
so
I
don't
know
I.
They.
A
D
The
solution,
so
they
gave
us
they
give
like
a
floor
for
projects
and
they
gave
us
right
there.
So
we
were
like
next
to
cross
plain
and
Captain,
and
you
know
ocm
and
all
the
other
projects
that
are
a
cert
manager.
D
And
then
our
booth
was
split.
Actually
Tech
contributor
strategy
took
it
for
the
afternoon
and
we
had
the
morning
I,
don't
know
if
anyone
else
had
a
booth,
any
of
the
other
tags.
A
By
the
way,
the
looking
at
the
schedule
right
now
and
the
conference
does
it's
Tuesday,
Wednesday
Thursday,
so
there's
not
even
a
Friday,
but
then
for
Amsterdam.
They
had
like
the
Monday
co-looking
events,
but
then
there
were
additional
co-located
events
on
the
Sunday
that
were
for
vendors,
I.
Think
I,
don't
know
if
they're
going
to
do
this
this
year
again.
C
We
had
Monday
and
Tuesday
for
color
events
and
then
we
had
Wednesday
through
Friday,
so
Chicago
is
now
Monday
and
then
Tuesday
through
Thursday.
A
A
E
E
D
A
D
Yeah,
what
do
we
think
this
should
look
like,
because
it's
kind
of
dictated
by
marketing
for
what
it's
worth
like
we're
getting
this
handed
to
us
and
should
we,
you
know,
have
established
some
opinions
from
the
technical
group
I.
Consider
like
the
tags
on
the
talk
like
we're
all
the
technical
group,
okay,
so
yeah.
Let's
keep
talking
about
that.
The
I
think
one
thing
we
can
conclude
here,
though,
is
that
we
do
want
to
Booth.
D
We
want
to
I
I
like
what
you
said
Leanne
about
lightning
talks
like
we
do
want
to
pursue
that
kind
of
thing,
wherever
it's
at
whether
it's
at
the
project
meeting
or
maybe
a
couple
times
of
the
booth,
we
should
get
clear
crisper
on
what
the
message
we
share
at
the
booth.
Definitely
the
things
Alex
said
showing
some
use
cases
and
finding
some
you
know
technical
uses
about
finding
some
like
business
use
cases
yeah
so
does
that?
Do
we
all
agree
that
we
should
have
a
booth
and
pursue
stuff
at
the
booth.
A
A
A
D
I
can
I
can
help
with
that
yeah
and
if
people
want
to
I
mean
you
have
it's
the
same
people
like
if
Alex,
if
you
want
to
get
together,
the
three
or
four
of
us
to
you,
know
just
drill
in
on
the
Charter
One
Day.
F
Very,
very
busy
I
mean
there's
meeting
for
for
project
all
around
Colo
even
all
around,
and
it's
going
to
be
impossible
for
for
all
of
us
to
let's
say
to
go
to
each
other
stuff
we
would
like
to
to
to
to
to
to
be,
and-
and
maybe
you
know
the
lightning
talks,
maybe
they
can
be
on
the
booth
only
and
not
on
Monday.
So
then
you
can
win.
F
Maybe
some
time
and
I
remember
the
last
time
was
maybe
one
or
two
hours
and
on
the
other
end
I,
don't
know
if
there
is
any
any
color
event
who
are
well
taking
the
full
day
on
Monday
or
the
only
Alpha
day.
Otherwise,
on
Monday
we
can
have.
Let's
say
it
could
be
great
if
it's
dedicated
to
cncf
event
on
on
Monday
morning,
for
example
Colo
the
afternoon
or
stuff
like
that
and
and
try
to
avoid
any
overlap.
F
But
I
clearly
think
that
lightning
talk
on
the
booth.
That's
maybe
a
good
way
to
win
some
time,
first
of
all
and
lightning
Thoughts
by
the
way,
especially
for
sandbox
project
of
people
who
like
to
jump
in
as
a
Sandbox
project
like
us
last
time
in
Amsterdam.
That
was
very,
very
valuable
and
appreciated.
D
D
I
think
I'm.
That
makes
sense
what
else
here
so
the
last
I
mean
the
last
couple
things
that
we
want
to
keep
going
through
the
agenda
or
yeah
it's.
What
does
anyone
want
to
talk
more
about
kubecon
anything
else?
D
Okay,
so
a
couple
other
things
on
the
agenda:
one
I
wanted
to
just
call
out
the
process
refinements
that
have
been
coming
up.
If
anyone
wants
to
contribute
to
them,
one
Jen
it
started,
but
I,
don't
think
she's
working
on
it
a
little
more
like
in
our
contributing.md
doc.
It
does
say
like.
Oh,
you
have
a
project.
D
Come
present
it
to
us,
but
can
we
elaborate
on
that
more
guidance
for
working
group
formation
that
that's
kind
of
on
me,
I
guess
what
we've
been
doing
with
Ouija
artifacts?
D
There
is
discussion
Upstream
about
in
in
the
talk
about
tag
formation,
if
anybody's
interested
in
there
they're
talking
now
about
I,
haven't
read
it
carefully
yet,
but
they're.
They
want
to
create
a
GitHub
org
for
us
to
have
tag
repos.
If
people
haven't
seen
that
so
that
will
be
helpful
for
things
like
potato
head
and
prototypes
and
Ouija
artifacts.
These
are
repo
so
and
then
the
last
one
was
there
was
some
feedback
that
we
were
we're
getting
like
AI
generated
content,
and
you
know
distracting
maybe
too
much
public
relations
content.
D
Marketing
content
in
some
of
our
forums
seems
like
the
best
way
to
tackle
that
is
to
just
describe
what
we
expect.
So
we
opened
an
initial
for
that
yeah.
If
anyone
wants
to
contribute
on
those
with.
E
E
E
We
can
confirm
that
shortly
with
Justin
yeah,
just
just
because
I
think
that,
as
I
said
earlier,
jokingly
like
there
is
a
kind
of
anxiety
around
like
I've
got
to
create
a
working
group
someone's
got
to
lead
it.
There's
all
you
know
all
these
things
you've
got
to
do,
but
actually
they
they
should
be
surgical
instruments
right
for
solving
problems
and
for
exploring
opportunities.
G
D
E
I'm,
just
I'm
just
reading
off
of
what
the
I'm
not
talking
about
I'm,
not
just
I'm,
not
debating
the
longevity
of
the
working
group,
more
the
formation
of
the
process
itself.
D
E
E
G
G
Also
a
reason,
our
problem
we
had
with
Cooperative
delivery,
slash
platforms,
working
group
initially
that.
E
D
C
So
with
the
platform
working
group
it
in
the
beginning,
it
felt
like
there
was
not
the
formation
of
it,
but
naming
it
took
longer
than
anything
else,
and
that
wasn't
a
Toc
issue,
and
so
myself
it
was
hard
trying
to
show
up
to
meetings
and
they
were
just
about.
What
do
you
name
something
or
so
I
just
wanted
to
say
that
and
then,
with
eight
minutes
left
can
I
mention
the
process
for
sandbox
really
fast.
C
Since
you
you
went
over
it
Josh
it's
something.
I
brought
up
with
them.
Toc
members
is
that
as
we're
looking
at
sandbox
projects
and
people
have
less
and
less
time
as
the
industry
is
what's
the
right
word,
retracting
or
people
have
to
be
more
efficient
with
their
time
as
projects
come
forward.
C
Sometimes
it
might
be
good
to
see
if
they
could
merge
with
another
project
that
you
know
might
be
similar.
Is
there
so
I
just
wanted
to
throw
that
out
there,
because
there's
so
many
projects
and
I
know
the
TOC
is
being
mindful
of
approving
projects.
So
maybe
another
alternative
could
be,
you
know,
is
there?
E
I
think
it's
a
it's
a
really
good
point
that
there
are
a
lot
of
beating
projects
that
are
looking
to
fill
in
the
same
space.
I
also
think
the
reality
is
that
many
of
these
projects
are
driven
by
commercial
entities,
and
these
are
the
open
source,
marketing
efforts
to
put
them
into
the
cncf
and
so
they're
going
to
be
dictated
by
the
mandate
to
get
their
project
in
and
own
exclusive
access
of
it
right,
control,
the
governance
and
it's
not
a
pessimistic
point
of
view.
E
It's
just
a
realistic
point
of
view
right,
because
their
money,
they
will
have
an
Enterprise
offering
offset
product
or
some
linkage
to
it,
and
so
you'll
see
that
many
of
these
people
are
very
resistant
to
that
idea
of,
and
you
sort
of
combine
two
projects.
One
one,
though
that
has
been
successful,
is
open,
Telemetry
right
because
that
combined
open
census,
open
metrics,
but
that
was
quite
a
rare
occurrence,
I
would
say,
but
I
I
would
welcome
that
as
well.
E
One
other
thing
is
that
I
think
we
need
to
sort
of
provide
a
barometer
of
How
likely.
Your
project
is
to
succeed
in
getting
through
sandbox,
because
it
can
help
save
a
lot
of
time.
I
think.
C
I
think
the
tocs
are
trying
to
also
guide
companies
are
not
using
the
cnciaphism.
It
is
I
mean
it
is
a
big
marketing
organization.
Right
I
mean
let's
be
real,
but
if
a
project
is
only
pushed
through
by
a
commercial
entity
and
it's
only
in
the
cncf
as
a
marketing
function,
is
that
really
adding
value
to
the
rest
of
the
cncf
ecosystem
so
yeah
anyway?.
D
That's
life
I
I
know
that
I
that
I
use
the
word
standards
before
that
probably
but
the
standards
bodies
are
not
necessarily
what
vendors
want
vendors
would
prefer
creating
their
own.
You
know
custom
solutions
that
they
can
iterate
on
as
fast
as
possible
that
have
the
the
API
shapes
that
they
completely
own,
but
the
standards
really
helped
the
end
users
because
they
don't
have
to
choose
from
10
different
similar
projects.
They
don't
have
to.
You
know,
have
the
vendors
bake,
all
the
vendors
are
supporting
each
other,
so
yeah,
that's
in
that
way.
D
An
open,
Telemetry
itself
is
unusual
in
that
it's
a
standard.
Really,
it's
not
a
project.
It's
not
an
implementation.
Like
most
I
mean
it
does
have
collector
and
stuff,
but
it's
more.
E
Api,
it's
a
really
good
point,
because
really
kubernetes
is
just
a
standard
now,
if
you
think
about
it,
the
API
there's
many
different
implementations
of
it.
Those
are
often
the
most
successful
projects,
the
ones
that
are
interoperable,
and
so
things
like.
If
you
look
at
Argo
CDN
flux,
is
there
more
a
pattern
of
git
Ops
as
a
practice?
That's
the
pattern
and
the
standard
like
it's
a
really
interesting
sort
of
way
of
thinking
of
these
things.
D
Yeah
I
love
that
you
brought
up
Argo
CD
influx
because
pipe
CD
just
came
through
us
the
other
week
and
like
how
do
they
like
now
do
I,
say
Argo
flux
and
pipe
or
is
pipe
just
a
second
one
like
I?
Don't
I'm,
not
no
offense
to
the
pipe
CD
folks,
but,
like
that's
yeah,
how
did
the
open
get
outs
project?
There's
an
Argo
project
meeting?
D
But
what
about
the
other
get
Ops
folks
or
even
chaos
like
chaos,
engineering
which,
by
the
way
I
put
on
the
Note
because
I've
been
trying
to
reach
out
to
those
guys
I
mean?
Is
this
a
thing
because
it
just
seems
to
be
litmus
chaos,
but
Now
kraken
is
coming
from
Red
Hat,
so
I
noticed
that
one,
but
there's
a.
C
E
E
Obviously
it's
probably
under
an
MIT
license
already,
but
the
actual
governance
and
direction
will
have
to
open
up
to
a
more
diluted
set
of
people
who
maybe
not
have
the
same
goals
as
yourselves,
who
are
funding
the
development
of
the
product
and
again
I'm,
not
a
pessimist
around
this
I've
just
done
this
quite
a
lot,
so
it
is
something
I've
had
to
really
think
about
with
even
legal
counsel,
sometimes
because
it
can
be
one
thing
to
hear
that
advice
would
be
another
thing
to
swallow.
C
E
Technically,
yes,
and
no,
there
are
many
ways
to
get
around
it,
which
projects
do
such
as
they'll
employ
contracted
people
to
work
inside
of
the
maintainers.
Also,
you
can
rotate
your
Governors,
your
governance
body,
so
that
they're
all
people
within
your
the
majority
within
your
company,
you
can
have
M
retis.
So
that
also
adds,
like
this
whole
bunch
of
ways
around
it.
You
are
right,
you
should
be
seeding
it
and
think
of
it
as
like.
E
It's
it's
there
for
the
world
for
everyone
to
use,
but
the
reality
is
that,
for
example,
kubernetes
is
still
pejoratively
Google,
who
and
and
red
hat
to
a
degree
who
really
do
run
that
project.
E
D
D
Yeah
I
know
I
like
to
go
through
and
think
of
action
items
and
figure
out,
but
it's
a
yeah
I
don't
know
if
I
could
do
that
right
at
this
minute.
So
look
over
the
the
stuff
I
know
there.
We
have
a
couple
conclusions
that
we
have
to
pursue
I'm
on
the
things
that
I'm
on
Leanne
is
working
on.
The
website
help
her
out
with
that
yeah
and
we'll
chat
more
on
on
slack
and
and
keep
moving
things
forward
and
GitHub.
F
G
You're
right
very
fine,
thanks
I
think
we
I
think
Josh
wrote
sent
out
a
meeting
for
a
Google
meeting
as
far
as
I
know.
Oh.