►
From YouTube: SIG Interoperability Meeting - Jan 19, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
D
I've
been
all
right,
you
know
just
were
you
trying
to
get
used
to
the
new
role
yeah
here.
B
D
E
C
Well,
it's
shaping
up
to
probably
be
a
short
meeting
unless
we
get
excited
about
talking
about
something.
I
know
we're
just
getting
started,
getting
started
again
with
our
new
year
here
so
and
I've.
We
just
had
kind
of
a
snowmageddon
yesterday,
so
I'm
digging
myself
out
of
snow
right
now,
but
yeah
so
glad
you
guys
can
make
it
I
know.
If
you
have
reached
out
to
me
and
said
they
had
conflicts
for
today
and
are
gonna
be
here,
but
Andrea
specifically
had
some
notes
I'll
put
in
the
doc.
C
If
he's
not
able
to
get
out
of
his
commitment,
we
will
see
him.
Hopefully
in
the
meantime,
he
gave
me
some
some
stuff
to
speak
about
so.
C
I
could
swing,
get
started
so
CD.
Con
cfp
is
open,
I
put
a
link
in
the
dock.
Let
me
share
that
screen.
We
can
all
follow
along.
A
C
Right
so
yeah,
yesterday,
I
went
Googling
for
the
cfp
link
and
I
couldn't
find
it
so
I
I
think
some
emergency
messaging
went
out
to
Linux
Foundation,
make
sure
that
people
can
find
this
now,
since
it's
been
announced
and
I
I
looked
for
it
again
today
and
found
it
right
away
so
I'm
hoping
that
we
can
all
help
with
this
share.
This
get
people
to
submit.
C
C
I
guess
last
time
we
met,
we
talked
a
little
bit
about
go
sem
and
following
that
meeting
they
presented
at
our
technical
oversight
committee
and
it
was
well
received.
There's
things
happening
there.
There
were
folks
from
the
committee
there
that
were
willing
to
push
this
forward.
There
were
a
couple
items
that
we
left
in
their
hands
to
get
resolved
before
we
move
any
further
with
you
know,
getting
it
into
the
foundation
formally,
that
is
around.
C
C
C
And
next
I
will
admit:
I
don't
have
a
lot
of
background
on
this
one,
but
we
discussed
briefly
in
our
last
meeting
about
the
value
stream
mapping,
interoperability,
technical
committee
and
some
of
the
things
that
we
have
in
common
and
might
you
know,
charge
the
same
Hill
together
so
to
speak.
C
We
have
a
call
scheduled
with
them
next
week
and
a
few
of
us
on
this
call
are
actually
going
to
be
there
listening.
So
let's
put
this
as
an
action
item
to
add
this
to
the
agenda
for
our
next
interoperability
meeting
to
share
what
came
out
of
that
meeting
and
any
updates.
C
Andrea
is
a
good
one
to
speak
to
this.
He
wasn't
unable
to
make
it.
He
did
send
me
some
notes,
I'm
going
to
add
those
to
the
doc
for
anyone
that
is
like
who
is
this
Oregon?
What
are
they
doing?
This
is
good
information
to
have.
C
Oh
goodness,
okay
I
will
put
that
in
in
a
moment,
came
from
slack,
so
my
copy
paste
isn't
going
to
be
friendly
with
me,
I'm
kind
of
rushing
through
that
because
I
want
to
get
to
this
part,
because
we've
we've
had
this
on
our
agenda
a
few
times
now
this
white
paper
that's
been
out
there
Justin
have
you
had
a
chance
to
look
at
this
at
all
over
the
break.
B
B
That
kind
of
shapes
that
concept,
the
example-
is
being
able
to
write
in
one
language
and
you
know,
make
a
tecton
pipeline
or
make
a
Argo
CD
pipeline
having
like
a
common
pipeline
definition,
language
that
doesn't
exist
to
my
knowledge,
but
it's
really
a
survey
of
the
space,
and
you
know
why
interoperability
is
important
and
some
examples.
D
A
B
That
feels
like
a
pretty
large
undertaking
to
me,
but
is
especially
in
an
organization
where
you
have
a
plurality
of
Technology
like
some.
Some
large
companies
are
like
here's,
the
one
true
way,
and
if
you
don't
do
it
then
like
good
luck
and
then
some
folks
are
like
some
folks
are
more
celebratory
of
technical
diversity,
and
so
certainly
in
that,
in
that
latter
context
it
would
be
a
boon
to
have
a
Common
Language,
where
you
can
kind
of
move
between
Technologies
who
originally
authored
this
there's
a
big
pile.
D
B
People,
if
you
scroll
down
to
the
bottom
of
the
con,
there's
a
contributor
list,
there's
a
ton
of
folks
I,
see:
okay,
yeah.
A
B
It
it
needs
an
editing,
pass,
I,
think
and
then
the
apis
section
interoperability
through
apis
is
blank,
so
that
would
need
to
be
updated.
That's
kind
of
like
near
the
bottom
of
that
POC.
C
Five
up:
oh
sorry,
I'm!
Oh
this
one
yeah
gotcha,
okay,.
B
B
One
thing
I
wasn't
entirely
sure
of
is
what
the
goal
of
the
paper
is
like
I
didn't
know.
If
the
goal
of
the
paper
is
to
like
tell
people
that
see
it,
interoperability
is
important
and
they
should
go.
Do
something
like
is
their
call
to
action?
Is
it
hey?
We
just
want
you
to
be
aware
that
interoperability
is
a
concern
or
like
the
the
actual
goal,
is
we
want
to
publish
something
so
the
CDF
looks
better
in
the
like
Marketplace
or
just
trying
to
understand
some
of
the
goals.
E
It
says
an
introduction
that
it's
actually
the
aim
is
to
to
describe
the
challenges
and
areas
of
focus
and
opportunities,
and
why
interpretive
honest
is
a
need,
I,
guess
it's
more
about
just
describing
State
and
State
rate
of
our
systems
and
why
we
have
a
problem
due
to
lack
of
interoperability.
A
E
So
I
see
it,
but
another
comment
is
that,
as
you
said,
I
guess
is
that
this
document
is
very
old.
I
mean
it
was
a
long
long
time
ago
it
was
initiated
on
a
lot
of
it.
You
might
probably
need
to
be
written
and
also
the
Run
shop
contributors.
In
the
end,
there
I
mean
I,
think
maybe
half
of
them
have
changed
companies,
and
many
of
them
are
not
at
all
active
in
our
communities
anymore.
E
C
E
C
A
D
Yeah,
it
looks
like
a
bit
of
a
solution
looking
for
a
problem,
that's
at
least
I'm
I
think
Justin
here
nodding.
Yes,
so
I
think
I
agree
with
that.
Do
do
we
know
at
least
from
the
paper.
I,
don't
see
a
you
know.
We
have
this
problem
or
somebody
described
this
problem
or
this
need
and
then
here's
what
we're
proposing
and
I
don't
see
it
that
way,
it's
just
sort
of
a
we
think,
there's
a
problem
or
we
think
this
is
needed
and
here's
how
it
will
be
solved.
Yeah.
B
D
In
the
background,
it's
it's
funny
that
we
should
talk
about
this.
This
point
this
morning,
when
I
it's
my
first
time
since
I
think
a
year
I
joined
there's.
Actually
this
is
actually
being
discussed
at
Salesforce
and
there
is
now
a
proposal
to
for
this
exact
thing
at
Salesforce
and
the
reason
for
it
is
that
at
Salesforce
the
the
CI
ecosystem,
it's
quite
fragmented,
there's
been
several.
D
There's
been
generations
of
of
CIS,
all
of
which
needed
workflow
functionality,
pipeline
column,
pipelines,
column,
workflows
and
that
we've
we've
decided
to
to
to
standardize
in
a
language
of
workflows
to
to
represent
more
genetically
represent
what
you
would
do
as
a
pipeline
and
they're
they're,
currently
using
Jenkins
and
and
those
Jenkins
files
pipelines,
but
believe
it
or
not.
D
They
want
to
switch
over
to
Tech
talk
well,
there's
even
prior
incarnations
of
that
even
before
Jenkins,
so
they've
had
they've
had
a
few
different
ways
of
describing
a
CI,
workflow
and
now
they're
thinking,
because
they've
had
so
many
different
dsls
for
those
you
know
you
know,
Jenkins
has
its
own
and
they've
had
homegrown
ones
before
that,
and
there's
one
called
nucleus.
D
It's
not
even
I
think
it's
a
Salesforce
only
Incarnation,
so
now
they're
thinking
they
really
need
a
universal
workflow,
DSL
I'm
in
contact
actually
with
with
the
people
who
are
in
our
in
our
cisfci,
which
is
the
Salesforce
CI
team
I'll
see
if
they
are
willing
to
contribute
and
or
yeah
to
contribute
their.
What
they're
writing
up
to
this
paper,
or
or
maybe
even
use
that
as
the
impetus
for
the
you
know
for
the
new
thing
we
will
rewrite,
but
I'll
I'll
find
out.
C
Four
I
mean
several
times:
we've
talked
about.
You
know
a
universal
language
and
abstraction
I
guess
to
describe
a
pipeline,
a
DSL
that
everyone
could
use
so
that
when
you're
moving
from
one
to
another,
it's
not
so
painful.
D
D
What
they
don't
want
to
do
is
tie
their
systems
again
to
something
very
you
know
concrete.
D
And,
let's
not
forget,
also
at
Salesforce
I'm,
actually
driving
a
an
effort
to
to
modernize
the
CD
ecosystem
based
on
Argo,
workflows
and
now
I
know,
and
people
say
you
know
using
both
techton
and
Argo
workflows.
Yes,
there's
there's
a
particular
need
that
the
CI,
the
CI
team
has
that
were
Argo
workflows.
They
actually
evaluated
it.
D
They
did
a
pretty
decent
evaluation
of
both
and
they
decided
that
Teflon
pipelines
fits
them
better
for
this
one
particular
feature
that
tecton
has
introduced
I
think
last
year,
early
last
year
and
so
they're
going
with
techcon,
but
for
the
rest
of
the
company
for
CD
general
purpose
CD,
because
right
now
Salesforce
is
very
Spinnaker.
Heavy
I
mean
they
are.
Every
Spinnaker
is
tied
in
Hook,
Line
and
Sinker
into
everything,
and
a
lot
of
processes
are
having
happening
with
Spinnaker.
D
All
of
their
get.
Ops
processes
are
tied
in
with
Spinnaker
and
a
bunch
of
other
homegrown
systems,
but
mainly
Spinnaker,
and
so,
and
it's
caused
quite
a
bit
of
problem.
I,
don't
want
to
go
into
it
here,
it's
it's
too.
Many
to
you
know.
We
don't
have
enough
time,
but
Argo
workflows
offers
really
a
much
better,
more
mature.
D
In
my
opinion,
in
our
opinion,
and
that's
what
we're
going
with
so
having
a
universal
way
of
describing
a
workflow
is
actually
something
that
the
company
has
ran
into
and
it's
it's
really
to
be
able
to
not
be
tied
into
one
and
what
they
want
to
do
is
have
that
DSL
and
then
have
a
interpreter
in,
for
you
know,
for
tecton
or
for
Jenkins
or
for
whatever,
so
that
that
the
interface,
the
user
interface
to
this
describing
workflow
is
singular
and
they'll
just
translate
to
other
things,
but
I'll
find
out
if
they,
if
they
are
willing
to
contribute
that.
C
A
C
Yeah
and
and
I'm
sure
there
will
be
others
too-
that
have
a
lot
of
empathy
for
this
issue.
C
I
think
it's
worth
doing,
I'm
going
to
put
it
as
an
action
item
to
maybe
take
the
next
steps
of
forming
a
working
group.
Is
this
something
that
you'd
be
interested
in
attending
rummy?
Sure?
Okay?
Why
not.
D
I
was
actually
a
little
bit
surprised
to
find
out
that
the
Argo
workflows
folks
originally
had
into
it
are
not
involved
in
in
the
CDF
they're,
not
members
of
CDF
they're
members
of
cncf
right,
but
not
CDF,
and
has
anyone
here
ever
approached
them
for
membership
in
CDF.
A
A
A
C
Andrea
good
to
see
you
we're
discussing
this
white
paper
and
we
we
got
off
on
the
subject
of
possibly
forming
a
working
group
around
a
Universal,
I'm
gonna
call
it
a
specification
for
workflows,
pipeline
workflows.
C
We
can
get
better
verbiage
there
later,
but
just
getting
into
the
notes,
and
some
of
the
discussion
around
the
white
paper
we
were
looking
at
is,
is
just
that.
There's
some
pieces
missing,
there's
some
updates
that
are
needed.
There's
contributors
that
are
listed
that
aren't
with
the
same
company
anymore.
So
we
may
need
to
be
rewriting.
You
know
some
of
this
and
then
also
we're
missing
real
life.
Examples
of
the
problem
that
we're
trying
to
solve.
C
C
C
C
Continue
white
paper
review
and
we'll
give
an
update
on
that
next
meeting,
all
right,
let's
back
up
a
little
bit
and
talk
a
little
bit
more
about
this
value
stream
mapping.
Since
we
have
Andrea,
you
had
an
opportunity
to
discuss
with
Helen
today,
I
was
going
to
copy
paste
our
chat
in
the
notes
and
that
didn't
work
out
so
well.
So
it's
better
for
that
you're
here.
Can
you
just
give
us
a
little
bit
of
background
in
how
that
call
went.
F
Yeah
sure
I
mean
the
the
call
was
just
like
a
quick
introduction,
you're
doing
Middle,
East,
sorry,
Helen
and
and
myself.
So
basically,
Ellen
gave
me
a
quick
introduction
about
what
what
they
do,
what
the
group
they're
doing.
F
So
they
have
a
a
set
of
member
companies
that
they
produce
software
in
the
area
of
value
management,
value
stream
management,
so
starting
from
feature
definitions
to
like
getting
the
feature
to
the
users
and
verify
that
the
value
was
actually
produced
for
the
users
and
being
completely
companies
like
atlassians,
for
instance,
where
you
can
Define
the
entire
workflow
of
your
feature,
requests
your
epics
and
then
get
all
the
way
to
the
users,
and
there
are
several
members
and
they
have
a
interoperability
issue
which
was
The.
F
Interpreter
will
be
technical
committee
was
born
and
that
of
the
ability.
Technical
committee
is
made
of
volunteers
and
they
want
to
try
and
decline
some
standard
for
this
solutions
that
exists
today
to
be
able
to
interpret.
So
it
will
have
some
common
format
to
describe
basically
the
data
that
they
they
would
deal
with.
F
I
mean
the
scope
as
quite
wide
I
would
say
it
goes
all.
The
way
from
defining
a
feature
through
you
know
all
the
software
pipelines
software
production,
then
all
the
way
to
the
end,
to
delivering
value
to
the
users,
but
so
I
think
there
is.
There
is
a
good
overlap
with
what
the
kind
of
topic
that
we
discuss
in
the
interoperability
working
group
as
well
as
India,
City
events,
project
yeah
and
the
I
guess.
The
objective
of
the
call
is
to
see
what
kind
of
synergies
may
exist
between
our
groups.
F
The
people
in
the
interoperability
technical
committee
group
they're,
not
necessarily
familiar
with
the
CDF
and
what
we
do.
So.
The
objective
of
the
call
that
will
happen
on
the
24th
so
next
week
is
to
basically
give
them
an
introduction
about
the
CDF
and
about
the
interoperability
special
interest
group,
as
well
as
the
CD
events
project,
so
that
they.
C
Excellent
okay
I'm
excited
for
that
call
and
we'll
make
sure
to
give
an
update
at
our
next
interoperability
meeting.
C
Thank
you
Andrea
for
that
very
good
stuff,
I'm
glad
we're
getting
some
attention
from
you
know
external
folks
wondering
what
we're
up
to
and
some
contribution.
That's
great
love
to
hear
that
all
right.
Next,
on
our
list
of
things,
we
had
down
defining
an
agenda
for
upcoming
meetings,
including
speakers.
We
may
want
to
come,
speak
I,
don't
have
anything
new
here
other
than
what
we
just
discussed,
giving
updates
on
our
current
activities.
C
All
right,
if
you
think
of
something
specific
something
comes
to
mind
between
now
and
then,
please
add
it
to
the
agenda,
feel
free.
C
Goals
of
the
Sig
this
year,
I
feel
like
just
getting
this
white
paper
done.
I.
Think
again,
that's
going
to
define
a
lot
of
what
we
want
to
do
this
year.
C
A
D
Is
this
still
happening
every
two
weeks
this
this
forum,
yeah,
okay,.
C
Yes
and
that's
something
worth
bringing
up
I
guess,
I
think
in
the
past
a
reminder
with
the
current
agenda
has
been
going
out
to
the
mailing
list,
maybe
put
in
the
slack.
We
haven't
been
doing
that
regularly
or
consistently
I.
Don't
know
if
people
find
that
helpful,
but
maybe
we
should
go
back
to
doing
that
so
like
at
the
beginning
of
the
week
of
when
a
meeting
is
scheduled.
C
Oh
I
froze
there
not
sure
where
what
you
heard
and
what
you
did
and
I'll
start
over
at
the
beginning
of
the
week
of
a
of
a
meeting.
Well,
we
can
send
that
out.
You
know
on
a
Monday
to
let
it
remind
everyone
we're
having
a
meeting
and
what
the
current
agenda
is
and
encourage
them
to
add
to
it.
If
they
have
something
they
want
to
speak
to.
A
C
Okay,
yeah
I'm
sure,
if
there
are
more
people
like
me,
that
will
forget
until
the
day
of
this
probably
helpful
to
have
that
happen
more
consistently.
We'll
work
on
that.
C
All
right
and
then
let's
I
can
start
a
document,
a
shared
document
or
something
and
put
the
link
in
here
where
we
can
brainstorm
on
a
more
formalized
bullet
list
of
goals.
A
C
C
And
updating
the
past
presentation-
Sig
documentation
I-
did
not
get
to
that
over
the
break
so
still
willing
to
do
that.
Maybe
some
you
know
just
some
leftovers.
Perhaps
we
need
to
Archive
our
previous
notes
from
last
year
so
that
we
don't
have
this
long
ongoing
list
like
we
do
right
now.
We've
done
that
the
last
couple
years.
So
anyone
want
to
volunteer
to
to
do
our
notes
clean
up
for
last
year.
A
C
F
F
I
just
wanted
to
mention
the
Lisa.
We
had
some
chat
on
the
CD
events
project
with
the
guys
from
that's
Cube,
Cube
test.
Sorry,
I,
don't
remember
it's
basically
the
that
they
provide
a
solution
on
kubernetes
to
to
manage
testing
or
kubernetes
basically,
and
they
are
interested
in
City
events.
Yes
called
Cube
test,
so
it's
like
they
have
an
open
source
project
called
Cube
test
and
they
are
interested
in
in
City
events.
F
We
we
met
them
back
in
Detroit
at
the
city
Summit,
so
now
they
actually
started
contributing
and
what
one
of
the
the
questions
when
setting
up
testing
related
CD
events
as
what
kind
of
name
they
want
to
use
for
a
certain
part
of
the
test
and
so
forth.
F
So
we
we
pointed
them
to
the
interoperability
working
group
into
the
existing
vocabularies
that
exist
within
the
interoperability
working
group
in
case
they
they
want
to
bring
up
some
yeah
vocabulary
discussion
in
terms
of
like
what
names
to
use
for
yeah,
test
priorities
or
kind
of
tests
like
because
in
in
the
context
of
City
events,
I
think
having
specific
names.
It
goes
a
long
way
in
terms
of
interpretability.
So,
for
instance,
if
a
tool
sends
an
event
about
an
end-to-end
test
and
another
one
stands
an
event
about,
and.
F
C
B
F
Them
about
the
the
interoperability
working
group
and
I,
don't
know
if
they
they
will
reached
out
or
reach
out
already,
but
yeah
I
just
wanted
to.
Let
you
know
that
and
very
interesting
to
have
that
discussion.
C
Maybe
yeah,
maybe
do
you
feel
comfortable
reaching
out
to
them
to
ask
if
they
want
to
present
to
us
at
one
of
our
meetings
coming
up.