►
From YouTube: CDEvents Working Group - Dec 19, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
C
A
D
B
A
Well,
he's
90
years
old,
so
if
but
I
think
it's
fourth
grade
would
be
in
UK,
because
it's
born
late
in
September.
So.
D
A
B
B
B
A
Right
makes
me
hi.
C
E
C
B
A
So
so
we
have
okay.
B
A
Week
we
have
the
sick
events
meeting
in
the
afternoon.
I
won't
be
able
to
attend
that
so
I
don't
know
if
there
is
any
plan,
as
you
were
saying,
maybe
we
can
cancel
it.
If
we
don't
have
an
agenda
depends
on
how
it
goes
today,
with
the
planning
yeah.
B
C
C
Yeah,
you
would
take
that
first,
maybe
so
we
know
what
what
meetings
to
plan
for
during
holidays
and
later
because
I'm
a
bit
of
course
a
slightly
different
people.
Maybe
coming
to
these
meetings
to
the
Sig
meetings,
there's
normally
a
bit
broader
audience,
maybe
yeah
yeah.
B
C
C
I
still
think
it's
valuable
to
have
those
big
meetings,
but
maybe
when
we
start
after
New
Year's,
if
we
should
change
the
time,
I
don't
know
over
the
same
week
or
the
day
before
the
the
ordinary
vocabulary
meeting
as
well
on
Tuesday.
So.
A
C
C
B
C
C
A
Makes
sense
to
me
I
think
we
can,
like
you
said,
make
it
clear
in
the
invitation
that
this
is.
These
meetings
are
happening
if
we
have
an
agenda
set,
but
still
I
will
still
keep
them
in
the
schedule.
So
if
someone
wants
to
do
a
presentation,
we
have
the
gender
and
we
have
the
debates
and
one
can
put
their
agenda
in
there
without
looking
for
a
date
and
time
you
know,
which
is
all
like
an
extra
hurdle.
A
Okay,
so
maybe
I
can
add
some
comments,
or
we
can
have
some
comments
on
the
on
the
invite
about
this.
For
this
meeting.
E
A
And
then
I
think
we
one
today
and
then
the
next
one
would
be
January.
The
second
yeah
I
will
be,
okay,
I
will
be,
I
will
be
off
as
well
and
I.
Don't
think
we
have
any
specific
agenda
for
that
day.
So
I
would
say
we
should
just
cancel
that
one.
B
C
A
Okay,
the
following
seek
events
meeting
would
be
then
later
in
January
or
the
seventh
yeah
I
know
we're
putting.
A
C
B
E
E
B
A
So
shall
we
look
at
the
planning,
then.
B
B
A
We
were
going
through
all
these
issues
and
decide
what
we
want
to
have
in
zero
for
two,
what
we
want
to
have
and
zero
three
or
later
and
trying
to
get
the
assignees
so
linked
produced
events.
We
already
looked
at
python,
SDK
abbreviations
incidents,
sort
of
secure,
Center
supply
chain
aspects,
I
think
all
these
we
discussed
last
time.
A
A
C
A
That's
fine,
okay,
trying
to.
B
D
C
B
C
The
result
is
on
on
the
issue
number,
the
ones
that
have
the
same
Milestone,
the
same
labels.
So
we
we
get
the
newest
on
on
in
the
bottom
or
a
top
or
something
if
there
are
any
new
ones,
I
mean
yeah
the
multiples
of
obvious,
but
they
should
number
there.
So,
but
then
we
sort
of
name
right
if
we
would
sort
in
the.
B
C
C
B
A
B
C
B
D
Or
is
this
stuff
like
we
were
talking
about
composition,
events
and
those
kind
of
things?
Is
that
what
we're
referring
to
here.
C
B
D
Even
okay,
it
changed
proposal
rather
than.
D
Right
yeah
I
remember
the
discussion
that
it's
called
the
change
and
I
think
that's
what
it's
called
in
Garrett
for
instance,
but
it's
not
actually
a
change
until
it's
merged.
Then
it
is
a
change
and
I
think
we
discussed
yeah.
Maybe
we
should
call
it
change
proposal.
C
A
A
Maybe
we
should
say
be
connected
which
yeah
connected
to
the
other
one
and
say
we
should
do
this
only
when
we
do
the
other
one.
C
A
B
A
B
A
E
A
C
Because
I
think
it's
maybe
still
a
little
bit
confusing
that
we
call
is
a
subject
when
the
subject
means
something
else
in
the
in
the
actual
City
events
type
definition.
There
is
just
one
dream:
well,
that's
not
really
correct
either,
but
no
I
was
more
thinking.
When
we
have
multiple
events
for
the
same
subject,
it
will
maybe
make
it
easier
to
see
that
well,
the
subject
object
in
that
event
is
the
same
for
all
of
them.
A
Right
so
to
have
like
the
the
fixed
part,
that
is,
you
know
all
events.
C
It's
a
little
bit
related
to
the
connected
events,
discussion
as
well,
and
because
at
least
as
we
have
it
in
Eiffel,
we
don't
read.
We
mentioned
the
subject
for
every
event:
I
mean.
If
there
is
a
link
we
can.
C
We
can
link
there
instead
and
say
that
well
for
the
subject
definition,
you
can
go
see
this
earlier
event
and
then
this
event
just
talks
about
the
predicate
models.
That's
one
way
to
do
it
not
saying
that
we
need
to
do
it
that
way,
but
splitting
the
subject
and
predicate
would
make
it
more
piece
to
discuss
those
things.
Maybe
an
under
make
it
clearer
in
the
in
the
schemas
as
well.
What
is
changing
between
different
events
on
the
same
subject
and
what
is
not.
C
And
this
is
also
one
of
those
things
that
shouldn't
change
multiple
times.
Of
course,
if
we
do
this
change,
we
should
do
it
once
and
maybe
it's
a
bit
premature
to
do
it
now
from
zero.
Two
again.
B
Yeah
yeah.
A
I
think
maybe
we
can
maybe
we
can
postpone
it
from
now
to
a
point
where
we
get
like
a
use
case
where
we're
I,
don't
know
searching
for
events
or
trying
to
do
some
change
where
we
see
this
with
actually
bring
a
change
in
what
we
can
express
or
I
don't
know.
A
I
think
I
see
your
point,
I'm
not
sure
yeah
I'm
not
sure
right
now
for
the
scope
of
zero
two.
This
would
bring
us
more
value
in
terms
of
the
use
cases
we
can
address.
A
C
A
A
I
guess,
I
think
I'll
assign
myself
to
it
since
I've
been
I
started
to
work,
internet
yeah,
that's
good,
and
next
one
payload
and
versioning
I
think
the
only
yeah
we
discussed
this
and
then
like
what
the
question
whether
this
is
addressed
by
custom
data
or
is
anything
more
that
we
need
to
do
here
so
I'll
just
leave
it
in
there.
It's
an
open
question
to
the
answer.
I
would
like
to
get
an
answer,
so
we
can
close
it
so
consider
it
in
band
pledge.
C
E
A
See
commonalities
across
different
subjects,
but
I
don't
see.
This
is
anything
really.
B
C
A
B
C
Out
there,
which
is
somewhere
number
51
number
42.
C
A
B
A
Okay,
you'd
have
to
see
the
event
translation.
A
So
this
well
I
can't
say
for
I
mean
Brad
and
debuff
have
been
working.
B
A
B
C
A
B
C
E
C
B
C
A
A
B
C
This
issue
is
currently
in
a
community
here
at
policy,
but
it
should
probably
move
to
the
website
to
operate.
But
then
that's
not
as
important
was
there
an
issue
written
for
the
TLC
feedback,
camera
or.
A
Bank
not
okay
check.
Let
me
check
the
connection
point.
E
A
Right
so
I
think
this
is
something
that
would
be
good
to
have
as
soon
as
possible,
and
just
you
know
not
sure,
if
that's
something
I
at
least
personally,
if
they're
trying
to
work
on
within
that
0.2
time
frame,.
C
B
C
Think
it
requires
also
some
someone
driving
it
and
someone
with
with
the
skills
really
driving
it,
as
well
as
a
good
idea
on
what
it
should
contain.
I
think
it
should
be
a
short
video,
obviously
so
it's
it
doesn't
take
too
much
time
to
consume.
It
I'm
not
exactly
sure
what
it
should
cover
and
I
mean
that
the
spec
is
is
moving
a
bit
not
too
much,
but
but
still
so
it
shouldn't
maybe
contain
too
much
details
from
the
species
there.
Otherwise
we
need
to
redo
it.
B
C
A
I
mean
I
I.
It
could
be
something
like
Okay,
maybe
some
diagram
with
animation.
B
A
Show
like
the
idea
of
the
two
use
cases,
maybe
like
of
the
pocs
that
we
have
in
place.
Maybe
yes
like
an
animated
diagram
that
shows
one
the
the
techtone
plus
Captain,
plus
Spinnaker,
POC
kind
of
the
flow
and
another
one
that
can
show
like
the
torometric
type
of
use
case.
C
C
A
It
be
okay
to
try
and
put
it
on
0.3
I
think
it
would
be
really
helpful
for
sure.
E
C
A
Okay,
I
would
say,
for
is
it
okay?
If
I
just
create
a
0.3
milestone
for
this
okay
Simplicity
for
now,
and
then
we
can
revisit
this,
maybe
instead
of
Meister,
we
should
use
labels
which
are
across
repo.
So
we
don't
go.
I
need
to
go
and
create
myself
everywhere,
but
I
don't
know
minutes.
A
B
A
B
C
A
Okay,
well
I
mean
we
can
maybe
set
it
for
myself
0.2.
It's.
A
B
A
E
A
A
Yeah
yeah,
that's
basically
it's
basically
saying:
if
you're
writing
an
SDK,
then
you
should
be
passing
these
tests
today,
shared
across
all
the
sdks
and
that
are
based
on
the
specification
based
on
the
schemas,
probably
right.
Okay,.
E
A
C
A
B
A
Format
for
I
mean
the
format
for
creating
the
event
would
be
different
for
just
the
case,
because
the.
B
B
C
Yeah
I
think
I
think
that's
template
events
or
such
could
then
be
maybe
stored
in
the
city
than
three
point
itself,
and
then
just
a
requirement
on
the
SDK
is
that
it
should
be
possible
to
generate
all
those
different
event
types.
There
are
events.
C
Yeah,
but
what
you're
saying
is
that
it
will
be
a
more
low
level,
implementation
or
no
low
level
description
than
what
is
in
this
number
four
issue
here.
This
is
very
high
level,
just
a
few
lines
on
different
aspects
of
the
sdks,
but
the
other
one
is
more
detailed
on
what.
A
A
A
A
B
A
It's
for
consuming
I,
think
SAS
when
they
made
their
presentation.
They
had
a
similar
component,
which
was
Central
to
their
architecture.
A
That
basically
was
able
to
receive
events
and
receive
them
from
multiple
services
and
even
accumulate
them,
and
then
say:
okay!
Well,
if
I
received
these
X
events
with
this
capabilities
of
our
this
sorry,
this
specific
Fields
values
and
so
forth,
then
I
would
trigger
the
next
step
in
the
in
the
workflow.
A
The
kind
of
policies
that
you
can
set
on
a
number
of
events,
not
single
events
only
and
I-
think
that's.
That
might
be
something
valuable
too
like
that
was
a
reusable
component.
But
if
you
want
to
adopt
City
events,
you
can
put
this
in
your
architecture
and
then
it's
basically
where
you
define
your
your
policies
for
workflows.
A
C
Yeah,
so
this
is
intended
to
be
part
of
your
production
system.
I
mean
to
be
in
production
with
your
cicd
system,
then
I
was
thinking
if
this
is
somehow
related
to
the
like.
We
have
the
cloud
events
player
that
we
use
if
there
should
be
a
corresponding
City
events
player,
but
that's
more
for
troubleshooting
and
visualizing
or
visualizing
your
event
chains
as
a
troubleshooting
thing
or
something.
This
is
more
something
that
should
be
in
production.
The
magnitude
part
of
your
system.
A
A
C
A
A
B
C
I
think
we
So
speaking
about
pocs.
By
the
way,
should
we
somehow
push
for
those
to
be
updated
before
we
go
to
zero
two,
or
is
it
okay
that
they
are
not
yet
there
I
mean?
Should
we
put
our
efforts
there
instead
of
progressing
the
the
schema
itself,
or
what
do
you
think
and
that
the
PLC
right
now
is
very
old?
We
have
the
ticket
area.
A
A
But
at
least
having
the
basic
poc
in
there
and
the
in
the
CD
event
organization,
I
think
is
it's
something
that
would
be
good
to
have.
A
C
C
Do
you
see
you
know
to
Upstream
it
to
the
Spinnaker
community?
The
changes
he's
done
there
with
some
some
changes
to
it,
but
that's
still
for
the
old.
A
B
C
A
A
Yeah
yeah,
that's
fine,
I
think
the
roadmap
is
not
like
a
contract
saying
that
we
wouldn't
do.
That
I
mean
that's.
A
We
we
should
have
like,
but
that's
what
we're
doing
now:
I
guess,
building
that
2023
roadmap,
all
right,
so
I
think
it's.
A
Yeah
everything
rush,
yeah
I
mean
we
can
put
it
in
0.3.
If
you
want
to
just
leave
it
open.
What
do
you
think.
A
All
right,
so
this
is
the
Java
SDK,
so
this
is
a
in
our
top
three.
So
I
think
we
should
put
it
in
0.2,
yes,
and
we
don't
have
the
security
to
Milestone
there.
So
let's
go
and
create
it.
E
C
This
one
actually
know
that
not
to
London
with
Adam
Yolanda's
teammate
is
working
on
it.
A
Okay,
do
you
know
Adam's
get
up,
handle.
C
B
C
B
E
A
Good,
so
at
schema,
URI
property
to
the
context
right
is
something
we
discussed
already
last
time
or
not
I,
don't
remember.
A
B
A
It's
something
that
we
should
do
most
likely.
E
B
A
I
was
going
to
say
that
I
think
there
is
enough
contact,
sorry
enough
scope
and
0.2
not
to
include
it,
even
though
it's
something
that
most
likely
you
want
to
do,
but
yeah
what.
C
B
A
So
this
is
part
of
the
roadmap
anyways
everything
that
is
in
here.
So
it's
something
that
someone
is
looking
for
things
to
do.
That's
it's
in
this
list
of
things
that
we
reviewed
and
definitely
want
to
consider
at
least
yeah.
B
C
C
A
B
D
Yeah
me
too.
Otherwise,
if
we
need
to
end
the
meeting,
I
will
take
all
the
python
SDK
stuff
and
set
it
to
0.2
and
assign
it
to
me.
I
saw
some
old
issues
down
at
the
bottom
that
weren't
designed.
D
A
Fine
yep,
yes,
okay,
then
let
me
just
put
this.
A
A
B
A
D
D
A
B
A
So
that
that
was
really
useful,
I
think
we
have
now
here
our
route
map
and
I
think
this
is
scores
back,
and
this
is
SDK
I.