►
From YouTube: SIG Interoperability Meeting - Aug 4, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
A
A
A
B
Sure
we
discussed
the
reference
architecture
and
we're
really
we're
looking
for
a
good
bit
of
input
from
the
interoperability
sake.
We
think
it
should
be
really
important
and
service.
The
work
that's
done
here
should
be
serviced
well
within
that
reference
architecture.
I
think
there's
a
link
to
the
deck
in
the
notes
from
the
last
meeting
on
july.
21St
tim,
do
you
have
do
you
have
access
to
those
meeting
notes.
B
B
You,
okay
great,
I
was
gonna
put
in
the
chat.
Otherwise,
yes,
so
it's
the
reference
architecture
is
really
an
attempt
to
bring
together
a
lot
of
the
more
detailed
technical
work.
That's
done
in
the
individual
things
and
have
a
sort
of
a
higher
level
view
on
cicd,
best
practices
really,
and
it's
come
out
of
the
best
practices
which
is
it,
which
is
where
discussion
on
the
reference
architecture
will
be
continuing.
B
B
It
should
be
a
great
contribution
to
the
wider
ecosystem,
we're
hoping
it
helps,
inform
people
more
broadly
about
the
benefits
of
cicd
done
well
and
ways
to
go
about
that
speaking
to
people
from
basically
where
they
are
from
their
own
position
and
their
own
point
of
view.
So
we're
moving
beyond,
say,
very
technical
teams
and
and
looking
at
how
to
approach
a
broader
audience
within,
I
guess
companies
or
wider
systems.
So
it's
not
just
speaking
to
development.
A
Excellent,
that's
something
I'm
really
excited
about
as
well.
I'd
like
to
see
that
being
pushed
forward,
so
hopefully
we
can
get
more
interaction
there
and
engagement
from
the
community.
On
that
too,
I
know
everyone
has
like
their
individual
use
case,
scenarios
and
stuff
that
they
are
concerned
with.
So
it's
important
that
we
pay
attention
to
the
real
problems
that
we're
trying
to
solve
and
make
sure
that
we
get
those
included
as
well
so
cool.
There
were
a
couple
of
items
that
came
up
over
the
last
couple
of
weeks.
A
I've
been
approached
twice
by
two
new
projects
that
would
like
to
be
considered
for
a
membership
to
the
cdf,
so
I've
been
working
with
them
on
getting
that
process
started
for
them,
and
one
of
those
things
is
for
them
to
present
to
our
group.
It
makes
sense
for
both
of
them.
One
of
them
is
called
j
releaser,
and
let
me
see
if
I
can
pull
up
the
project
here
just
so
we
can
see
it
online.
A
A
Tasks
like
announcing
that
a
new
release
is
out
posting
you
know
on
on
social
media
and
that
kind
of
stuff
making
sure
that
it's
tied
into
github
into
your
source
control
make
sure
things
are
tagged
appropriately
and
there's
a
lot
of
things
that
you
know.
It
goes
into
a
lot
of
details
on
what
you
actually
have
to
do
when
you
release
something
and
get
something
and
for
continuous
delivery.
Obviously
that's
something
that
we
should
be
concerned
with,
so
I
spoke
to
the
maintainer
of
this
project.
It's
relatively
new.
However.
A
A
So
I'm
going
to
throw
that
out
there
and
see
if
we
can
go
ahead
and
put
that
on
the
agenda
on
september
1st,
I
think
this
is
a
a
good
one,
a
good
find
we
need
more.
He
does
need
more
visibility
on
the
project
when
you
know
more
contributors,
things
like
that-
and
this
is
a
good
start,
at
least
to
get
that
part
going.
A
This
is
one
that
just
came
over
the
channels
last
week,
so
I'm
looking
a
little
bit
more
at
it,
but
I'm
sure
they
will
be
interested
in
scheduling
a
time
as
well.
So
I
can
take
that
as
an
action
item
to
reach
out
to
them
and
find
out
when
they
can
best.
You
know
what
works
for
them.
As
far
as
presenting
kara
in
the
past.
Have
we
ever
had
two
at
the
same
time,
or
is
that
too
much
for
a
meeting?
A
B
B
I
actually
have
an
issue
on
the
rebound
from
like
years
ago,
because
it
was
being
used
in
a
number
of
projects
that
are
part
of
the
cdf,
and
it
is
something
that
we
did
have
discussions
with
them
about
joining,
but
I
think
that
the
project
is,
you
know
sometimes
past
it's
more
developed.
They
have
a
wider
range
of
contributors.
Things
like
that
more
momentum,
it's
a
really
nice
time
to
reopen
those
conversations.
So
thank
you
very
much
for
doing
that
and
jv
lisa
looks
great.
B
A
A
B
A
B
A
This
is
the
current
version
of
the
landscape,
as
you
can
see,
there's
quite
a
few
on
here.
Obviously,
this
is
not
quite
as
overwhelming
as
like
the
cncf
landscape,
which
I
sincerely
appreciate,
there's
a
little
bit
more
there's
a
focus
here
on
projects
that
have
to
do
with
continuous
delivery
and,
as
you
can
see,
j
releaser
since
they
reached
out,
I
asked
them
to
put
make
themselves
a
part
of
the
landscape
so
that
we
can
start
looking
at
where
they
might
belong.
This
does
not
imply
membership
in
the
cdf
or
acceptance
of
the
project.
A
B
Yes
and
to
that
to
that
point,
if
you
feel
that
a
project
either
one
you're
working
on
or
one
that
you
use
a
lot
of,
should
be
on
the
landscape,
please
do
make
a
pull
request.
It
is
you
know
it's
open
source,
it's
an
open,
repo
and
being
on
the
landscape.
It
is
a
good
way
to
raise
awareness
of
your
project
and
your
your
placement
within
the
wider
ci
cd
ecosystem,
but
just
and
having
your
project
on.
B
There
is
a
really
nice
entry
point
to
greater
engagement
within
the
cdf
itself,
but
it's
not
necessary
that
the
project
then
would
go
on
to
be
a
cbs
project.
So
if
you're
thinking
well,
I'm
already-
you
know-
that's
that's
not
for
me,
but
nonetheless
it
would
be
nice
to
be
shown
on
the
cdf
landscape
to
be
shown
to
be
part
of
this
wider
ecosystem
and
how
you
fit
in
by
all
means
make
a
pull
request.
So.
A
Excellent
I'll
go
ahead
and
add
that
I'll
add
the
link
in
the
notes.
So
everyone
knows
where
it
is
and
knows
where
to
look
so
I'll.
Add
these
again
I'll
give
myself
an
action
item
to
reach
out
to
goscm
to
find
out
when
they
can
present
other
than
those
two
items.
I
don't
have
anything
else
to
discuss
this
time
around.
A
We
have
an
outstanding
item
to
get
our
stuff
up
on
the
best
practices
website.
I
know
last
month
and
the
month
before
has
been
pretty
crazy
for
a
lot
of
us.
So
I'm
looking
forward
to
getting
that
done
and
having
more
of
a
discussion
around
that
and
what
that
looks
like
the
next
meeting,
and
we
can
do
some
of
that
chatting
and
stuff
online
too
we're
not
just
reserved
to
this
period
of
time
when
we
meet
so
we'll
get
more
of
a
momentum
behind
that
and
get
that
part
done.
C
If
there's,
if
there's,
if
there's
nothing
else
on
the
agenda,
would
it
be?
I
have
a
couple
questions?
Would
it
be
okay
to
ask
those
now
or
do
you
rather
do
it
offline
off
the
recording,
absolutely
sure
so
so
I
I
know
I
just
kind
of
kind
of
showed
up
here,
I'm
I'm
tim
miller,
I'm
from
a
startup
called
kusari
and
we're
focusing
on
supply
chain
security.
C
So
we've
been
presenting
a
lot
of
the
a
lot
of
the
other
six.
So
six
software
supply
chain
tag
security.
A
couple
of
a
couple
of
others:
we've
been
working
on
an
open
source
project
called
fresca,
which
is
a
factory
for
repeatable,
secure
creation
of
artifacts,
it's
a
bit
of
a
mouthful
but
to
the
landscape.
C
Question
fresca
is
basically
a
configuration
and
set
of
defaults
for
a
series
for
a
different
set
of
tools
within
the
landscape,
so
tecton
tecton
chains
a
couple,
others
I'm
not
sure
exactly
how
it
would
fit
into
the
landscape,
as
it
is
basically
a
way
to
configure
them
to
work
together.
It's
a
it's
like
an
abstraction
on
top
of
a
set
of
them.
C
Is
that
something
is
there
someone?
I
could
talk
to
about
that
specifically
if
that
would
even
make
sense
in
the
landscape
or
if
it's
too
too
weird,
because
from
our
perspective,
there's
there's
cutting
across
these
things
and
how
to
use
them
together
is
one
of
the
big
pieces
that
we've
found
a
a
gap
in,
especially
if
you
want
the
security
and
the
ways
that
they
all
work
together,
which
is
why
we're
interested
in
this
meeting
to
actually
still
still
hit
the
goals
that
you're
trying
to
achieve.
C
B
So
so
I'm
so
glad
you
brought
this
up
at
the
the
meeting.
We
actually
ran
a
tim
welcome
by
the
way,
welcome
to
the
interoperability
segment.
We're
really
happy
you're
here
your
project
sounds
like
a
very
interesting
project,
good
fit
for
the
interoperability,
it's
a
good
fit
for
the
software
security's
sake,
and
we
would
like
to
have
it
on
landscape,
I'm
carl
delamok.
B
I
work
at
the
cdf
and
a
few
months
ago
the
beginning
of
the
year
ended
last
year
we
kicked
off
a
sort
of
revamp
of
the
landscape,
but
it
was
almost
like
we
did
the
phase
one.
It
was
a
bit
of
a
cleanup
and
a
little
bit
of
a
augmentation,
but
in
by
no
means
are
those
categories
written
in
stone.
In
fact,
in
many
ways
this
should
be
just
you
know:
it's
a
living
document,
it's
always
evolving
and
that
revamp
doesn't
need
to
at
all
stop
at
phase
one.
C
B
You
know
we
can,
we
can
keep
going.
So
if
you
feel
there
is
a
category
missing
on
the
landscape.
Probably
the
thing
to
do
is
to
raise
an
issue
on
that
cdf
landscape
repo,
and
we
can
start
a
discussion
there.
That
would
be
a
great
way
to
go
about
it
and
I'm
really
happy
to
continue
that
discussion
with
you
as
well.
So
you
can
ping
me
anytime,
but
keeping
it
open,
keeping
it
on
github
as
an
issue
is
great
and
we
can
get
feedback
from
more
people.
C
No,
no
I'll
definitely
do
that
yeah,
and
it
was
interesting
because
we
had
put
in
a
a
bunch
of
work
using
something
called
keylang
in
particular
to
make
a
lot
of
these
tools
work
together.
So
we
had
put
a
lot
of
thought
into
into
the
interoperability
of
a
lot
of
these
a
lot
of
these
things.
So
we
were
interested
in
the
topic
for
sure
we'd
love
to
get
more
involved.
C
A
Definitely
add
it
to
the
notes.
This
is
stuff.
This
is
something
I'd
like
to
look
at
later,
too
and
you're
in
the
right
place.
I
mean
especially
with
the
concept
of
interoperability
and
getting
these
projects
working
together,
and
I
don't
know
this
sounds
to
me
like
something
that
a
larger
group
would
be
interested
in
listening
to
a
presentation
about.
Would
you
be
interested
in
presenting
to
this
group.
C
A
A
There
might
be
some
other
outlets
for
you,
especially
if
you
know,
if
there's
other
sigs
that
might
be
interested
in
this
as
well.
We
can
put
an
advertisement
in
their
channels
to
let
them
know
that
you'll
be
presenting
here
at
the
interoperability
group,
so
you
might
get
more
attention
that
way
as
well.
A
Okay,
I
don't
have
anything
either
I'll
reach
out
to
justin
too,
and
I
didn't
hear
from
him
from
this
meeting
so
I'll
find
out
if
there
was
anything
that
he
wanted
to
bring
up
and
that
we
can
continue
on
for
next
time
other
than
that
have
a
lovely
first
part
of
your
month.
Here
I
had
to
remind
myself
what
the
date
was.
This
is
how
crazy
it
is,
and
we
will
see
you
again.
The
next
meeting
in
august.