►
From YouTube: CDEvents / SIG Events Vocabulary - Oct. 18, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
D
E
D
Okay,
okay,
shall
we
get
started
I'm
doing.
F
Yes,
I'm
on
my
phone
and
computer
at
the
same
time,.
B
D
All
right,
let's
get
started
so
welcome
to
the
city
event,
a
couple
of
discussion
making
today's
October
18th
I'm
under
effectively
I
work
for
IBM,
and
please
sign
yourself
in
the
police,
at
least
if
you'd
like
to
I.
Only
added
a
couple
of
things
on
the
agenda
for
today,
mainly
I,
was
wanted
to
to
discuss
the
adopting
CD
events,
PR
review
the
plan
for
0.1
and
discuss
SDK
status
updates.
B
G
D
Thank
you,
I,
we're
just
about
to
start
so
for
the
pr
I
think,
thanks
for
the
reviews
on
that.
D
D
So
this
in
this
PR
I
mean
you
Eric
and
Emily
have
reviewed
it.
I
think
I
was
adding
some
content
about
adoption,
CD
events
with
some
diagrams
on
how
an
incremental
adoption
could
look
like.
E
E
One
thing
I
was
reflecting
on
when
reviewing
this
was
the
arguments
for
declarity
versus
imperative
events.
It's
maybe
a
bit
thin
I
think
it's!
It's
good,
that
it's
not
too
extra
to
should
I,
say
to
involved
or
to
do
large,
too
long
certification,
but
I
was
thinking
if
there
was
something
on
the
cloud
events
where
they
that
we
could
base
our
argumentation
on,
but
I
couldn't
find
anything.
E
I
I
happen
to
find
a
the
presentation
by
Clements
Walters,
who
is
one
of
the
the
founders
I
think
of
the
cloud
events,
but
it's
that's
just
an
Arctic,
because
it's
not
really
something
we
could
be
linked
to.
But
it's
if
everyone
here
knows
about
some
good
point
Thursday,
which
we
could
use
here
to
make
this
these
statements
even
more
heavy,
so
to
say,
okay,
but
but
for
now
I
think
that
we
have
good
augmentation
is
I,
think
it's
it's
good
enough,
but
yeah
just
messenger.
D
I
mean
one
thing
that
I
did
add
in
here.
Is
this
sentence
so
CD
events
do
not
support
imperative
events.
Today,
the
specification
may
include
imperative
events
in
future
to
Foster
interoperability
in
system
that
ion
imperative
events
today,
so
it
is
based
on
Brands
input
and
what
we
discussed
also
in
the
city
event,
Community
Day.
Is
that
something
do
you
think
this
is
okay
or
you
would
rather
not,
and
this.
E
D
All
right,
then,
I
think
we
can
keep
the
discussion
on
this
VR
short
I.
D
I
think
we
can
merge
it
then,
after
the
after
the
meeting,
unless
there
is
anything
else
and
I,
think
it
banners
some
further
comments,
we
can
do
some
amendments
later
on.
D
Okay,
so
next
to
the
project
and
clear
in
in
good
shape.
So
this
is
the
remaining
open
items
so
for
the
release.
Announcement.
D
E
D
Yes,
I
think
the.
D
D
D
What
it
covers
events
planning
from
configuration
management
system,
cicd
and
enough
to
calculate
levels
of
metrics
like
delete,
timer
change
and
deployment
frequency
features
in
1.0
version
schemes
for
all
events,
sdks
for
colon
and
Python,
and
we
are
working
on
a
job
SDK
and
we
have
Cloud
events
binding.
So
we
support
how
to
debbox
transport
over
several
different
messaging
system
and
then
links
links
to
the
white
paper.
G
D
A
E
One
yeah
I
can
comment
there.
We
we
pasted
some
valuable
inputs
to
this
governance
model
there,
some
some
months
a
few
months
ago,
then,
when
I
looked
into
this
more
in
detail,
what
we
actually
already
have
is,
so
we
have
a
document
stating
their
governance
model
where
it
mentions
a
bootstrap
committee
which
deals
with
the
governance
under
some
of
us
here
in
this
meeting
are
then
part
of
the
bootstrap
Community.
You
know
with.
E
As
stated
in
that
document,
so
I
think
that's
good
enough.
I
I
cleaned
it
up
a
bit
fixed
some
links
and
made
sure
that
we
have
references
in
the
correct
places
to
the
government's
document
itself.
So
I
actually
think
that
this
is
good
enough
now,
because
there
was
one
we
don't
need
to
have
it
in
a
better
shape
for
0.1
and
I.
E
Think
for
the
future
we
should
probably,
of
course
we
should
set
up
the
city
Dance
Project
as
a
as
well-defined
projects
with
a
well-defined
committee
steering
committee
or
governing
committee
for
it,
but
that's
not
really
that
doesn't
need
to
be
in
relation
to
any
specific
release
of
the
protocol.
I
think
that
could
be
done
in
parallel,
so
I
think
what
we
have
now
is
good
enough.
We
don't
need
to
feel
ashamed,
I
guess
what
we
have.
Other
people
go
to
the
website,
so
I
can
see
it
for
the
GitHub
project,
foreign.
D
Sounds
good
for
the
future,
shall
we
do
you
want
me
to
remove
this
then
the
issue
this
issue
from
the
project
so
that
we
track
independent
from
releases
or
we
close
this
one
and
maybe
reopen
new
one.
A
A
Like
maybe
what
I
can
do
is
just.
D
Okay,
highlight
supporter
use
cases
on
cdevents.dev.
This
is
still
missing
foreign.
D
G
D
All
right,
the
next
two,
the
document
subscriber
model
for
events
and
backward
compatibility
strategies
I,
would
consider
these
two
covered
by
the
the
pr
we
discussed
in
the
beginning
of
meeting.
E
Yeah
I
haven't
done
that,
of
course,
it's
not
it's
not
mandatory
I
think
to
have
in
the
spirit
one
it
would
have
been
good,
but
yeah
I
guess
I
still
have
maybe
some
some
time
that
this
week
to
do,
but
if
not
I,
think
it's
it's
fine
that
we
leave
it
out.
E
Regarding
the
other
two,
there
are
the
terminology
and
the
task
steps
that
types
big
in
the
terminology.
I
have
created
a
pull
request
to
the
Sig
interoperability
repository
where
the
terminology
document
is
stated
right.
A
E
E
So,
where
the
City
events
there
to
the
digital
tools
and
then
below,
there's
students
section
where
I
know
it's
copy
paste
it
from
our
website
and
add
some
of
the
terms
that
are
somewhat
relevant
and
then
obviously,
in
the
end,
there's
a
table
of
the
relating
how
different
things
are
called
in
different
tools.
So
I
already
see
the
advanced
there
with
the
terms
that
we
we
have
used
so
far.
It's
not
exactly
clear
what
all
these
columns
mean.
A
E
E
Levels
I
mean
type
that
the
right
most
or
the
third
last
column,
something
with
this
Pipeline
and
then
the
program
C11.
So
that's
the
highest
level
of
activities.
Let's
say
I
think
it's
what's
what
clicked
on
calls
like
the
pipeline
as
well?
So
if
you
relate
to
take
it
down
there,
I
guess
you
could
maybe
make
more
sense
out
of
it.
So
pipeline
contains
tasks
and
the
tasks
contain
steps,
and
then
steps
could
contain
something
which
is
not
defined
intact
on
either
and
we
have
the
same
procedure.
Events
models
with
pi,
plus
and
topics
right.
A
C
D
E
D
G
D
D
E
So
yeah
I
think
the
the
intention
is
that
whenever
Sig
interrupt
the
sets
a
some
kind
of
de
facto
standard
or
some
kind
of
recommend
recommended
terminology
for
each
of
these
different
columns
that
we
saw
on
the
table,
then
I
think
City
events
should
align
with
that.
But
before
that
has
happened,
there
is
no
no
reason
to
to
push
this
even
more
I.
Think.
E
Another
thing
about
that.
Thank
you.
Thank
you
very
much.
So
the
list
task
step
types,
that's
more
about
how
we
call
the
different
types
of
tasks,
for
example,
build
deployments
the
release,
publish
delivery
whatever
and
that's
a
related
document
in
the
or
another
document
in
the
same
signature,
probability
folder,
but
that
document
doesn't
contain
any
tools.
E
Relations,
let's
say
so:
you
can't
really
State
there.
What
we
I
mean
how
seated
events
is
conformed
with
those
terms,
but
of
course
we
are
not
fully
component
with
them.
I
would
say
and
I'll
show
what
we
intend
will
be
there
or
we,
the
ticket
was
written
by
Anne,
Murray
I
think
it
was
right
from
second
job.
B
E
E
For
that
yes
yeah,
so
that's
the
stages
of
Step
types
and
those,
so
here
I
think
it's
still
in
build
this
one
build
stages
there,
for
example,
and
we
have
test
stage
I
mean
we
call,
we
call
things
build
on
tests.
E
D
E
E
D
E
C
A
E
E
A
D
Yeah
no
I
think
what
we
said
is
that
we
could
make
a
statement
in
the
spec
saying
Okay.
We
are
aware
of
this
work
and
the
seek
interoperability
and
then
the
plan
to
to
work
in
it
in
the
next
release.
I
think
that's
what
we
discussed.
E
Yeah
that
sounds
familiar,
but
don't
we
already
have
something
like
that.
Actually,
nowadays,.
A
E
E
It's
rather
on
the
other
one
above
in
the
project
place
there
I
would
say,
consider
taking
advantage,
I
think
some
statement
there
that
we
should
be.
A
A
A
D
E
B
E
D
Would
remove
it
yeah
I
mean
we
can
still
do
it,
but
I
think
having
it
in
the
project
is
maybe
a
sign
that
we
want
to
have
that
and
like
mandatory
things
that
we
want
to
do
so.
I
would
remove
this.
A
D
D
Okay,
so
in
terms
of
call
SDK
I'm
working
on
a
PR
that
aligns
with
the
versioning
as
it
is
in
the
spec
and
adds
any
missing
field,
and
once
that
is
done,
I
will
make
another
PR
to
basically
do
the
version
switch
so
set
the
version
to
0.1.0,
as
opposed
to
tiered
1.0.
draft,
and
once
that
version
is.
D
D
F
Yeah,
the
python
SDK
has
quite
a
bit
more
work
left
than
the
go
SDK
and
basically,
what
we
have
is
we
have
the
this
data
type
that
matches
the
specification
as
far
as
I
know,
they
are
all
correct
and
based
on
on
quick
inspection,
it
seems
like
it
produces
this
Json
that
matches
the
schema,
but
obviously
this
needs
to
be
tested
more
then,
there's
a
bunch
of
things
that
is
not
implemented.
One
is
parsing,
which
is
obviously
something
we
would
like
to
do.
F
I
have
a
feeling
that
that
might
be
a
bit
more
complex,
I'm,
really
jealous
Andrea.
By
the
way
it
seems
like
in
go.
You
can
just
add,
like
scheme
my
information
in
the
code,
basically
which
looks
really
nice.
There
is
no
such
thing
in
in
python
as
far
as
I
can
see
at
least
yeah,
so
yeah
a
bit
more
hands
on
there,
but
the
main
thing
that
is
missing
I
think
is
the
actual
mapping
to
Cloud
events.
F
D
G
But
yeah
yes,.
F
And
yeah,
as
it
tends
to
happen
for
in
in
my
life,
I
started
this
on
Sunday,
with
a
plan
to
be
done
quite
soon,
because
I
feel,
like
yeah
I,
have
some
time
left
over,
but
then
the
whole
universe
crashed
down
around
me.
So
I
can
say
now
that
the
way
it
looks
like
now,
the
absolute
earliest
I
can
bid
on
with
this.
Is
this
coming
Sunday
or
or
early
next
week?
F
E
F
D
Okay,
I
mean
that
that's
fine,
for
me,
I
mean
I,
guess
we
could
also
do
it
so
such
as
like
incremental
I
mean
if
you
can
produce
valid
Json,
you
can
still
use
the
cloud
event
SDK
to.
B
D
Know
add
that
Json
into
a
cloud
event
yeah.
So
that
could
be
a
favorite
stage
and
then
you
know
adding
the
Cloud
events
built
in
as
a
second
step.
F
Yeah
I
think
that
is
a
really
good
way
to
do
it,
so
so
for
me
not
to
to
try
to
get
all
of
this
done
at
the
same
time,
but
but
focus
on
like
okay.
Now
we
have
at
least
some
value.
So
if
at
least
someone
can
use
this
to
send
a
valid
CD
event,
that's
a
good
start
and
then
maybe
parsing
can
just
be
something
we
will
have
to
add
a
little
bit
later.
D
F
D
All
right
anything
else
on
sdks.
G
D
We
still
have
20
minutes.
Maybe
we
can
use
the
time
to
discuss
a
bit
about
the
website.
I
mean
we
have
this
idea
of
improving
our
website
and
I
think
it
would
make
sense
to
make
it
a
bit
more
narrowed
down
so
that
we
can
yeah
actually
plan
for
it.
G
D
D
So
most
of
us
are
not
native
English
speakers.
So
it's
good
to
to
some
review
on
that
as
well.
Even
though
we
we
do
our
best
to.
E
Yeah
I
think
that
goes
both
for
the
the
overall
intro
text
on
the
primer,
which
explains
some
Concepts,
but
also
maybe
the
the
specification
itself
so
I
think
there
are
three
parts
of
it
and,
of
course,
the
overall.
The
introduction
texture,
of
course
be
understandable
standard
one
and
the
primer
might
require
some
more
understanding
of
the
subject
and
then
the
spec
itself.
Of
course,
then
you
need
to
more
or
less
understand
the
primary
before
you
can
understand
this
thing.
E
C
So
if
I
can
jump
in
here
when
you're
publishing
like.
H
This
it
really
helps
to
have
a
sort
of
narrative
Journey
for
for
the
user
and
right
now.
What
you've
got
is
a
lot
of
content
and
quality
at
the
end
of
the
journey,
but
there's
there's
not
enough
to
to
actually
suck
the
the
reader
in
at
the
beginning
to
get
them
to
invest
in
in
reading
that
content,
so
I
think
one
of
the
key
pieces
that
needs
to
be
done
is
to
first
of
all
highlight
what
the
what's
the
difficult
challenge
that
you're
actually
trying
to
address
with
this.
H
What's
the
problem
that
you're
solving
and
then
spell
out
how
that
affects
the
the
person
is
reading,
the
document
say
what's
in
it
for
them
and
what
might
happen
to
them
if
they
don't
go
down
that
route
and
then
move
into
the
explanation
of
what
the
detail
of
the
solution
is.
E
Makes
a
lot
of
sense
to
me
and
I
think
in
order
that
the
information
could
be
taken
from
from
the
white
paper?
If
nothing
else,
I
mean
we
have
quite
a
lot
of
information
there,
but
of
course
it
needs
to
be
condensed
on
the
medium
crisper
probably
stated
there,
but
that's
the
tasty
source
of
information
to
look
into.
When
writing
this
text.
D
C
H
I
think
the
the
content
is
generally
good
and
quite
readable,
but
it
is
very
wordy,
so
some
of
the
audience
will
struggle
to
engage
because
it's
just
a
wall
of
text.
So
so
one
of
the
things
to
consider
is
diagram
content.
And
how
much
of
this
can
we
translate
into
architectural
diagrams?
And
you
know
simple
block
diagrams
or
sketches
so
that
you
can?
You
can
get
the
the
meaning
across
in
more
than
one
way.
H
So,
if
you
give
you
know
a
text,
description,
a
diagram
and
a
code
example,
then
you
you
have
the
ability
to
cross-check
your
understanding
against
those
three
different
things
and
and
therefore
discover
whether
the
mental
model
that
you're
building
is
actually
consistent
with
what
what
the
narrative
is
intended
to
be.
D
So
what
what
would
it
take,
then
for
us
to
go
from
where
we
are
today
to
this
kind
of
content,
I
mean:
do
we
need
to
food
kind
of
drafters,
catch
the
diagrams
and
a
review
of
what
we,
the
content
that
we
have
in
there?
Do
you
think
Terry?
There
is
enough
content
in
there
to
try
and
draw
the
diagrams
and
from
it
or.
H
With
this,
one
of
the
things
that
you
would
do
early
on
in
the
process
is,
if
you,
like,
a
gap,
analysis
to
say,
okay,
this.
H
This
piece
feels
like
it
needs
more
detail,
or
this
piece
feels
like
it
needs
a
supporting
diagram
and
then
go
through
and
pin,
pin
those
in
the
in
the
narrative,
because
at
the
same
time
you
can
have
too
many
pictures
and
and
and
and
then
you
end
up
with
a
lot
of
scrolling.
H
So
you
really
want
to
get
a
nice
flow
through
the
document,
so
that
people
are
are
moving
through
images
and
blocks
of
of
text
in
a
way
that
that
makes
it
very
easy
for
them
to
read
and
understand
comfortably
what's
going
on,
and
you
know
that
that's
certainly
something
I
I
can
help
out
with.
If,
if
that's
what
you
need,
the
other
thing
that
I
suggest
that
needs
consideration
up
front
is
how
you
want
to
publish
to
to
this
View.
H
H
D
I
see
yeah
I
mean
what
we
have
today:
I
mean,
except
for
the
home
page.
Basically
yeah
the
spec
is
displayed
on
the
website,
so
we
basically
publish
things
on
the
on
the
spec
repo
and
it's
then
synced
on
a
nightly
basis
to
the
website.
D
So
that's
how
it
works
today,
I
mean
I,
guess
we
could
have
some
part
of
the
content
hosted
on
the
website
and
if
it
makes
sense,
so
we
could
add
in
the
spec
report
some
documents
which
are
dedicated
to
be
like
introduction
or
introductory
introductory
content.
H
So
it's
it's
not
necessarily
right
or
wrong
either
way.
H
But
you,
you
need
to
sort
of
just
bear
in
mind
the
constraints
that
that
that
that
that,
so,
if
what
you're
doing
is
automatically
releasing
the
the
spec
from
another
Repository,
then
you're
going
to
have
very
limited
ability
to
play
with
the
styling
and
look
and
feel
of
that
in
the
published
document.
H
So
so
that
means
that
the
the
spec
itself
my
be
harder
to
read
and
therefore
you
might
need
other
supporting
documentation
around
it
to
to
provide
you
know
extra
information
or
clarification.
Or
you
know
if
we're
going
to
put
diagrams,
then
we're
not
going
to
be
able
to
put
those
diagrams
in
the
in
the
spec
we're
going
to
have
to
have
a
narrative
and
then
and
then
a
specification,
a
separate
pieces.
D
H
H
D
H
H
Yeah,
this
is
where
the
the
sort
of
the
user
Journey
comes
back
into
play,
because
what
you
can
do
potentially
is
structure
things
so
that
you're
you're
moving
the
reader
between
a
narrative
section
and
a
specification
section
and
another
narrative
section,
so
that
your
your
giving
them
a
preparatory
Concepts
that
they
need
to
read
part
of
the
specification
and
then
you're
giving
them
the
spec
so
that
so
that
they
can.
Then
you
know
dive
into
the
detail
of
it,
but
potentially
breaking
that
up
into
bite-sized
chunks,
so
that
it's
it's
easier
to
absorb.
D
Right,
yeah,
yeah
I
think
it's
not
too
far
away
from
the
structure
we
have
today
with
a
primer
and
a
spec,
so
the
primary
is
like
a
non,
a
non-referenced
document
where
we
give
more
like
architecture
or
overview
of
what
City
events
is
and
try
to
you
know
give
our
higher
level
understanding
of
what
this
is
about
and
then
the
spec
is
we
link
into
the
spec
from
their
occasionally
and
so
that's
but
yeah,
and
look
at
a
more
formal
user
journey.
D
B
H
H
H
H
It's
probably
best
to
think
about
that
as
as
at
least
two
different
audiences,
so
you've
got
a
browsing
audience
you
may
or
may
not
be
fully
conversant
with
all
of
the
issues
and
then
you're
going
to
have
a
highly
technical
audience.
That
does
understand
the
issues
who
are
looking
for.
You
know
reference
implementation
pointers
because
they're
they're
planning
to
actually
do
something
with
this.
With
this
specification.
C
H
And
those
typically
are
not
comfortable
bedfellows,
so
you,
you
need
to
split
that
content
up.
C
H
That
you're
you're
allowing
people
to
to
comfortably
browse
and
get
the
concepts
without
scaring
them
off
with
too
much
detail
specification.
D
Yeah
I
guess
that's
I
mean
what
we
have
today
is
the
white
paper,
but
that's
it's
a
PDF
hosted
in
our
gate,
repo
for
now,
but
that's
I
think
what
Emma
was
saying.
I
mean
we
could
try
and
get
some
of
that
content
that
we
have
in
the
white
paper.
That's
meant
for
more,
like
browsing
type
of
audience
or
someone
who
wants
to
know
what
City
events
are
and
decide.
D
If
there's
something
interesting
for
me
or
not
to
dive
in
and
then
yeah,
so
that
the
primer
I
guess
it's
more
gives
you
Dives
more,
gives
you
more
architecture
decisions
and
how
we
do
things
and
the
specification
is
the
reference
when
you
go
and
look
for
like
yeah
I'm
implementing
these,
as
is
a
line
with
the
spec
or
not
okay,
yeah.
We
are
at
time
now,
but
thanks
a
lot.
Terry
I
think
this
is
very
good
coverage
of
what
we
need
to
do.
D
Yeah,
so
the
main
concerns
that
we
we
have
I
think
that
we
discussed
are
like
we
we
do
want
to
to
do
this.
We
are
very
limited
bandwidth
on
our
side,
in
terms
of
you
know,
work
that
we're
doing
ourselves
ourselves
to
to
make
this
happen,
but
yeah
we,
we
really
would
like
this
to
to
to
take
place.