►
From YouTube: CDEvents / SIG Events Vocabulary Meeting - Apr 19, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
A
B
A
B
A
A
Yeah,
it's
all
to
us
and
I
was
hoping
more
research
to
join,
because
we
had
some
discussion
on
the
github
request
this
earlier
today,
but
not
an
issue.
So
I'm
not
sure
I
mean
unless
anyone
else
joins,
we
might
call
the
meeting
off,
but
but,
however,
we
can
get
chit
chat
a
bit.
Have
you
been
on
one
of
these
meetings
before
by
the
way.
B
I've
co-chairing
with
fatigue
the
software
security
supply
chain.
No,
no,
the
software
supply
chain.
A
Yeah,
so
I
met
fatih
a
couple
of
times
and
I
know
him
quite
well.
That's
good
and
I
started
out
in
the
cdf
foundation
in
his
first
sig
in
the
sage.
Interoperability.
Yes,.
B
A
A
B
Supply
chain:
well,
I
don't
know
if
it's
the
best,
but
I'm
trying
to
provide
the
best.
I
guess
it
fits
just
fine
and
what's
your
background.
B
A
Been
with
ericsson
for
many
many
years
over
20
years
now,
and
I've
been
working
with
tools
more
more
than
half
of
that
time,
and
the
last
like,
I
don't
know,
eight
nine
years
since
c,
I
was
inventing
more
so
I've
been
working
with
continuous
integration
at
ericsson
and
the
tooling
perspective
of
it.
Mostly.
A
A
It's
also
about
events
in
the
ci
cd
system
or
a
delivery
chain
or
so
supply
chain
or
whatever
you
want
to
call
it.
So
it's
something
that
we've
been
using
internally
in
ericsson
for
a
long
time,
but
also
published
open
source
a
few
years
back.
A
So
we
are
a
group
of
people
and
companies,
companies
evolving
that
existing
profitable,
which
is
actually
in
use
in
production
use.
But
but
this
is
a
new,
this
city
events
thing
is
a
new
initiative
to
to
broaden
the
scope
a
bit
and
to
to
get
more
people
involved
and
more
tools,
providers
involved
and
so
on.
So
because
we
see
a
very
big
benefit
of
having
more
providers
on
board
on
the
same
idea
and
implementing
support
natively
for
the
for
for
an
event
protocol
and
that's
why
we
need.
A
We
think
this
is
a
good
thing
to
to
start
modest
from
scratch
here
in
this
group
and
creating
a
good
event
protocol,
together
with
all
the
tools
providers
that
are
interested
to
do,
of
course,
to
support
this.
A
So
that's
the
idea.
There
sorry.
B
A
I
don't
myself,
I
think,
techton
is
deployed
in
some
places
in
ericsson
in
use,
but
I'm
not
really
sure
in
the
neighborhood,
where
I,
where
I
normally
spend
my
days,
I
haven't
seen
anyone
using
tecton.
Actually
so
so
we
are
currently
using
argo.
The
argo
workflows
as
pipeline
engine
in
our
kubernetes
clusters
and
the
the
main
reason
there
was
that
I
mean
when
we
decided
on
argo.
Tekton
wasn't
really
around.
I
think
it
was
some
very
pre-er
pre-release
existing,
maybe
of
tecton,
and
it
sounded
maybe
something
that
could
come.
B
B
A
B
And
you
know
I
I
I
used
to
be,
how
do
you
say
business
owner
and
I
built
my
business
on
on
clear
case
expertise.
So
I
cannot
blame
a
clear
case,
but
because
it
was
a
complex
tool
and
expertise
was
really
required.
But
nowadays,
when
I
look
back
to
clerk,
who
is
going
to
take
clear
case
and
why
why.
A
Right
now,
everyone
is
in
vietnam,
but
we
for
some
reason
chose
garrett
in
ericsson.
Gitlab
is
in
some
part
of
ericsson,
also
used,
but
still
garrett
is
the
most
used
internal
source
code
manager
at
least.
A
Oh,
I
couldn't
compare
it
myself.
I
hadn't
haven't
really
used
any
of
them
from
what
I
could
guess
is
I
mean
gitlab.
Sia
is
probably
the
tool
you
should
use.
If
you
are
only
in
gitlab
and
you
are
always
working
in
a
gitlab,
then
I
don't
see
why
you
should
not
use
github
ci.
I
mean
that
you
will
get
a
lot
of
things
for
free
there,
an
integration
with
your
sem
repositories
and
everything.
A
A
So
that's
why
we're
interested
more
in
cloud
native
workflow
managers
like
argor
tecton,
but
we
of
course,
would
like
to
integrate
this
event
protocol
that
we
are
emptying
here
with
git
lab
as
well,
so
that
we
can
have
interaction
and
integration
interoperability
with
the
with
gitlab
ci
workflow,
so
to
say.
B
B
Okay,
okay,
okay,
yes,
we
we,
we
are
using
git
lab
for
our
both
our
open
source
projects
and
our
downstream.
You
know
like
internal
projects
as
well.
Gitlab
is
a
because
github
is
eventually
it's
an
open
source
tool,
but
we
are
using
a
gitlab.com
which
is
a
hosted
version
of
github,
and
we
don't
and
internally
we
have
few
instances
of
gitlab,
both
community
versions
and
also
enterprise
versions
as
well,
and
because
we
are
working
like
I'm.
A
product
owner
like
the
product
that
I
am
working
on
on
its
supply
chain
is
the
operating
system.
B
Means
that
the
code
base
is
spam
on
multiple
repos
gitlab,
git
repos
that
are
hosted
in
gitlab
so
and
that
that's
you
know
my
concern
is:
how
do
I
manage
gitlab
ci
when
you
want
to
orchestrate
you
know
like
pulling
sources
from
400
git
rippers,
not
one
usually
gitlab
ci
is
you
know
it's
tied
into
one
repo?
If
something
happens
in
that
repo,
then
well
you
you
can
manage
it.
I'm
not
saying
that
it's
not
manageable.
It's
not
doable
to
integrate
that,
but
it's
not
out
of
the
box.
B
B
A
B
Okay,
so
we,
as
I
said
we
are
generating-
I
don't
know
young
repo-
is
that
something
that
you're
aware
of
yeah.
B
It's
like
a
repository
of
rpms,
so
this
is
what
this
is
our
product,
because
eventually
a
customer
will
take
those
this
repo
and
we'll
generate
an
image
out
of
the
packages
that
are
in
this
year.
Okay,
so
so
we
are
planning
to
eventually
to
to
push
this.
You
know
regenerate
this
yam
repo
and
push
it
into
an
artifact
store.
There
is
no,
you
know,
deployment
right.
A
A
Right
so
the
one
one
use
case
with
these
events
that
we
are
even
inventing
here,
then
we
are
trying
to
to
create
a
specification
for
is
to
to
be
able
to
connect
also
downstream
integrators
of
your
product
to
your
pipelines,
yourselves,
your
own
pipelines
to
to
bridge
the
the
gap
between
your
delivers
to
to
report,
to
artifact
repository
manager,
then
or
young
rapport
manager
to
the
ones
who
actually
then
download
those
and
start
using
those
and
integrate
those
in
their
applications
and
eventually
deploy
their
applications.
A
A
So
we
can
bridge
the
gap
between
different
platforms
and,
of
course,
those
integrators
that
might
not
use
git
lab,
for
example,
when
they
integrate
your
libraries
and
download
it
from
from
the
am
repository
they
might
use
some
other
sm
tools
to
to
handle
that
stuff
and
they
might
use
ticket
on
them
to
to
run
their
integration
pipelines
and
then,
if
we
would
have
such
a
common
event
protocol,
that
would
mean
that
we
could.
B
My
personal
case
right
in
the
program
that
I'm
part
of
because
the
operatings
that
the
operating
system
that
we
are
currently
working
on
is
for
the
automotive
industry,
and
I
think
that
car
manufacturers
are
not
that
you
know
they
are
reluctant
to
share
their
what's
happening
in
their
environment
with
the
the
outer
outer
world.
This.
A
Is
the
current
situation?
You
know
interesting?
I
I
wouldn't
say
that
they
are,
I
mean,
of
course
they
they
would
not
want
to
reveal
any
secrets
and
say
we
are
now
developing
this
car
model
or
whatever,
of
course,
but
they
might
be
willing
to.
I
mean
because
they
would
themselves
be
helped
by
publishing
that
now
we
are
using
this
repository.
So
please
provide
me
quick
feedback.
B
B
It's
not
me
pushing
back,
it's
just.
You
know
representing
what
I
think
that
is
the
current
situation.
Okay,
I'm
sure
that
the
the
automotive
industry
is.
Is
you
know
it's?
It's
a.
There
is
a
lot
of
disruption
in
the
in
the
latest
years.
You
know
telsa
came
on
board
and
there
is
all
those
discussions
and
and
work
that's
been
done
with
the
automotive
cars
and
stuff
like
that.
So
it's
it's
it.
B
A
Yeah,
of
course,
that's
a
quite
forehead
in
the
future.
I
I
would
guess
as
well.
I
think
you
would
be
interested
to
to
discuss
these
matters
a
bit
with
eric,
who
is
also
one
of
the
people
in
this
sig
normally
on
in
this
project,
normally
eric
stanley's
on,
because
he
is
also
working
as
a
consultant
towards
volvo
cars
with
actually,
and
he
has
his
own
ideas.
A
I
guess
on
where
the
event
protocol
this
event
protocol
that
we're
developing
is
suitable
to
use
there
if
he
sees
the
need
for
for
connecting
the
pipeline
that
he
is
working
on
within
volvo
cars,
with
the
providers
of
the
libraries
that
he
uses.
I
I
don't
really
know,
but
but
it
could
be
an
interesting
discussion
to
have
with
eric.
I
think,
for.
B
B
B
Is
building
the
product
so,
but,
but
from
my
you
know,
from
the
talks
in
the
program
is
that
the
customers
are
reluctant
to
share
their
a
lot
of
information
outside
their
environment
and
information
is
infrastructure,
source
code,
tooling
pipelines,
progress.
You
know
all
kinds
of
information
that
right
now,
it's
it's
not
in
the
scope
and
and
by
the
way,
because
you
know
I
don't
know
if
you're
aware
of
how
reddit
is
working
so
reddit
is
a
we
are.
B
We
are
working
in
an
open
source
development
practice.
It
means
that
our
operating
system
is
actually
like
hundreds,
if
not
thousands,
of
open
source
projects
that
are
very
that
are
not
stable
right.
Each
project
has
its
own
cycle,
release,
cycle
and
development
and
stuff
like
that,
and
we
tend
to
take
snapshots
to
test
them
to
repackage
them
and
to
provide
our
customers
stable
versions
of
those
packages
as
a
product.
B
So
therefore,
this
continuously
update
is
not
something
that
we
are
probably
want
to
share
in
the
in
the
automotive
industry.
By
the
way,
each
update
needs
to
be
certified,
functional
safety
certification-
and
this
is
a
very
long
process,
months
of
work.
So
every
change
requires
a
certification.
So,
as
I
see
I
have
plenty
of
pushbacks
in
my
my
bag,
but.
A
Yeah
yeah,
that's
good
sounds
good,
no,
but
yeah,
but
we
we
don't
need
to
dig
deeper
into
that
now,
of
course,
either
of
course,.
B
A
I
think
that
eric
is
planning
to
go
to
the
city
landscape
in
valencia.
Actually,
are
you
going
there
or.
B
Yes,
I
actually,
I
think
that
fatigue
shared
with
me,
the
information,
but
I
was
not,
I
don't
know
I
would
need
to
to
you
know
I
didn't
travel
since
covet
yeah.
A
A
B
And
I
don't
have
the
you
know
the
taller
or
the
tolerance
you
know
for
all
kinds
of
checkups
and
and
to
to
go
with
this
mask
all
the
time
and
stuff
like.
A
A
A
B
A
Yeah
so
with
like
50
percent
and
not
victors
are
covered
mainly,
but
because
of
the
carbon
dioxide
emissions
to
be
more
environmental
friendly
and
since
the
industry
has
moved,
I
mean
the
the
kind
of
meeting
that
we
have
now
is
what
wasn't
really
possible
some
years
back,
but
now
it
is,
and
it
is
possible
to
have
virtual
conferences.
So
why
shouldn't
we
have
virtual
conferences
and
such
discussions?
A
So
I'm
not
too
optimistic
that
I
will
be
allowed
to
travel,
but
if
I
will,
I
will
go
to
valencia
and
we
we
might
meet
there,
and
I
know
I
would
say
that
I
know
that
eric
is
planning
to
go
there.
So
if
you
would
go,
you
could
meet
with
him
there
can
we.
I.
B
Will
do
you
have
like
a
like
the
link
handy,
so
I
can
share
the.
B
A
A
Sorry,
it's
a
one,
maybe
one
day,
even
it's
only
one
day,
I
think,
but
the
cube
coin
is
of
course,
a
full
week
and
you're
required
to
have
a
cube
con
registration
to
be
able
to
go
to
go
there
to
see
the
event.
B
A
It's
focusing
on
kubernetes,
cognitive,
tooling
in
our
area.
A
A
Yeah
yeah,
it
is,
it
is
for
sure,
also
for
the
city
events
con.
It's
a
virtual
option.
Yeah
and
now
I
will
go.
I
will
be
there
virtually
if
I
can't
come
in
in
person
for
sure
I
just
told
you,
but
it
was
easier
to
chitchat
in
in
between
presentations
and
such
if,
if
we
meet
at
the
conference
but
anyway,
let's
see
I
just
wanted
to
share
also
the
link
to
the
we
will
have
a
meet
up
in
the
city
events
group
next
wednesday.
B
A
A
There
would
be
a
webinar,
slash
meetup
for
an
hour
where
actually
eric
and
andrea
frictory
will
morris
revisit
the
presentation
they
had
earlier
this
year
on
the
foster
conference.
B
A
I
think
you're
getting
mail
at
least
you
might
be
able
to
create
the
calendar
invite
by
yourself
from
the
mail
somehow
or
from
this
webpage.
Maybe
I
don't
really
remember
now
I
created
a
meeting,
so
I
can
really
say
I
maybe
don't
see
the
same
things
as
you
as
you
do.
B
What
is
the
target
of
the
meeting
here
it
is,
I
took
the
calendar
book
could
find
it.
B
Is
to
to
to
get
more
custom,
you
know,
like
users.
A
Yeah
yeah,
of
course
I
mean
it
is
to
reach
out
to
a
broader
group
of
people
who
might
be
interested
in
events
and
to
make
sure
that
we
we
consider
any
use
case
that
is
relevant
for
for
the
users
that
are
interested
in
events,
so
that
we
don't
spend
a
lot
of
time.
Inventing
events
for
things
that
no
one
is
interested
in
more
or
less
so
we
focus
on
the
right
thing,
the
right
things
of
course,
and
that
we
I
mean
since
now,
we
will
also
set
the
vocabulary
on
the
events
I
mean.
A
A
So
it's
a
lot
about
naming
and
also
how
how
you
can
combine
or
link
or
reference
different
events
together
and
so
on.
So
it's
like
the
ground
work.
We
are
doing
right
now
for
that.
A
I
mean
that
that's
the
the
main
common
part,
so
the
project
aims
to
provide
a
a
protocol
specification
and
then,
of
course,
we
will,
together
with
that
specification,
we
are
also
developing
sdks
to
make
it
easier
to
use
the
protocol
and
also
developing
pocs,
to
see
that
we,
what
we,
what
the
protocol
specifies,
is
possible
to
use
in
reality.
A
So
there
is
a
poc
from
last
autumn,
sometime
or
maybe
even
last
summer,
where
the
captain
tool
and
tekton
was
integrated
through
these
kinds
of
events,
not
the
latest
version
of
the
spec
that
we
have,
but
an
earlier
version
of
it.
So
at
least
could
make
a
proof
of
concept
that
it's
actually
worked
to
integrate
those
two
different,
completely
different
systems
with
each
other.
Using
these
kinds
of
events-
and
we
will
have
we
look
forward
to
having
more
such
pocs.
A
A
So
when
it
comes
to
the
architecture,
well,
seed
events
is
is
currently
based
on
the
cloud
event
specifications.
So
cloud
events
is
a
kind
of
generic
event
specification
for
transporting
information
from
a
producer
to
consumer.
A
Regardless
of
what
messaging
transport
system
you
would
use,
underneath
it
could
use
kafka,
rabbit,
mcu
or
whatever,
more
or
less
and
cloud
events
is
the
the
layer
where
all
those
things
come
together
and
you
can
connect
your
rabbit,
mq
bus
to
something
somewhere
that
sends
things
using
kafka
as
soon
as
you,
you
have
the
cloud
events
layer
in
your
system,
you,
you
could
understand
each
other,
and
then
we
provide
this
specification
on
top
of
cloud
events
where
we
define
the
language
for
the
ci
series,
specific
events
that
we
intend
to
to
show
here
or
into
yeah
specifically
to
enable
interoperability,
then,
of
course
between
the
different
cicd
tools.
A
B
B
A
I
mean
if,
if
as
long
as
the
producer
fulfills,
the
cloud
events,
infrastructure,
spec
so
to
say,
and
and
some
these
events
have,
the
tech
stack
needed
to
to
send
proper
cloud
events
and
this
cd
events
on
top
of
it,
then
any
consumer
that
also
can
is
is
compatible
with
cloud
events
regarding
of
what
text
deck
it
uses.
A
Underneath
should
be
able
to
to
read
the
information
and
get
the
information
subscribe
to
it
coming
from
another
producer,
and
that's
the
the
intention
with
cloud
events
as
I,
as
I
see
it,
to
be
able
to
bridge
the
different
architectures
that
might
might
exist
or
different
text
stacks
that
might
exist.
B
But
it
would
be
interesting
to
see
it
in
in
you
know,
in
action
to
see.
A
Yeah,
I
don't
really
remember
now.
If
eric
and
andrea
has
some
live
demo,
I
think
they
might
have.
That
will
also
be
shown
then
next
week
on
wednesday,
together
with
the
presentation
it
might
be
so
otherwise
I
that
there
is
still
the
poc
from
last
autumn
that
could
be
revisited.
I
think
there
is.
There
are
recordings
of
it
as
well,
which
you
can
see
on
youtube
somewhere.
I
don't
have
the
links
now,
but
that's
possible
to
find
out.
A
A
B
A
B
A
Yeah,
for
sure
I
don't
know
if
you
know,
but
my
co-chair
in
in
this
sig,
I
mean
I'm
one
of
the
chairs
in
the
in
the
sig
events
and
my
co-chair
is
andrea
frittori
and
he
is
one
of
the
main
maintainers
of
the
techtone
project
as
well
interesting.
So
I
might
like
to.
A
B
Several
acquisitions
ibm.
B
B
A
B
A
A
It
was
nice
chatting
with
you,
it
seems.