►
From YouTube: CDF SIG Interoperability Meeting 2020-05-14
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).
A
A
A
So
I
gender
looks
similar
to
the
last
one
and
I
added
an
additional
topic
to
the
agenda.
The
co-chair,
the
additional
topic
which
we
need
to
have
a
quick
conversation
around
and
then
it's
perhaps
be
good
to
have
a
recap
of
the
update
we
provide
to
talk
last
week,
and
maybe
it
is
better
Tracy
or
others
who
were
in
that
meeting
to
share
the
response
from
talk
rather
than
me
saying.
Oh,
it
was
great.
A
I
mean
to
again
give
total
mystery
and
the
topic
you
want
to
propose
doesn't
I'd
like
more
than
few
minutes.
We
can
take
it
before
Christy's
presentation,
otherwise
we
can
take
the
topic
during
the
upcoming
meeting.
So,
let's
see
I
think
we
can
start.
We
have
11
people
in
the
meeting.
I,
don't
remember
any
action
point
from
the
previous
meeting.
Let
me
check
I
think
the
only
action
point
was
on
Stefan
to
upload
the
slice
to
store
the
slice
on
CDF
presentation
repository,
which
happened
already.
A
So
we
can
skip
action
point
you
will
ex-knight
Emil
and
move
to
the
next
topic,
which
is
a
topic
we
discussed
before
few
weeks
ago
and
agreed
to
adapt
co-chair
set
up
for
the
seek
and
Christie
is
with
us
today.
Maybe
Christie.
You
want
to
talk
about
the
situation
with
your
workload
and
then
the
content
from
there
sure.
C
So
I
think,
can
everyone
hear
me
first
of
all,
I'm
using
the
web
interface
with
zoom
and
I?
Don't
trust
it
I,
don't
know:
okay,
okay,
yeah,
so
I
was
excited
to
be
the
co-chair
for
the
stig
and
just
looking
at
my
schedule
and
I.
Just
don't
think
I
can
devote
enough
time
to
this
to
continue
to
be
the
co-chair.
C
So,
basically,
if
anyone
else
is
interested
in
taking
my
position,
I
would
really
appreciate
that
I'm
hoping
that
folks
on
my
team
will
continue
to
participate
and
I
want
to
set
up
a
rotation
with
my
team
to
make
sure
that
someone
from
someone
from
Tecton
is
always
attending,
because
we're
really
interested
in
the
sig
but
yeah
I
have
to
I
have
to
step
away
from
the
position.
Unfortunately,.
A
A
Okay,
so
let's
move
I
will
send
a
mail
on
the
main
list
and
describe
what
we
discussed
right
now.
What
I
was
talking
about
last
few
minutes
and
then
I
see
what
happens
on
my
list.
So
the
next
topic
is
sig
update
to
talk.
So
this
presentation,
which
was
which
has
been
here
since
the
previous
meeting
and
we
presented
or
I
present
this
to
tech,
Oversight
Committee
ring
last
week
and
before
I,
say
what
I
think
I
think
Traci
you
were
there.
What
do
you
think
the
response
of
talk
to
say
it.
A
It's
always
great
to
get
feedback
from
people
a
bit
outside
of
what
we
are
doing
or
what
we
have
been
talking
about,
or
what
we
are
working
with
and
I
think
we
should
continue
providing
regular
updates
talk,
maybe
quarterly
updates
or
every
few
weeks,
and
it
could
perhaps
make
it
even
better
if
next
time
someone
else
can
take
this
and
price
the
update
by
looking
at
from
different
perspective.
So
we
can
also
talk
to
talk
and
see.
Who
is
there
and
what
kind
of
questions
they
ask
and
what
are
they
interested?
A
B
It's
very
quickly
think
if
folks
did
not
see
the
interoperability
newsletter
that
went
out
of
link
to
the
archive
there,
but
do
check
it
out
some
really
great
articles,
including
our
CI
CD
rosetta
stone,
and
how
we're
working
towards
establishing
a
shared
vocabulary,
and
also
yesterday
we
had
a
CDF
members
meeting
and
I
had
a
couple
of
slides
on
the
interoperability
group.
So
if
well,
if
anyone
is
joining
off
the
back
of
that,
welcome
to
your
first
interoperability
sig,
but
yeah
and
I
think
just
nice
to
keep
spreading
the
word
and
every
time
we
do.
B
A
Okay,
thanks
Tracy,
so
moving
to
the
next
topic.
I
think
the
road
map
is
one
of
the
important
things
we
need
to
have
some
kind
of
settlement,
because
Tracy
starts
the
road
map
work
few
weeks
ago,
maybe
a
month
or
two
ago,
and
there
are
already
things
which
you
can
start
or
we
can
talk
about
and
agree
on
and
perhaps
start
working
with
them.
So
let
me
open
the
road
map
document
and
you
can
see
the
document
right
now.
Yeah.
B
A
A
First
parts
like
all-wheel
charter
and
outcomes,
I
think
they've
been
same
as
they
were
before,
so
there
is
no
update
there
and
time
horizons.
That
is
I
think
it's
good
way
to
take
the
roadmap
and
the
first
item,
which
is
what
we
have
been
doing
class
three
weeks:
knowledge
transfer
of
CI
CD
two,
so
we
have
presentations
from
different
projects
and
end-users
and
I
think
this
person
I
think
we
have
good
idea
about
what
the
different
projects
offer,
what
kind
of
capabilities
they
have,
what
they
are
working
with,
and
we
will
continue
having
these
presentations.
A
Obviously,
but
looking
at
what
we
did
last
few
weeks
make
me
realize.
Maybe
it
is
time
to
identify
a
few
focus
areas
based
on
what
we
heard
from
projects
and
users
and
I
put
some
of
the
examples
there
and
then
some
like
some
example
use
cases
followed
by
some
areas
that
were
discussed
during
our
previous
meetings
and.
A
So
I'm
I'm
just
going
to
stop
right
now
and
give
people
to
look
at
those
areas
and
the
proposal
to
see
if
it
makes
sense,
and
then
we
can
perhaps
start
a
conversation
on
mail
lists
and
I
get
another
discussion
to
see.
If
the
way
that
proposed
on
the
document
make
sense
or
not-
and
I
expressed
explicitly
put
that
before
standardized
frameworks,
because
it's
it
feels
like
it
would
be
better
to
have
a
bit
more
structure
around
what
we
are
working
with
before
we
start
talking
about.
A
A
He
was
talking
about
some
kind
of
standardization
across
pipeline
languages
or
migration
from
one
tool
to
other
and
how
to
make
it
easier
for
the
users,
and
that
made
me
think
and
put
as
an
area
to
focus
on
seeing
that
we
have
people
interested
in
it
and
the
second
area
is
event
driven
approach.
The
CI
CD
and
the
examples
are
Tecton
captain
and
Eiffel.
D
D
I'm
so
sad
that
James
just
stepped
away,
because
one
of
the
things
you
know
I
have
been
talking
about
is
it
would
be
nice
to
do,
and
this
may
fit
into
the
format
you're
suggesting
it
would
be
nice
to
do,
and
we
were
thinking
a
month.
I
get
together
where
we
talked
about
certain
elements
that
the
different
CI
CD
tools
have
in
common
and
the
way
that
we're
thinking
of
grouping
them
was
just
run
either
common
components
or
common
issues,
they're
dealing
with
like
web
hooks
or
whatever,
but
I
actually
think.
A
I
think
what
you
just
mentioned,
like
like
web
hooks,
that
could
be
another
area
to
focus
and
the
following
paragraph
actually
proposes
how
we
could
work
with
it's
like
if
we
assume,
like
we
agree
on
these
four
areas.
Like
stammers
the
Python
standardization
languages,
you
went
through
an
approach,
integration
with
other
tools
and
that
hooks,
for
example,
one
approach.
This
could
be
to
create
like
work
streams
on
these
different
areas.
A
Don't
have
to
solve
the
problem.
It
could
be
just
like
collecting
the
state
of
things
in
a
specific
area
of
different
projects
or
firm
users,
and
just
recommending
that
and
say
this
is
what
is
happening
in
this
specific
area,
and
this
is
what
we
are
seeing
hearing
from
our
users
to
attract
more
interest
or
some
work.
Streams
called
go
even
further
and
propose
solutions
for
some
of
the
problems.
B
Yeah
I
I,
agree:
I'd
love
to
see
us
start
tackling
some
of
the
nitty-gritty
of
this
and
working
to
actually
solving
some
of
these
challenges.
I'd
love
to
actually
get
some
input.
Raman,
if
you
don't
mind
me
putting
you
on
the
spot
from
another
end-user
perspective,
what's
what's
kind
of
one
of
the
most
valuable
things
we
can
do
as
a
community
here.
E
E
Need
to
and
spend
a
little
more
time,
looking
at
exactly
what's
what's
required
and
so
give
me
give
me
a
little
more
chance
to
take
a
look
at
that
and
I
can
I
can
provide
some
input
for
you
for
you
guys
next
time,
perhaps
yeah.
B
I
think
just
what
kind
of
problems
that
we
could
solve,
what
I
guess,
they're
just
helping
us
prioritize,
which
areas
you
think
you
know,
are
already
kind
of
done
and
dusted
and
not
likely
to
change
and
which
ones
are
kind
of
evolving,
so
perhaps
makes
more
sense.
So
any
direction
on
that
would
be
useful
sure,
yeah.
E
The
big,
the
biggest
area
that
we
here
at
eBay
are
are
I,
don't
want
to
say
struggling
with,
but
just
having
challenges
with
all
the
time
is
is
the
is
the
area
of
quality
assurance.
If
you
will
in
in
pipelines
in
computers
to
read
pipelines
and
attestation
and
object
constraints
and
things
of
that
sort,
you
know
that
does
it
package.
E
E
How
do
you
define
those
quality
standards
and
how
do
you
enforce
them?
These
are
the
things
that
were
having
to
constantly
deal
with
and
in
fact,
I'm
as
a
part
of
tectonic
wipe
lines.
We
have
come
up
with
a
way
of
dealing
with
all
of
that,
and
that's
that
that
is
the
part
I'm
working
on
it
and
the
part
that
wasn't
really
fully
baked.
B
E
I
may
I
may
just
put
myself
on
the
schedule
for
just
to
give
you
the
presentation,
but
I
I'm
I'm,
very
much
show
me
what
you
can
do
kind
of
person.
You
know
with
demos
with
live
demos.
That's
just
that's
just
me!
That's
why
I
wanted
to
give
you
that,
but
I
may
just
give
you
the
presentation
first
and
then
do
the
demo
for
you
later.
A
A
C
This
working
can
people
see
slides,
yeah,
okay,
great
all
right.
So
thanks
for
having
us
I
broke
Vincent
into
joining
me
to
talk
about
this
we've
been
both
of
us
have
been
very
excited
to
be
focusing
recently
on
two
parts
of
Tecton
that
haven't
gotten
a
lot
of
attention
in
the
past
and
one
that's
cool,
one
of
which
is
completely
brand
new,
which
are
the
hub
and
the
catalog.
So
I
like
to
talk
about
those
today,
I,
don't
think
it's
gonna
be
a
super.
C
Long
presentation
should
have
lots
of
time
for
questions
as
a
reminder
if
you're
not
familiar
with
Tecton
and
what
our
goals
are.
Pectins
mission
is
to
be
the
industry
standard
cloud
native,
see,
ICD
platform,
components
and
ecosystem,
which
is
a
bit
of
a
mouthful
and
still
kind
of
grammatically
incorrect,
but
generally
it
is
what
we
want,
and
so
the
catalog
and
hub
portion
that
I'm
going
to
talk
about
today
is
all
about
the
ecosystem
piece
of
venison.
C
It's
all
about
the
Tecton
ecosystem,
so
I'm
going
to
start
by
talking
a
little
bit
about
tech,
Tom's,
reusability
model,
so
basically
how
how
tasks,
work
and
kind
of
how
the
catalog
fits
into
that.
So
for
our
examples,
let's,
let's
pretend
that
we
have
kind
of
two
general
groups
of
people.
We
have
a
release:
engineering
team
who
is
responsible
at
a
company
for
how
software
is
delivered
in
deployed,
and
we
have
an
application
development
team
who
is
creating
that
software?
That's
not
to
say
that
this
is
how
how
every
team
and
company
has
to
organize.
C
But
let's
just
say
that
we
we're
talking
about
a
company
that
has
these
two
groups,
so
you
could
imagine
that
maybe
at
this
company
there's
a
release,
engineering
team
there
supporting
many
application
development
teams,
every
application,
development
team
is
rating,
multiple
services
and
the
release
engineering
team
has
has
some
requirements
around
the
pipeline
that
they
want.
They
want
these
application
developers
to
be
using
to
deliver
each
of
these
three
services.
They
want
basically
the
same
pipeline
to
be
used.
C
They
don't
want
the
application
delivery
team
to
be
reinventing
the
wheel
for
every
piece
of
that
pipeline
and
they
have
some
mandatory
steps
they
want
to
include,
but
they
want
to
make
sure
if
we're
building
an
image
that
owner
ability
scanning
is
done
for
it.
So
looking
at
the
pipeline
that
they
might
define,
they
want
all
the
teams
to
be
using
the
same
pipeline,
they
want
to
insert
mandatory
pieces
into
it.
C
C
You
can
take
tasks
and
assemble
them
into
pipelines.
So
the
idea
behind
the
Tecton
catalog
is
that
this
is
a
place
where
people
can
publish
tasks
that
can
be
reused
across
many
pipelines.
At
the
moment.
We're
focusing
on
tasks
in
the
future
I
think
that
instance
is
going
to
mention
this
a
bit,
but
we're
hoping
to
expand
into
more
reusable
pieces,
for
example,
pipelines
and
maybe
parts
of
Tecton
triggers
as
well
at
the
moment
we're
focusing
mostly
on
tasks.
C
C
It's
called
go
test
when
you
look
at
what
it
actually
does
it's
using
a
Goulding
image
and
it's
doing
what
it
says
it
does
it's
running,
go
tests
and
then,
if
and
then
to
actually
use
this
you'd
be
applying
it
to
your
kubernetes
cluster
and
in
this
example,
we're
using
the
Tecton
CLI
tkn
to
start.
Let's
start
that
task
running
and
stream,
the
logs
and
I
want
to
talk
just
a
little
bit
about
how
we
make
this
reusable.
C
C
We
also
have
the
concept
of
outputs
or
results
from
tasks.
So
in
this
example,
we
have
a
task
that
runs
Kanak
o
if
you're
not
familiar
with
Kanna
KO,
it's
a
tool
for
building
and
pushing
images.
So
here
you
could
imagine
that
this
task
as
a
result
called
image
which
is
basically
just
a
string,
but
that
string
could
contain
the
exact
URL
and
digest
of
the
image
that
was
just
built.
C
So
if
we
wanted
to
put
these
pieces
together
into
a
pipeline,
for
example,
in
this
pipeline,
we
have
the
first
task
that
runs
is
refering
is
referencing
that
Kanaka
task
that
we
were
just
looking
at,
which
has
an
image
result,
and
you
can
have
other
tasks
in
the
pipeline.
Take
the
results
from
that
task
and
use
it.
C
So
we
can
build
the
image
using
the
Kanna
co
task
that
we
maybe
took
from
the
catalog,
and
then
we
can
use
another
task,
ideally
also
from
the
catalog,
to
deploy
it
and
link
the
result
from
the
can
ago,
tasks
to
a
parameter,
that's
in
the
deployment
task
and
something
else
that
we're
working
on
right
now.
This
is
in
progress,
but
it's
pretty
exciting.
Is
that
we're
looking
at
how
to
fund
little
tasks
into
OCI
images,
and
the
idea
is
that
we
can
then
actually
store
these
tasks
in
image?
C
So
in
this
example,
this
is
maybe
a
catalog,
that's
specific
to
this
individual
company,
but
we
also
are
going
to
have
an
official
tech
time.
Catalog,
that's
part
of
the
Tecton
Oregon
maintained
by
the
people
contributing
to
Tecton,
so
the
catalog
that
we
have
right
now
is
in
the
Tecton
github
or
gets
called
catalog.
This
is
a
list
of
the
tasks
that
have
been
contributed
to
it
so
far.
C
So
if
you
are
interested
in
contributing
a
task,
that
would
be
great
also,
these
are
all
the
ones
that
are
available
that
you
can
start
using
in
your
pipelines
today
for
2020
some
things
that
we're
hoping
to
do
or
want
to
add
the
component
versioning.
That
I
was
discussing
yeah
the
OCI
image
registry,
so
that
we
can
actually
publish
these
tasks
to
an
SDI
image
registry,
and
then
you
can
just
retrieve
them.
We
want
to
make
it
so
that
you
can
indicate
what
versions
of
techsan
pipelines
your
cat.
Your
tasks
are
compatible
with
we're.
C
Also
looking
at
increasing
our
integration
testing
so
that
you
can.
You
can
feel
very
confident
when
you're,
using
something
that's
in
the
catalog
that
it's
actually
going
to
work
as
advertised
and
we're
using
dogfooding
to
do
that
so
using
base
leasing,
tech
time
to
test
the
Tecton
catalog
tasks,
we're
also
expanding
this
into
multiple
tiers.
At
the
moment,
the
proposal
is
that
we
would
have
three
tiers
of
tasks,
basically
we're
trying
to
meet
the
requirements
of
making
it.
C
So
you
can
have
really
well
tested
truck
tasks
that
you
can
trust
with
official
being
the
most
trustworthy,
because
they're
maintained
by
the
Tecton
community
and
then
having
just
kind
of
community
tasks
which
are
sort
of
like
people
can
kind
of
add
them
as
much
as
they
want.
But
they
don't
have
to
necessarily
provide
rigorous
tests
for
those
and
we're
also
adding
the
hub,
which
I
will
pass
it
over
to
Vincent
to
talk
about
and
I
guess.
You
could
just
tell
me
when
to
go
to
the
next
slide,
because
I'm
yeah
I'm,
sharing.
G
G
F
Community
tasks
for
them
to
create
pipeline
and
and
Astrix
there
is
because
right
now
it's
just
tasks
that
are
on
Kellogg,
and
this
is
just
task
that
would
show
on
the
hub.
But
the
long-term
goal
is
anything
that
any
resource
made,
because
that
can
be
reused.
So
some
of
the
pipelines,
some
other
objects
under
the
tectonic
components,
could
also
be
on
the
hub
next
one
and
so
right
now.
F
This
is
how
it
looks
we
can
show
it
live
if
you
want
I,
have
it
deployed
somewhere,
but
overall,
this
is
kind
of
made
on
the
same
model
of
lots
of
other
help.
Docker
have
been
stuff
where
you
would
be
able
to
search
for
those
see
quickly.
What
are
the
type
of
tasks?
What
what
are
the
tears?
So
as
here
it's
just
official
task,
because
this
is
based
on
the
official
catalog
repo,
which
contains
only
official
tasks
and
so
on.
F
The
road
map
which
you
can
go
to
the
next
slide
under
robot,
there's
at
least
making
sure
we
publish
this
because
right
now,
it's
it's
a
work
in
progress
and
it's
not
published
anywhere.
But
it's
publishing
its
unhappy
attic
on
the
bed
most
most
likely
making
sure
we
support
multiple
catalogs.
So
right
now
we
are
placing
everything
on
top
of
Tecton
city
corral,
but
we
want
to
make
sure
other
companies,
the
vendors
and
other
community-
can
have
their
own
piece
of
catalog.
F
F
Specific
catalogues
and
third
item,
which
is
also
really
important,
is
integration.
We
want
to
make
sure
that
the
help
as
a
very
good
API
so
that
people
can
use
the
API
to
search
for
it
to
get
the
correct
and
correct
images
or
the
code
metadata
so
that
they
can
use
it
inside
there
too.
The
first
integration
we
are
thinking
about
is
using
is
inside
the
components
of
technology
also
can
for
the
CI,
but
our
board
and
others,
but
it
could
be
for
anything
really
and
yeah.
C
So
if
you
are
watching
this
and
you
work
on
a
CI
CD
system,
please
consider
supporting
the
Tecton
catalog.
That
would
be
super
amazing.
Also,
if
you're
interested,
we
have
a
working
group.
That's
actually,
starting
later
today,
we're
going
to
have
our
first
meeting
to
talk
about
the
hub
and
the
catalog.
So
I
put
a
link
in
here
and
I'll
share
these
slides,
but
you
can
find
in
the
tech
community
repo
you
can
find
all
of
our
working
groups,
completing
a
catalog
and
hub
working
group
and
then
maybe
I'll.
C
Just
a
very
last
thing:
I'm
gonna,
open
and
open
the
stating
this
aging
hug
I
assume
it
okay
to
go
to
that
cuz
in
submission
showing
it
something
go
to
stop
me
if
it's
not
okay.
Here
we
go
yeah.
So
this
is
the
hub
and
I
particularly
love
this
cat
logo.
For
our
official
official
tier
tasks
they
cool,
you
can
go
in
and
see
dogs
and
eventually
is
install
and
rate
them
and
a
lot
of
versions,
cool
yeah.
So
does
anybody
have
any
questions.
G
F
C
Think
that
there's
a
we're
in
the
process
of
adding
adding
all
of
the
code
to
the
I
don't
actually
know
what
state
that's
in,
but
like
I
think
because
there
was
a
proof
of
concept
of
a
hub
which
is
what
you're
seeing
there
and
then
we're
migrating
code
over
into
this
hub.
We
don't
know
and
then
I
think
the
goal
is
yeah.
F
I
forgot
to
add
the
context
there.
The
beauty
was
developed
inside
Reddit
and
learning
process
of
my
ring,
the
code
from
our
reddit,
the
repo
living
there
to
this
one,
and
we
have
we're
also
refactoring
some
stuff
because
it
was
a
POC.
So,
as
Opio
see,
there's
some
really
bad
code.
There,
that's
yeah,
it's
in
the
process
of
mumbling
migrating.
The
coding
inside
the
technology
have
projects
and.
C
B
Yeah
and
I
was
just
gonna
say,
looks,
looks
really
good
you're
happy
too
I
know.
We've
got
similar
kind
of
concepts
with
the
the
whole
Jenkins
plug
in
infrastructure.
So
it's
nice
to
see
kind
of
you're
thinking
through
the
the
tiers
and
things
like
that.
So
it
always
happy
to
I'll
poke
around
a
bit
more
and
anything
think
I'll,
let
you
know
but
yeah.
It
looks
really
good.
C
B
I
seem
to
recall
having
lots
of
conversations
with
folks
around.
Like
marketplace
governance.
You
know
Gareth
rush
Grove
talking
about
the
you
know
the
model
of.
What's
the
onus
on
like
who
looks
after
things,
who's
gonna
come
back
and
apply
the
security
patch
after
a
year
of
things
sitting
around
and
think
so.
Yeah
be
interesting
to
see
which
way
you're
leaning
in
terms
of
is
it
heavily
community,
managed
and
operated,
or
do
we
differ
a
lot
to
the
catalog
providers,
the
people
creating
the
tasks
and
pipelines.
C
Yeah,
that's
a
really
good
point,
I.
Think
I.
Think
our
current
thinking
is
that
for
the
official
tier
it
would
be.
The
tech
town
community
would
definitely
be
responsible
for
applying
security
patches
and
keeping
things
up-to-date
and
dealing
with
any
bugs
that
come
up
the
on
the
other
extreme.
The
community
side
I
think
that
the
assurances
would
be
significantly
less
if
possibly
none
at
all
and
then
in
the
middle.
C
We
have
this
verified
concept,
which
we're
kind
of
still
trying
to
figure
out,
but
what
we
would
like
is
to
make
it
possible
for
people
to
contribute
things
from
the
community
but
then
provide
via
some
interface
that
we
haven't
quite
figured
out
yet,
but
basically
like
provides
sort
of
evidence
or
assurances
that
you
have
been
applied
security
patches
and
then
you
have
been
running
tests
regularly
and
maybe
like
the
status
of
the
last
test
that
ran
and
that
kind
of
thing,
but
we're
still
definitely
still
here.
You
know.
C
A
D
A
A
And
if
you
click
the
cig,
interoperability
playlist,
you
will
see
all
the
meetings
except
the
very
first
one
why
I
am
talking
about
this
is
because
we
had
presentations
from
many
during
our
previous
meetings
and
you
may
want
to
go
back
and
look
at
what
we
discussed
there
and
what
for
the
questions
or
what
was
that
pasted
from
projects
for
users?
It's
great
to
have
those
meetings
there
so
just
browse
through
and
see?
If
you
missed
anything-
and
that
was
the
last
thing
on
the
agenda,
anyone
wants
to
wind
up
lost
me
topic.