►
From YouTube: CNCF SIG-App Delivery Meeting - 2019-07-31
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
Is
the
fantastic
app
delivery
call
so
today
on
the
call
Alexis
and
I
would
like
to
discuss
number
one.
The
Charter
I
think
finalizing
the
Charter
talking
about
any
last
point
that
we
want
to
discuss
before
we
send
it
off
to
the
TOC
to
get
voted
on
and
then
the
second
thing
that
we'll
discuss
is
just
like
answer
any
questions
around
being
sig
chair
that
application
is
open.
We
encourage
anyone
who
is
interested
to
fill
out
the
application,
so
I'll
paste
and
the
relevant
links
here
in
a
second
yeah.
A
A
Great
alright,
so
the
first
comments
that
we
had
Liz
Rice,
who
chaired
the
GOC,
had
a
comment
around
listing
the
current
projects.
So
we
had
some
of
the
projects
listed
in
the
Charter
originally,
but
I
think
they
were
taken
out,
but
I
think
it
was
Ellis.
Yes,
as
Ellis
who
mentioned
that
we
could
add
some
related
projects
in
this
sample
list
of
in
scope,
items.
A
C
Reason
by
the
way
why
we
took
them
out
for
everybody
on
the
call
we
had
lots
and
lots
of
projects
listed
in
there
that
somehow
fall
into
some
of
the
areas
and
we
could
like
make
his
list
endless,
like
a
landscape.
So
what
we'll
do
we'll
just
put
in
a
note,
unrelated
CNCs
project?
Obviously
there's
out
there,
but
people
just
kept
adding
more
opens
with
projects,
but
I
think
you
have
this
later
today.
D
Yes,
I
actually
I
just
caught
that
I
haven't
added
it.
There,
I
I'd
suggested
adding
a
line
in
the
areas
considered
in
scope
and
I
thinks
I'm
gonna.
Take
that
one
earlier
I
think
like
we
had
like
designing
developing,
bundling,
deploying
configuration
management,
delivery,
release
management
and
operations
and
I
think
it's
worth
calling
out,
like
validation
and
testing
I.
A
Objections,
okay,
all
right,
all
right,
really
the
projects.
Okay,
how
do
you
see
the
team
working
in
those
areas?
I've
had
significant
overlap
with
other,
for
example,
do
you
see
this
big,
providing
tooling
assessments
of
any
project?
In
the
same
way,
we
can
provide
security
assessment
of
non
security
as
well.
Security
projects
might
be
worth
saying
something
explicit
to
be
scopes
and
non
management
aspects
of
projects
and
the
space
is
covered
by
others
sake.
I
love
see
when
I
go
ahead
and
explain
your
point
to
that.
Yeah.
C
My
point
is,
as
we
were
going
through,
the
Charter
I
think
the
key
difference
between
this
second
law
and
some
of
the
other
six,
that
this
has
a
pure
end-user
application
developer
as
we
focus
so
there
will
be
overlaps,
for
example,
in
security
space,
but
this
is
really
related
to
application
development
on
top
of
the
other
projects,
rather
than
building
the
core
infrastructure
technologies
themselves.
So
I
think
the
OLAP
is
more
than
intended.
Just
the
area
of
work
might
be
different
and
rather
complimentary
to
to
some
extent.
D
I
is
that
restricted
to
just
CN
CF
projects,
just
open
source
projects
or
any
projects,
and
obviously
a
number
of
us
here
where
multiple
hats,
like
someone's
work
for
software
vendors
itself,
provide
you
software
some
ways:
work
on
open
source
things
in
that
context,
some
open
source
things
outside
that,
and
so
there's
the
risk
that
like
well.
Basically,
it's
not
a
risk,
there's
a
reality
of
all
of
those
like
guides
carrying
some
yes
and
I.
Think
it's
just
worth
and
that's
not
a
bad
thing.
D
D
B
Art
what
was
that
who
said
that
sorry,
somebody
responded
saying
it:
okay,
maybe
it
was
just
noise.
I
agree,
Gareth
that
it's
worth
calling
this
out.
This
topic
of
bias
come
up
again
and
again
and
again
when
we
discuss
the
SIG's-
and
you
know
the
TOC
as
an
organization
I
either.
The
nine
voted
in
people
already
have
struggled
on
a
few
occasions
with
discussions
around
bias,
explicit
or
implicit
and
I-
think
it
only
gets
more
complex.
B
They
may
be
superseded
by
other
things.
They
represent
a
set
of
opinions
of
people
in
the
community
who
have
spent
time
focusing
on
this
problem,
and
you
know
in
order
to
you
know,
if
you
even
want
to
go
one
step
further,
you
should
list
the
names
of
the
authors
or
you
know
whatever
it's
the
right
practice
there,
but
I
think
that
it
is
a
reasonable
consideration.
It's
something
we'll
have
to
learn
how
to
deal
with
over
time.
Yes,.
B
It's
sorry
to
interrupt.
I
think
this
is
one
that
the
TOC
is
to
figure
out
as
a
general
thing
for
all
things,
but
Gareth.
If
you
want
to
suggest
in
language
email
it
to
Michelle
myself
and
Liz,
we
can
take
it.
The
other
TOC
folks,
I'll,
just
put
it
on
the
CNC
FTO
CLS,
is
a
topic
that
would
actually
get
them
to
do.
Yes,
yep.
D
B
It's
since
I
seem
to
have
the
Micra
now
may
I
continue
with
a
related
thing
recently
a
couple
of
projects
and
that
a
Daphne
would
belong
in
this
in
the
focuser
of
the
sig.
The
do
application
definition.
B
D
Been
a
fast-moving
space
as
well
and
like
that,
like
a
lot
of
those
projects
and
that
I
like
that
were
quite
very
very
similar
two
years
ago,
watching
and
now
no
longer
exists
like
for
all
intensive
purposes
that
they
were
frozen
in
time.
That
point
so
there's
been
a
lot
of
experimentation
in
the
space
and
fewer
things
that
are
broken
out.
C
Do
you
have
criteria
for
a
certain
say,
use
cases
and
what
tools
should
provide,
and
my
time
there
nicely
so
that
people
cannot
simply
claim
I
wanted
because
question
that
came
up
in
discussion.
We
had
ok,
let's
create
a
landscape
for
all
the
tools
out
there
and
ever
you
put
wind
or
wants
to
be
in
every
part
of
the
landscape.
I
think
we
as
a
Sikh
have
at
least
the
chance
to
say.
C
D
A
Lane
I
think
Alice
hit
on
a
good
point
where
I
just
assigned
the
first
donor.
That
was
schooling
that
we're
talking
about
you
know,
commits
end-users
I
think
he
could
go
a
bit
further
and
say:
okay,
well
we're
talking
about
application
management
related
tooling,
which
you
know
we
see
from
the
perspective
and
users
is
really
broad,
so
maybe
application
operators
and
application
developers,
because
when
I
read
this
section,
you
know
it's
it's
in
depth,
but
it's
also
I'm
very
broad,
and
you
know
a
lot
can
can
fall
in
to
this
particular
bullet
point.
C
Yeah
I
think
release
could
be
a
bit
shorter
and
a
bit
more
condensed
I
can
take
it.
I
can
take
another
stab
at
calm,
because
some
of
those
pieces
could
actually
build
could
be
put
together
like
the
debugging
is
definitely
developer.
Focus
deployment
configuration
more
of
a
DevOps
focus,
interoperating
should
be
there
anyways,
it
could
probably
be
put
out
there.
Management
of
history.
C
I
can't
answer
right,
I
think
to
condense
them
a
bit
more
and
we
had
the
target
audiences
in
there
before
we
just
kicked
them
out,
because
we
thought
their
implicitly
mentioned
by
what
we're
doing
so.
If
we
talked
about
right
developers,
but
I
agree
that
the
list
is
long
and
it
can
be
pretty
much
everything
or
nothing
I'm,
not
the
biggest
fan
of
this
list
either
so
I
think
condensing.
We
found
a
bit
makes
sense.
A
B
D
The
sort
of
the
application
survey
that
was
like
I
am
covered
lots
of
busy
and
use
a
question
just
like
what
people
were
doing
alongside
that.
We
did
the
whole
like
more
landscaping,
big
lists
of
that
horrifying
spreadsheet
of
of
tools
so
that
they
were
mainly
separate
in
that
one
was
mainly
sort
of
book
research
and
one
was
mainly
an
end
user
survey.
I'm,
not
sure.
If
we're
conflating
those
two
things
I
viewing
them
as
the
same
or
being
wounded
more
interesting.
The
other.
D
D
A
A
A
A
E
A
Yeah,
so
you
know
say:
got
started
as
a
place
where
tooling,
on
top
of
kubernetes
would
come
to
demo
and
talk
to
these.
What
we
used
to
be
a
smaller
body
of
people
smaller
for
people
who
were
also
working
on
the
workloads
API,
because
that
related
most
so
the
application
level
tooling,
and
so
there
was
a
nice
feedback
loop
there.
Since
the
workloads
API
is
now
stable
before
it
wasn't,
so
it
was
necessary
for
all
these
people.
It's
going
to
be
a
same
room
so
really
be
on
the
lookout
for
needs.
A
Big
changes
that
effects
on
now.
That's
not
so
much
the
case,
so
there
will
be
some
overlap
with
Cabrini's,
big
apps,
so
some
of
the
tooling
may
want
to
come
in
to
machines.
You
have
say,
gaps
delivery
wherever
it
makes
them,
and
we
just
wanted
to
like
acknowledge
back
here,
we'll
focus
on
and
to
end
aspects
of
application
delivery,
while
you're
brewing
is
big.
Apps
will
focus
on
tooling,
that's
specifically
just
related
to
kubernetes.
A
E
A
A
C
Thanks
so
what
I
also
will
do?
I
was
also
looking
into
the
CN
CF
project
pieces
and
Delta
TS
AF
project
that
they're
related
what
they
were
covering
and
then
condensing
it
down
to
also
what
they
are
working
on
right
now,
because
technically
that
will
be
what
we're
working
on
right
now,
anyways
yeah.
B
B
I
would
go
straight
ahead
and
send
it
to
the
both
the
slack
Channel
and
the
apps
sake,
and
also
to
the
TOC
list.
Okay
posted
on
the
TOC.
That's
the
main
thing
is
getting
it
on
to
the
TOC
list
and
saying
that
the
you
know,
first,
draft
of
the
Charter
from
the
app
dev
sig
is
available
for
review.
The
next
steps
are
following:
broader
review
will
come
up
with
a
final
version
of
the
Charter
for
a
vote.