►
From YouTube: CDF SIG Interoperability Meeting - 2020-10-01
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
D
A
D
D
F
A
The
agenda
was
updated,
comparing
to
what
I
sent
to
mail
list.
So
let
me
quickly
go
through
the
topics
on
the
agenda.
The
first
topic
is,
as
usual,
action
item
review,
followed
by
cdcon
and
tracy.
I
hope
you
can
talk
about
this
because
I
put
your
name
there
and
the
next
topic.
Yeah
thanks
and
the
next
topic
is
on
cd
corner
as
well,
but
this
time
on
interoperability,
birth
of
a
feather
session
and
tracy.
A
Again,
if
you
can
walk
us
through
how
the
session
format
is
about
and
linkster
and
then,
as
usual,
we'll
continue
talking
about
the
interpret
white
paper.
A
So
we
have
eight
people,
which
seems
we
have
people
successfully
find
found
the
meeting
id.
So
we
can
start
with
action
items
and
the
first
first
item
is
this
zone
thing
tracy
and
I
see
you
updated.
The
invitation,
which
makes
me
think
you
can
close
the
item
and
the
issue.
D
It
should
be
okay
from
next
week.
They
gave
me
access,
I
broke
everything,
but
I
think
it's
good
now,
okay,
so
let
me
close.
A
D
A
Yeah,
I
think
if
you
can
give
access
to
cara
as
well,
so
you
know
if
one
of
us
is
not
available,
the
other
can
take
it
over
like
fix.
What
is
what
means.
D
A
A
Oh,
we
don't
have
christy
here,
but
we
have
cameron
so
kind
of
you
know
cameron.
You
and
christy
started
this
new
document
about
ci
cd
definitions
and
you
missed
the
earlier
meeting.
So
I
can
summarize
this.
A
A
D
Yeah
and
just
as
a
follow-up
we'll
do
this
via
the
topic,
we'll
kick
off
a
not
a
special
interest
group,
but
a
working
group
just
to
come
together
set
out
those
definitions.
A
D
Yes,
yes,
so
there's
been
just
a
lot
of
activity.
We
made
a
few
big
changes,
so
I
just
wanted
to
highlight
those.
So,
first
of
all,
we
had
been
asking
for
donations
for
people
to
register,
and
then
we
had.
This
was
a
bit
of
a
barrier
to
people
signing
up.
So
these
are
now
optional.
D
D
I
think
we're
well
on
track
for
a
thousand
attendees
next
week
and
we
also
made
the
changes
to
the
program
so
we'd
start
earlier,
especially
for
folks
in
europe,
we've
kept
the
keynotes
at
the
same
time,
but
there'll
be
sessions
kicking
off
a
bit
more
reasonably
and
we
added
in
a
whole
bunch
of
interactive
sessions.
So
where
folks
could
you
know
just
try
to
get
together
with
community
and
focus
on
theme?
D
So
that
takes
us
into
the
next
agenda
item.
We
will
have
about
30
minutes
in
the
conference
platform
where
we'll
say:
okay,
this
is
a
birds
of
a
feather
informal
discussion
for
the
interoperability
sig,
we'll
invite
people
to
to
just
jump
in.
They
can
either
go
on
on
camera
like
zoom
or
they
can
just
hang
out
in
the
chat
but
we'd
like
a
couple
of
folks
from
this
group
or
as
many
as
possible
to
be
on
hand
there
to
welcome
folks.
C
A
Thanks
for
the
tracy-
and
I
read
the
document,
this
document
you
put
there
and
following
the
advice
you
put
here,
so
I
created
this
md
document,
which
is
linked
on
the
meetings
as
well.
A
It's
simply
like
it
looks
like
regular
meeting
minutes
but
like
participants,
so
we
can
capture
who
joined
and
we
can
try
to
reach
out
to
them
if
they
have
shown
interest
during
the
session
and
also
some
topics
and
please
feel
free
to
update
topics
like
basic,
simple
welcome,
so
we
can
ask
everyone
who
is
there
and
why
they
are
there
and
to
know,
allow
people
to
speak,
and
then
we
can
also
like
people
coming
from.
The
sikh
can
also
talk
about
what
this
sufficient
test
group
interval
is
about.
A
So
we
give
some
background
information
to
people
how
to
join
collaborate
and
contribute,
so
people
can
click
right
during
the
session
and
bring
them.
You
can
bring
them
to
slack
or
mail
list
and
also
where
to
find
more
information
link
to
github
and
depending
on
how
the
conversation
goes
and
if
there
is,
you
know
why.
A
If
people
are
silent,
we
can
talk
about
our
progress
like
vocabulary
stuff
and
the
roadmap,
and
the
work
stream
like
trying
to
you
know
get
people
speak
up
and
if
it
doesn't
help,
then
we
can
continue
talking
about
the
ongoing
work.
Like
the
events
in
cicd
and
I
hope
ravi
andreas
emily.
You
can
join
to
the
session
helping
people
understand
what
this
work
stream
is
about,
and
then
white
people
could
be
another
topic
to
discuss,
and
then
you
can,
I
know,
usable
libraries.
D
D
A
Session,
I
don't
know
what
call
okay
yeah.
That
would
be
great,
so
people
can
click
right
when
they
join
so
and
the
other
thing
was
in
this
document.
Why
was
that?
A
G
A
Okay,
so
you
know
where
the
hack
and
leader
could
for
the
session
is
they're
all
linked
on
the
agenda.
The
document
to
sign
up
as
volunteer
is
on
the
agenda
as
well,
and
thanks
dave
for
signing
up
and
the
schedule.
This
is
the
burst
of
feather
sessions
for
all
the
ones
scheduled
like
we
have
some.
We
have
from
projects
all
projects
under
cdf
have
both
sessions
and
we
have
made
of
envelopes
session
as
well,
and
that's
this
topic.
A
Okay,
maybe
before
we
move
to
the
white
paper
topic,
because
we
have
lots
of
things
to
discuss
based
on
previous
weeks,
is
there
anyone
who
wants
to
bring
up
a
different
topic.
A
Okay
and
we
move
to
the
white
paper
topic,
so
I
think
we
started
this
work
during
august
now
we
are
almost
two
months.
We
are
working
with
this
document
and
I
think
we
have
ideas
about
some
chapters,
like
the
definitions,
as
we
discussed
during
previous
meetings
and
as
noted
here,
we
realize
this
is
an
area.
Cdf
should
put
an
effort
and
contribute
to
domain
definitions,
and
while
that
work
starts
happening,
we
can
look
at
the
existing
material.
A
I
think
we
got
material
from
trace
reagan
during
previous
meeting,
so
we
can
take
some
definitions
from
this
document
and
put
them
there
as
placeholders
and
if,
by
the
time
we
have
the
white
paper
interpreted,
white
paper
is
ready
and
if
the
cic
definition
work
stream
has
something
we
can
perhaps
take
some
stuff
from
that
document
and
replace
what
we
have
here
and
then
cdf
needs
to
schedule
these
white
papers
in
right
order.
So
we
don't
spoil
definition
white
paper,
so
that
is
yeah.
D
D
For
starters,
so
I
don't
know
folks,
so
I
wrote
a
blog
post
about
what
a
terrible
term
it
is
and
why,
and
so,
instead
of
that,
we're
leaning
towards
saying
you
know,
let's
use
the
term
continuous
delivery
as
this
overarching
umbrella
for
ci
version
control,
automated
deploy
security
and
that's
pretty
consistent
with
the
accelerate
book
and
how
they
talk
about
continuous
delivery.
So
I
think
we'll
be
really
moving
that
direction
and
sharing
a
lot
more
about
kind
of
all
these
different
things
and
that's
where
tracy
reagan
brought
in
the
the
landscape
we
have.
D
D
And
yeah
now
I
think
we
as
they
say,
we're
spinning
up
the
screen.
We're
just
gonna,
be
writing
some
blog
posts
and
things
to
get
feedback
and
to
hear
what
people
think.
But
I
think
who
is
it.
D
Owen,
adams
in
the
ambassador
group
he's
just
saying
you
know
the
cicd
people
think
it's
you
do
ci
and
then
you
do
cd
and
you're
done
and
it
kind
of
either
simplifies
that
oversimplifies
the
problem
or
makes
you
think
of
these
silos
and
really
it's
just
all
these
practices
that
that
need
to
come
together
under
this
one
umbrella.
So
yeah
read
the
post
and
I
really
love
any
thoughts
and
whether
you
agree
disagree.
I
think
it's
all
part
of
us
figuring
this
out
together.
G
What
it's
worth,
I
think,
that's
great,
I
think,
we've
really,
as
we've
been
getting
more
automation
and
pushing
things
left
a
lot
more
than
we've.
You
know
with
those
those
boundaries
that
we've
kind
of
put
up
previously
in
previous
of
getting
a
little
bit
more
blurry.
It's
about
delivering
software.
We're
having
you
know
the
shifting
left
is
we're
having
automated
deployments
into
there,
but
deploying
code
we're
having
running
tests,
we're
maybe
putting
sharing
some
traffic
in
between
them
as
well.
D
Yeah
and
then
we
want
to
just
establish
those
practices,
have
a
way
of
sort
of
saying.
Okay.
This
is
where
this
is
where
the
cutting
edge
of
the
industry
is.
This
is
where
most
people
are
here's
how
you
figure
out
how
to
get
better
and
better
in
each
of
these
things
and
just
evaluate
yourselves,
but
you
know,
every
everything
is
about
just
improving
steadily
in
the
different.
C
A
Yeah,
I
was
going
to
say
tracy,
I
think
the
I
think
you
tweeted
about
this
blog
post
and
I
was
looking
at
the
replies
you
received
some
people,
weren't
so
I'll,
say
positive
to
your
blog
posts,
any
feedback
or
any
reflections,
because
it
is
difficult.
You
know
changing
people
from
using
ci
cd
to
continuous
delivery
and
you
directly
got
feedback
from
people.
D
Yeah
no,
I
appreciate
that,
like
I
think,
like
I'm,
under
no
solutions
that
we're
gonna
completely
get
rid
of
the
term,
but
I
think
if
cdf
wants
to
be
a
place
driving
for
clarity
and
really
helping
people
get
better,
then
we
need
to
be
consistent
internally
and
just
set
out
what
we
mean
by
the
different
terms
and
how
that's
going
to
influence
what
we're
building
going
forward
and
how
it's
all
going
to
fit
together.
F
D
Yeah
thanks
for
that,
and
and
just
so
you
know
like
we,
I
think
we're
christy
myself
we're
doing
a
keynote
at
cdcon,
so
we're
gonna,
I
think,
just
start
kind
of
trying
to
get
that
message
across
and
talk
about
how
how
we
want
people
to
just
be
consistent
and
use
the
terms.
F
You
know,
because
that
that
was
one
thing
that
stood
out
to
me
about
the
discussion
a
couple
about
a
month
ago
was:
it
was
both
sides
were
kind
of
like
well,
the
experts
say,
and
it's
like
well
we're
all
experts,
you
know,
or
at
least
trying
to
be
so
so
yeah,
maybe
even
just
lampshading
and
being
like.
This
is
not
about
you
know,
disrespecting
anyone's
expertise
or
or
opinions
or
beliefs
about
this.
This
is
just
about
trying
to
find
common
language,
and
this
is
the
way
we're
going.
F
That
that
might
be
an
american
term.
Lamb
shading
means
to
like
explicitly
call
out
something
like
as
that
that
might
be
subtext,
otherwise,.
A
Okay,
I
think
this
the
terminology.
I
think
you
all
probably
remember
the
discussions
we
had
on
this
time
manager
vocabulary
document
when
we
collect
all
the
different
terms
used
by
different
projects.
One
of
the
topics
or
discussions
was
like
establishing
shared
time
manager.
Endeavor,
like
I
think
I
remember
I
mean,
was
talking
about
like.
Is
it
why
we
are
here
like
why
we
like?
Should
we
really
think
that
that
type
of
you
know
a
bit
pessimistic
comments?
A
Well,
I
think
if
cdf
can
push
on
this
direction,
starting
with
basic
ci
or
cd
terms,
that
could
actually
help
us
to
help
us
to
talk
to
people
who
have
similar
tools
and
perhaps
starting
in
working
on
shared
vocabulary
in
different
or
more
external
civ,
like
using
pipeline
everywhere,
for
example,
just
speculating
or
using
stage
error,
node
everywhere,
and
especially
this.
You
know,
the
language
reform
is
going
on
within
all
these
different
communities,
like
changing
the
branch
names
or
changing
the
terms
jenkins
uses,
for
example.
So
it's
like
about
similar
thing.
A
A
Okay,
so
that
was
definition
chapter,
so
we
parked
that
chapter
until
we
get
some
input
or
something
to
reuse
from
the
tracey's
work
stream
and
you
can
see
in
the
white
papers.
I
am
still
sharing
here
because
I
move
around
pro
serving
those.
A
Okay
and
the
next
chapter
is
about
what
does
intervention
mean
in
cicd
context.
I
think
this
is
a
key
chapter,
because
this
is
this
interval
by
paper,
and
we
need
to
describe
what
we
are
talking
about
here.
So
people
see
if
this
is
something
they
should
continue
reading
if
they
should
come
and
contribute.
So
this
is
key
chapter
and
please
like
there
is
some
suggestion
here.
Please
look
at
it
and
you
know
comment
contribute
improve.
A
A
A
Again,
this
looks
at
what
we
discussed
over
the
past
few
months,
like
these
bullet
points.
Like
some
people
talked
about
pipeline
standardization
languages,
others
talked
about
connecting
integrating
pipelines,
and
I
think
andreas
mlu
were
talking
about
this
pipeline
data
for
trace
video
visualization
and
events
in
ci
cd.
So
I
think,
like
this
could
all
be
considered
as
things
to
deal
with
when
we
work
on
intervals
in
ci.
A
B
Sure
yeah,
so
in
our
work
stream,
we
iterated
on
a
problem
statement
which
we
would
like
to
solve.
Also
the
problem
which
we
would
like
to
solve
with
using
events
and
then
with
that
sets
down
and
discussed
how
this
interoperability
can
be
increased
using
events.
So
I
would
like
everyone
to
read
through
these
two
paragraphs
and
give
us
feedback
or
extend
it
directly,
and
the
feedback
is
welcome.
E
B
And
honestly,
or
if
you
don't
agree,
of
course-
and
we
still
have
some
wording
issues
so
some
terminology
which
we
are
not
sure-
whether
we
should
use
it
or
how
to
streamline
this
in
the
entire
document.
So
also
here
in
the
feedback,
is
welcome.
For
example,
we
are
not
sure
whether
we
call
products
projects
what's
the
different
difference
here,.
B
G
As
part
of
that,
just
wondering
is
there
a?
Was
there
already
some
work
done
on
the
glossary?
I
can't
remember:
maybe
somewhere
else,
is
it
worth
having
something
like
a
glossary
of
what,
like
you
said,
project
and
what
these
things,
because
there
are
so
many
different
terms
and
they're,
overused
as
well
as
quite
quite
heavily,
they
can
be
in
different
things,
a
different
context.
I
don't
know
if
that
that
might
be
useful
as
part
of
this
white
paper
as
well
as
we
go
along.
E
I
guess
that
that
specific
item
that
the
product
projects
discussion
has
not
been
raised,
but
we
have
the.
As
you
know,
I
guess
this
vocabulary
document
in
the
sig
where
we
define
like
what
is
a
pipeline.
What
is
a
pipeline
step
or
a
stage
or
whatever
different
tools
use
the
different?
I
don't
know.
Maybe
we
could
maybe
add
product
projects
there
as
well,
or
it
could
also
be
components
or
a
lot
of
different
names.
For
mostly
the
same
thing,
I
guess
yeah.
E
Actually,
so
I
looked
in
the
cncf
landscape
and
there
is
actually
a
division
there
where
what
they
call
the
products
projects
the
same
as
we've
done
here,
so
they
actually
use
both
terms
there,
but
when
they
want
to
show
different
kinds
of
tools
or
items
whatever
that
you
handle.
When
you
run
your
to
pipeline.
G
E
G
I
think
the
the
cncf
they
were
working
on
what
is
an
application?
I
think
I
don't
know
how
far
they
got.
I
know
it
was
going
on
for
quite
some
time,
but
it
might
be
worth.
E
G
A
Okay,
for
thanks
andreas
again
and
to
ravi
okay,
really
controversial
materials;
okay,
thanks,
sorry,
matthias,
missed.
F
Tracy
real
quick
that
just
made
me
think
of
something
too
around
communicating
language
right,
which
is
to
I
think,
to
the
point
you're
making
like
it
doesn't
matter
how
you
discuss
these
terms
elsewhere.
Right
like
this,
is
our
definition
of
it.
Well
you're!
Well,
you're
in
cdf
space
right
like
you,
can
you
can
talk
about
ci
cd
in
any
other
community
that
you're
talking
about
this
stuff
in,
but
when
you're
in
this
space?
This
is
it
right.
I
mean
similar
to
that
like
this
is
what
app
mean
in
this
space
right
totally.
D
Yeah,
no,
I
think
that
will
be
useful
and
I
I
think
we
need
to
think
about
putting
together
that
glossary
so
that
we're
saying,
okay,
we
just
all
need
to
work
together.
We
need
to
be
clear
about
what
we
mean
by
different
things
when
we're
in
these
working
groups.
So
here's
the
definitions,
we're
working
to
it
doesn't
mean
they're
fixed,
so
they
won't
evolve,
but
it
does
mean
if
we
change
them.
We
all
agree
that
things
have
evolved.
The
moon
or
the
common
usages
has
changed,
and
so
it's
just
to
avoid
confusion
for
us.
D
C
D
C
B
A
G
Yeah
it's!
I
can
probably
pick
that
up
now,
but
we've
had
a
bit
quite
a
lot
on
recently
and
the
story
around
there
is
going
to
be
a
lot
better,
we're
actually
working
on
the
jenkins
x3,
it's
currently
in
alpha,
but
we're
the
it's
native
integration
with
techton
and
tekton
catalogue.
So
it's
there's
a
nice
story.
I
guess
so.
We
kind
of
slightly
dragged
our
feet.
G
I
think,
but
it's
because
it's
a
better
story
very
soon,
so
I
can
probably
start
putting
filling
that
out
within
the
next
week
or
certainly
by
the
next
by
next
time,
but
socialize
it
for
the
next
week.
A
A
Okay
cameron,
I
think
last
time
you
were
in
the
meeting,
you
were
positive
about
bringing
something
from
speaker
community.
I
A
Okay,
thanks
and
when
jeremy
was
year
during
class
meeting,
he
talked
about
having
a
case
study
from
zul
for
a
manufacturing
company,
but
he
didn't
want
to
spoil
their
keynote
in
upcoming
for
summit.
So
we
will
ask
him
again
once
the
summit
is
over
and
the
end
user.
So
dave
thanks
out
for
putting
your
story
here
and
and
then
you
can
tell
us
about
what
you
put
here.
F
Yeah,
so
I
mean
I
just
kind
of
based
this
off
of.
I
was
trying
to
very
much
summarize,
like
the
presentation
I
gave
a
month
ago,
so
yeah
I
mean
happy
to
get
feedback
on.
This
is
purely
just
a
draft
kind
of
based
on
that
trying
to
summarize
that
story,
so
any
feedback
people
got
it
love
to
work
it
in
including
this
is
not
the
right
direction.
You
know,
but
yeah
just
feel
free
to
post
in
there,
and
let
me
know
what
what
could
be
better.
A
Okay,
emil,
anything
from
you.
E
Yeah
we
are
we're
in
a
review
review
still
of
this
meeting.
We
need
to
have
it
approved
before
we
can
bring
it
out
to
the
public,
but
it
will
hopefully
come
before
the
next
meeting.
I
was
like
yep,
so
it's
soon
to
be
there
nope.
A
A
Because
again,
as
we
discussed
last
during
class
meeting
now,
we
have
go
spot
check
here.
It's
different
industry,
we
have
telecom
and
if
you
can
like
an
angel
case
study
would
be
from
manufacturing.
A
D
Them
here,
fintech
capital,
one
pretty
active
in
cdf,
we'll
see
what
we
can
reach
out
to
a
few
folks.
Actually,
questions
for
dave.
What
is
good
spot
check
is
that,
are
you
considered
retail?
What's
your
industry.
F
We're
I
mean
we're
a
tech
company
like
we.
We
provide
an
application
that
is
used
across
retail
alkbev
facilities,
management
like
we.
We
have
customers
in
many
different
verticals,
but
but
we
we
make
an
application
that
is
used
by
other
companies
to
track
feel
to
track
and
and
and
analyze
like
field
data
right
about
about
anything.
To
do
so,
like
outback,
companies
make
sure
that
local
liquor
stores
have
the
correct
promotional
stands
up
and
facilities
management
companies
use
it
to
make
sure
that
rooms
are
being
cleaned
to
the
correct
standard
right
like
it's.
F
Yeah
yeah,
but
I
mean
as
a
as
a
case
study
it's
mostly
for
a
small
smallish,
but
not
four
people
startup
right
like
we're,
we're
on
the
lower
end
of
size
compared
to
erickson
or
ebay.
But
but
not
you
know
a
five
person
shop
or
something.
D
Yeah
and
I
think
actually
that's
something-
I'm
hearing
repeatedly
people
are
keen
to
know
the
difference
between
what
teams
can
do
and
based
on
size
of
companies.
So
it's
a
big
difference
for
like
a
five
person
team
versus
50
people
versus
a
few
thousand.
So
I
think
that's
that's
a
nice
distinction
to
make
in
in
the
case,
studies
here.
F
Yeah
and
that's
why
every
time
I
do
one
of
these,
and
even
when
I'm
like
speaking
at
conferences
and
stuff,
I
always
mention
how
big
we
are,
because
there
is
a
huge
difference
between
like
we
have
people
who
can
contribute
back
to
these
projects,
and
I
can
put
four
people
to
make
our
pipeline
versus
like
it's
me
and
a
guy,
and
we
have
to
make
sure
that
everyone
can
deploy.
You
know
yeah.
A
B
A
Okay,
then,
thank
you
all
for
joining
and
we
will
talk
to
each
other
next
wednesday
and
thursday
yeah
soon
and
eight
and
eight
so
yeah
wednesday.
We
will
have
the
sick
interoperability
course
of
feathers
session
and
in
parallel
to
that,
we'll
have
jenkins
changing
sex
session
and
on
thursday
we
will
have
envelopes
tactone,
spinnaker
and
screwdriver
for
further
sessions
like
interactive
sessions
and
the
rest
of
the
sessions
are
on
the
agenda.
So
you
can
look
at
the
agenda
here
and
talk
to
you
on
wednesday
and
thursday.