►
From YouTube: CNCF TAG App-Delivery 2022-02-16
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
B
A
B
I've
been
debating
should
I
get
like
my
own,
like
a
mic
like
a
problem,
it's
just.
My
camera
picks
me
up
now.
So.
A
C
Yeah
one
question:
I
would
have
one:
does
it,
doesn't
it
kind
of
what's
the
word,
isn't
it
in
your
site
authority
and
isn't
it
disturbing
you
a
little
bit
that
you
have.
C
C
C
B
A
I'll
point
it
directly
at
my
face,
but
the
nice
part
is,
is
like
anything
could
happen
around
me
like
a
door
could
slam?
Maybe
you
would
hear
that
maybe,
but
somebody
could
be
like
outside
with
a
pressure
washer.
This
has
happened
before
and
it
doesn't
get
picked
up
on
the
mic
at
all.
So
when
I
was
in
my
unfinished
basement,
it
was
like
the
perfect
mic
to
have,
because
there's
just
so
much
noise.
D
A
Like
a
lot
of
the
stuff,
I've
just
had
right.
The
upgraded
camera
is
actually
not
really
an
upgrade.
It's
a
used
camera
right.
So
really,
I
spent
money
on
a
good
lens
right
like
that's
it.
The
lights
were
cheap.
Like
80
bucks,
it
was
probably
as
much
money
to
buy
the
mount
and
the
monopod
that
the
lights
sit
on
as
the
lights
themselves,
so
I've
gone
through
quite
a
few
brackets
and
microphone
arms
like
within
the
first
two
years
of
having
a
mic
like
this.
A
I'm
with
you,
five
arms,
like
one
literally
exploded
during
a
live
stream
once
it
was
kind
of
funny
like
this,
is
all
springs
and
housing
and
such,
and
if
this
goes
it
all
like
just
goes
down
from
there.
D
Today
I
had
the
mechanic
there.
He
has
never
seen
this
in
his
entire
career.
What
did
you
do
with
the
thing
that
always
comforting
anyways
yeah,
but
I
learned
a
lot
about
how
they
actually
work
internally
today,
yeah,
we
are
five
minutes
in
so
that's
when
we
get
started,
see
you
already
adding
yourself
to
the
list.
As
you
can
see,
we
already
have
worked
on
an
agenda,
so
I
already
got
the
golden
star
from
amy,
I'm
a
bit
bragging
here,
because
we
now
have
an
agenda
up
and
running.
D
So
that's
great
and
obviously
it's
even
it's
even
greater
that
actually
people
volunteer
to
contribute
because
I'm
more
or
less
dmc
here
on
most
of
those
topics
so
yeah.
It's
mostly
working
group
updates
today
project
update
on
potato
head
and
then
I
put
two
things
in
there
kubicon
eu,
which
is
more
of
an
open
discussion
like
what
are
we
going
to
do
around
kubecon
eu
for
the
app
delivery
team
and
then
a
short
update
on
the
application
delivery
conference.
So
before
we
jump
into
the
details
the
actual
conference
day,
it
was
tight.
D
D
But
for
this
is
where
I
put
kubecon
you
in
there
separately,
I
think
we
should
still
have
the
chance
maybe
to
meet
up
and
do
something
on
a
socializing
type
of
of
of
level
and
how
we
want
to
get
together.
Okay,
but
let's,
I
think,
jump
right
into
chaos.
Engineering,
kartik,.
D
E
Is
hey,
hey,
we've
done
hope.
Everyone
is
doing
great
sorry
about
not
being
able
to
turn
on
the
camera.
Today,
a
very
quick
update
on
the
chaos
engineering
work
group.
E
We
made
some
progress
on
the
the
charter.
The
charter
did
get
a
lot
of
feedback
from
the
tag,
leads
tag,
security,
observability
and
tag
app
delivery.
We
resolved
most
of
the
comments
factored
in
the
feedback
and
modified
this
charter.
Now.
This
is
also
committed
in
current
form,
into
the
chaos
engineering
work
group
repository
here,
and
I
think
from
my
understanding.
We
probably
need
to
go
for
a
2c
vote
on
this
working
group
based
on
the
the
current
charter.
That's
my
understanding.
At
this
point.
C
E
So
this
information
is
also
placed
into
the
repository
we
had
a
few
user
interviews.
One
of
the
working
model
points
in
the
charter
was
to
invite
users
and
vendors
to
come
and
talk
about
their
perspectives.
E
Around
chaos,
engineering,
we
had
some
end
users
from
organizations
like
linscott,
hello,
doc
and
iag
talk
about
how
they
started
their
chaos,
engineering
practice
where
they
are
right
now
and
what
challenges
they
face,
what
they
are
looking
forward
to
from
the
the
community,
the
cncf
community
and
helping
them
do
better
in
their
chaos
journey.
E
There
are
a
few
user
interviews
that
are
lined
up
for
the
coming
months.
As
you
can
see
there,
there
have
been
no
user
interviews
over
the
last
few
months,
but
there
is
one
lined
up
for
the
next
meeting,
there's
one
tomorrow,
but
the
one
that
is,
after
that
we
do
have
a
inducer
discussion
lined
up
and
that's
something
that
we
are
sort
of
collating
here
and
hope
to
take
information
from
there
and
add
back
into
the
into
the
white
paper.
E
I
I
did
see
a
couple
of
comments,
the
ones
that
are
tbd
at
this
point,
apart
from
us,
going
to
the
toc
vote
and
what
other
things
need
to
be
changed
on
the
charter
is
increasing
the
interested
parties
and
taking
it
to
a
wider
audience
right
now.
This
this
is
fairly
smaller
group
and
the
group
meeting
attendance
is
also
limited
to
a
few
members.
So
we
would
definitely
like
to
increase
that.
E
So
that's
something
that
we're
working
towards,
and
the
other
aspect
is
that
of
sponsorship
and
the
chair.
There
was
a
comment
from
alex
on
the
charter
about
as
having
an
interim
chair
before
we
actually
end
up
having
actual
chairs.
So
those
are
two
things
that
are
tbd
and
the
items
that
we
would
need
help
on
like
clothes
mentioned
on
the
on
the
on
the
slack
is
anybody
that
is
interested
in
contributing
to
the
white
paper
in
in
terms
of
topics
or
or
some
topics
that
you
would
like
to
see.
E
I
think
that
that
would
be
great.
That
is
probably
the
main
activity
that
we
are
engaged
in
as
a
working
group
in
the
next
few
days.
The
the
recent
discussion
was
about
adding
some
infographics
and
make
it
simpler
for
folks
to
use
so
any
feedback
around.
E
What
you
would
like
to
see
in
terms
of
explanation
to
chaos
and
scenarios
covered
that
that
would
be
a
great
area
to
contribute,
and
if
you
are
already
practicing
chaos,
engineering
or
know
someone
that
does
if
they
are
willing
to
share
their
story,
then
I
think
inviting
them
to
this
working
group
would
be
another
way
great
way
to
contribute.
We
were
always
happy
to
speak
to
them
that
there
is
a
template,
basically
a
three-fourth
slider,
which
which
has
some
basic
questions
about
how
they
got
started.
E
D
A
quick
update,
yeah.
I
think
it's
actually
amazing
that
there
was
actually
content
out
there
that
I
even
didn't
know
like
the
interviews.
I
think
this
is
super
super
amazing.
These
are
videos
right.
I
assume
right,
yes,
yeah
yeah
do
to
be.
I
also
add
them
to
the
app
delivery
youtube
channel.
I'm
looking
at
thomas
because
I
did
not
add
them,
so
my
answer
would
be
no.
D
C
E
We
did
add
into
the
app
delivery
channel.
Probably
not
all
the
recordings
have
gone
in
there
been
a
little
bit
lacks
on
updating
it
right
away,
but
some
of
these
are
already
there.
I
think
there
are
a
few
which
needs
to
go
in.
I
think
the
last
three
four
meetings
are
not
yet
in
the
app
delivery
channel,
but
we
will
get
it
up
there.
E
B
Yeah
I
just
was
wondering
kartik:
how
did
you
find
those
user
interviews?
How
did
you
find
those
users
and
get
them
to
agree.
E
Yeah,
I
think
a
couple
of
them
were
leads
josh
from
an
event
that
we
conducted
called
chaos
carnival.
We,
as
in
the
litmus
community,
was
involved
in
that
effort,
and
these
folks
happen
to
use
the
platform
and
we
learnt
about
their
usage
there
and
just
wanted
them
to
come
over
and
talk
a
little
bit
at
length.
What
they
presented
was
a
little
specific.
E
We
wanted
them
to
talk
more
about
the
not
so
much
about
the
tool
or
the
platform,
but
their
general
philosophy,
around
chaos
and
things
like
that.
That's
how
we
invited.
D
D
E
Right,
I
think
alex
did
volunteer.
I
was
a
little
confused
about
what
is
a
chair
versus
a
sponsor,
not
too
clear
about
that.
That's
the
question
that
I
asked
here,
but
yeah.
D
I
think
that's
a
historic
template,
maybe
to
quickly
jump
in
here.
The
chair
is
the
one
who's
actually
doing
the
work
and
like
organizing
it
not
like
doing
all
the
work
but
like
keeping
the
team
organized
and
it
shows
it's
moving
forward.
Sponsors
were
in
there
if
you
have
a
dedicated
sponsor,
say
from
the
toc.
So
in
the
past
four
working
groups
we
had
in
there
so
assume
like
harry
from
the
toc,
would
say.
Yes,
I'm
sponsoring
this,
I'm
thinking
it's
a
good
idea.
It's
usually
helpful.
D
If
you
have
those
sponsors
directly
from
from
the
toc,
you
don't
actually
need
them
necessarily,
but
we
are
still
using
the
old
template
for
the
charter
that
we
used
before
chairs
is,
I
think,
really
the
key
topic,
because
in
order
to
vote
on
something,
people
need
to
ensure
that
things
are
moving
moving
forward
and
if
you
and
alex
are
willing
to
take
this,
I
think
it's
it's
great,
but
because
this
would
be
most
likely.
The
the
initial
feedback
like
who's
who's,
driving
this
activity,
and
then
we
can
go
like
again.
D
E
Got
it
yeah,
understood
yeah,
I
I'll
probably
work
with
alex.
I
I'll
be
happy
to
assist
him
as
well.
So
I
think
we
will
also
bring
this
up
in
tomorrow's
discussion.
We
have
a
few
folks
from
chaos
mission.
Here's
blade
that
join
in
to
these
calls
sometimes
as
well.
So
we
will
definitely
take
this
knowledge
back
there.
Yeah.
D
D
Yeah
on
the
white
paper,
I
think
it's
best
to
like
really
reach
out
to
people
where
you
really
would
like
help
and
what
you
would
like
help
on.
I
think
that's
the
like
hell.
Can
you
help
me
here?
Can
you
do
this?
This
is
usually
more
helpful
than
one
thing
I
would
put
in
there.
I
don't
know
whether
we
need
it,
but
thomas
knows
from
the
operator
white
paper
where
we
were
like
literally
circling
around
a
large
number
of
times
is
who
this
white
paper
is
actually
for.
D
So,
if
you
don't
have
the
target
audience
in
there,
that
might
be
one
of
my
tips
because
we
were
talking
in
the
beginning.
It
was
yes,
this
is
for
practitioners
who
want
to
learn
it.
Then
it
was
yeah.
This
is
for
people
who
want
to
use
it.
Then
it
became
this
is,
and
this
was
actually
a
real
request.
So
I'm
not
making
this
up
to
make
some
more
funny
meeting.
This
is
for
my
boss,
who
doesn't
understand
cloud
native.
We
wouldn't
say
no
stop.
This
is
not
who
this
is
for.
D
This
is
for
people
who
want
to
adopt
chaos,
engineering
or
who
started
to
do
chaos,
engineering
and
want
to
get
better
and
like
do
it
in
a
more
mature
way.
That
usually
avoids
a
lot
of
conversations
you
have
later
on
when
people
say
well,
they're
not
talking
about
the
business
impacts.
I
know
because
these
people
want
to
get
stuff
done
just
as
something,
but
we
learned
what
helped
us
to
avoid
a
lot
of
conversations
where
we
just
said:
ask
them
what
we're
doing
here.
E
Right
right
got
it,
I
think
right
now.
The
way
we
are
sort
of
going
about
it
is
targeting
the
the
people
who
are
beginning
their
chaos
journey,
which
explains
some
more
theory
on
what
is
chaos
and
how
to
get
started,
and
things
like
that
but,
like
you
said
there
would
be
lot
of
practitioners,
people
who
already
got
started,
who
might
want
to
take
their
practice
to
the
next
level
by
taking
reference
from
this.
E
So
I
think
we
would
gradually
get
both
elements
into
the
white
paper
and
I
I
will
respond
on
the
will
sort
of
try
to
post
some
messages
on
the
slack
channel,
app
delivery,
as
well
as
the
group's
live
channel
on
specific
work
items
that
we
need
help
on.
I
agree
it's
like
a
little
too
dissolved
or
high
level
right
now.
I
probably
will
work
that
out
and
make
that
as
more
actionable
items
and
ask
for
help
there.
D
B
Yeah,
so
I'm
representing
me
and
robert,
I
will
I'm
just
going
to
quickly
share
my
screen
that
seemed
to
work
well
for
you
karthik,
so
I'll
put
everyone
over
there
and
I
will
close
so
I'm
just
gonna
walk
through
the
stuff,
that's
in
the
in
the
dock
and
the
meeting
node
stock.
So
first
thing
first
area
is
we
we
want
to
gather
more
use
cases
from
users.
That's
why
I
asked
about.
What's
going
on
with
the
user
interviews,
we've
published
a
couple
forms.
B
This
is
kind
of
a
minimum,
viable
survey
and
kind
of
minimum
viable.
How
we're
publishing
it
just
to
see.
What's
going
on
just
to
see
how
it
works
yeah,
it
might
even
be
interesting
to
add
the
chaos
one
here
too,
so
yeah
so
send
people
here.
I
I'm
curious.
Also,
you
know
we.
B
We
talked
about
what
what
our
core
goals
are
and
cooperative
delivery,
and
so
these
kind
of
capture
that
too,
what
we're,
what
we're
hoping
to
ultimately
build
or
ultimately
help
people
with
related
to
that
we've
got
alex,
opened
an
issue
about
a
multi-tenant,
kubernetes
white
paper.
So
towards
that
end,
people
are
talking
in
that
issue,
but
we
also
that's.
B
We've
got
a
couple
comments
here
about
you
know
people
submitting
their
their
use
cases
last
thing
that
I
put
on
the
list
for
cooperative
delivery
is
like
something
that
I'm
working
on
and
something
you
know
it's
one
of
our.
I
guess
two
streams,
one
is
gathering
information
and
the
second
one
is
based
on
the
information
actually
developing
a
library
of
patterns.
So
that's
kind
of
an
ask.
You
know
what
do
you
think
of
this?
You
know.
Do
you
have
any
recommended
patterns
to
add.
B
Yeah,
so
that's
kind
of
high
level
we're
where
we're
at
today
for
cooperative
delivery.
C
B
Publish
it
on
my
like
linkedin,
I
didn't
publish
it
on
twitter,
yet
kind
of
wanted
to
see
how
it
went
for
the
first
few
people.
You
know.
If,
if
yeah
we
can
think
about
how
to
publish,
you
know
make
this
more
public
or
you
know
we
can
decide.
Okay,
these
are
good
questions.
We're
getting
the
right
answers,
let's
put
it
in
a
different
format,
but
you
know
a
little
bit
of
ins.
I
always
say
one
customer
is
better
than
none.
So
a
little
bit
of
insight
is
good.
B
A
E
D
B
Just
those
first
couple:
if
you
look
in
the
issue,
what
happens
is
when
they
fill
it
out?
It
creates
a
public
issue
that
gets
and
then
we
can
continue
discussion
there
or
you
know
it's
just
insight
for
us.
B
D
D
D
This
moving
forward
so
I'll
also
put
this
into
the
next
toc
update
as
well
great
that
we
also
ask
people
because.
B
D
C
D
C
Sorry,
one
question
to
the
previous
one
is
like
there's
the
organization
question,
but
do
could
it
be
interesting
to
have
a
little
bit
of
insights
about
the
the
user
itself,
because,
okay,
that
the
information
comes
in
but
might
be
pretty
specific,
whether
you
are
a
tackle
finance
or
startup?
C
So,
just
now
that
I
I
started
to
look
into
it
a
bit
more
and
of
course
you
want
to
keep
it
small
and
short,
so
I
don't
really
have
a
good
proposal,
just
the
the
topic
itself,
like
a
single
question
about
about
the
user
type.
If
you
could
come
up
with
something,
perhaps
I
would.
E
B
B
Yeah
yeah,
that's
true:
it's
just
attributes
instead
of
the
actual
name,
but
by
the
way
a
good
thing
about
doing
github
is
you
can
just
submit
a
pull
request
that
modifies
the
template
and
it's
just
the
ammo.
So
you
can
add
another
field.
You
can
debate.
B
Yeah,
it's
just
under
the
dot
github!
Oh
right,
your
gitlab!
Sorry,
if
you
just
under
the
github
folder
issue,
template
is
where
there's
just
yaml
files
to
describe
those
things.
So
it's
pretty
self
intuitive.
B
Okay,
so
I'll
switch
over
to
potato
head.
So
just
a
couple
things
to
call
out.
You
know
I'm
pretty
interested
in
using
this
towards
one
of
those
initiatives
in
the
cooperative
delivery.
Ouija
to
use
it
to
demonstrate
you
know
integrating
some
infrastructure
with
app.
So
that's
why
I'm
pretty
involved
in
this
one
too.
There's
three
pr's
out
there.
You
know
the
more
comments,
the
better.
I
guess,
we'll
merge
them
eventually,
with
minimal
comments.
One
is
to
make
service
discovery
work.
B
I
did
a
quick
demo
on
that
in
the
last
cooperative
delivery
one.
It
basically
lets
the
service
discovery
of
the
backend
parts,
be
done
through
a
config
map
or
a
file
instead
of
static.
So
it's
just
a
start.
I'm
hoping
that
people
like
service
mesh
people
and
stuff
like
that
can
can
you
know
leverage
it's
an
interface.
So
can
leverage
the
same
thing
to
you
know.
Do
something
else
demonstrate
other
integrations
in
the
future.
B
So
that's
that
one
catch
is
catch
came
to
the
toc
a
few
weeks
ago,
so
I
noticed
they
were
coming,
so
I
pinged
them.
Can
you
please
update
your
thing
there?
So
they
did.
I
haven't
had
a
chance
to
review
it
yet,
but
if
anybody
else
wants
to
they'll
be
great
and
an
operator
framework
is,
is
one
that
I
have
in
there
also,
which
I
need
to
kind
of
finalize,
but
I
had
to
argue
I
had
the
sorry
I
was
looking
at
argo.
B
I
had
the
operator
team
look
at
it
too,
and
they
were
okay
with
it
asks
in
potato
head.
We
could
use-
and
I
I
know
aloe's
gonna
say
you
should
reach
out
to
them
directly.
So
I'm
reaching
out
to
some
of
you
right
here.
We
still
need
a
little
help
with
the
remaining
delivery
scenarios.
Argo
kept
in
cube,
vela
and
then
the
kind
of
the
long
tail
gimlet
k
app
cnab.
B
Now
you
know
I'll
get
that
eventually
or
someone
will
but
yeah
the
more
people
that
can
help
the
better
and
then
the
last
thing
I
wanted
to
show
is
kind
of
an
idea.
I
think
we
have
time.
So
if
you
don't
mind
I'll,
just
quickly
share
my
screen
again,
I've
already
gotten
to
the
page,
so
it's
actually
inspired
by
a
customer
that
I'm
helping
them
out
with
eclipse
shay
which
red
hat
you
know
sells
as
code
ready
workspaces.
B
So
that's
what
it
says
here,
but
that
is
based
on
a
well
they're.
They
they
use
a
format
called
dev
file
which
is
actually
in
they've
applied
for
sandbox
at
cncf.
So
I
just
wanted
to
to
show
whoops
what
that
could
do
for
us.
So
I've
already
opened
it
up
in
here,
but
I
want
to
show
how
easy
it
is
to
get
that
I've
already
put
a
dev
file
into
a
fork
of
my
own
repo.
You
can
kind
of
see
there.
The
soya,
so
workspaces
at
openshift.com
is
an
eclipse
shea
server.
B
So
sorry,
I'm
using
that
here,
but
you
just
pointed
at
where
your
dev
file
is-
and
this
is
the
main
demo-
it
picks
it
up.
This
is
actually
free,
so
you
can
you
can
try
it
here.
It
will
go
through
that.
It's
gonna,
it's
gonna,
do
all
this
stuff
applying
dev
file.
It's
not
happy
because
I
can
only
run
one
at
a
time,
so
you
can't
start
more
than
one
workspace,
but
this
is
what
you'll
end
up
with
afterwards
and
you
can
hack
around.
B
So
basically
what
you
get
in
this
I'm
getting
a
little
too
far
into
dev
file,
but
you
get
a
pod
with
a
lot
of
containers
that
you
can
kind
of
go
off
and
run
things
in
so
ideally
I'd
be
able
to,
you
know,
run
all
the
tests,
but
this
is
early
days.
I
don't
have
all
the
I
don't
have
jq.
It
doesn't
have
cube
cuddle.
So
this
it's
not
quite
working,
but
but
you
get
the
idea
and
I
could
point
this
container
dev.
B
Yeah,
so
that
that
was
it
I
just
wanted,
like.
I
was
kind
of
thinking,
eventually
there's
a
there's
def
file
v2.
This
is
actually
v1,
but
eventually
maybe
drop
a
dev
file
in
and
that
will
make
it
even
easier
for
folks
to
you
know,
use
it
as
a
playground
hack
on
it.
You
know
and
demonstrate
another
cncf
project.
At
the
same
time,.
D
B
Yeah,
no,
you
don't
need
it's
not
red
hat
at
all,
but
you
need
an
eclipse
shape
server.
If
you
want
to
use
you
know
our
host
that
red
hat's
hosted
eclipse
shay.
Then
it's
at
workspaces.openshift.com,
that's
free
you,
but
you
have
to
sign
up.
You
don't
have
a
red
hat
email,
but
it
you
know
you
have
to
put
an
email
and
register
and
it's
publicized
all
over
the
eclipse
shea.
So
it's
the
cncf
plus
eclipse
here.
D
It's
like
in
the
past.
We
edited
it
for
like
local
kubernetes
environments,
but
I
mean
cloud-based
environments
are
even
more
convenient.
B
D
What
about
you
thinking
about
potato
head
when
we
again
do
google
summer
of
code
applications
within
the
cncf?
That
might
be
something
to
ask
chris,
because
officially
we
can't,
but
I
mean
we
can't
we
kind
of.
Can
we
just
have
to
politely
ask
but
we're
not
a
cncf
project
per
se,
but
we're
one
of
those
demo
projects.
So
I
wouldn't
see
why
we
couldn't.
C
B
D
D
Okay,
looking
at
the
time
green
time
so
asks
okay,
find
people
who
do
it.
Def
file
demo,
anything
else
from
your
side.
You
want
to
bring
it
up
on
potato
head.
D
A
Yeah
so
there's
a
contributor
summit
happening
at
kubecon
eu.
I
forget,
which
day
day
zero.
It
is
but
because
there's
two
day
zeros
nowadays,
but
that
is
a
space
that
this
group
could
use
if
they
so
wanted
to
to,
like
you
know,
just
meet
and
say
hi
or
whoever's
there
there's
not
really
we're
not
putting
a
ton
of
rigor
into
like
programming
for
the
contributor
summit
this
year.
It's
just
gonna
kind
of
be
just
a
meeting
space.
A
D
Yeah,
I
think
it's
good
to
share
with
them
yeah.
We
can
then
discuss
format,
but
there's,
I
think,
some
words
that
we
could
share
and
yeah
by
the
way
I
didn't
know
whether
you
saw
this
people
are
referencing
the
operator
white
paper
just
for
not
liking
operator,
but
that's
that's
another
topic,
but
it
gets
public
attention,
so
people
are
referencing
it
as
an
official
resource.
I
think,
is
good.
D
Yeah
yeah:
let's
comment
on
this
one
then
yeah
and
I
think
we'll
get
together
how
we
would
set
it
up.
Yeah
app
delivery
conference,
quick
update.
I
I
briefly
mentioned
it.
D
The
the
zero
type
conference
yeah,
okay,
is
there
events?
It's
not
conference,
it's
your
event,
yeah.
Obviously
we
are
too
late
for
the
one
happening
in
in
valencia.
I
think
which
that's
why
I
think
that
that
one
would
be
a
great
way
of
getting
together-
and
I
think
also
for
the
for
this
group
here-
where
a
lot
of
people
have
never
met
the
other
people
like
in
person
while
collaborating
for
two
years.
D
I
think
we
could
also
find
some
type
of
social
gathering
for
us
to
at
least
meet
in
person,
which
we
haven't
done
so
setting
this
up
as
well
and
sharing
it
for
the
bigger
delivery
conference.
Yeah.
Let's
plan
for
fall,
I'm
still
working
through
the
details
of
what
we
actually
need
to
do
there
and
what
type
of
support
we
will
need.
D
Obviously,
we
will
need
a
couple
of
people
supporting
this
event,
so
I'm
not
taking
the
task
of
like
figuring
out
what
we
need
to
do
working
with
security
and
with
the
events
team
to
have
an
idea
and
in
the
next
two
weeks
I
should
have
a
clear
understanding
what
needs
to
be
done
there
like.
We
need
to
obviously
take
care
of
a
lot
of
things
ourselves,
there's
also
a
lot
of
infrastructure
on
the
cncf
I'll.
D
Do
a
bit
more
detail
deep
dive
into
this
in
in
the
in
the
next
meetings,
because,
quite
honestly,
I
just
have
to
get
myself
familiarize
myself
with
what
really
needs
to
be
do
to
be
done
there,
but
I
think
it's
a
great
opportunity
for
us,
which
then
brings
us
to
the
next
point
on
volunteers.
So
we
will
need
people
to
obviously
support
this
from
a
program
committee
from
the
day
of
the
conference
and
I'm
sure
there's
like
100
other
things
that
you
we
need
to
take
care
of,
so
that
this
really
runs
smoothly.
D
A
I
think
that
would
go
really
well
to
be
honest
with
you.
If
there
was
a
potato
hackathon
like
and
we
got
the
word
out
there,
somehow
that
would
be
really
cool
yeah.
It
could
be
fun.
D
D
But
there
are
services
that
have
apis
because
we
need
an
external
third
party
service
anyways
that
should
be
integrated
with
api
keys.
Actually,
that's
useful
yeah.
That's
it
pretty
much
for
this
weekend.
Looking
at
do
we
have
def
file?
Okay
future.
Do
you
think
that
the
dev
file
people
would
actually
be
willing
to?
Because
we
haven't
done
this
in
a
while,
like
having
smaller
project
presentations?
D
B
Yeah,
I
could
ask
them
it's
because
they're
in
sandbox
anyway,
so
yeah
great
chance
for
they're
trying
to
get
the
sandbox,
it
would
be
a
great
chance
for
them
to
to
talk
they're
they're,
the
eclipse
shade
developers
are
a
lot
of
them,
are
red
hat.
So
that's
why
I
say
I
can
ask
them.
D
D
That's
that's
something
like
reaching
out
more
to
projects
to
once
this
group
is
bigger,
but
not
like
having
a
separate
video
on
specific
projects
and
what
they're
doing
and
sharing
it,
because
many
people
can
do
the
cncf
also
for
exposure.
D
B
Just
that
awesome,
because
there's
actually
it's
a
great
time
because
what's
happening
right
now
is
there
was
dev
file
v1
and
now
there's
a
v2
which
is
further
kind
of
separating
the
ide
from
the
workspace
and
I'm
excited
about
it.
So
I'd
love
for
them
to
it's
a
good
inflection
point
for
them
to
talk
to
us.
D
A
D
What
we
would
we
want
projects
to
show
when
they
introduce
themselves
like
not
that
we
like
forcing
them
to
do
exactly
what
we
want
them
to
do,
but
giving
them
an
idea
like.
We
should
cover
like
these
things,
that,
as
part
of
the
project,
because
to
be
fair,
most
of
the
incubation
project
proposals
cover
rather
project
growth
and
what
they're
doing
roadmap-wise
but
they're
never
actively
showing
how
like
people
could
use
it
like
on
an
everyday
basis,
and
that
also
helps
us
to
share
more
of
those
use
cases
yeah.
D
Another
thing
that's
coming
up
for
the
next
one,
there's
actually
a
project.
We
are
working
on
right
now
that
will
be
submitted
into
sandbox
and-
and
we
means
dynatrace
plus
some
other
companies
in
the
field
on
creating
a
cloud
native
feature
flagging
project.
D
D
Yeah,
it's
it's
early
stage
to
talk
to
thomas
I'll
put
in
there.
Next
time
we
will.
We
will
be
able
to
show
a
bit
more
actually.
D
Without
we
talked
to
gitlab
we're
talking
to
aws,
we
talked
to
google
microsoft,
red
hat,
pretty
much
reached
out
to
everybody.
I
think
the
challenge
is
right
now,
there's
like
many
apis
out
there
and
they're
not
interchangeably.
Also,
they
are
technically
kind
of
like
doing
the
same
thing
and
there
is
no
cloud
native
version
like
there's
some
external
feature,
flagging
server,
that's
running
where
you're
controlling
your
feature,
flags
and
your
application
doesn't
know
anything
about
it.
So
it's
not
part
of
your
github
process.
Really,
it's
not
really
linked
to
your
application
deployment.
D
D
Just
as
we
added
some
minutes
left,
I
just
wanted
to
to
bring
it
up
again.
If
you
want
more
information,
feel
obviously
free
to
ping
me
on
this
one,
I
think
it's
that's!
That's
why
we
kicked
it
off.
I
think
it's
well
worth
working
in
that
that
that
direction
and
it
will
be
the
next
round
of
sandbox
submissions,
and
yes,
it's
done
at
race.
It's
gitlab,
we
have
also,
I
think
who's
already
agreed
is
yeah.
D
That's
the
old
one
canonical
is
part
of
it
as
well,
reaching
out
to
replicate
it
who's,
not
officially
yet
there,
but
also
trying
to
chime
in
there
we'll
talk
about
it
more
next
time
and
again,
if
you
want
to
know
something
early
on
or
if
you
know
would
know
somebody
inside
your
company
organization,
other
projects,
you're
involved
in
for
three
to
seven
hour
away,
but
next
time
I'll
bring
the
product
manager
and
also
from
some
of
the
participating
teams
on
to
talk
a
bit
more
about
it.