►
From YouTube: Interoperability SIG - March 16, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
A
So
I've,
you
know
everyone
here
on
this
side
of
the
world
anyway,
my
little
pace
of
it
time
has
changed
so
I'm
curious.
If
we're
gonna
miss
a
few
folks.
Just
because
of
that.
B
A
B
Yeah
I'm
not
really
literally
part
of
the
community,
yet
just
new,
so
there's
no
one
else.
I
guess
maybe
actually
I
just
some
questions
actually.
Regarding
the
interoperability,
it
will
say
interest,
there's
just
so
many
questions,
sure
let's
do
it
yeah,
so
I
actually
got
them
Esther
yesterday
about
the
event
and
then
just
yeah
actually
I've
been
watching
some
of
the
interoperability
meetings
notes
the
reason
I'm
joining
is
they're,
just
yeah
there's
so
many
meetings,
so
I
try
to
get
a
grasp
of
at
this
point.
B
B
From
the
from
all
the
works,
that's
been
done
so
far
like
if
I
use
Jenkins
same
job,
what
kind
of
I
guess
interoperability
there's
no
like?
Maybe
there
is
that
I'm
aware
of
like
a
either
a
white
paper
or
like
a
summary
of
where
we
are
with
interoperability?
Yes,.
A
Where
we
are
right
now
so
I'm
glad
that
you
asked
that,
because
that's
actually
on
our
agenda
for
today,
this
group
has
been
normally
a
group
like
this
has
a
sponsored
on
the
technical
oversight
committee
and
unfortunately,
this
group
has
been
around
longer
than
I
have
and
longer
than
the
original
sponsor.
A
So
we
have
no
sponsor
anymore
and
that's
one
of
the
topics
that
we
need
to
discuss
today
and
probably
something
I'm
going
to
need
to
find
out
I'm
a
member
of
the
TOC,
so
I'm
not
sure
if
I
can
also
be
a
sponsor,
but
we'll
figure
that
out
and
get
that
taken
care
of.
But
the
reason
I
bring
that
up
is
part
of
the
responsibility
of
the
sponsor
is
to
make
sure
that
we
have
regular
updates
quarterly
updates
progress
reports.
A
You
know
some
goals,
things
like
that
to
provide
for
the
community,
so
that's
something
we
have
yet
to
do
this
year,
kind
of
struggles
at
getting
started
up
this
year
and
last
time
we
met,
we
discussed
putting
getting
a
conversation
together
in
the
interoperability
channel
to
discuss
our
goals
and
objectives
that
we
want
to
do
this
year.
Since
I've
been
a
part,
we've
done
a
lot
of
you
know.
Bringing
projects
in
that
we
find
are
interesting
that
touch
some
level
of
interoperability
in
the
continuous
delivery
in
that
area.
A
So
obviously
I
mean
we
would
like
to
do
more
than
that.
Some
of
the
other
items
that
have
come
up
just
a
couple
of
them
was
a
white
paper
that
had
been
started
a
long
time
ago.
It
needs
revisions
and
reviews
edits.
We
wanted
to
get
that
out.
This
quarter,
I
was
hoping
to
get
Fati
on
the
line
here
today
to
see
if
he
would
be
willing
to
just
help
us
get
that
up
and
out
the
door,
but
that's
something
that
we
would
be
continuing
to
work
on.
A
Another
item
is
something
that's
come
up
repeatedly
in
our
meetings.
Is
this
idea
of
interoperability
between
like
when
it
comes
to
Pipelines,
so
when
continuous
Delivery
Systems,
when
they
utilize
or
Implement
a
particular
project
to
handle
their
pipelines,
whether
that
be
commercial
or
open
source,
it
seems
we've
kind
of
we've
started
to
land
on
this
idea
of
a
yaml
description
of
this
process,
but
all
of
them
are
slightly
different
and
that's
something
that
the
interoperability
group
has
worked
on
as
well
in
the
past
is
defining.
A
You
know
trying
to
get
a
common
common
words
around
what
we
mean
when
we
say
pipeline
what
we
mean
when
we
say
steps
what
we
mean
by
you
know
what
what
is
available
to
people
in
a
pipeline.
The
struggle
is
when
you
move
from
one
project
to
another,
or
you
want
to
implement
a
different
in
either
a
different
commercial
product
or
a
different
open
source
product.
It's
really
hard
to
move
Pipelines.
A
So
that
was
something
that
this
group
I
was
hoping
that
we
would
be
able
to
tackle.
That
might
result
in
a
completely
different
working
group,
though,
at
this
point
we
may
need
to
spend
something
off
to
focus
on
that.
Specifically,
that's
similar
to
what
happened
with
CD
events,
the
project
that
came
out
of
the
interoperability
Sig.
That
was
a
discussion
that
came
up
this
idea
of
being
able
to
consume
and
emit
events
that
are
commonly
recognized
and
accepted
in
the
community,
and
that's
how
that
project
happened.
I'd
love
to
see
something
similar.
A
You
know
a
specification
for
like
a
common
common
pipeline
language
so
to
speak
or
a
way
to
communicate
about
it,
so
that
it
in
fact
we
can
make
that
whole
system
a
little
bit
more
plugable.
B
Yeah,
that's
very
exciting
yeah.
It
would
be
great
yeah
yeah!
You
don't
want
to
really
join
because
I'm
trying
to
figure
you
know
the
whole
cic
and
stuff
but
yeah.
It
would
be
great
if
we
have
those
documentations
so
standardizations
to
make
it
easier
to
move
between
the
instead
of
pipeline
yeah.
That's
a
quite
exciting
new
feature,
so
it
can.
A
So
yeah
my
job
in
the
next
few
weeks
is
to
make
sure
that
we
have
everything
up
to
date,
for
this
particular
special
interest
group
that
we're
ready
to
move
forward
so
keep
an
eye
on
the
slack
Channel
I'm,
going
to
start
up
a
conversation
there
about
our
goals
and
objectives
for
the
rest
of
this
year
and
we'll
be
adding
a
new
sponsor
here.
So
it'll
be
a
little
bit
more
formalized
process
moving
forward.
B
A
B
Supply
yeah
I
have
a
look
at
some
of
that
and
yeah
I
tried
watch
the
video
where
I
can
so
I
don't
have
to
interrupt
the
real
expert
talking
to
each
other
yeah
when
I
do
have
a
question.
I
yeah
I
did
join
yeah.
A
Feel
free
pop
in
anytime
you're.
More
than
welcome.
We
definitely
don't
want
to
be
exclusive,
so
yeah,
even
if
you
just
pop
in
to
listen,
that's
totally
fine
but
I
understand
everyone's
schedules
are
difficult
as
well,
so
nice
to
I,
just
myself
I'm
a
sponsor
of
the
supply
chain.
Special
interest
group,
so
I
was
busy
watching
some
videos
on
that
as
well,
because
I
wasn't
able
to
attend
all
of
those
meetings.
A
A
Yeah
bye
thanks
all
right
all
right.
Thank
you!
Victor!
It
doesn't
look
like
anyone
is
going
to
come
this
time
around
so
I'm
going
to
go
ahead
and
sign
off
but
happy
to
see
you
are
you
on
the
slack,
the.