►
From YouTube: CNCF TAG App-Delivery 2022-04-06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
C
C
Someone
from
red
hat
just
went
to
get
labs,
told
them
to
look
out
for
you.
He's.
A
A
E
D
D
D
D
Yeah,
while
we're
waiting,
we
have,
I
think,
some
new
people
joining
in
here.
I
think
daniel.
It's
your
first
time.
At
least
I
can't,
unless
you
have
been
there
when
I
was
there
last
time,
we'd
usually
give
new
members
the
opportunity
to
introduce
themselves
in
the
beginning
of
the
meeting.
Oh
yeah.
B
B
This
is
some
new
open
source
project
to
help
people
to
I
mean
migrate,
your
monetize
application
to
like
a
cloud
application,
as
well
as
the
virtual
machine
to
queue
some
of
the
stuff,
and
I'm
just
wondering
if
there's
something
some
kind
of
interesting
part,
I
can
contribute
this
app
delivery
group
along
with
the
conveyor
project,
so
I
just
try
to
go
through
our
git
repository
and
what
kind
of
stuff
you
are
doing
recently
and
then
maybe
it'll
be
very
helpful
for
me.
B
If
I
join
the
group
and
try
to
understand
what
you
guys
are
actually
doing,
and
then
I
try
to
find
out
what
kind
of
stuff
actually
I
need
to
contribute
to
this
group
yeah.
Hopefully,
I'm
going
to
keep
joining
unless
my
existing
network
meeting
does
not
conflict
with
this
meeting
by
the
way
I'm
based
on
boston,
oh
okay,.
B
Exactly
the
last
time,
actually
I
tried
to
figure
it
out
at
the
meeting
time
after
day,
saving
time
stuff
and
that's
always
the
worst
I
I
joined
at
the
meeting
and
the
no
one
actually
shows
up.
Oh
wow,
maybe
I
missed
the
right
time,
but
today
I
made
it
yeah.
Thank
god.
D
Yeah
great
we
had
the
we
had
some
discussions
with
the
conveyor
people
in
the
past
already
cool.
I
have
to
admit,
I
don't
know
the
exact
status
of
the
sandbox
submission
where
it's
at
right
now,
where
it
was
accepted
or
not.
Eventually,
it
was
a
discussion
about
sandbox
meetings.
Oh.
B
D
F
Yes,
hi
I've.
I've
been
a
member
of
the
group
for
a
long
time,
but
I
haven't
been
able
to
come
to
the
meetings
I
thought
today.
F
I'd
come,
I'm
a
member
of
the
operator
framework
group
specifically
working
on
olm
and
we
are
sort
of
iterating
on
our
apis
and
developing
some
some,
basically,
some
new
functionality
to
deliver
content
onto
a
cluster,
an
entirely
new
project-
and
I
thought
I
could
come
to
this
group-
maybe
share
that
share
that
project
at
some
point
and
get
some
ideas
about
how
we
how
we
can
develop
those
apis
in
you
know
a
more
upstream
fashion
and
successfully
deliver
them.
So
that's
kind
of
about
me.
D
Okay,
great,
that
actually
is
a
perfect
transition
into
the
first
actual
agenda
item
and
why
we
were
waiting
here
for
thomas
one
of
the
authors
of
the
original
operator
white
paper,
so
mr
hand
it
over
to
you,
thomas.
G
So
one
thing
I
came
across
in
the
last
few
weeks
was
that
last
year
we
published
the
first
version
of
the
operator
white
paper,
and
this
was
sort
of
one
of
such
a
such
a
first
step
towards
towards
a
comprehensive
thing,
and
what
I
just
wanted
to
ask
the
group
here
was:
if
we
should,
if
you
think
it
would
make
sense
if
we
would
go
for
a
version
two
of
the
operator
white
paper,
and
if
you
have
some
proposals,
what
additional
contents
could
be,
and
yes,
who
would
like
to
contribute.
G
For
me,
it
was
one
one
funny
thing
was
finalizers
and
whatever,
and
I
also
thought
it
might
be
that
we
have
some
new
people
here
who
want
to
join
the
efforts
for
for
a
new
version
and
also
yes,
if
it
would
make
sense.
So
what
do
you
think
about
this.
E
Yeah,
I
think
it's,
I
think
it's
a
good
idea,
because
we
like
updating
these
white
papers,
it's
kind
of
like
a
necessity
in
in
our
business,
at
least
stuff
happens,
and
obviously
there's
there's
there's
things
that
might
not
have
been
part
of
the
original
white
paper.
That
could
potentially
be
be
very,
very
useful.
E
Then.
Obviously,
it's
like
the
the
the
bandwidth
issue.
I
guess
we're
not
that
many
people
we
have
already
a
different
white
paper
in
like
the
in
the
makings
aka.
Not
it
really
started
yet
so,
but
but
I
I
think
that
will
kind
of
solve
itself
out
and
as
long
as
you
know,
if
you
build
it,
they
will
come.
E
So
if
we
start
creating
a
secondary
white
paper,
I
think
we
should
be
able
to
get
like
if
we
build
on
version
one
so
to
speak.
I
think
I
think
that
would
work
out
right.
E
G
E
It's
I
I
think.
If
I
remember
correctly,
there
was
some
sort
of
feedbacks
like
in
the
issues
about
the
white
paper
and
if
there
are
any
still
that
aren't
kind
of
not
addressed
instead
of
like
doing
patch
versions
of
the
of
the
white
paper,
we
could.
We
could
just
as
easily
go
for
a
version
two
and
then
get
anything.
That's
in
in
issues
get
off
issues.
E
You
know
get
that
in
there,
but
also
just
you
know,
go
through
the
list,
see
what
is
missing
from
version
one
and
then
just
you
know
build
upon
was
in
in
version
one,
and
it
shouldn't
be
that
big
of
a
project
compared
to
starting
from
scratch.
G
D
Also
mentioned
during
the
new
operator
framework
project
that
they
are
working
on
there
yeah,
I
mean
one
thing:
I
would
I
don't
know
how
much
recovery
they
initially
want,
but
that
came
up
at
least
the
conversation
that
I
had
is
operators
and
security,
especially
it's
just
I'm
just
deploying
something
that
can
be
like
really
funky.
C
That
kind
of
remind
like
that's
like
get
ups
like
magic
things
get
ups
is
is
magic
things,
and
I
was
kind
of
going
to
mention
that
as
a
segway
like
operate
like
I
posted
a
thing,
that's
interesting
that
operators
and
git
ops
are
kind
of
getting
considered
together
now,
because
operators
kind
of
facilitate
get
ups.
So
that
might
be
an
angle
we
talk
about
here,
meaning
declarative
is
kind
of
magic.
Always
I
declare
it
and
somehow
it
happens.
G
D
Yeah,
let's,
let's
do
this
like
like
really
collect
issues,
try
to
reach
out
to
as
many
people
like
everybody
who
commented
on
the
initial
one
and
then
also
share
it
on
a
wider
scope
and
then
just
put
the
topics
down
there.
I'm
not
sure
whether
we
want
to
create
a
dedicated
working
group
we
could,
but
this
is
usually
maybe
a
bit
of
an
overhead
for
working
on
it.
G
So
I
think
we
could
deal
with
this
kind
of
the
tech
security
does.
I
think
they
never
create
working
groups
for
white
peoples.
They
only
do
some
projects
which
are
finished
after
the
white
papers
is
done.
Yeah.
E
E
Issues
and
stuff
in
github
is
there
and
we
have
that
those
kind
of
discussions
and
if
then
something
comes
up
that
needs
a
bit
of
like,
like
you
know,
face-to-face
discussion
or
face
to
screen
just
face
to
you
know
whatever
we
call
that,
then
you
could
do
like
just
single
meetings
on
specific
topics
if
it's,
if
needed
at
all,
who
knows.
D
I
mean
the
most
important
thing
is
that
somebody
is
like
actively
driving
this
forward
and
you
kind
of
volunteer
right
now,
so
that's
like
bringing
it
up
you
kind
of
volunteer
as
well,
yeah,
and
also
for
everybody
here
like
again
on
black
on
whether
it's
on
the
right
hand,
side
or
also
on
the
the
gitlab
side.
If
there's
any
people
who
you
want
to
bring
in
or
foreign
to
contribute
on
your
side,
it
might
definitely
be
helpful.
D
I
guess
obviously,
a
lot
of
operator
related
knowledge
on
the
the
gitlab
side,
with
everything
you
do
around
your
kubernetes
operator
like
share
it
with
people
and
then
like
get
more
people
involved,
which
is
kind
of
like
what
we're
trying
to
generally
do.
Anyways.
A
D
D
C
Yeah,
I
could
take
a
start
coming
off
mute
there.
So
to
be
honest,
it
was
a
rough
february.
Basically
robert
and
I
are
only
are
the
only
people
attending
and
I
we're
struggling
to
well,
we
need
to
orient
around
something
and
we
we're
having
having
trouble
getting
end
user
input.
The
survey
that
we
did
on
github
hasn't
been
attractive
enough.
Maybe
we
should
do
it
a
different
way,
I'm
not
sure,
that's
why
I'm
open
up
to
the
to
the
crew,
but,
but
I
also
wanted
to
I
put
up
one
suggestion.
C
Possibly
I
know
a
lot
of
other
groups
have
started
with
a
white
paper
and
that
kind
of
develops
the
initial
hypotheses.
I
mean
I'd,
love
to
not
start
from
nowhere
with
the
hypotheses,
so
I'd
rather
get
input
from
users,
but
maybe
that
maybe
now
it's
time
for
us
to
just
facilitate
a
discussion
around
a
paper
with
a
bunch
of
opinions
so
that
you
know
we
have
something
to
start
from
anyway.
That's
my
idea.
I
wanted
to
put
it
out
there
for
discussion.
D
D
D
Another
one
is
really
like
for
people
learning
new
stuff
that
they
are
interested
anyways
and
engaging
with
people
who
have
that
knowledge
like
a
way
of
like
having
access
to
people
you
otherwise
might
have
a
harder
time
to
have
access
to.
D
So
I
think
we
might
want
to
find
a
way
there
to
talk,
maybe
about
some
very
specific
problems
and
maybe
also
starting
to
actively
publish
something
around
this
and
not
maybe
starting
with
the
white
paper
per
se,
but
individual
questions
and
then
maybe
putting
some
material
together
that
we
can
share
with
people
and
put
them
in
the
right
direction.
Maybe
even
invite
somebody
like
if
you
find
somebody
who
has
done
something
interesting
on
specific
topics.
D
Just
starting
to
collect
this
information
because
there's
always
people
who
especially,
are
in
the
deaf
real
space,
who
want
and
kind
of
need
to
present
on
topics
anyways
based
on
their
role,
and
there
are
other
people
who
want
to
have
this
information
about
us,
creating
them
around
the
topic.
This
might
be
something
like
very
helpful.
D
A
D
Like
very
straightforward
approach
would
be,
if
you
want
to
get
like
people
involved,
you
create
the
landscape.
I
mean
landscapes
are
landscapes,
but
still
everybody
wants
to
be
on
that
landscape,
and
we
can
say
well
forever,
landscape
right
that
we
want
to
link
at
least
to
a
short
demo
what
the
tool
is
doing
or
something
like
this.
D
This
could
also
be
an
opportunity
that
would
at
least
get
you,
vendors
and
open
source
projects
to
more
actively
engage
with
you,
because
there
are
still
a
lot
of
people
have
to
go
to
be
on
a
landscape
and
as
much
as
people
say
that
they're
like
the
worst
thing
on
the
planet,
at
least
they
draw
interest
in
a
certain
direction
and
just
have
to
kind
of
use
it
wisely.
To
put
it
that
way,
and
maybe
not
everything
should
be
a
white
paper.
It
could
also
be
just
a
short
article.
D
That's
maybe
a
takeaway
from
me
like
how
can
we,
as
a
working
group,
actually
sorry
as
a
tag,
publish
a
blog
post
on
topics
under
the
cncf
umbrella.
E
E
It
might
be
something
to
kind
of,
like
stir
up
some
interest
in
that
topic,
and
then
maybe
we
will
get
more
responses
on
things
so
and
also
seeing
as
the
the
like.
The
the
the
multi-tenant
white
paper
idea
is
also
under
the
cooperative
delivery
working
group.
You
know
there
will
be
a
lot
of
work
in
in
different
work
streams.
E
So
if
we
could
take
some
of
the
ideas
that
we
had
originally
and
have
that
as
a
as
an
article
instead
of
a
full-on
white
paper
or
you
know,
descriptive
patterns
or
whatever
just
something
a
little
bit
more
simpler
to
get
going
and
maybe,
through
the
you
know,
working
with
version
two
of
the
the
operator
white
paper
also
kind
of
like
gets
us
in
the
you
know.
A
D
D
We
mentioned
it
yesterday
in
the
toc
meeting
and
there
was
interest
from
other
people
as
well,
but
we
could
ask
them
like
write
something
on
a
specific
topic,
and
I
remember
like
when
I
wrote
my
first
book.
I
did
exactly
this.
I
started
out
with
blog
posts,
lots
of
them
and
then
eventually
took
the
blog
posts
and
combined
them
into
like
a
initially
a
bigger
series
that
wasn't
like
the
perfect
book
like
it
would
read
like
front
to
end,
but
it
had
like
very
specific
chapters
on
specific
topics.
D
Still
that
was
yeah
back
in
the
days
when
we
printed
books.
Well,
let's
do
this
kind
of
do
it
today.
It
was
almost
like
an
me
back
then
called
like
the
almanac.
That
was
like
the
collection
after
the
post
that
had
the
most
interest
collected
them
together
and
then
had
a
printed
format
on
it,
and
it
was
actually
very
well
received
because
it
was
also
easier
to
digest
for
people,
because
a
book
you
very
often
have
to
read
from
like
front
to
back,
while
these
kind
of
things
can
be
consumed.
D
Okay,
like
have
now,
I
know,
20
minutes
on
a
train
or
I'm
waiting
at
the
airport
or
whatever
situation
that
you're
in
and
I'm
quickly
reading
like
this
short
piece.
That
is
usually
a
couple
of
pages,
long
yeah.
Let's
try
to
do
this.
Let's
let
me
figure
out
what
the
best
channel
would
be.
D
G
I
also
think
jennifer
already
reached
out
to
amy,
but
I
don't
know
what
the
outcome
was
so
she's.
The
only
thing
she
said
was
that
it
should
not
be
on
medium.
As
far
as
I
know,.
D
You
can't
do
a
github
page,
because,
whatever
I
don't,
I
I
don't
really
care
just
wanted
to
run
it
by
amy,
because
at
some
point
there
was
a
discussion,
especially
on
cncf,
published
content,
because,
as
you
might
be
aware
of-
or
most
of
you
might
be
aware
of,
there's
also
the
like
commercial
arm
of
just
the
cncf.
That's
pushing
in
that
direction
like
where
you
obviously
pay
for,
like
a
webinar
or
or
something
like
that,
that
we
might
want
to
obviously
handle
slightly
different
over
here.
Yeah.
C
So
our
so
yeah
this
is
really
so
it
just
to
some.
I
think
our
general
action
item
for
ourselves
and
anybody
here
is.
We
want
to
develop
a
series
of
hypotheses
here,
maybe
published
in
blog
posts,
tech
radar
things
like
that,
and
I
guess
we
have
a
few
couple
that
we
mentioned
in
the
charter,
but
yeah
there's
probably
a
lot
more
ideas,
because
you
know
this
kind
of
an
emerging
space
for
us,
so
I
guess
communicate
with
us
on
slack
or
github.
C
If
you
have
ideas,
I
mean
obviously
we'll
be
at
the
meetings,
but
don't
wait
for
them.
Yeah
actually.
D
A
Yeah,
so
good,
perhaps
for
a
something
like
a
user
story
app
here,
because
we
were
building
one
here
at
gitlab
and
probably
I
can
I
can
share
it
in
some
form.
It's
a
mirror
right
now.
There
isn't
that
there
isn't
anything
very
specific,
but
it
just
highlights
all
the
many
color,
as
well
as
the
kind
of
stable
pattern
of
moving
from
from
that
to
production.
A
So
I
don't
know
how
to
share
it
best,
but
we
can
try
to
do
it
somehow.
D
A
D
Yeah,
I
think
also
everything
we
can
share
and
also
ask
other
people
like
chris,
who
used
to
be
here
to
like
put
it
into
like
a
newsletter
like
devopsish.
I
think
everything
we
can
like
have
that's
easily
shareable
like
on
twitter
or
other
channels
is
helpful
for
raising
awareness,
but
also
it
should
be
value
content.
I
mean
that
that
would
be
the
case
here
as
well,
so
like
a
short
version
of
the,
for
example,
cooperative
delivery
and
maybe
like
what
it
is
why
it
exists.
D
I
mean,
if
you
really
do
kind
of
understand
it,
but
everybody's
still
kind
of
like
with
the
name
still
having
like
this
hard
time
like
I
understand
it.
Doesn't
what
again,
it
really
is.
Yeah,
I'm
I
mean
naming,
is
hard,
but
I
think
just
getting
like
two
more
like
one
of
the
specific
problems
and
and
picking
it
and
like
sharing
ideas
and
then
inviting
people
to
present
on
those
specific
topics,
I
think
the
gaining
momentum
is
is
always
the
hardest
one
and
it's
like
more
or
less
acting
like
a
community
manager
even
like
driving.
D
Some
of
these
activities
here
is
yeah,
and
I
think
we
also,
I
think
it
might
change
hopefully
now
a
bit.
I
think
people
a
bit
over
online
content
right
now
and
everybody's,
like
looking
forward
to
physical
events
more
again
or
at
least
getting
out
of
their
house
more
and
they're
like
want
to
consume
content
in
a
more
interactive
fashion.
Now
again,.
D
And
there's
also
way
more
content
out
there
like
a
lot
of
people
move
to
online
content
production
like
I
don't
know
how
it's
for
you,
but
I
can't
even
keep
up
with
all
the
content.
That's
that's
currently
available
on
the
market.
Yeah
yeah.
I
also
have
to
drop
in
like
roughly
15
minutes
here.
So
we
will
finish
definitely
on
time
I
mean
you
obviously
can
continue.
C
Yeah,
that's
me
so
I
put
in
there.
One
thing
I
wanted
to
mention
is
you
know:
we've
been
working
on
this.
I've
been
working
on
this
a
lot
the
past
six
months.
Maybe
there's
some
opportunity.
I've
seen
a
lot
of
initiatives
that
are
very
similar.
The
open
get
ops,
one,
the
observed
k
s,
one
which
are
both
both
oriented
around
creating
a
resi.
You
know
kind
of
a
resilient,
reusable
demo
environment
to
show
you
know,
patterns
for
observability
in
the
case
of
zero
kns,
open,
git
ops.
C
At
this
point,
so
you
know
I
I
kind
of
have
chimed
in
on
the
observed.
Kns
stuff,
like
hey
potato,
would
be
great
yeah,
so
I
just
wanted
to
kind
of
bring
that
up
if
we
can
encourage
them
if
they're
interested,
obviously
but
yeah.
C
The
the
next
thing
is
that
we
are
continuing
to
adopt
microservices
with
the
operator
framework
example
which
daniel
wasn't
you,
but
I
asked
a
couple
of
folks
on
your
team.
They
reviewed
that
so
I
merged
that
catch
is
out.
There
still
needs
a
review,
I'm
hoping
to
work
on
argo
cds
soon.
Those
are
both
still
open,
argo,
cd
and
captain.
C
I
did
add
a
service
discovery
scenario
which
is
kind
of
towards
what
we're
thinking
about
with
co-op
delivery
like
how
do
you
get
infrastructure
and
other
service
discovery
is
a
little
bit
not
quite
this,
but
it's
like
it's
the
first
one,
I'm
thinking
towards
like
how
do
we
combine
bits
of
infrastructure
with
with
app
logic?
I
still
want
to
work
on
the
database
one.
I
actually
needed
this
service
discovery,
one
because
my
idea
for
the
database
or
authentication
one
was
to
have
a
different.
A
different
part
show
up.
C
You
know,
based
on
your
session
or
something
and
catch
the
session
redis
so
yeah.
That's
why
I
did
the
service
discovery
early,
but
yeah
feedback
on
that,
like
that,
I
kind
of
I'm
thinking
of
that.
As
integration
like
we
have
a
bunch
of
delivery
scenarios,
but
now
we're
kind
of
like
how
do
we
deliver
and
integrate
with
the
rest
of
your
environment?
You
know
which
is
kind
of
what
co-op
delivery
is
is
about.
C
Maybe
we
should
call
it
integration,
app
integration
and
then
the
last
thing
I
put
a
note
there,
which
is
that
there's
a
now
a
workflow,
because
I
just
wanted
us
to
have
it
like
to
be
able
to
tag
the
repo
and
the
images
kind
of
asynchronously
pretty
easily
because
there's
a
workflow
into
the
tags,
the
repo
for
every
push
to
master.
But
I
don't
know
if
that's
the
best
for
the
long
term.
C
You
could
tag
the
repo
manually
could
tag.
Images
could
even
tag
it
latest.
You
know
if
that
actually
happened
to
me.
I
don't
think
it
got
tagged
late
as
the
last
one
yeah
and
that's
it.
We
could
use
more
yeah
a
pitch
to
everybody.
We
could
use
need
to
migrate.
Argo,
cd
and
captain,
I
think,
are
the
most
important
to
get
migrated
to
the
microservices.
C
C
D
As
good
first
issues,
because
I
know
that
a
lot
of
people
usually
reach
out
and
looking
for
open
source
projects
that
they
can
contribute
to
also
like,
I
think
we
can't
really
apply
for
google
sum
of
code
because
we're
not
an
official
project
and
it's
too
late,
now
anyways.
D
D
F
Sorry
seriously,
I
just
want
to
say
I
think
it's
a
cool
project.
I
started
looking
at
it.
I
shared
it
with
some
folks
on
on
my
team
and
I
think,
as
we
develop,
you
know
like
a
new
system
for
delivering
content.
We
should
definitely
be
mindful
of
the
existing
solutions,
which
I
think
your
repo
does
a
great
job
of
capturing.
F
So
there's
a
great
deal
of
content
there
for
us
to
consume
and
think
about
and
yeah.
I
think
it's
cool.
D
And
I
think
it
was
a
nice
detox
demo,
especially
like
the
the
services
that
are
slower
than
the
old
ones,
where
I
could
like
really
show,
is
like
an
automated,
a
b
testing,
automated
rollback
scenario
in
there
that
you
could
play
around
and
maybe
also
for
you
daniel.
We
have
an
operator
example
in
there
that
is
based
on
a
helm,
chart
for
historic
reasons
more
or
less.
D
F
Yeah,
no
that's
cool.
We
have
this.
This
is
a
one
thing.
We're
working
on
is
like
new
packaging
format
for
operators.
I
think
you
know
in
the
llm
world
we
have
this
concept
of
like
it's
called
the
registry.
V1
bundle,
which
is
essentially
a
container
image,
contains
manifest
directory
with,
like
a
csv
and
stuff
like
that
in
it.
F
We're
moving
to
more
of
just
a
plain
manifest
format
where
you
can
just
provide
raw
kubernetes
manifests
and
those
get
applied,
and
we
don't
support
templating
or
anything
like
that
yet,
but
like
obviously,
how
much
to
do
that,
but
yeah
it
would
be,
it
would
be
really
interesting
to
if,
if
once
we
stabilize
on
sort
of
the
the
structure
for
the
new
newer
format,
maybe
we
can
contribute
that
to
the
to
the
project
to
the
potato
head
once
it
becomes
more
stable.
D
D
C
I
I
actually
have
been
thinking
of
this
as
like
the
the
apps.
This
is
the
get
ops.
If
you
want
your
own
bespoke
get
ops,
you
write
an
operator
for
your
app.
That's
it's
like
an
app-specific,
git
ops
operator,
to
what
I
keep
doing.
D
D
Yeah,
given
that
I
have
to
draw
like
last
topic,
which
is
still
mine
here,.
D
The
app
delivery
conference,
so
I
was
a
bit
too
optimistic
which
amy
also
wanted
me
to
be,
but
I
still
tried
to
be
too
optimistic
so,
and
there
was
some
real
issue
going
on
there
as
well,
like
I
had
the
issue
that
my
corporate
email
client
was
following
all
of
my
emails
from
the
cncfs
spam,
so
I
didn't
get
any
updates
on
on
this
topic.
So
this
is
really
like
my
fault
kind
of
still
blaming
it
on
some
tooling
that
I'm
using
anyways
it
won't
happen
for
kubecon
eu.
D
We
could
still
plan
a
get
together
in
one
or
the
other
way
for
everybody
who's
going
to
be
there.
I
mean
there's
going
to
be
plenty
of
places
to
do
it,
but
for
north
america
I
really
want
to
kick
off
the
planning
that
we
have
on
app
delivery
day
for
north
america,
and
we
have
more
than
enough
time
now
planning
this
out.
So
I
think
it's
september
october
this
year
to
really
have
something
around
app
delivery.
D
That's
I
think
we
just
got
and
we
can
talk
to
like
lots
of
other
people
who
can
provide
us
input
like
the
security
team
is
doing
their
day.
Zero
event
seek
a
tech
network
is
doing
that
day.
Zero
events,
so
there's
lots
of
them
do
their
day,
zero
events
where
we
can
like
go
for
advice,
how
they
make
it
work,
what
they
learned
out
of
it
and
so
forth.
D
So
this
is
definitely
something
that
we
can
drive
forward
right
now,
so
it
would
have
been
nice
at
eu,
but
definitely
for
the
end
of
the
for
fall.
We
should
working
on
on
making
this
actually
work
all
right,
any
other
topics
anybody
wants
to
bring
up
today,
because
otherwise
I
would
close
like
five
minutes
early,
simply
because
I
have
to
jump
on
another
call
in
five
minutes.
I
mean
you're
free
to
continue
here,
obviously,
but
I'll
have
to
drop
ahead
of
time.
E
I
don't
know
if
scott
was
going
to
jump
in
and
talk
about
the
ghettos
working
group,
but
yeah
we
can.
You
can
do
that
and
then
next
time
anyway,.
D
Right
yeah:
we
can
do
this
next
time.
Also
what
I
put
in
there
there
might
be
actually
two
project
presentations
for
the
next
meeting
that
I
still
need
to
confirm.
First,
one
is
miss
style
who's
applied
for
send
a
project,
that's
supplied
for
sandbox
and
the
second
one
would
be
open
feature
which
is
also
sandbox
projects.
I
mean
you
might
have
getting
interviews
with
having
projects
again.
D
C
Folks,
one
other
thing
before
I
conveyor
we
had
said
a
while
ago
that
we
would
open
an
issue
for
them
in
the
tag
app
delivery,
repo
at
least
to
track.
The
conversations
can
we
do
that
I
didn't
want
to
do.
I
think
maybe
jennifer
should
do
it
or
elise.
If
you
think
you
should
do
it.
D
C
Came
into
our
meeting
in
beginning
of
february,
and
we
said
that
you
know
we'd
open
it,
that's
what
I
was
just
going
from
so
yeah.
D
G
D
Just
know
it
was
a
very
lengthy
discussion
where
I
then
had
to
drop
on
that
meeting,
but
I'll
ask
him
what
the
tc's
opinion
is
I'll,
take
it
from
there
yeah
and
also
like
for
you,
daniel.
If
you
want
to
bring
up
a
specific
topic,
I
mean
this
team
has
seen
conveyor
as
a
whole,
but
if
you
want
to
bring
in
specific
topics,
feel
free
to
do
that
as
part
of
the
the
agenda.