►
From YouTube: CNCF Cooperative Delivery WG 2021-12-08
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
There
better
hurry
up.
It's
there's
little.
D
B
B
Yeah,
you
know
a
couple
times
where
I
spoke
at,
like
in
like
indian
conferences
and
stuff,
like
that,
I
just
you
know,
try
to
make
sure
that
they
know
which
time
someone
I'm
actually
in,
because
that
could
get
really
early
if
they,
if
they
schedule
me
at
the
wrong
part
of
the
evening
for
them,
you
know.
B
B
She
she
is
seven
in
february,
but
she's
still
as
stupid
as
she
wasn't
three
so
yeah.
B
You
know
she
always
have
to
be.
You
know
bothering
me
when
I'm
doing
meetings,
so
you
know
I
I
we
we
started
having
like
lockdowns
again,
which
is
no
fun,
so
I
haven't
been
to
the
office
for
for
a
week,
so
she
keeps
on
bothering
me
in
all
these
meetings.
C
B
What's
the
what's
this,
what's
their
slack
reminder,
setup
right
did
that
work
does
that
trigger?
I
can't
find
slack.
B
A
Hello,
good,
yes,
so
the
only
thing
which
is
quite
a
bit
a
bit
difficult
at
the
moment
is
that
we
have
to
upload
the
meetings
manually
to
youtube
afterwards.
But
I'll
take
care
of
that,
and
I
also
uploaded
your
last
recordings
to
to
to
youtube
right.
B
C
D
B
Yeah
I
saw
that
that's
that's
really
good.
A
So
we'll
discuss
if
the
working
group
cheers
will
be
able
to
to
to
add
events
and
so
on.
B
But
at
that
point
you
know
just
make
sure
we're
early
again
asking
people
to
to
happen.
Is
it
it's
not
just
you
know
it's
you
as
well.
You
can
also
add
stuff.
So
all
the
the,
although.
B
C
Yeah,
okay,
so
should
we
it's
a
few
minutes
past
the
hour?
Should
we
go
ahead
and
kick
things
off
sure.
C
So
yeah,
I
guess
where
to
start
the
agenda
from
just
reviewing
briefly
last
time
we
met,
which
was
three
weeks
ago.
We
talked
about
the
survey,
we
talked
about
patterns
library
and
we
talked
about
infrastructure
models.
Robert
was
off
working
on
survey,
stuff
and
and
some
others
too.
I
just
was
glancing
at
this
morning.
He'll
start
us
off
today
the
pattern
stuff.
I
submitted
a
couple
issues.
C
I
don't
plan
to
talk
about
it
today,
unless
people
want
to
and
then
the
resource
model
stuff
I
I
haven't
tackled
yet
just
in
the
interest
of
time,
I'm
I'll
get
to
that.
Eventually,.
B
We
could
we
could
talk
about
patterns
as
well,
because
I
have
an
idea
and
now
I'll
just
want
to
see
if
we
we're,
if
we're
doing
it
right,
let's
see
if
we're
doing
it
right,
but
yeah
we
can
talk,
but
we
can
talk
about
the
survey
goals
and
and
there's
no
reason
to
even
mention
me
because
this
it's
it's
raining
all
all
the
way
so
irene's
doing
a
great
job
at
filling
out.
This
form
the
the
document
here
so
so
kudos
to
you.
D
It
probably
me
just
writing
comments,
as
as
I
work
with
a
document.
B
Yeah
yeah,
so
it
was
just.
It
was
a
bit
funny.
Also
there
was
a
lot
of
I
had
to
try
to.
I
had
to
try
to
google
translate
it,
but
I
don't
yeah.
I
didn't
want
that
to
be
my
interpretation
of
the
text
so,
but
but
obviously
then
I
guess.
B
B
I
guess
because
we
were
kind
of
we
wanted
to
do
a
survey
for
many
reasons,
but
we
didn't
really
have
a
really
good
like
like
a
definite
goal
for
everything
and,
like
I
said
irene
here,
has
been
doing
a
lot
of
affiliate
work
based
on
what
we
talked
about
last
time
and
and
you
you
have
written
out
a
couple
of
calls,
do
you
want
to
go
through
them
or
actually
just.
D
D
It's
two
documents
in
one.
I
have
not
touched
the
bits
that
I
think
josh
added
last
time.
D
D
So
so
it's
it's
good
to
see
that
we
are
thinking
in
the
same
similar
direction.
D
So
I
tried
to
write
out
the
motivation
why
we
are
planning
to
run
the
survey
and
I,
if
I'll
refer
back
to
what
josh
wrote
here
under
the
girls,
I
think
one
of
the
outcomes
is
is
to
actually
gather
their
ideas
or
or
build
build
agenda
for
for
the
working
group.
What
are
the
problems
that
people
are
facing?
What
what
are
the
challenges
that
the
working
group
should
be
focusing
on
or
or
if
we
have
a?
D
If
you
feel
that
something
is
important,
is
this
actually
the
problem
that
the
people
are
facing,
so
so
I
think
what
we
should
do.
Okay,
the
second
second
bit
I
wanted
to
mention
is
I
tried
to
pick
up
the
hypothesis
from
the
work
group
charter.
D
I
think
these
these
are
the
things
that
we
feel
that
are
valid,
but
I'm
not
sure
if
they
have
been
validated
of
the
if
there
isn't
any
data
behind
it.
So
so
these
questions,
like
the
disconnect
between
application
and
infrastructure
delivery,
is
causing
problems.
How
painful
are
these
problems?
Is
it
worth
dealing
with?
D
These
what
example
of
these
problems
are:
are
there
something
that
are
segment
specific,
and
I
think
this
is
the
this
is
the
most
valuable
bit
if,
if
we
have,
if
we
can
come
up
of
the
list
of
the
problems
that
we
think
are
relevant,
we
should
try
to
validate
these
problems
so
that
we
could
get
feedback.
What
are
the
things
that
people
relate
to,
or
or-
and
we
should
leave
an
open
open
answer
so
that
people
can
add
to
these.
D
But
yeah,
I
hope
that
I
I
can
do
more,
but
it's
it's
at
least
it's
the
start
also
for
for
the
segmentation.
D
B
Yeah
yeah
yeah.
I
think
it's
a
good
like
at
least
like
it's
a
good.
B
Yeah,
if,
if
I
was
just
trying
to
summarize
a
lot
of
industries,
I'm
probably
going
to
miss
most
of
the
industries
in
the
world,
so
why
not
copy
what
everyone
else
do?
No,
but
it's!
I
think
it's
a
really
good.
You
know
starting
point
and
I
I
like
the
the
that
we're
trying
to
think
of
like
the
motivation,
because
I
think
many
of
us
are
in
agreement
with
what
the
motivation
or
why
we
want
to
do
a
survey,
but
it's
kind
of
hard
to
put
into
words.
B
Sometimes
that
makes
sense
and
you
actually
have
some
sort
of
outcome,
but
but
I
think
we're
we're
we're
getting
there.
I
don't
think
this
should
be
too
rushed,
because
we
have
things
that
we
can
do
like,
for
instance,
document
patterns
and
and
try
to
help
in
like
that
aspect,
so
that
we
don't
just
get
the
service
survey
out
there
just
to
just
do
it
and
and
then
the
data
is
not
useful
because
we
didn't
think
it
through.
B
So
I
think
it's
better
that
we
spend
a
little
bit
of
time
on
on
doing
exactly
this
trying
to
figure.
You
know
figure
directly
out
what
we
actually
want
to
do
here
so,
but
this
is
a
really
great
start
and
thank
you
rain
and
also
thank
you
josh
for
spending
time
on
getting
stuff
in
here.
C
B
We
yeah
we
can.
I
think
we
can
at
least
get
like
there's.
B
One
goal
right,
so
you
know
it's
gonna
be
hard
to
to
word
one
goal
that
would
fit
the
entire
survey,
but
at
least
kind
of
ballpark
a
couple
of
goals
like
what
do
you
want
to
get
out
of
it?
B
And-
and
perhaps
you
know
at
least
like
a
like
a
a
working
draft
of
what
our
goals
are
and
I
think,
trying
to
figure
out
what
people
are
doing
and
or
if
it's
even
valuable
for
people
to
try
to
use
the
same
approach
both
for
app
delivery
and
infrastructure
like
it
does
people
do
people
want
that
or
do
people
want
separation
and,
and
maybe
that
differs
from
sector
sector
et
cetera,
et
cetera
things
like
that,
so
we
have
something
to
work
on
when
it
comes
to
patterns
and
and
other
helpful
things,
and
I
don't
want
to
say
white
paper
because
every
time
I
do
that,
I
think
people
are
going
to
go.
C
Through
and
looking
through,
like
ring
your
last
two
pages
map,
the
state
of
the
art
and
disco,
like
that
seems
like
you're
starting
to
okay,
these
are
specific
details.
Now
we
can
form
a
question
that
would
tell
us
if
some
people
might
answer
in
a
way
that
says.
Oh,
the
organization
does
have
transfer
problems
like
it
feels
like
we're
getting
close
to
that
down.
There.
D
If
you,
if
you
move
up
a
bit
to
the
motivation
of
put
off
a
part
of
the
sentence
to
italic
there,
I
think
this
is
the.
This
is
the
core.
I
think
the
core
reason
to
run.
The
survey
is
to
make
sure
that
the
that
the
working
group
is
focusing
on
on
the
right
thing,
so
you
you
described
it
through
the
problems.
D
We
want
to
understand
what
the
problems
are,
but
it
pretty
much
comes
down
to
the
same
same
idea
that
we
want
to
know
what
the
problems
are,
so
that
we
are
focusing
on
the
right
thing
and-
and
the
second
part
is
when
we
are
trying
to
have
an
impact
on
on
the
community
or
change
something
we
should
be
monitoring.
What's
what
the
current
current
state
of
the
art
and
if
we
would
repeat
this
work
survey,
try
to
figure
out
or
validate
new
problems.
D
B
Yeah
yeah,
it's
it,
but
everything
is
moving
here
right
so
every
year
there's
going
to
be
something
new.
That
might
be
the
way
that
everything
you
know
it's
gonna
like
this
is
the
right
direction
up
until
when
the
new
year
comes
and
we
move
in
a
different
direction,
you
know
that's
I.t,
but
but
yeah.
B
I
think
that's
that's
valuable,
at
least
to
see
at
least
like
map
out
like
where,
where
stuff
is
going
so
yeah,
like,
I
said
it's
a
really
good
good
starting
point,
and
and
thanks
for
doing
all
this
work.
B
Really
awesome
is.
C
B
A
Also
like
the
idea
of
the
survey
in
this
case,
because
I
think
that's
a
that's
a
problem
which
many
which
which
many
companies
might
face-
and
I
think
you
as
a
working
group,
should
know
which
problems
they
face
and
what
you,
what
you
could
deal
with
yeah.
We
did
some
some
similar
thing
for
the
operator
working
group
working
group
about
one
year
ago,
and
I
I
also
agree
with
with
robert.
You
don't
have
to
rush
and
think
over
the
things
you
are
doing
here,
so
we
we
did
it
in
a
very
short
term.
A
So
our
survey,
we
didn't
get
much
much
feedback
and
therefore-
and
therefore
you
should
you-
you
should
have
an
idea
what
you
want
to
know
really
and
how
long
your
your
your
your
survey
should
be.
So
we
had
us
with
about
10
to
15
questions.
I
think
this
was
this
was
too
much.
A
A
Reach
out
to
jennifer
and
you
when
we
when,
when
you
are
at
that
point.
B
A
And
chris
also
seems
like
he's,
adding
something
there.
B
B
Are
there
anything
that
we
should?
Is
there
anything
more
that
we
should
talk
about
when
it
comes
to
search
because,
obviously,
like
I
said,
I
don't
think
we
need
to
rush
this.
I
think
we
we
need
to
just
continue
to
work
on
these
documents
and
and
and
see
where
this
leads
us,
and
I
think
we
have
a
great
starting
point.
I
agree
that
if
we
want
to
have
this
like
a
a
an
annual
thing,
you
know
to
to
map
out
the
the
current
trends
and
stuff
like
that.
B
It
we
we
should.
You
know
we
should
spend
some
time
actually
knowing
what
we're
gonna
ask
people,
because,
or
else
and
and
obviously
yeah
too
long.
That's
that's
not
good,
because
no
one
has
time
for
anything
and
if
they
see
like
15
questions,
they're,
probably
gonna
go
15
questions
all
right.
I
don't
want
to
do
that,
so
we
we
need
to
work
a
bit
on
condensing
what
we
want
and
to
I
don't
want
to
say
a
number
but
like
five
to
ten.
Let's
say
that
questions
maybe.
D
I
I
think
the
the
goal
to
keep
the
service
short
is
is
the
right
one,
but
but
now
when
we
want
to
get
some
feedback
about
these
problems
that
we
want
to
validate,
I
think
we
should
start
writing
down
these
ideas
or
or
what
problems
we
would
like
to
validate,
because
probably
there
are
more
than
15
of
these
problems
alone.
So
we
need
to.
We
need
to
pick
our
most
probable
candidates
from
from
the
list
and
and
we
should
start
putting
this
list
together.
C
Are
you
suggesting
that
I
mean
building
up
a
list
of
scenarios,
makes
sense,
but
he's
suggesting
that
we
should
ask
the
users
about
specific
scenarios,
as
opposed
to
say,
being
a
little
more
open-ended
and
letting
them.
D
D
A
B
And
that
that
is
also
a
thing
that
we
could
do,
but,
but
obviously,
if
we
can
back
that
up
also
the
data
from
the
survey.
So
I
think
that
we
should
at
least
like
get
the
survey
and
the
general
idea
at
least
of
what
we're
trying
to
figure
out
and
and
at
that
point
we
might
just
do
some.
You
know
you
know
talking
to
end
users
and
stuff
like
that,
but
obviously
that
can
come
both
from
the
survey
and
and
just
asking
for
people's
opinions.
D
There
is
one
problem:
when
you
start
asking
for
people's
contact
information,
you
get
all
kind
of
compliance
requirements
and
and
how
you
process
the
data,
how
you
store
their
contact,
data
or
email
addresses,
so
how
we
are,
or
or
actually
what
tools
are
going
to
be
used
to
run
the
survey,
how
the
data
is
going
to
be
stored.
Who
will
have
have
access
to
the
data
to
do
that?
Analyzes
just
mention
these.
These
questions
in
one
bullet
point
there.
So
this
will
be
relevant.
B
D
Just
dropped
the
link
in
chat
that
will
get
you
what
you
need
as
far
as
like
that,
data
compliance
and
all
the
fun
regulatory
bits,
because
cnc
maintains.
B
Yeah
there's
actually
like
a
process.
You
get
surveys
out
the
door
and
cncf
managed
that,
for
you,
yeah,
that's,
that's
perfect
and
and
using
something
like
surveymonkey,
and
it
makes
it
much
better
than
creating
google
forms
or
yes
or
microsoft.
Forms.
C
B
C
Just
thinking
one
other
thing:
we,
if
somebody
wants
to
come
to
this
meeting
and
talk
about
an
issue
for
10
minutes.
I
mean
it's
a
little
risky,
but.
B
I
think
we
should
be
open
to
just
if
people
have
something
that
affects
this
working
group
in
any
way
that
they
can
just
come
and
say
yeah.
I
want
to
discuss
this
issue
I
have,
and
obviously,
if
you,
if
you
work
with
clients
and
stuff
like
that,
you
you
can
just
not
mention
who
you're
you're
having
this
issue
with
or
not
who
you're
having
decision
but
which
clients
you're
working
on
that
and
where
you
have
this
issue
or,
and
that's
also
for
like
end
user
interviews,
that
could
be
totally
anonymous.
B
Even
you
just
you
know,
reach
out
to
us
and
and
we'll
you
know,
then
find
a
time
where
we
can
just
sit
down
for
like
30
minutes
and
talk
about
stuff
and
the
only
thing
that
we
document
is
like
what
kind
of
type
of
issues
are
you
having
not
who
you
are
or
anything
like
that.
So
then
you
know
that
would
be
totally
on
anonymous
at
that
point.
B
D
B
No
more
all
right
patterns
seems
like
everyone's
talking
about
patterns
so
josh
you,
you
submitted
a
couple
patterns,
but
I,
but
I
have
a
I
wanted
to
submit
that
as
a
discussion
or
an
issue
all
depending,
but
at
the
same
time
I
just
kind
of
want
to
talk
about
it.
So
I
was
thinking
of
documenting
a
sort
of
like
trying
to
find
a
name
for
it
as
well
like
a
terraform
all
up
or
everything
on
terraform
or
whatever
you
want
to
call
it.
B
So
you
know
doing
the
entire
process
with
one
tool,
and
I
think
that
for
that
to
make
sense
as
a
thing
that
you
do,
you
there's
a
lot
of
code
involved.
So
I
I
kind
of
need
to
show
how
you
would
do
that
in
a
more
dynamic
way,
not
just
like
creating
a
bunch
of
static
files.
B
B
Because
at
one
point
you
you
would,
we
would
start
producing
a
lot
of
things.
It
can
get
pretty
big
if
the
things
that
I
think
of
when
it
comes
to
the
like
a
terraform
for
everything
to
get
that
to
a
point
where
it's
actually
a
good
pattern,
I
would
actually
need
to
just
have
a
like
a
big.
You
know.
Deployment
scenario
set
up
that
can
that
can
be
pretty
involved?
C
C
There
would
be
a
base
implementation
in
potato.
I
guess
it's
a
little
tricky
like
right
now
the
basement
might
be
like
kind
to
get
a
kubernetes
cluster
and
a
script.
That's
that's
pretty
raw
and
then
maybe
your
like
your
terraform
would
say
replace
the
database
with
this,
or
maybe
you
say,
replace
the
whole
sale
thing
with
this,
but
yeah
it
is
it's
a
pretty
the
yeah.
C
So
the
answer
to
your
question
is
that
potato
has
meant
to
gradually
evolve
into
more
and
more
of
a
framework
that
gives
you
that
stuff,
but
if
you're
replacing
chunks
of
it,
then
yeah.
If
you're
gonna
replace
like
four
parts
of
the
infrastructure,
then
that's
that
would
be
pretty
big
code.
I
agree.
C
C
What
we
could
do,
maybe
we
could
start
from
a
doc
like
it,
doesn't
have
to
be
finished.
In
other
words,
let's
say
you
I
would
suggest
in
your
case,
is
that
you
would
start
with
a
proposal.
You'd
open
a
proposal.
People
say
hey.
I
want
to
show
how
to
use
terraform
to
deploy
five
different
parts
of
the
infrastructure
for
a
potato
head
like
app.
You
know
we
discuss
it
there.
Maybe
you
write
the
doc
first
and
we
I
mean
I
could
help
you.
C
Others
could
chime
in
and
say:
okay
I'll
help,
you
write
the
implementation
or
you
know,
you've
got
snippets
in
there
and
you're
able
to
show
some
of
it,
but
you
weren't
able
to
put
together
all
of
the
error
checking
or
something.
But
you
know,
maybe
we
could
advance
it
that
way
like
you
could
do
the
doc
first.
But
then
we
get
the
code
before
we
finalize.
B
And
for
me
to
show
off
a
solution
using
terraform
for
everything,
so
meaning
you're,
setting
up
your
infrastructure
and
you're
able
to
add
applications
in
in
in
a
cert
like
iterative.
So
you
don't
need
to
find
everything
every
time
you
do
that,
so
there's
going
to
be
a
lot
of
input
variables,
creating
lists
doing
loops
based
on
that
do,
checking
for
putting
it
into
the
right
et
cetera.
So
it's
going
to
be
it's
going
to
be
pretty
complex.
B
That's
basically
what
I
work
with
that's
exactly
what
I'm
saying
right
now
so
so
I
know
for
a
fact
that
you
can
do
that
and
but
it's
a
relatively
big
thing
and
I
don't
want
to
start
off
just
creating
this
giant
example
and
then
it's
out
of
school
for
what
we're
trying
to
do
with
patterns.
I
think
that's
kind
of
what
I'm
getting
at,
but
if
people
agree
that
you
know,
for
instance
like
terraform
for
everything
or
all
in
all
on
board
a
terraform
train
or
whatever
you're
gonna
call.
It
call
that
pattern.
B
If
that's
useful
for
people
to
show
off
in
a
real
example
of
how
you
would
do
that,
then
I
would
be
happy
to
do
it.
It's
just
it's
going
to
get
pretty
big
pretty
quickly
and
I'm
not
totally
sure
if
it's
actually
going
to
fit
into
the
structure
of
the
tag,
app
delivery.
Repo
with
you
know,
there's
going
to
be
a
lot
of
things
there.
You
know,
maybe
that
just
completely
you
know
directly
into
the
potato
head
use
that
as
an
example
set
that
up
there
in
in
that
repository.
B
So
I
it's
gonna
open
any
question
I
don't
expect
to
get
like
this
is
what
you're
supposed
to
do,
but
I
think
I'm
going
to
add
a
discussion
on
the
and
try
to
get
in
the
points
that
I
want
to
get
across
like
why
you
can
do
that
with
terraform
and
then
see
if
people
agree
or
disagree
or
if
they
want
to
see
something
over
something
else.
B
So
this
has
a
start.
I
guess
you
josh
added
a
couple
of
patterns
right.
C
I
added
two
things
actually
so
just
one
pattern,
but
the
first
one
is
a
meta
pattern,
a
pattern
for
patterns
and
that's
kind
of
what
I'm
referring
to
now.
My
that
one
is
a
proposal
like
hey.
If
robert
wants
to
start
terraform
for
everything,
how
do
we
get
a
little
feedback?
How
does
he
you
know
verify
that
we
agree
or
you
know,
how
do
we
even
give
you
input
like
hey?
Could
you
do
a
database
first,
because
I
need
that
for
mine,
so
yeah.
C
So
that's
that's
what
that
first
one
is
kind
of
about
it's
just
rough.
It's
just
to
say.
Oh,
this
is
our
process
and
then
the
second
one
is
just
just
to
have
one
as
an
example
of
here's,
the
process,
here's
how
it
would
look.
So
I
put
up
a
proposal
of
something
that
I've
encountered,
not
with
red
hat,
but
when
I
was
at
a
customer
before
was
deploying
databases
and
synchronizing
credentials.
So
I
know
that
was
a
problem
for
a
customer,
or
at
least
one.
C
So
I
put
that
up
there
and
and
the
goal
is
kind
of
what
you
were
just
saying.
Robert
to
I
haven't
even
started
working
on,
it
is
just
to
say,
hey,
I'm
thinking
about
this.
Is
anyone
else
thinking
about
this?
You
know
what
what
are
the?
What
are
the
things
people
are
trying
and
so
far
it's
all
crickets,
but
you
know
gotta
start
somewhere.
B
You're,
usually,
is
it's
you
know
like
I
said
people
are
busy.
I
just
keep
using
that
as
a
thing,
but
but
people
are
but
I
think
if
we
first
look
at
the
the
pattern
for
pattern
pattern
for
patterns
for
pattern,
that
makes
it
hard
for
me
as
a
norwegian,
but
if
you
can
like
start
there,
I
think
just
getting.
How
do
we?
How
do
we
show
off
the
code
and
like
where
do
we
put
it
in
a
way
that
can't
get
translated
to
any
of
the
no
matter?
B
What
we're
going
to
use?
I
think
that's
at
least
a
like.
I
said,
a
a
good
start,
everything's
a
good
start,
but
for
the
way
that
the
different
examples
for
potato
had
have
been
added.
That's
that's
on
delivery,
folder
in
the
potato
ad
repository
right,
yeah,
yeah,.
C
Yeah,
I
haven't
totally
thought
through
how
new
patterns
will
actually
fit
in
there
like
the
dock.
If
that's
what
you're
calling
out
like
like,
if
I
do
that
database
pattern
and
yeah
I'll
implement
it
in
potato
head,
but
then
I'll
write
a
walkthrough
and
maybe
that
would
go
in
the
app
delivery
repo.
I
think
that's
what
we
started
discussing
last
time.
B
C
B
I
guess
that's,
that's
that's
something
we
need
to,
I
guess
discuss
on
a
higher
level
and
because
some
of
these
aren't
cooperative
delivery
in
itself
and
then
some
will
be
so
this
is
the
pa
is
the
idea
of
patterns.
I
know
I
know
the
ghettos
working
group
is
is
doing
a
lot
of
pattern
stuff,
but
that's
under
the
open
get
ups
project
so
that
kind
of
lands
in
its
own
repository.
B
B
A
And
let's,
let's
see
where
this
leads
to
so
I
think
I
think
currently
we're
not
in
the
state
that
we
could
open
up
a
project
as
open
keytops
or
whatever.
B
B
Would
it
be
overkill
if
I'm
thinking
that
there's
a
patterns
folder
in
the
tag,
app
delivery,
where
you
have
like
the
documentation-
and
you
know,
step
two
things
and
then
it
will
actually
reference
code?
That
would
be
because
you're
using
potato
ad,
it
will
reference
code
in
the
potato
head
organization,
and
then
you
would
have
its
own
repository
for
that
pattern.
C
A
A
And
we
should
try
to
find
the
easy
way
to
describe
the
pattern
in
the
in
the
potato
head
itself,
so
I'm
not
sure
if
it
has
to
be
an
own
repository
for
that
it
might
also
be
that
a
folder
is
enough
for
each
pattern,
but
yes,
it
would
be
totally
okay.
For
me,
I
think.
B
A
A
B
Yeah,
so
just
to
be
totally
clear
what
you
know
why
I'm
saying
this
is
because
in
people
will
come
into
the
tag,
app
delivery
repository
and
find
the
patterns
list
there,
they
would
read
about
the
patterns
and
why
that
why
it's
a
good
way
to
do
whatever
you
want
to
try
to
describe
with
the
pattern,
because
it
might
be
from
corporate
delivery,
it
might
not
be,
and
then
the
example
called
then
would
that
get
built
in
its
own
repository.
A
For
me,
so
I
think
as
long
as
these
are
examples
only
for
deploying
the
potato
head
itself
so
yeah
and
then
they
would.
Then
it
would
make
sense
that
you
that
you
have
them
in
the
deliver
in
the
delivery
folder
of
the
potato
head,
because
that
these
things
should
be
part
of
that.
B
C
C
Maybe
we
could
I'll
I'll
put
a
note
in
the
number
167
or
if
you
all
robert,
if
you
want
to,
I
really
like
the
way
you
described
that
I
think
there
were
a
couple
gray
points,
but
overall
I
love.
I
like
those
ideas.
C
C
One
other
update
on
that,
so
I
did
talk
briefly
with
scott
rigby
from
the
get
ops
group
and
a
little
bit
with
the
observability
group,
the
observability
group.
I
just
chimed
in
on
their
slack,
because
I
noticed
that
they're
also
trying
to
build
a
library
of
patterns-
and
I
was
like
well,
they
even
mentioned
potato
head,
but
they
mentioned
a
couple
other
ones
too.
So
I
wanted
to
encourage
them
to
use
that
and
I
don't
have
they.
We
were
going
to
talk
last
week,
but
it
didn't
work
out.
C
So
I
I
have
to
see
what's
going
on,
but
but
it
seems
like
they're
they're,
the
kind
of
interest
is
there
and
then
on
the
open,
git
ops.
One
thing
that
we
kind
of
realized
is
that
they've
got
a
lot
of
the
governance
in
place,
but
they're
still
they
don't
really
have
many
like
actual
tutorials
and
patterns.
Yet
so
there
might
be
some
synergy
there.
Like
hey.
Can
we
utilize
your
you
know,
chrome,
your
framework
and
and
and
start
putting
in
this
content.
C
B
A
lot
of
the
a
lot
of
the
open
get
ups
and
pattern
discussions.
I
I've
been
a
part
of
that
and
and
the
reason
why
it
kind
of
works.
B
There
is
because
you
have
your
you:
have
the
open
get
ops
organization
where
you
can
have
its
own
repository
for
these
things,
so
it
kind
of
makes
it
a
little
bit
more
cleaner,
while
we're
kind
of
like
in
a
in
a
software
of
a
subfolder
of
a
subfolder,
and
at
that
point,
if
we
then
gonna
start
adding
like
60
teraform
files-
and
you
know
it's
gonna-
get
really
complicated,
really
quickly
to
figure
out
where
everything
is.
So
that's
why
I'm?
B
So
you
know
having
that
in
in
the
middle
of
everything
else
could
be
a
little
bit
massive
and
at
that
point
having
its
own,
you
know
repository
for
that
just
makes
sense,
but
others
might
be
really
small.
On
the
other
hand,
so
yeah.
A
B
B
All
right,
let's
talk
about
that
some
more
in
the
in
the
in
the
tag
meeting,
rather
than
doing
it
here,
because
it
kind
of
affects
every
everyone
at
this
point
all
right,
I
guess
that's
the
agenda.
B
Everything
is
moving.
Well,
I
don't
want
to
say
slowly
but
but
we're
getting
there.
I
think
the
the
work
that's
been
done
on
the
the
server
draft
document
is
really
good
and-
and
I
think,
we're
all
kind
of
landing
some
of
the
ideas
that
we
have
a
little
bit
more
like
like
getting
a
more
you
know,
yeah
we're
starting
to
to
to
be
able
to.
Actually
you
know
word
what
we're
trying
to
do,
which
is
good,
because
at
the
start
we
were,
it
was
really
hard.
B
C
It's
it's
about
the
next
step,
it's
just
about
taking
the
next.
I
don't
care
if
you
take
a
big
step
or
a
little
step
or
anything
just
take
the
next
little
step.
B
A
Yeah
right
so
starting
a
working
group
is
always
hard
yeah,
but
I
think
you're
making
good
progress
and
it
looks.
B
I
think
this
will
be
really
good
we're
just
we
just
need
to
start
to
get
the
ball
rolling
and
and
like
any
like
big
avalanche,
you
you
start
in
the
small,
the
small
little
snowballs
and
then
all
of
a
sudden,
it's
big
snowballs
and
all
of
a
sudden,
the
entire
mountain
comes
down.
So
you
know
we
just
need
to
get
started
and
then-
and
everything
will
work
by
itself.
Apparently.
B
All
right,
well
thanks,
so
much
for
for
for
joining
us,
it's
good
to
see
more
than
than
than
the
few
people
have
been,
and
I
guess
we'll
reconvene
well
in
two
weeks
but
next
week
for
tire
gap,
delivery
as
well.
C
D
B
So
I'll
say
that
the
the
the
logical
thing
here
is
that
this
20
seconds
is
awfully
close
to
christmas,
and
people
probably
have
taken
time
off,
and
everything
like
that.
So
at
that
point,
so
maybe
not
have
it
20
seconds
and
then
rather
was
the
fifth
yeah
fifth
of
january
being
the
next
one.
D
D
You
could
perhaps
just
have
any
updates
or
anything
like
a
sink
on
the
channel,
and
then
people
who
want
to
like
get
away
from
their
families
and
do
some
work.
They
could
like
optionally,
talk
only
on
slack
and
then
just
make
it
to
like
a
sink.
B
Yeah,
let's,
let's
just
keep
it
open,
though
I
guess:
okay
sounds
good
awesome
thanks,
all
I'll
we'll
see
each
other
soon.
D
B
A
B
Hope
that
works
out
for
for
all
the
chinese
people,
that
you
know
they
get
a
kick
out
of
it
and
it's
good.
It's
good.
It's
global,
global,
global.