►
From YouTube: Interoperability SIG - Apr 20, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
The
same
I
was
reminded:
that's
happening
this
week,
so
we
might
have
low
participation
because
of
that
I
know,
fatigue
won't
be
joining
us.
For
that
reason
he
says
they're
having
a
lot
of
good
conversations
over
there.
So
I'm
really
excited
to
hear
about
what
he
has
to
share
when
he
gets
back,
probably
at
our
next
meeting.
Hopefully
if
not
before
so
anyway,
since
I'm,
not
sure
who
else
will
be
joining
considering
this
week
is
pretty
busy
for
folks.
A
A
A
You
know
things
like
that.
We
do
not
have
a
sponsor
and
have
not
had
one
for
a
while,
because
we
didn't
really
have
a
process
in
place
for
when
the
TOC
members
of
you
know,
change
and
move
in
and
move
out.
A
They
might
you
know
I,
don't
know
if
they
would
start
joining
or
if
they
could
just
at
least
listen
to
the
recording,
so
they
can
at
least
report
back
to
the
group,
but
I
can
certainly
help
with
that
as
long
as
I'm
a
member
of
the
TOC
as
well.
So
that's
our
first
item
on
the
agenda.
I
just
wanted
to
make
you
all
aware,
and
for
anyone
watching
this
in
the
future,
make
you
aware
that
we're
working
on
that
and
getting
that
done.
A
Let's
see
I'm
just
gonna
share
what
I
have
right
now.
I
just
have
a
few
things.
A
We
talked
about
the
sponsorship
of
the
Sig.
We
do
need
to
define
the
agenda
for
upcoming
meetings
now
something
that
never
happened
was
this
this
year,
when
we
moved
over,
we
need
to
Archive
everything
you
know
from
the
previous
year,
get
it
moved
and
clean
up
our
repo
a
little
bit
clean
up
our
nodes,
a
little
bit
clean
up
all
of
the
previous
speakers.
A
We
have
a
list
out
there
of
all
the
speakers
that
we've
had
talk
along
with
their
slides
and
the
recording
link,
and
things
like
that.
I
would
like
to
make
sure
that's
clean
and
crisp
for
new
members
as
they
arrive
this
year,
we'll
be
working
on
getting
more
of
our
community
involved
and
then,
if
you
all
have
any
speakers
or
any
projects
that
sound
interesting
that
you
know
of
that,
we
would
like
to
have
present.
We
definitely
love
to
do
that
during
these
meetings.
We've
had
some
really
interesting
ones.
A
In
the
past,
when
I
was
reviewing
recently
was
we
had
a
someone
from
dagger
come
and
speak
to
us?
That
was
interesting
and
it
kind
of
aligns
with
a
possible
goal
that
we
may
have
want
for
this
year.
I'd
love
to
get
your
opinion
on
it.
A
We
have
been
talking,
you
know
now
and
then
the
subject
of
coming
up
with
a
a
more
abstract
version
of
pipelines,
for
example,
just
like
we
have.
We
have
our
you
know,
description
of
CD
events
that
that
whole
project
it
would
kind
of
it
would
be
nice
to
be
able
to
do
this
for
pipelines,
anyone
on
a
development
team.
Obviously
we
all
use
our
own
build
servers.
A
We
all
you
know
are
dealing
with
all
of
the
you
know,
whatever
language,
whether
you're
you're
using
a
yaml
file
or
whatever,
to
build
your
pipelines,
it
would
be
nice
to
have
some
standard
way
of
doing
it.
So
it's
not
so
painful
when
you
want
to
move
from
one
product
to
another,
for
whatever
reason.
C
Yeah,
that's
a
big
one,
so
when
you
say
that
or
you're
saying
that
the
the
definition
of
what's
the
steps
are
going
through,
the
tools
are
defined
as
pipeline
steps
for
all
CI
tools,
or
is
it
like
different
for
CI
and
CD
or
like
would
it?
How
is
that
going
to
overlap
for
this
pipeline
is
super?
You.
A
D
A
Mean
just
for
CI
I
mean
I,
know
so
many
people
that
are
you
know
using
a
particular
tool.
They've
used
all
the
bells
and
whistles
and
now
they're
stuck
there
right.
They
would
love
to
use
a
feature
of
another
tool
or
or
try
something
else,
but
it's
just
too
much
effort
to
move,
because
there's
too
many
different
things
going
on
right.
A
A
Oh
I,
don't
know
if
they're
they're
called
plugins
what
the
term
is,
but
you
can
write
these
things
that
actually
communicate
with
whatever
build
server,
for
example
that
you're
using
and
then
be
able
to.
You
know
have
a
more
abstract
way
of
working
with
your
Pipelines.
D
D
A
And
we
did
have
you
know
we
did
have
a
presentation
on
this
project
in
the
past
and
I
really
like
the
idea,
but
my
concern
with
something
like
this
is:
you
know,
often
an
interoperability.
We
talk
about
this
idea
of
glue
code
and
how
you
need
all
the
you
know
glue
code
to
integrate
all
of
these
different
products
together
in
order
to
make
them
useful
for
you
and
then
now
you're
involved
in
maintaining
this
glue
code
to
make
sure
that
it
operates
for
every
release
and
maybe
is
Backward
Compatible.
A
Things
like
that
and
I
feel
like
dagger,
might
be
in
that
Realm,
oh,
okay,
that's
even
better
yeah,
so
I
mean
the
worry
with
dagger
is.
If
you
know
you've
built
all
these
things
that
are
intended
to
be
used
for
a
particular
build
server
and
then
the
build
server
decides
to
do
something
different
now,
you've
got
to
fix
all
your
dagger
stuff
right.
A
So
if
we
go
one
step
further
and
have
you
know
a
definition
that
everyone
strives
to
use,
you
know
if
we
can
get
support
from
other
projects
to
say
you
know,
I
I
am
compatible
much
like
we
do
with
CD
events.
A
We
could
do
a
similar
thing
with
you
know,
pipeline
descriptions,
I'd
love
to
see
that
happen.
Yeah.
C
A
I
know
I've
spoken
about
it,
so
General
I
know
it
sounds,
might
sound
easier
than
it
really
will
be,
but
it's
something
I
think
we're
ready
to
start
working
on
I'm
sure
we're
not
the
first.
So
that
might
be.
One
of
our
steps
is
to
find
out
if
there's
other
groups
that
have
already
tried
this
or
attempted
this,
and
why
we
don't
see
it.
Why
why
it's
not
out
there
already
and.
D
C
Mean
when
we,
whenever
we
sit
down
and
say
hey,
we
need
a
DSL
that
we
can
use
across.
Everything
is
is
that
problem
as
soon
as
you
say
that
each
product
wants
it
like?
This
is
how
this
should
be
like.
You
know,
because
we
do
this
and
yeah,
and
it's
that
deviation
and
getting
them
to
own
those
deviations.
That
becomes
the
challenge
right,
and
you
said
it
yourself.
It's
like,
as
you
go,
there's
slight
differences
in
those
differences.
C
A
Exactly
so,
it'll
be
interesting,
we
do
have
you
know
representation
in
this
group
from
a
lot
of
different
projects
that
are
open,
source
and
available
I'm
thinking,
you
know,
Jenkins
Jenkins
x,
taking
a
lot
of
these
types
of
tools,
I'm
sure
that
we
can
get
a
lot
of
participation
from
these
groups
to
get
started
with
something
like
this
yeah
and
then,
of
course,
you
know
this
is
also
beneficial,
for
you
know,
organizations
to
for-profit
organizations
to
be
able
to
say
yes,
we
are
also
compatible
with
this,
so
that
the
rest
of
us
are
free
to
use
what
tool
we
choose.
C
A
C
It's
a
CI,
CD,
DSL
I.
Think
right
is
that
what
we're
looking
for
or.
A
A
DSL
or
a
yeah
yeah
there
might
be
a
better
better
word
for
that.
C
I,
don't
want
to
say
language,
but
you
know
that's
the
other.
The
only
other
term
like
we
need
a
configuration
language
that
describes
or
a
pipeline
pipeline
is
code.
It's
still
yeah
I
mean
whatever
name.
It's
fine
I'm,
not.
A
A
C
So
I
have
a
question
about
like
so
the
the
way
that
I've
seen
CD
events
or
been
you
know
talking
to
the
city
events.sig,
it
seems
like
CD
events
is
expected
to
work
both
as
something
that
uses
an
event,
bus
and
something
that
works,
peer-to-peer
who's.
Building
that
first
event,
bus
kind
of
service
for
CD
events
is
that
something
that's
been
described,
or
is
that
like
a
project,
that's
already
within
the
CDF
somewhere?
Or
is
it
just
up
to
the
user?
So
people
who
are
gonna?
C
A
Mean
this
first,
the
first
like
actual
implementation,
yeah
yeah
of
CD
events,
so
I'm
not
super
expert
on
CD
events,
but
my
understanding
is:
they
started
with
Cloud
events
right
that
that's
the
initial
implementation.
Okay,
as
far
as
anything
else,
that's
been
developed,
I,
don't
know.
Okay,
just
curious
and
I
I
would
assume
the
like
the
CD
events.
C
A
D
A
C
No
I
was
just
saying
right:
you're,
absolutely
right
and
specification
is
a
nice
way
of
saying
that
I.
C
C
And
then
I
say
this
because,
like
we,
the
CF
has
a
portfolio
of
things
and
as
that
portfolio
of
things
you
know,
even
if
they
start
to
adopt
CD
events
the
how
to
interconnect
the
pieces,
like
users
aren't
going
to
know
that
right,
there's
going
to
have
to
be
some
place,
they
go
within
the
CDF
to
say
oh
you're,
using
CD
events.
This
is
how
you
tie
these
Services
together
and
a
little
bit
of
that
would
come
from
each
service,
of
course,
so
I'm.
So
is
this
sig,
the
Sig
that
says
hey?
C
A
I
think
we
do
a
little
of
both
I
know.
There
was
a
lot
of
work
done
in
the
interoperability
seg
already
around,
like
getting
common
language
around
a
lot
of
these
things.
Having
a
common
vocabulary,
we
do
have
you
know
quite
a
list
of
you
know
Common
ideas.
When
we
talk
about
pipelines
like
what
steps
are
what
jobs
are.
You
know
things
like
that,
but
I
think
the
next
step
now
is
with,
with
all
of
that
in
mind,
take
a
stab
at
an
actual
specification
right.
D
A
C
Exactly
exactly,
and
then
that
circles
back
to
like
the
getting
that
implementation
within
the
the
projects
within
the
CDF
portfolio
to
support
it
and
use
it
like,
like
they're,
looking
to
do
in
CD
events
right.
C
All
right,
I
think
both
of
those
things
should
be
like
listed
as
part
of
the
goals.
Then.
A
C
A
D
A
So
something
I
will
admit
right
up
right
here
is
you
know,
I've
been
an
engineer
most
of
my
career,
so
I
often
start
at
the
implementation
level,
so
I'm
going
to
struggle
a
bit
with
the
higher
level
abstraction-
and
that's
you
know
we're
probably
going
to
need
to
work.
Both
ends
a
little
bit
here,
so
I'm,
hoping
that
folks
in
this
group
will
help
keep
me
out
of
the
nitty-gritty
details
enough,
so
that
we
can
actually
get
a
specification
that
makes
sense.
C
Yeah
I
think
this
is
a
I
mean
it's.
This
is
a
huge
goal
right
to
say:
hey
we're
going
to
do
a
cicd
specification
for
this
other
question.
I.
Think
part
of
the
challenge
here
is
getting
all
of
the
challenges
from
all
the
people.
Who've
attempted
this
and
the
reasons
why
it's
not
worked
to
keep
it
broad
enough
to
say:
okay,
you
know
these
are
the
minimum.
C
You
know
this
is
the
lowest
common
denominators
or
or
how
do
you
fill
that
Gap
and
and
how
you've
and
again
this
is,
like
part
of
me-
is
like
down
in
the
details
of
like
okay.
This
didn't
work
specifically
because,
but
with
enough
of
that
information
then
collect
it.
We
get
the
abstract,
that's
all
I'm,
saying
because
we've
tried
it
at
Apple,
of
course,
and
there
are
several
different
libraries
of
different
people
who
have
trying
to
take
on
this
task,
and
then
they
eventually
throw
up
their
hands
and
run
out
screaming.
C
I
think
that's
the
thing
that
I
don't
have
all
the
answers
to
right.
It's
that's
exactly
what
I'm
talking
about
it's
like
okay,
but
why
did
you
stop
like
if
you
went
down
this
path
and
then
why
does
something
like
gloomy?
How
did
that
exist
right
and
so
like?
Why
were
they
able
to
do
it,
but
then
over
here
we
can't
do
it
so
yeah.
C
Right
and
that's
the
challenge
and
then
even
if
and
I
know
like
we're
non-profit,
but
that's
that's
the
challenge
and
that's
why
you
need
you
know
a
company
behind
it
and
having
it
as
a
product,
because
there
is
so
much
work
to
do
in
that
maintenance.
And
if
we
make
that
a
part
of
we
get
a
specification,
it's
vetted
and
it's
happening
and
we
say
to
all
of
the
CDF
participants.
You.
C
Hey
you've
got
to
maintain
this
portion
of
this.
This
is
what
you're,
on
the
hook
for
at
least
in
the
spec,
so
that
we
can
make
and
maintain
the
sdks
that
come
out
of
this
right
right,
because
it's
the
only
the
specification
that
we're
asking
them
to
help
maintain,
and
so,
as
the
versions
change
with
some,
you
know
and
I'm
more
of
a
tdd
developer,
and
so
it's
like
well
I
can
write
tests
and
have
all
the
tests
rating.
C
So
as
things
change,
it'll
fail
and
be
like
okay,
there's
something
else
for
me
to
go.
Do
but
I
also
respect
that
not
everybody
thinks
that
way
or
Engineers
that
way,
and
so
yeah
it's
a
little
mix
up
on
it.
A
Right,
that's
true
and
I
mean
that's
a
dedication
of
your
time
too,
to
keep
that
up
exactly
keep
that
maintenance
up
exactly
well.
It
would
really
be
nice
to
pull
in
folks
like
anyone
involved
with
palumi
or
with
dagger,
for
example,
into
this
group,
to
have
these
discussions
with
them,
because
I'm
sure
they
have
very
first-hand
knowledge
of
what
the
struggles
are
with
keeping
up
with
all
of
these
other
tools,
yeah.
D
A
A
Not
not
as
direct
anymore
with
palumi
but
I'm
sure
I
can
find
someone.
C
Yeah
and
I
I
can
too
so
I
mean
okay,
cool.
Definitely
as
an
action
item.
We
can
do
that
I,
I,
think
for
so
Fati
is
actually
coming
out
to
the
Bay
Area
next
week
and
what
I
this
is
literally
my
first
interoperability
meeting
so
I
apologize
I've
been
trying
to
get
to
this
meeting
for
months.
C
And
so
this
particular
like
the
fact
that
you
want
to
do
a
CI
CD
specification
is
huge
and
there
are
a
lot
of
people
involved
in
my
org
that
are
trying
to
do
the
same
thing.
So
one
of
the
things
that
I
am
going
to
do
like
as
soon
as
we
get
off.
C
This
call
is
to
gather
some
of
those
people
ask
some
questions
about
their
challenges
and
then
see
if
we
can
see
who
they've
talked
to
to
add
to
this
list
right,
so
it
might
be
Beyond,
because
we've
gotten
several
demos
from
people
that
do
some
of
those
languages
that
I
can
find
out
who
they
are
and
see
if
we
can
get
them
involved
in
this
interoperability
process.
Just
to
start
having
the
conversation,
because
I
wasn't
aware
that
we
were
going
to
tackle
trying
to
create
this
particular
spec.
A
A
That's
fine,
at
least
we'll
have
the
documentation
we'll
have
the
information
out
there
for
the
next
person
that
tries
to
do
this
right,
don't
mean
to
be
pessimistic
but
trying
to
be
realistic
about
it,
because
I
do
know
that
you
know
I'm
coming
in
thinking.
C
I
think
it's
at
a
good
point
to
stand
on
some
of
the
shoulders
that
people
have
already
done
it
and
that's
what
I'm
saying.
Let
me
take
some
time,
try
to
find
some
of
those
people
so
that
as
we're
taking
this
on
we're
going
in
the
right
direction,
I
think
having
taken
the
step
with
CD
events
to
kind
of
break
down
like
the
areas
and
then
the
possibilities
underneath
them.
C
We
also
have
some
idea
of
just
the
language
structure
and
how
the
abstracts
should
look
as
we,
you
know,
move
into
those
same
Primitives
to
kind
of
write
some
code.
Next,
you
know
to
create
the
specification,
so
I
think
you're,
absolutely
right.
This
is
a
great
time
to
do
it.
I
know
a
lot
of
people
want
to
get
to
that
very
very
end
thing
where
everything
is
code
is
just
maintained
and
just
kind
of
happens
so.
D
C
A
All
right
so
sometimes
when
we
we
come
up
with
ideas
like
this
I
was
discussing
with
fatigue
at
our
last
meeting.
It
was
just
he
and
I
at
our
last
meeting
whether
it
was
appropriate
to
spin
off
a
working
group
for
this
type
of
activity,
or
in
our
case
I
mean
we
don't
really
have
anything
else
going
on
at
the
moment.
It
probably
doesn't
make
sense
to
spin
anything
off.
A
A
You
know,
unless
you
know
we
get
a
bunch
of
people
involved
that
are
super
excited
about
something
else.
Then
we
can
make
that
decision.
Then,
of
course,
of
course,.
C
A
Totally
makes
sense,
cool
cool
all
right,
the
only
other
thing
I
had
to
discuss.
We
have
this
white
paper,
that's
been
sitting
out
there
aging
and
molding,
and
we
had
this
wonderful
idea
of
getting
it
all
cleaned
up
and
out
by
the
end
of
q1.
A
That
did
not
happen
and
now
we're
in
the
situation
where
we
have.
You
know
so
many
authors
that
have
moved
on
you
know
we
need
to
I,
don't
know
if
we
need
to
step
back
and
consider
just
rewriting
this
thing
or.
C
But
he
had
asked
me
to
take
a
look
at
it,
and
I
had
taken
a
look
at
it
and
started
down
the
process
of
you
know
what
would
I
do
how
to
fix.
It
is
what
it
basically
like.
How
do
we
finish
it?
What
I
couldn't
figure
out
when
I
looked
at
the
document
is
who
was
it
for
because
technically
usually,
when
I
see
white
papers,
they're
very,
very
specific
about
the
target
audience,
and
so
as
I
read
through
it,
I
was
like.
C
Oh,
this
is
actually
like
seems
to
be
like
three
or
four
white
paper,
just
kind
of
combined
around
the
same
subject,
and
one
of
the
things
that
I
was
going
to
do
with
fatigue
here
was
to
sit
him
down
and
go
okay.
This
is
what
I've
started.
Let's
see
if
this
works
for
you,
so
I
could
present
it
back
to
this
group.
C
So
I
am
actually
going
to
be
working
on
finishing
some
of
that
this
weekend
and
then
writing
that
for
his
visit.
So
I
think
this
is
still
a
great
document,
but
it
it's
just
hard
to
tell
like
who
were
we
talking
to
right.
C
C
That's
pretty
good
yeah
next
time,
yeah!
No!
Definitely
next
time
like
I,
said,
I
was
going
to
share
it
with
Fati
next
week
to
be
like
okay,
is
this
am
I
even
close
to
what
you
expected,
and
it
was
because
I
hadn't
been
able
to
come
to
the
meeting
I.
That's
also
why
I
didn't
want
to
just
start
commenting
on
the
document
and.
A
D
C
Is
this
guy
commenting
on
our
document
like
that's,
not
really
my
style,
yeah
cool
yeah,
so
so
definitely
next
time,
yeah
I'll
have
definitely
have
stuff
to
show
so
awesome.
A
Cool
looking
forward
to
that
I
know,
several
of
us
have
looked
at
it
and
we're
just
like
we're
not
getting
anywhere
with
this
so
excited
to
have
some
new
eyes
on
it.
Maybe
A
New
Perspective
will
help.
D
A
Well,
good!
Okay!
That's
all
that
I
had
for
this
particular
meeting.
Just
getting
your
goals
outlined,
I'm
gonna.
Add
some
action
items
here,
because
I
did
talk
about
cleaning
up
the
notes
and
things
like
that.
I
think
I'm,
the
only
one
right
now
that
has
like
sync
access
and
stuff
in
order
to
move
things
around.
So
that's
on
me
to
do
that.
A
A
Promotion
of
those
sometimes
they're
they're
super
interesting
content,
but
maybe
we,
you
know,
maybe
have
10
of
us
on
the
call
at
the
time
or
something
I
think
for
for
folks
to
spend
their
time
and
do
that
with
this
group
we
should
be
promoting
that
a
little
bit
more,
whether
that's
just
in
our
our
private
social
media
accounts
or
possibly
linking
you
know
from
our
YouTube
accounts
recordings.
You
know
to
those
recordings
so.
A
To
conferences
just
have
more
links
available
for
people
to
look
at
I
think
we
have.
We
have
one
document
that
lists
them,
it's
kind
of
hidden
right
and
then
you
know
this
is
my
personal
pet
peeve.
But
when
a
video
goes
around,
I
really
want
to
know
what
it's
about.
I,
don't
like
sitting
and
watching
a
video
when
I
don't
know
the
content
or
I.
A
A
We
could
spend
a
little
bit
more
time,
and
maybe
that's
not
this
group
in
particular,
but
something
I'll
bring
up
to
the
TOC
that
that
might
be
something
that
would
be
helpful
to
CDF
as
a
whole
to
spend
a
little
bit
more
time,
curating
our
content
and
improving
searching
of
it
and
promoting
it
a
little
bit
better
yeah
yeah,
so
there's
one
in
particular
I'm
looking
at
and
we
had
them
present
to
us.
A
It's
called
j
releaser,
a
project
I
was
super
interested
in
and
they
just
released
I
mean
they
just
were
working
on
like
a
a
way
for
their
project,
to
integrate
with
CD
events
or
to
you
know,
work
with
the
spec,
and
that
was
pretty
exciting.
So
I
would
like
you
know
when
they
announced
that
that's
ready
for
folks
to
use
and
take
a
look
at
I'd
love
to
take
a
peek
back
and
and
maybe
promote.
You
know
the
presentation
they
gave
to
our
group.
A
A
All
right,
good
deal
and
that'll
help
too
I
mean
I'm
on
the
TOC,
so
I
know
you
know.
I
can
make
that
happen
for
now,
but
I
definitely
want
to
make
sure
that
we
always
have
a
sponsor.
That
is
a
member
of
the
TFC,
because
you
know,
all
of
our
terms
are
are
varied,
so
I
won't
be
part
of
the
TOC
forever.
A
B
For
one
question
for
me,
but
I'm
just
interested
in
the
the:
what
are
you
talking
about
interoperability?
Is
there
like
a
a
list
of
the
CVS,
the
the
foundation
members?
That's
part
of
this
interview
like
interoperability
between
what
is
the
beginner
question.
So.
C
C
Well,
as
much
as
I
can
speak
about
it,
it's
like
there
are
a
lot
of
people
using
open
source
tools
and
I
am
looking
for
a
way
to
understand
end
to
end
what
that
process
looks
like
and
you
can
take,
metrics
or
or
you
know,
from
everything
and
try
to
pull
it
all
together.
But
if
the
systems
have
some
self-awareness
or
awareness
of
their
environments
that
they
can
speak
to
each
other,
then
we
get
some
sort
of
commonality
between.
C
You
know
how
we
present
that
information
on
the
other
end
of
that
and
how
we
communicate.
So
it's
literally
everything
can
be
involved
in
it,
but
it
kind
of
has
to
describe
itself
I.
Think
one
of
the
things
that
was
really
well
done
with
CD
events
is,
it
begins
to
section
off
the
different
parts
of
what
CI
CD
actually
is
in
a
way
that
each
relevant
piece
can
still
contain
its
own
self-awareness.
But
then
we
have
this
ability
to
track
it
from
beginning
to
end.
C
The
only
thing
that
I
found
missing
in
the
spec
was:
how
do
we
relate
things
that
are
happening
in
parallel
and
then
so?
That's
the
the
contribution
that
we're
working
on
adding
to
the
spec
right
now
to
say
hey!
This
is
how
these
events
are
linked
together,
so
that
you
get
that
full
and
Broad
picture
of
not
just
when
was
something
committed,
but
then
from
that
commit.
When
did
it,
deploy
and
being
able
to
have
each
system
then
kind
of
be
drop
in
Drag
and
still
be
able
to
collect
that
information?
C
B
It
definitely
helps
yeah.
It
would
be
great
if
if
this
effort
will
start
with
some
diagrams
so
for
beginner
I'm,
actually
not
even
a
TI
CD
person
I'm
a
database
guy
I'm
just
interested
in
so
it
would
be
great
to
have
some
diagrams.
So
I
can
have
a
clear
picture
of
what's
going
on
what
what's
involved
yeah,
for
example,
you
know,
for
you
know,
Jenkins
and
jfrog,
and
how
what's?
What's
the
workflow
like
right
now,
I'm
The
Wiz,
this
interoperability,
how
it
works
better
and
all
that
in.
A
I'm
going
to
add
that
to
our
goals,
because
I
think
you're
right
I
think
it's
a
really
good
introduction
just
to
get
everyone
on
the
same
page
as
far
as
what
we're
actually
trying
to
do.
I
like
pictures
too,
it's
very
helpful
all
right,
good,
all
right!
That's
all
that
I
had
all.
C
A
Yeah
all
right
all
right,
I'll,
give
you
back
some
time
for
your
day,
good
talking
to
you
and
until
next
time,
bye.