►
From YouTube: SIG Interoperability Meeting - Apr 21, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
C
A
C
A
A
A
Okay,
well,
we
had
a
couple
of
items
on
our
agenda.
I
guess
we
can
go
ahead
and
get
started
with
those
and
then
I'm
hoping
we
can
just
jump
into
suggestions
and
guidance
from
terry
as
far
as
what
to
do
with
our
documentation.
Now
I
think
we
still
have
some
work
to
do
as
far
as
getting
those
pr's,
finalized
and
and
put
in
we
can.
We
can
do
that,
but
we
can
still
benefit
from
advice
from
best
practices
on
how
to
present
this
in
the
future.
A
C
And
I
also
have
pr
not
pr
action
item
on
me
to
reach
out
to
people
I
actually
pinged
mathias
and
eric,
because
they
had
some
comments
spending
on
those
pr's
and
they
both
went
back
and
you
know
I
think
they
said
they
are
fine
with
how
it
is
now
and
we
can
work
on
them
incrementally
once
they
get
merged
and
I
also
pinked
on
mary.
I
remember
seeing
message
from
justin
you
own
slack
as
well,
but
I
haven't
got
any
response
from
anne
marie
about
what
she
thinks
us
merging
those
pr.
C
A
D
A
A
We
do
have
one
other
announcement
I
want
to
get
to
for
cara.
We
are
going
to
be
opening
up
nominations
for
co-chair
she's,
been
with
us
for
two
years
and
is
ready
to
pass
the
torch
to
another
person
for
co-chair
cara.
Do
you
want
to
do
you
want
to
talk
to
us
a
little
bit
make
us
feel
better
about
your
leaving
us
well
you're,
not
really
leaving
us
yeah.
E
I'll
still
be
here,
I'll
still
be
joining,
but
after
two
years
it's
a
good
time
to
make
space
for
someone
else.
I
have
loved
being
crochet
of
the
interoperability,
so
it's
a
highly
recommended
endeavor
and
I
would
say
that
I
think
melissa
already
is
showing
how
fantastic
it
is
to
have.
You
know
a
little
bit
of
churn
and
have
new
people
come
in
and
bring
their
enthusiasm
and
energy.
A
A
We
have.
One
of
you
know
describing
pipeline
steps
that
we
were
talking
about
another
describing
pipeline
stage,
terminology
and
there's
been
a
ton
of
work
on
these
items
and
it's
it's
time
about
time
to
start
moving
these
forward
and
getting
them
into
a
presentable
format
for
the
community.
So
we
were
wondering,
given
your
you
know
what
you
discuss
in
best
practices
and
stuff.
If
you
have
some
advice
for
this
type
of
documentation,.
B
So
so
what
we've
been
doing
is
creating
an
overview
of
the
whole
continuous
delivery
process
and
then
trying
to
structure
that
so
that
people
from
different
backgrounds
and
different
audiences
can
get
up
to
speed
with
the
whole
picture
of
what's
involved
in
imagining
continuous
delivery,
so
we're
we're
building
a
a
website
which
will
have
multiple
resources
in
it.
There's
there's
an
overarching
narrative
that
explains.
B
So
there
there's
an
area
of
the
site
which
is
already
set
aside
for
the
various
cdf
projects
to
introduce
using
their
tools
to
achieve
the
continuous
delivery
goals.
So
we've
got
the
opportunity
here
to
to
both
expand
on
standards
as
part
of
the
the
narrative.
So
we
can
call
out
the
importance
of
of
interoperability
between
tooling
as
part
of
the
explanatory
narrative,
but
we
can
also,
if
you
like,
host
deep
dives
into
the
the
detail
of
of
what
you've
produced
here.
B
A
Okay,
fati
and
justin,
I'm
going
to
lean
on
you
too.
How
would
you
best
describe
what
we
have
so
far?
I'm
I'm
imagining
you
know.
Some
of
it
is
like
just
a
list
kind
of
a
grab
bag
to
make
people
aware
of
what
the
possibilities
are.
That's
that's
always
helpful,
especially
as
far
as
you
know,
pipeline
steps
and
things
like
that
to
consider
what
other
people
are
doing
and
maybe
implement
something
they
hadn't
thought
of
before
I'm
not
sure
like.
Where
exactly
would
that
align
with.
C
C
C
C
So
now
I
am
taking
a
bit
more
broader
look,
so
this
may
be
a
useful
thing.
It
is
not
a
best
practice
per
se,
but
it
could
help
people
to
get
started
with.
You
know,
learning
about
the
technology
space,
so
this
could
be
a
candidate
to
publish
as
part
of
best
practice
websites
linked
by
link
from
some
best
practices
or
by
the
way.
C
C
Look
here
is
what
others
are
doing.
These
are
the
type
of
stages
they
have
for
building
stuff
for
running,
static,
analysis
or
security
type
of
stuff
or
deployment.
So
you
can
get
some
idea
from
this
type
of
input
and
the
other
thing
I
want
to
highlight
is
like
okay,
the
two
prs
are
there.
This
document
has
been
there
looking
at
technology
aspects,
I
want
to
highlight
the
discussion
justin
started
in
february.
C
This
is
again
another
input.
It
could
be
considered
as
another
input
for
organizations
or
people
on
their
way
to
embrace
countries
there.
Okay,
now
you
learned
about
stages
and
steps,
but
what,
as
people
are
running
as
part
of
their
pipelines-
and
here
you
can
see-
we
have
some
conversation
here
about
what
different
organizations
are
using
and
maybe
like
again,
as
you
said
terry,
these
may
not
be
considered
as
best
practices,
but
this
could
be
considered
as
practices
employed
by
different
organizations
that
may
be
under
certain
best
practices.
C
You
are
promoting
on
your
website
and
the
question
is
like
how
to
make
these
things
visible
and
easily
accessible,
because
some
people
find
this
document,
the
vocabulary
document
or
the
conversation,
the
discussion
or
the
pr's
by
chance
or
by
pointing
to
each
other
but
making
them
easily.
You
know
findable
and
consumable
is
another
thing,
which
is,
I
think,
the
conversation
we
are
having
here.
B
So
as
a
result,
there's
lots
of
people
doing
things
that
they
think
are
continuous
delivery,
which
clearly
aren't
so
we
have
to
have
one
track
through
this
documentation
that
allows
people
to
come
in
and
and
get
a
really
firm
grounding
in.
You
know
what
what
are
the
key
points
here?
What
do
I
need
to
understand
about
the
concepts?
B
B
B
But
then
there's
also
a
third,
very
important
audience,
which
is
the
people
who
were
building
the
tools
in
the
first
place.
So
yeah.
That's
not
just
our
project
teams
but
other
tool,
vendors
and
and
the
cloud
providers
who
are
utilizing
that
tooling
to
provide
their
products
to
customers
and
obviously
it's
very
important
to
get
those
people
involved
in
this
discussion.
Because
that's
that's
the
path
that
we
need
to
take
to
standardize.
Some
of
this-
and
you
know
not
just
improve
interoperability
but
improve
the
communication
around
the
the
concepts
that
we're
using.
B
I
think
that
would
be
useful
to
to
use
the
same
site
as
a
place
to
publish
this
information
so
that
you
know
we're
connecting
the
ideas
of
best
practice
in
the
methodology
and
tooling
that
implements
best
practice
and
therefore
a
list
of
vendors
that
can
provide
you
with
best
practice.
Tooling.
That
will
will
give
you
what
you
want.
So
I
think
there
is
a
continuity
here,
but
it
might
not
always
be
the
same
document
that
you
you
need
for
the
different
audiences.
B
Well,
I
would
have
to
go
through
an
an
and
read
it
to
get
a
feel
for
the
language.
But
from
from
what
you've
shown
me
today,
it
feels
that
that's
addressing
the
low-level
concepts
at
a
fairly
technical
level,
and
so
there's
a
lot
of
presupposed
knowledge
that
that's
em,
embedded
and
so
that's
great,
because
you've
got
the
piece
that
addresses
that
audience.
A
B
B
We
we've
got
one
big
outstanding
pr
that
we
need
to
get
in
shortly,
which
is
the
structure
of
the
majority
of
the
information
once
that's
in.
It
will
then
become
clearer
where
to
hang
the
other
bits
off
around
around
the
outside
of
that,
so
I
would
say,
within
a
few
weeks
we
should.
We
should
be
in
a
position
to
start
accepting
contributions
from
outside
the
core
team.
So
we
can,
we
can
begin
to
add
additional
information.
A
Okay,
how
about
we
have
an
action
item
for
one
or
more
of
us
to
go
check
that
out
and
just
you
know,
get
an
overview
of
what
what
is
existing
right
there
already
and
see.
If
you
know
where
we
could
possibly
fit
our
information
in,
so
that
we're
ready
to
submit
that
or
or
you
know,
to
give
that
suggestion.
B
A
B
A
A
C
I
have
a
question
actually,
if
I
may
now,
you
know
everyone
is
talking
about
software
spiking
and
all
those
things
and
this
there's
a
project
called
salsa.
I'm
sure
you
all
heard
about
it
and
it
talks
about
best
practice
and
they
determined
some
levels.
I
think
they
have
four.
There
was
as
part
of
their
spec
or
whatever
they
call
it
like.
Terry,
do
you,
like,
I
don't
know
like
if
it
makes
sense
to
have
such
approach
for
cd
best
practices
as
well.
I'm
not
saying.
D
C
E
C
And
they
talk
about
certain
best
practices
and
based
on
those
best
practices.
They
have
like
different
levels.
Okay,
if
you
are
following
these
best
practices,
if
you
have
these
things
in
your
supply
chain,
you
are
level
one
level
two,
I'm
not
actually
after
at
this
point
in
time
having
levels,
but
could
there
be
some
kind
of
place
on
the
best
practice
say:
let's
benchmark
yourself,
are
you
doing
these
things?
Okay,
then,.
B
So,
in
fact,
justin
has
already
encouraged
us
to
to
to
put
a
maturity
assessment
into
into
the
site,
so
that
that
that
is
something
that's
that's
already
in
the
works.
Yes,
okay
done
yeah
and
software
supply
chain
itself
is
is
part
of
the
best
practice
discussion
and
that's
one
of
the
areas
where
we
we've
got
a
lot
of
work
left
to
do
to
to
fill
that
out
to
an
appropriate
standard.
B
B
So
obviously,
the
the
dora
metrics
are
a
key
part
of
of
what
we're
discussing
but
the
to
give
and
get
to
the
dora
metrics
you've
already
got
to
be.
You
know
at
level
four
of
maturity,
so
there's
a
there's,
a
there's,
a
lot
of
basic
concept,
understanding-
and
you
know,
structuring
of
your
organization
that
you
need
to
get
right
before
you
you.
B
You
can
even
start
to
benefit
from
from
some
of
the
detail
and-
and
that's
been
part
of
the
you
know,
the
the
more
challenging
exercise
is
that
you
know
we've
had
a
group
of
very
technical
people,
contributing
the
detail
of.
You
know
how
to
optimize
a
specific
type
of
pipeline,
but
the
there's
a
big
gap
in
what
is
this
continuous
delivery
thing,
and
why
are
we
doing
it
in
the
first
place?
B
So
so
we
we've
had
to
do
a
fair
amount
of
work
to
to
to
fill
in
the
the
business
concepts
and
the
you
know
the
drivers
and
constraints
around
well.
This
is
of
benefit
to
you.
If
you
are
this
type
of
organization
pursuing
this
type
of
product
commercialization,
but
we
also
have
to
flag.
You
know
if
you're
this
type
of
organization
following
this
type
of
you
know
strategic
planning
methodology,
then
you
really
shouldn't
be
trying
to
implement
continuous
delivery,
because
it's
going
to
hurt
you
rather
than
benefit
you.
B
E
Yeah,
that's
really
valuable
to
take
more
of
a
high
level
and
in
some
ways
some
ways
introductory,
but
a
really
really
high
level
of
the
sort
of
terrain,
the
space
yeah
okay.
So
what
we're
really
coming
in
with
is
much
more
detailed
and
technical
steps
and
stages.
Okay,
that's
really
interesting!
Just
to
just
to
recap
our
previous
conversation.
B
B
B
A
These
are
really
good
notes.
I'm
trying
to
capture
everything,
to
put
it
in
our
in
our
notes.
So
we
remember
it's
a
little
bit
overwhelming
because
there's
a
lot
of
a
lot
of
work
that
we
can
do,
but
I
like
the
step,
one
approach,
just
get
our
stuff
linked
in
resources
and
then
next
stop
think
about
where
we,
where
we
want
to
go
from
there,
where
you
know
we
can
change
the
content
a
little
bit
to
match
the
audience
we
want.
I
like
it.
C
Gently
pulling
sorry
to
interrupt
gently
pulling
people
into
more
details
like
oh
you.
If
you
are
reading
this,
it
means
you
are
after
this
type
of
stuff,
and
this
is
because
of
this,
and
then
they
can
slowly
get
into
that
mindset.
Okay,
now
I
am
going
to
into
details
so
yeah,
instead
of
just
suddenly
getting
hit
by
tons
of
details.
Yeah.
B
This
is
a
problem
that
exists,
and
this
is
how
it
might
affect
you,
and
this
is
how
we
have
tried
to
draw
out
this
information
into
a
way
that
you
can
build
from
it
and
then
understand
it,
and
then
that
narrative
can
be
targeted
to
the
different
audiences.
So
you
can
do
a
lightweight
version
of
that
for
decision
makers,
and
then
you
can
do
a
much
more
in-depth
narrative
for
the
the
people
who
are
building
tools
and
and
then
both
of
those
things
leak.
It
link
into
the
detail.
E
I
do
thinking
back
to
bringing
up
the
maturity
model.
Do
you
think
that
using
a
maturity
model
is
helpful
for
signposting
that,
at
all
these
different
levels
of
discussion
and
allowing
people
to
sort
of
come
to
a
common
understanding?
You
know
we
we're
at
this
level.
This
is
what
we're
struggling
with
here's.
How
we're
looking
to
improve
here
are
best
practice,
suggestions.
B
E
Absolutely
I'm
sure
you're
familiar
with
the
research.
I
think
it
came
out
of
the
latest
store
report
that
people
vastly
overestimate
their
the
efficacy
or
the
capabilities,
the
reliability
of
their
ci
cd
systems-
and
this
is
more
so
for
people
who
are
farther
away
from
the
implementation
of
the
use
of
it.
So
when
you,
when
you
move
down
to
the
more
technical
teams
that
they
have
a
more
accurate
sense
of
actually
where
they're
at
with
their
ci
cd
systems,
so
it's
it's
really
good.
D
I
think
that,
like
part
of
the
door
metrics
come
with
a
set
of
capabilities,
I
think
there's
like
17
of
them,
and
you
know
those
are
super
critical
they're,
not
all
created
equal
and
some
of
them
have
a
fair
amount
of
depth.
Where
you
know
you
might
have
feature
flagging.
I
think
that's
one
of
the
capabilities.
D
You
might
have
feature
flagging.
That's
like
I
checked
in
a
config
and
that's
my
feature
flag
or
you
might
have
a
launch
darkly
type
thing,
and
those
are
two
very
different
levels
of
maturity
within
that
capability
and
you
probably
it
would
be
easier
to
start
with
the
config
type
thing
in
order
to
play
with
feature
flags
than
it
is
to
do
like
a
vendor.
Evaluationy
sort
of
thing
similar,
like
the
thing
I
often
tell
people
at
ebay,
is
the
whole
point
of
this.
D
Like
framework
of
evaluation,
is
you
shouldn't
spend
time
doing
chaos
testing?
If
you
don't
have
unit
tests
like
you
have
to
you,
we're
not
there.
Yet
it's
an
awesome
tool,
but
you
got
to
get
the
basics
done
first,
and
so
I
like
identifying
what
the
basics
are
and
saying,
like
you
like
chaos,
testing
is
more
in
line
with
trunk
based
development
feature
flagging
type
world
than
it
is.
B
C
One
last
question:
this
is
terminology
question
you
know
I
like
determination,
like
some
people,
don't
like
term
maturity
level
like
I
know
again,
it's
not
about
like
us
using
it
but
like
when
you
go
out
with
like
maturity
level.
I
know
what
would
be
the
reaction
for
such
people
with
strong
opinions.
C
E
I
I
think,
there's
a
sense
that
historically
maturity
models
have
been
used
to
say
once
you
reach
the
end
level.
Like
you're
done,
you
know,
you're,
there
you've
succeeded,
you're,
you're,
all
good,
and
one
of
the
things
I
really
like
about
the
the
door
metrics
is
that
they
really
emphasize
that
this
is
a
continual
process.
E
You
are
never
done,
you
can
always
improve,
so
I
think
bringing
that
in
even
if
we
did
have
some
sort
of
framework
of
levels
we're
bringing
that
in
and
making
it
really
clear
that
we
don't
think
level
four
or
whatnot
is
is
the
final
level
and
then
you're
you're
done.
You
can
walk
away
and
do
something
else.
D
D
A
Is
it
right
to
say
to
that
someone
at
a
higher
level
or
a
further
along
maturity
level
that
that
they
can
be
rated
better
than
someone
at
an
earlier
level,
because
it
might
be
more,
some
of
these
cases
might
be
just
more
about
priority
like
what
is
necessary
for
that
particular
system.
You
know,
maybe
it's
not
necessary
for
an
organization
to
be
at
the
highest
maturity
level
that
that's
not
the
best
way
for
them
to
focus
their
energies.
B
B
So
what
people
really
want
to
understand
is
how
close
they
are
to
you
know
the
theoretical
maximum
pace
they
could
ever
go
up
so
you're
you're,
not
offending
people,
if,
if
you
allow
them
to
see
where
they
sit
compared
to
others
doing
the
same
thing,
but
if
you
put
a
lot
of
value
judgments
around,
you
know
how
good
they
are
as
an
organization,
then
yes,
you're,
going
to
put
a
lot
of
backs
up
as
a
result
of
doing
that.
It
is
not
helpful.
B
B
A
A
A
A
I,
like
it:
okay,
before
we
run
out
of
time,
let's
figure
out
what
we
want
to
do
next,
I
think
we
know
we
definitely
want
to
submit
material
and
it
looked
like
you
had
some
contribution
guidelines,
so
maybe
we
can
follow
that
with
getting
our
stuff
linked
into
your
system.
Now
we
want
it
in
a
better
format,
not
just
in
the
not
just
in
the
github
repo
right.
So
we
need
to
do
that
and
then.
B
C
B
So
the
aim
is
to
try
and
get
that
publication
out
this
this
year
and
you
know
hopefully
within
a
matter
of
months
but
from
from
your
perspective,
if
you're
interested
in
seeing
the
content
of
the
site,
the
the
bulk
of
the
information
is
currently
sitting
in
a
in
a
pr
rather
than
in
in
in
maine.
So
that's
a
that's
a
piece
of
work.
I
need
to
get
finalized
this
this
month.
We've
just
got
some
debates
over
over
terminology
that
we
need
to
clean
up,
and
then
you
know
what
that's
like.
B
E
C
B
B
Yeah,
I
can't
remember
what
the
what
the
link
to
monology
is
for
this.
I'm
just
going
to
go
and
look
at
that.
I
know
I
think
that
is
the.
That
is
the
current
pr
actually,
in
that
link.
Looking
at
the
content,
so
yeah
yeah,
so
you'll
you'll
be
able
to
see
most
of
the
content
from
that
from
that
link,
but
it
will
probably
go
away
once
the
once
the
pr
is
submitted
and
then
you'll
you'll
need
to
go
back
to
the
main
site.
E
A
B
C
Yeah,
I
can,
minister,
you
can
action
me
for
about
this
interoperability
story
part,
so
we
can
at
least
start
crafting
that
paragraph
that
could
take
people
into
more
details.
Think
where
references
link,
so
at
least
we
can
also
learn
if
you
go
boxy
how
it
works
via
that
pr
yeah.
I
can
take
that
part,
but
then
the
stage
step,
stuff
or
quality
gates.
C
E
Did
we
say
that
we
would
put
roughly
what's
in
the
what
we
have
for
steps
and
stages
in
sort
of
a
reference
section
so
to
have
it
completely
in
one
place
and
then
in
other
areas,
maybe
link
in
give
a
little
introductory
link
and
people
can
deep
dive
as
they
would
like
is?
Is
that
a
a
good
starter
workflow,
or
did
you
want
more
of
a
specific
breaking
up
of
the
information
depending
on
the
audience
throughout
the
site.
B
E
C
I
think
to
us:
some
standing
comments
were
like
the
two
people
with
outstanding
comments
was,
were
matthias
and
eric
and
they're
able
to
say
that
these
versions
can
go
in
and
then
we
can
work
on
them
once
they
are
in.
I
think
justin.
You
were
fine
with
the
latest
steps.
Pr,
maybe
you
can
approve
the
stage
pr
as
well.
I
think
one
of
them
didn't
have
approval
or
something
and
then
like.
We
can
try
and
marry
again
at
least
give
her
a
heads
up.
C
We
are
going
to
merge
these
things
one
last
time
she
may
be
busy
and
then
yeah
then
the
rest
is
like.
We
continue
improving
or
splitting
the
document,
because
now
it
is
kind
of
mixed
between
technology
and
the
other
stuff.
So
we
can
split
it
while
we
work
with
best
practices,
but
that's
a
good
opportunity
to
speak
to
documentation
or
reorganize.
E
C
A
A
Yeah,
it's
a
good
start.
We
can
definitely
add
to
it
and
get
that
out.
How
do
we
go
about
that
cara?
We
should
probably
I
need
to
be
more
thoughtful
with
your
time
where
a
couple
minutes
passed,
but
maybe
I'll
reach
out
to
you
and
and
find
out
like
how
how
we
progress
and
getting
an
article
published
and
stuff
like
that
with
the
secretary.
A
Cool
all
right.
Well,
thank
you
very
much
everyone
for
your
time.
Please
update
and
if
I
missed
something
or
whatever
in
our
agenda
and
notes,
I
think
I
got
all
the
action
items
in
there,
I'm
just
adding
one
for
you
cara
for
getting
the
initial
links
in
there.
Thank
you
so
much
terry
for
your
input.
That
was
an
awesome
conversation.
Let
us
off
on
a
couple
of
other
paths
too,
which
were
great
to
talk
about
so
yeah.
This
is
this
was
awesome.
Thank.