►
From YouTube: CDF SIG Interoperability Meeting - 2020-10-15
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).
C
Yeah,
oh
oliver,
I
meant
to
I'll
drop
you
an
email.
Just
I
was
going
to
invite
you
along
to
the
end
user
council.
We
have
on
november
19th.
C
So
I
think
I'll,
I'm
I'll
drop
you
an
email
to
invite
you
to
the
end
user
council
meeting
we're
gonna
have
in
november,
but
I
think
yeah
there's
a
good
group
gathering
there
just
to
talk
about
developer
experience
and
productivity
and
other
factors
for
for
the
internal
kind
of
ci,
cd
setup.
Okay
and
yeah
just
feel
free
to
forward
it
to
to
anyone
else
at
slp
who
wants
to
to
come
along
yeah.
D
I've
had
meetings
since
seven
this
morning
and
I
didn't
get
up
until
6
50.
D
I'm
kind
of
looking
like
I
just
woke
up.
C
E
E
Talking
about
the
cdcon,
which
happened
last
week
and
then
the
white
paper
topics
two
of
them,
I
suppose
we
are
coming,
I'm
approaching
to
having
something
there
to
start
talking
about
setting
up
some
kind
of
time
plan,
and
then
I've
seen
few
updates
since
the
previous
meeting
captain
fox
added
some
a
case
study
from
one
of
the
companies
using
captain
and
I've
seen
erickson
case
study
there.
E
So
we
have
case
studies
which
is
good,
and
then
we
can
discuss
some
other
topics
if
anyone
has
any
thing
to
add,
but
before
we
start
with
ajanda,
maybe
oliver
you
joined
us
today,
so
you
want
to
introduce
yourself
if
any
of
us
missed
your
message
on
slack.
B
B
G
E
Welcome
oliver
thanks
for
joining
it's
great
to
have
you
with
us,
so
I
don't
know:
do
we
have
anyone
else
because
johannes
siva,
he
also
joined
during
tweet,
but
he
I
don't
see
him
in
the
meeting,
so
he
is
working
for
a
german
insurance
company
according
to
what
he
wrote
on
slack,
let's
see
whenever
he
joins,
we
ask
him
and
the
agenda.
E
The
first
topic
is
action
item
as
usual,
and
the
first
action
item
was
on
tracy
miranda
on
you
and
I've
seen
you
already
included
the
link
to
a
candy
document
for
the
birth
of
a
feather
session.
So
thanks
for
that,
you
can
close
that
item
and
the
next
action
item
was
on
christy
and
cameron
about
moving
the
current
the
work
from
the
white
paper.
The
definitions,
work
from
white
paper
interrupt
white
paper
to
see,
I
see,
definitions,
document
and
I've
seen
cameron
or
christie.
You
did
some
updates.
E
H
I
think
I
think
cameron
did
all
sorry.
I
think
cameron
did
all
the
hard
work
it
looks
like.
I
was
just
going
through
the
comments
to
make
sure
I
think
they're
all
looks
like
they're
all
moved
over,
so
I
think
that
we
could
safely
delete
the
section
in
the
interoperability
white
paper
and
just
put
linked,
there's
already
a
link
to
the
other
doc.
H
So
I
think
we
could
delete
the
I'm
even
going
to
hit
I'm
going
to
hit
the
delete
button
right
now,
if
nobody
objects,
because
I
think
everything's
been
moved
over
to
the
other
dock.
E
Yeah
but
but
we
agreed
during
the
meeting
like
a
month
ago
or
something
we
will
take,
the
definitions
from
the
document.
Tracy
reagan
shared
like
from
top
definitions
to
have
something
there,
and
while
you
work
on
the
definitions,
why
people?
If
something
comes
out
from
that
work,
then
we
kind
of
paste
those
things
and
refer
back
to
that
paper.
So
because
we
don't
know
who
may
see
this
white
paper,
they
may
need
some
kind
of
quick
intro
to
the
terms,
so
we
can
yeah.
We
can
delete
these
things
yeah.
E
H
From
the
other
documents
sounds
good,
any
objection
to
removing
the
continuous
integration
section.
I'm
thinking
that
maybe
in
this
section
we
could
just
because
it
starts
off
with
what
are
we
discussing
in
ci
cd.
So
maybe
if
we
just
had
a
sentence
or
two
that
just
kind
of
says
like
what
the
acronym
means,
but
then
we
define
and
then
we
put
in
the
definition
of
cd
and
we
don't
really
go
into
ci
and
we
don't
go
into
continuous
deployment.
Does
that
seem
fair.
E
E
One
of
your
both
of
you
said
like
ci,
is,
can
be
considered
as
one
important
factor
within
continuous
delivery.
So
we
can
again
do
it
like
that
here
and
put
an
acronym
and
explain
this
like
it's
part
of
continuous
delivery
in
order
for
you
to
have
need
to
have
like
content
stage
type
of
you
know
summary,
and
so
I
am
replacing
all
the
ci
cd
things
here
to
be
up
to
date
with
the
latest
terminology.
E
E
I
C
Up
from
the
definition
so
just
put
that
in
the
chat
and
so
something
tracy
reagan,
christie
and
I
synced
on
yesterday
and
then
so.
This
is
more
like
a
white
paper
that
trying
to
be
more
higher
level
and
more
convince
your
boss
or
sort
of
buy
into
why
this
is
important.
So
it's
a
very
quick
outline.
It's
looking
for
a
nice
title,
first
of
all,
but
it's
kind
of
focused
on
on
business
requirements
and
then
it's
got
a
section
on
okay.
C
What
is
continuous
delivery
and
we
want
to
cover
a
bit
of
the
history
of
how
we
got
to
where
we
are
go
through
some
benefits.
So
you
know
why
bother
so
that's
the
impact
and
talk
about
organizations
and
process
and
people,
and
I
think,
tie
that
in
with
a
lot
of
the
research
from
accelerate
and
then
going
into
the
continuous
delivery
practices.
C
So
this
is
a
bad
mock-up
of
trying
to
say,
okay,
here
all
the
things
that
make
up
continuous
delivery-
and
that
includes
you
know,
version
control
and
continuous
integration
and
automated
deployment
and
test
automation
and
security.
So
it's
all
these
practices
coming
together
and
then
connecting
that
to
the
landscape
instead
of
saying,
okay.
C
Well,
when
it
comes
to
automating
these
things,
here's
how
these
different
categories
of
tools
connect
and
then
we
wanted
to
just
have
some
kind
of
case
studies
of
folks
who
have
become
more
agile
or
better,
have
better
teams
with
continuous
delivery.
C
And
then
just
finish
with
you
know:
what's
the
continuous
delivery
foundation
doing
to
help
move
this
conversation
forward
so
yep
any
feedback
on
this
outline
christie's
already
gone
and
put
a
whole
bunch
of
really
good
points
on
fleshing
out
what
the
practices
are,
and
you
know
how
we
should
separate
them
and
what
we
should
talk
about.
E
C
C
E
E
C
E
Okay,
so
this
is
great
and
then
this
because
there
are
like
people,
are
ending
up
on
this
document
and
there
are
lots
of
conversations
here,
so
this
will
continue
on
this
document.
C
E
C
Yeah,
I
think
at
city
corner
was
pretty
obvious.
There's
lots
of
folks
coming
in
who
want
a
starting
point
and
first
they
want
to
know
what
it's
all
about,
and
then
I
think
the
next
thing
is.
They
want
to
know
why
everything's
different
with
cloud
native-
and
I
don't
think,
we've
done
a
good
job,
spelling
that
out
for
folks
who
want,
in
it
day
in
day
out.
C
Yeah,
I
can
give
a
high
level,
but
I'd
love
to
hear
from
folks
and
the
different
buffs,
but
just
as
a
high
level
yeah,
I
think
we're
pretty
happy
just
having
our
first
event
online.
We
felt
the
community
really
came
together.
People
seem
to
love
the
the
interactive
sessions.
The
most
those
were
some
of
the
most
popular
ones.
I
think
they
can
take
spot
did
really
well.
C
Some
of
the
the
tacton
talks
were,
I
think,
andrea
fracholi's
on
cloud
native
pipelines
was
the
best
performing
talk.
We
had
some
glitches
with
the
platform,
but
I
think
overall,
pretty
happy
and
it
kind
of
went
well,
people
loved,
the
selfie,
booth
and
yeah.
I
thought
it
was.
It
was
good
and
I'd
love
to
hear
other
folks
experiences
and
how
they
found
it
for
meeting
folks
and
engaging
and
having
good
conversations.
J
Basically,
just
the
question:
how
many
participants
were
there
on
the
on
the
summit
for
the
yeah.
C
So
we
had
a
total
registration
of
1
354
and
we
had
about
70
of
those
checked
into
the
platform
about
900
folks
access
the
platform.
So
we're
pretty
pleased
with
that.
I
think
we
were
looking
for
a
thousand
registrations
and
fifty
percent
of
those
two
to
get
involved.
So
we're
happy
with
with
those
numbers.
C
Yeah
we
had
about
200
on
the
first
day
and
about
115
on
the
second
day,
it's
good
and
77
selfies
in
case
you
want
it.
A
C
E
And
are
the
recordings
and
like
they
when
they
will
become
available
on
youtube.
C
Latest
22nd,
but
we'll
probably
start
to
see
some
this
week
and
just
to
note-
and
this
we
did
opt
not
to
record
the
both
sessions.
So
we
don't
have
recordings
of
those.
It
was
a
well.
There
was
a
trade-off
we
had
to
make
in
number
of
attendees
versus
recording
and
we
kind
of
said.
Let's
just
make
sure
people
can
participate,
so
we
will
won't
have
off
recordings.
It
was
kind
of
you
had
to
be
there
type
thing,
but
just
for
awareness
we
have
all.
The
talks
will
be
posted.
C
G
Better,
I
thought
I
enjoyed
it
doing
the
the
jenkins
x,
one,
I'm
not
sure
we
were
too
prepared
for
it,
but
I
think
that
probably
worked
in
our
favor
slightly.
So
lots
of
people
got
involved
lots
of
questions
like
countless
questions.
I
think
it
was
quite
good.
G
We
figured
out
about
halfway
through
it's
quite
good
for
some,
if
you're
not
talking
to
try
and
keep
an
eye
on
the
chat
and
then
and
then
just
kind
of
then
re
reply,
rather
than
replying
in
the
chat
replying
the
thing,
but
it's
quite
interactive
for
the
record
I
didn't
realize
when
I
first
joined
I'd
actually
didn't
realize
other
people
were
there.
I
thought
it
was
just
three
people,
so
I
was
talking
about
beer
and
drinking
in
london
and
I
realized
there's
like
50
people
there.
G
So
I
think
there
was
just
a
bit
of
a
learning
thing,
but
that's
more
of
a
personal
stupidity
more
than
anything
else
yeah,
but
I
thought
it
was
really
good.
I
thought
I
thought
it
was
great
to
get
involved
and
unfortunately
I
didn't
get
to
attend
any
of
the
other
sessions,
but
I'm
playing
catch
up
on
those.
It's
good
that
we
can
watch
those.
K
I
I
loved
it
too.
I
I
was
wondering
if
the
next
time
we
do
something
like
that
we
could
have
a
a
more
generic
buff,
because
I
think
there's
a
lot
of
things
we
could
talk
about.
That's
you
know
it's
not
necessarily
jenkins
or
jenkins,
x
or
tekton,
or
even
spinnaker.
It's
kind
of
there's
meta
stuff.
Like
you
know,
how
do
you
do
versioning,
and
how
do
you
integrate
your
issue
tracker
with
your
chat
up
so
get
up
somewhere,
so
it
might
be
nice
to
see.
K
I
have
a
forum
to
discuss
things
which
are
in
many
ways
things
like
jackie's,
eggs
and
text
on
the
low
level
ish.
It
might
be
nice
to
have
a
a
buff.
That's
for
kind
of
practitioners
just
to
debate.
You
know,
what's
your
biggest
problem
in
cicdm,
what
are
the
biggest
challenges?
You
think
there
are
seven,
because
we've
got
some
amazing
feedback
in
jenkins
x.
K
C
J
I
J
And
many
new
faces
or
new
people
showed
up
there,
that
we
haven't
seen
before,
I'm
not
sure
if
anyone
on
this
meeting
now
came
from
that
path,
but
anyway
we
got
some
new
contacts
there
and
I
I
believe
that
was
quite
successful.
Actually,
it
was
interesting
to
see
other
people
interesting
in
this
as
well.
I
wanted
to
come
to
that,
but
it
clashed
with
the
jenkins
section.
I
know
I
know
so.
Actually
that's
one
of
the
points.
Let's.
C
D
Yeah
there
was
some
work
we
could
have
done
on
the
calendar
I
had.
I
was.
I
had
two
presentations
at
the
same
time,
so
I
told
everybody
I'd
set
my
replication
set
to
two,
but
on
that
that
topic
as
well.
Another
thing
we
didn't
really
leverage
like
we
should
have-
and
these
are
all
you
know
lessons
learned-
is
we
could
have
had
more
chat
rooms.
We
should
have
had
like
an
ask
the
expert
chat
room.
D
We
could
have
a
speaker
chat
room.
We
could
have
had
like
a
you
know,
a
general
forum
chat
room,
and
so
I
think,
if
we
use
hop
in
the
next
time,
the
use
of
the
chat
rooms
can
be
kind
of
leverage
that
kind
of
discussion.
D
I
know
at
devops
world.
There
was
a
lot
of
stuff
being
talked
about
in
one
of
the
one
of
the
ask.
The
experts
chat
rooms.
J
J
D
And
you
have
a
you:
can
watch
the
threads
just
like
you
would
on
slack
or
something.
K
I
D
I
agree
I
thought
about.
I
wonder
if
there
was
ways
that
we
could
just
interface
or
integrate
somehow
a
slack
channel
into
the
chat
room
because
then
it
could,
it
could
live
on.
So
we
would
have
a
in
our
existing
chat
slack.
We
could
have
a
cd
con,
you
know
area
and
then
have
have
stuff
under
that.
D
Slack
some
way
would
be
a
very
interesting
thing
for,
for
the
hip,
the
hop-in
or
whatever
it's
called
people
to
do.
C
Oh
yeah,
let's
ask
for
that
yeah,
I
think
the
kubecon
folks
they
do.
They
promote
having
all
the
discussions
in
slack,
so
they'll
have
the
videos
and
then
they
discourage
people
from
chatting
in
the
conference
and
they
try
to
funnel
them
to
to
channels.
I
guess
we
could
have
done
that
as
a
way
to
hold
on
to
people
interested
in
the
conversations
and
have
them
stick
around
long
term
or
just
stay
engaged
with
the
discussion.
J
C
Yeah,
so
on
the
the
james
shark,
you
brought
up
the
the
topics.
Do
you
think
it
would
work?
Well
as
like
we'd
have
a
a
general
hey,
let's
just
discuss
any
issues
or
do
you
think
it
would
be
better
to
kind
of
say:
okay,
now
we're
discussing
version
control
now
we're
discussing
configuration
management
now
we're
discussing
security.
K
A
good
question
I
I
guess
I
was
wondering
almost
like
a
user
forum
or
something
like
that,
where
anybody
who's
doing
ci
cd
could
just
bring
up
things,
they
think
get
interesting,
get
they
feel
pain
points
because
I'm
not
sure
how
many
people
would
say.
Hey.
Let's
I
mean
I
know
a
lot
of
people,
love
security,
but
I'm
not
sure
I'd
want
to
sit
through
an
hour
of
just
security,
for
example.
Okay,
I
don't
wish.
K
Security,
I
think,
like
a
user
forum
thing
where
it's
not
necessarily
interrupted,
it's
not
necessarily
a
specifics.
The
icd
tech,
it's
more,
you
know,
bring
your
user
stories
to
the
forum
and
we
could
maybe
have
some
kind
of
content
to
give
people
a
clue
as
to
what
we
might
talk
about
like.
What's
your
big
success,
what's
your
biggest
issue
problem
or
whatever
you
know,
what?
K
What
are
you
really
missing
from
the
technology
and
ux
perspective,
or
something
like
that
just
to
get
people
chatting
about
you
know
kind
of
fellow
users
talking
to
each
other
yeah,
which
I
think
is
always.
C
So,
oh
actually,
that's
gonna!
I'm
gonna
segue
just
into
I'm
going
to
stick
a
link
to
the
there's,
an
end
user
console
that
we
are.
C
Yeah,
I
just
I
just
put
it
in
the
chats
if
you
want
to
link
to
that
so
there's
one
of
the
keynotes,
which
was
john
mark
of
capital,
one
having
the
discussion
with
art,
butler
and
jasmine
blanton,
both
in
financial
services
and
that's
something
we
we
kind
of
want
to
do
at
cdf
with
folks
who
are
end
users
so
have
topic
based
like
how
do
you
improve
your
developer
productivity?
C
What's
the
developer
experience,
how
are
you
measuring
success
and
just
have
folks
come
together
and
just
have
those
conversations
in
you
know
just
in
an
open
way,
sharing
what
they're
able
to
share
and
talking
about
pain
points,
so
that
might
be
kind
of
one
angle,
but
I
think
we
wanted
to
start
with
the
meeting
and
then
work
out
what
kind
of
forum
to
move
that
into
is.
Is
that
discourse
or
slack
or
where
can
these
questions
live
long
term?
C
So
people
can
know
where
to
go
to
to
just
ask
for
those
but
yeah
I'll
reach
out
to
folks
here
to
just
get
invite
you
to
that
those
who
can
attend
and
yeah.
I
think
that
would
be
really
nice.
E
C
Just
to
finish,
we
will
we
have
started
planning
for
the
next
one,
so
that
will
be
june
big
cd
con.
C
It
is
going
to
be
virtual,
probably
use
hopping
again,
but
the
big
questions
we're
asking
now
are
just
do
we
want
to
have
a
distinct
north
america
and
emea,
european
wider
area,
so
two
different
time
zone
versions,
and
then
the
other
thing
is
we're
thinking
about
having
a
day
before
the
conference
to
be
more
contributor
summit
for
each
project,
so
they
can
have
a
very
focused
chance
to
welcome
new
people,
get
them
committing
and
get
them
kind
of
onboarded
into
the
project.
K
E
J
Oh,
it
was
me
emil.
Okay,
hear
me
yeah!
No,
I
was
just
saying
that
in
our
birth
in
interpretability,
for
I
believe
we
had
also
some
people
from
asia
joining
and
obviously
it
was
very,
very
late
for
them
at
the
time
of
the
buff
and,
as
you
said,
if
we
would
have
different
time
zones
that
would
of
course
benefit
other
people
from
around
the
globe
to
come
as
well,
not
just.
I
J
J
F
Yeah
I
mean
I
was
that
same
day.
I
was
also
flipping
back
and
forth
because
I
was
presenting
in
the
sumo
logic
conference
and
I
was
expected
to
be
there
at
12,
45
pm
mountain
time
and
9
45
pm
mountain
time,
because
they
were
doing
a
rebroadcast
later
in
the
evening,
and
I
mean
it's
a
little
inconvenient.
But
if
you're,
if
you're
presenting
you
know,
I
mean
that
was
told
me
well
up
front
right.
So
I
could
plan
for
it.
C
E
Okay
to
the
next
topic
white
paper.
E
So
when
we
start
this
work
around
august
or
during
summer,
like
we
didn't
really
put
any,
you
know
time
plan
about
when
we
should
have
the
first
draft
available,
then
we
should
reach
out
to
cd
foundation
stuff
for
some
editorial
support
and
so
on.
But
I
think
after
seeing
the
discussions
and
having
some
kind
of
structure
in
place
and
like
I
think
we
have
four
or
five
case
studies
here,
maybe
we
can
start.
E
C
Yeah,
that's
fine.
I
can
just
check
in
with
the
the
creative
folks
who
format
it
and
edit
and
make
it
all
nice
and
just
give
you
some
some
dates
and
then
maybe
we
can
just
work
backwards
and
sort
of
put
out
some
okay
last
rough
by
here
reviews
and-
and
this
is
the
date
we'll
go-
live.
E
Okay,
can
I
I
can
action
you
with
some
kind
of
proposed
timeline.
Then.
E
E
Sorry,
okay,
that's
done,
and
the
next
topic
is
simply
again
the
white
paper
and,
as
I
noted
in
the
beginning,
we
have
some
contributions
from
captain
and
eriksen.
I
don't
see
andreas
or
anyone
else,
anyone
else
from
captain
here
but
yeah.
If
you
can
look
at
their
case
study,
they
put
a
case
study
based
on
a
company
called
amazon
from
europe
and
india.
C
E
G
To
started
the
reply,
there
is
a
there
is
a
reason.
The
the
case
study
will
be
a
lot
better,
probably
within
well
the
next
week
or
two
james,
on
the
call.
There
is
currently
in
the
process
of
moving
all
of
jenkins
ex-own
pipelines
over
to
vanilla,
tecton,
and
so
the
reason
is
we
could
have
talked.
We
could
have
done
this
okay
story,
but
wouldn't
be
relevant.
We're
we're
madly,
getting
the
version
three
out
at
the
moment,
so
I
promise
it'll
be
done
by
the
next
time.
G
E
For
zul's
stuff
again
I
have
some
kind
of
guess
about
which
company
case
study
may
appear
here,
but
I'm
not
going
to
spoil
that.
I
think
opening
for
summit
is
happening
next
week.
If
I
am
not
mistaken
so
week
after
next,
we
can
ask
jeremy
to
bring
that
here
as
well.
So
we
have
some
coverage
from
open
stack
foundation
as
well
and
dave's
case
study
has
been
here
for
a
while.
So
I
hope
you
had
a
chance
to
look
at
his
contribution
thanks
again
today.
E
For
that
then
emil,
you
want
to
talk
about
ericsson.
J
Yeah,
we
just
started
a
quite
short
user
study
there
from
american
perspective.
Our
journey
has
been
in
in
the
interrupt
session,
and
it's
as
you.
If
you
read
it,
you
will
see
that
it's
we
have
produced
in
this
event
protocol
the
eiffel
protocol
that
we
use
quest
extensively
now
within
ericsson,
and
we
look
forward
to
taking
part
in
in
developing
a
standardized
event
protocol
for
interoperability
in
larger
scale.
E
E
Yeah,
you
don't
have
to
promise
anything
just
to
you
know,
because
it
would
make
it
better.
You
know
if
we
have
again
as
discussed
before,
having
different
industries,
different
size,
companies
or
communities
contributing
case
studies
would
make
it
even
better
for
others
to
see
they
are
not
alone
in
this
journey
and
they
can
come
and
contribute
and
collaborate
within
continuity
foundation.
E
Absolutely
I
will
have
it
thanks.
Tracy
you
mentioned
again.
I
forgot
on
some
fintech
last
time
when
we
discussed
any
news.
C
E
And
again,
we
discussed
based
on
this,
the
other
document
you
shared
yeah
this
one.
If
some
of
the
case
studies
like
they
don't
talk
about
intervals,
they
are
candidates
for
this
paper.
You
know
if
they
are
talking
about.
I
E
E
C
Yeah,
like
I
think
we
can
have
that
conversation
for
the
purpose
of
the
white
paper.
I'd
keep
it
pretty
simple.
What
you
know
conclusion
is
interoperability
is
important
and
will
be
better
for
everybody,
and
the
future
can
just
be
during
the
interoperability
group
because
we're
trying
to
make
it
happen,
but
yeah,
I
wouldn't
over
promise
on
anything,
but
I'd
love
to
have
actually
that
conversation
now
about
what
like,
let's
get
the
white
paper
done.
But
what
are
the
next
practical
steps
we
could
be
doing
to
actually
move
move
or
change
change
things.
E
E
Okay,
the
other
thing
I
want
to
mention
is
there:
is
this
industry
workshop
happening?
I
don't
know
if
any
of
you
heard
this
this
icst
like
ieee.
E
What
was
the
international
conference
on
software
testing,
verification
and
violation?
This
is
happening
and
it
was
originally
planned
for
before
some
writing.
They
postponed
it
to
next
week
and
it
is
partly
virtual
and
within
that
conference
there
are
multiple
workshops
and
one
of
them
is
called
cicd
industry
workshop
and
when
this
was
planned
first
time
I
submit
the
proposal
and
it
got
accepted
at
that
time
and
they
came
back
this
week
saying
this
is
happening,
so
I
will
go
and
talk
about
interoperability
there
and
there
are
some
other
talks
there.
E
E
C
Now
that's
awesome
I'll
highlight
that
too
to
the
team.
Here
we
can
help
promote
that
and
just
highlight
use
your
speaking
edit.
C
Yeah
well
just
this
whole
idea
of
looking
ahead
and
you
know
kind
of
other
low-hanging
fruit.
We
can
do
more
on
the
technical
side
that
we
should
be
steering
people
to
kind
of
talk
about
or
get
together,
and
I
and
I
know,
there's
stuff
going
on
the
event
side.
But
I
was
curious
if
anybody
here
has
some
thoughts
or
some
kind
of
more
urgent
things
or
low
hanging
fruit
that
we
could
tackle.
K
K
Yeah,
I
guess
this
goes
with
the
it's
a
little
bit
like
the
the
erickson
comment
on
the
events,
interchange
and
stuff,
but
certainly,
I
think,
test
results
interrupt
like
we
have
test
creating
the
kubernetes
infra
project
for
visualizing,
test
results
and
we've
never
really
tackled
that
in
an
industry
and
we're
all
using
ju
xml,
which
is
a
reasonable
thing
to
use
for
now,
but
test
test
results
interrupt
would
be
great
and
I
think
metadata
about
we've
had
various
discussions
with
spinnaker
folks
over
the
years
of
should
we
have
a
canonical
data
format
for
like
what
does
the
release?
K
Look
like.
What
does
the
change
look
like
I'm
talking
about
like
metadata
like
how
can
we
can?
We
have
a
canonical
blob
of
yellow
for
a
release
with
where
the
changelog
is
and
the
git
tag
and
the
git
url
and
the
what
artifacts
are
including
the
release
and
is
it
on
github
on
the
auto?
Is
it
on
gitlab
or
not?
Is
it
has
it
got
helm
charts
inside?
Has
it
got
binaries?
So
I
think
there's
there's
a
whole
metadata
topic
that
we
could
pick
something
whether
it's
releases
test
results
reporting.
K
J
Yeah,
that's
very
very
interesting
because
that's
exactly
what
we
use
our
events
for
in
ericsson,
we
use
them
for
interoperability,
for
test
results
and
for
releases
and
for
artifacts
and
all
these
kinds
of
things.
So
that's
very,
very
interesting
to
be
to
be
part
of
yeah
and
of
course
we
could
have
that
in
the
event
since
the
icd
work
stream
or
we
could
have
it
in
a
separate
one.
That's
fine
as
well,
because
it
doesn't
need
to
end
up
in
events
of
course,
even
though
that's
how
we
have
done
it
so
far.
But
I'm
very.
K
K
So
we
just
made
one
up:
it'd
be
kind
of
nice
if
the
cdf
could
come
up
with
the
definition-
and
this
could
just
be
a
blob
of
yaml
right
with
a
schema,
it
doesn't
have
to
depend
on
you
know
using
kafka
or
using
git
or
using
a
crd.
K
It
could
just
be
a
file
folder
right
that
we
all
can
write
tools
to
consume
and
to
generate,
and
we
could
have
a
tecton
generator
in
the
jiggers
x
generator.
I
mean
that
could
be
the
same
thing.
We
would
maybe
have
a
jenkins
generator.
K
People
could
generate
them
by
hand.
We
could
have
a
schema
to
verify
that
metadata
is
valid,
you
know
and
so
on
and
so
forth.
So
I
think
starting
simple
and
small,
and
then
eventually
it
can
become
an
event
stream,
but
how
you
consume
these
things
could
be
file
systems.
Crd
events,
the
database
anything,
but
I
think
that
would
be
really
useful
to
try
and
raise
the
obstruction
of
it.
I
Totally,
I
don't
have
any
thoughts
on
the
top
of
my
head
about
reporting
tests
data.
Normally,
we
we
don't
do
too
much
testing
the
from
what
I've
seen
in
our
cd
pipelines.
A
lot
of
that
happens
as
part
of
the
cici
build
systems
we're
trying
to
push
people
right
towards
stuff.
I
You
know
it's
not
not
too
many
people
are
there
yet,
but
I
think
we
do
see
a
lot
of
value
in
like
canary
deploys.
We
do
see
a
lot
of
people
wanting
to
get
to
just
put
it
in
production
and
and
see
how
it
compares
to
previous.
I
Previous
versions,
but
yes,
I
I
would
be
interested
in
a
standard
format
for
testing
that
that
could
even
relate
to
the
events
working
group
that
we
talked
about
in
the
bof
session
at
the
interoperability
interoperability
bof
session
at
cdcon
yeah,
I
feel
like
there
could
be
some
some
overlap
there.
B
K
But
I'm
sure
once
we
get
started,
we
could
think
of.
For
example,
should
we
have
a
generic
if
using,
if
you
are
using
kubernetes,
should
we
have
a
generic
annotation
with
the
url
to
where
this
method
iterates
or
should
we
have
a
standard
label
in
the
hamster
or
something
or
a
container
image
label
or
something
anyway?
Should
we
have
a
canonical
place?
You
could
find
it
and
you
could
go.
Oh
look.
K
There's
a
cdf
release,
metadata
string
in
this
binary
hamster
image,
whatever
it
is,
or
get
repository
or
whatever,
whatever
just
have
a
canonical
standard
place,
to
put
it
so
that
people
get
used
to
looking
for
it,
and
if
it's
not
there,
you
know
people
say
cool.
Could
I
have
that
metadata?
Please,
because
you
know
even
little
things,
like
so,
let's
say
you're
doing
a
canary
department.
K
What
is
the
canary
like
what
is
the
church?
That's
in
them,
like?
Oh
there's,
canary
five,
seven,
six
of
us
because
there's
two
three
four,
I
don't
know
what
they
are
they're
just
images
with
random
shows
on
them.
It'd
be
nice.
If
there
was
a
canonical
way
of
going.
This
has
got
the
experimental,
you
know
food
switch
and
that's
got
the
bus
switching
or
whatever
you
know.
So
this
details
about
the
issues
or
the
pull
requests
or
the
changelog.
That's
happened,
or
the
people
who
have
created
it
or
whatever
it
is.
E
Yeah,
I
think
we
these
some,
like
majority
of
these
things,
are
like
implicitly
within
our
roadmap
as
well.
So
it's
like
it's
if
we
can
do
something
like
this
like
james,
that
would
you
know,
help
a
lot
to
everyone
and
if
cdf
can
endorse
this
type
of
you
know
outcome,
and
then
it
would
get
even
more
attention
from
other
communities,
not
just
the
communities
that
are
part
of
cdf,
but
elsewhere.
E
E
I
don't
want
to
call
workstream,
but
it
could
be
work
stream
as
well
and
while
event
work
stream
worked
on
event
type
of
stuff.
This
work
stream
works
in
parallel
to
events
determining
some
kind
of
metadata
thing,
and
over
time
these
could
could
be
converged.
You
know,
oh
here
is
the
metadata
thingy.
Here
is
the
event
thingy
and
let's
work
together
and
come
up
with
how
this
can
be
utilized
within
events,
and
vice
versa.
Type
of
thing.
C
So
yeah
speaking
of
next
meetings
and
just
a
couple
of
things,
I'd
love
to
see
so
like
for
the
jenkins
x.
Folks,
if
you
are
kind
of
getting
to
a
point
where
you
can
you,
you
have
something
to
show
with
the
tactile
integration.
C
It
would
be
great
to
have
a
demo
of
that
at
this
group,
and
I
see
tracy
reagan
if
you're
still
there
just
having
ortivius
in
the
the
configuration
management
as
well,
I
think
would
be
really
good
to
just
have
everyone
on
the
same
page
of
what
that
can
do
and
how
they
fit
in
with
what
we're
talking
about.
E
Yeah,
we
can
definitely
have
let
me
open
that
like
if
anyone
wants
to
reserve
spot
right
now,
I
can
open
that
presentation,
schedule
and
just
put
tentative
dates
for
jenkins
extect
on
here
like
jenkins,
x
and
techton,
and
then
the
next
one
could
be
ortelius,
and
what
was
it
all
tell
us
did
I
spell
it
right.
E
I
can
put
like
october
29th
as
tempted
here
for
both
of
them
and
then
james,
james
and
tracy.
Just
you
can
update
this.
You
know
table
and
post
point
for
the
up
for
the
next
meeting.
If
you
can't
be,
you
know
like
ready
with
material.