►
From YouTube: CDEvents Working Group - Dec 13, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
C
C
C
B
Okay,
I
guess
it's
free
past
tense.
Maybe
it's
a
good
time
to
start.
It's
all
right!
Yeah
I
always
tell
my
everyone
to
the
city.
That's
working
group.
B
My
name
is
Andrea
Creek
Sally,
I
work
for
IBM
and
today's
December,
the
30th,
and
this
meeting
is
recorded
as
we
should
Retreat
designers
I
think
the
participant
list,
okay,
I,
set
up
a
small
agenda
and
that
they
are
more
things
to
be
discussed
refer
to
it
as
we
go
so
first
I
wanted
to
go
through
kind
of
action
items
from
last
time
and
I
said,
but
all
variety
last
day
meeting
discussed
it's
the
current
time
and
it
does
not
work
for
Eric
Superman
conflict.
B
Oh
I
see
Emil
and
Enrique
already
vote,
but
it's
great.
So
hopefully
we
get
some
more
roads
and
then
we
can
move
the
meeting
before
next
week.
So
we
cannot
new
meeting.
B
And
the
other
thing
we
discussed
last
time
was
the
top
three
priorities.
So
this
was
after
the
presentation
of
the
DLC.
Previously,
requests
have
to
have
like
a
list
of
top
three
priorities
for
when
asking
for
new
contributors
to
join
the
project,
and
so
we
discussed
three
things:
python
SDK,
Java,
SDK,.
B
And
kind
of
surface
existing
POC
migrate
them
to
cdmi
0.1,
so
I
created
this
top
free
label
with
the
stock
free,
unwanted
view
in
the
existing
CD
events,
releases,
project
and
I've
put
in
here
the
free
items
we
discussed
so
for
the
PLC.
There
was
no
issue
so
I
created
a
new
issue
specifically
points
to
the
existing
pocs
and
seek
events
so
and
yeah
so
make
sure
it's
okay,
they're
hosted
in
sick
events.
They
use
an
old
version
of
the
SDK.
B
B
B
A
D
B
Don't
remember
yeah
if
you
can
find
it.
Maybe
we
can
link
it
in
here
or
just
close
this
one
and
add
the
label
to
the
other
one.
B
B
All
right,
finally,
we
had
some
good
discussion
about
connecting
events
last
time,
so
I
started
a
new
issue
and
document
to
start
tracking
the
work
and
the
discussion
on
that.
So
this
is
connecting
events
issue.
B
It
links
to
my
original
issue
link
for
this
events
to
consume
events
and
to
the
issue
band
created
about
the
global
ID
and
I
created
a
new
design
document
where
I
started,
putting
some
some
content,
I
kind
of
copied
a
bit
of
the
template
we
use
on
technical
site,
but
yeah
basically
provide
summary
motivation
goals,
not
goals,
use
cases,
requirements
related
work
and
then
implementation
or
if
there
are
multiple
implementation
possible
so
Alternatives,
and
for
here,
foreign.
B
Capture
for
each
of
the
alternatives,
kind
of
description,
pros
and
problems,
but
it
involves
in
terms
of
spec
changes,
SDK
changes
and
tools,
adoption
yeah
and
then
we
can
hopefully
pick
one
or
two
they're,
not
necessarily
exclusive,
like
yeah,
excluding
each
other.
B
C
B
And
in
terms
of
updates,
City
events.tet
PRS
from
Terry
had
been
merged
thanks
anyway,
reminding
me
that
you
should
merge
them,
so
I
just
merged
them
a
few
minutes
ago.
Hopefully.
C
A
B
C
C
B
B
B
D
B
B
Yeah
so
other
things
that
I
what
we
could
do,
we
could
continue
discussion
on
connective
events.
If
you
wanted
to,
we
could
discuss
last
time.
We
brought
up
released
events
as
well,
which
is
an
interesting
topic
we
should
discuss
about
at
some
point.
So
any
a
favorite
option,
yeah.
D
Could
we
maybe
revisit
also
the
scope
of
the
zero
two
release?
What
we
want
to
be
want
to
get
in
there,
this
the
people
on
this
call,
if
there
are
any
any
preferences
on
what
to
prioritize.
Of
course,
connecting
events
is
something
we
have
discussed
that
might
end
up
there,
unless
it
will
take
too
long
to
discuss
it,
but.
D
B
D
The
structure
of
this
is
not
as
copied
from
the
zeroth
One
release,
but
then
we
have
the
roadmap,
which
also
has
a
label
for
zero,
two
I
believe,
no,
maybe
it
doesn't
I
think
that's
some
kind
of
property
saying
it
was
aimed
for
zero.
Two
didn't
we.
D
D
Infinity
but
there's
no
label
for
it,
so
we
can't
really
see
in
the
roadmap
which,
oh
can
you
add,
the
Milestone
okay
I
was
thinking
in
the
roadmap
view,
if
you
could
add
the
milestone
column
to
start
and
reveal
the.
B
D
Today,
but
there
should
be
a
milestone
as
well
yeah
and
then
you
could
get
yeah
there.
You
get
zero
two,
so
we
can
see
if
anything
from
the
rest
of
the
roadmap
should
also
be
in
zero
two
or
if
we
should
move
things
away
from
conservative,
because
we
don't
think
it
will
be
possible
to
have
it
there
and
I'm
not
sure
which
way
to
do
this,
if
we
should
do
it
from
the
roadmap
or
from
the
other
and
and
also
in
the
roadwork.
D
D
B
D
C
B
D
C
D
C
D
D
C
D
B
D
B
I
think
roadmap
is
yeah,
but
for
me
it's
for
like
the
next
year
or.
C
B
All
foreseeable
future
yeah,
so
maybe
we
could
have
like
the
2022
broad
map,
a
2023
world
map,
or
things
like
that.
That
says,
but
yeah
I
I
understand
here.
A
D
B
B
Payload
and
versioning,
this
is
the
issue
that
the
band
created
and
I
left
a
comment
asking
whether
is
this
something
we
can
close
and
something
that
custom
data
addresses
or
if
there
is
any
scope
left
but
I
think
for
now,
until
we
get
an
announce
where
I
would
keep
it
in
the
world
map.
D
B
You-
and
this
is
the
Java
sdk1,
which
is
definitely
a
part
of
the
remote,
but
we
don't
have
a
roadmap
label
on
the
Java
or
the
Java
SDK
three
plus.
So
we
need
to.
B
D
I
need
to
check.
There
is
a
you
can
have
a
default
repository,
so
any
new
repository
will
get
the
same
labels
lists,
but
there's
probably
nothing
such
as
a
global
label
which
can
be
done
added,
which
then
and
works
for
all
sub
repositors.
D
D
Or
do
you
see
them
that
we
should
use
that
of
GitHub
as
a
template
repo
in
some
way,
because
I
don't
think
it's
done
that
way
by
default?
And
if
you
would,
then
they
would.
Of
course
those
Superstars
will
get
the
same
files
as
dot
GitHub
has
and
we
don't
I,
don't
want
the
profile,
for
example,
to
be
analogs
today
in
all
repositories
that
were
created
on
the
door.
D
D
D
D
Exactly
so,
that's
not
what
we
are
to
hear.
That's
yeah,
so
I
think
a
synchronization
thing
or
a
Global
configuration
external
thing.
I
think
that
there
are
at
least
two
different
GitHub
projects
which
can
handle
this
kind
of
configuration
as
code
on
top
of
all
your
repositories
in
organization.
Somehow.
D
I,
don't
know,
maybe
not
in
your
roadmap,
yet
okay,
it
I
think
it
requires
someone
to
be
interested
in
working
right
and
if
there
is
no
one
yet
well,
I
wouldn't
like
to
remove
it
to
close
it.
So
that's
the
option
then
I
think
we
should
have
to
enrollment,
but
I
wouldn't
say
that
it
would
happen
anytime,
coming
in
six
month,
sales.
B
So
I'm
gonna
leave
it
there
I
think
we
requested
events
and
things
okay,
so
this
is
something
we
discussed,
so
this
is
about
like
imperative
events,
learning
number
correctly
and
I
think
we
actually
write
wrote
now
that
the
expect
that
we
want
to
use
the
clarity
events
yeah.
B
D
B
Property
to
the
context,
this.
C
B
D
We
didn't
do
it
right
yeah.
This
is
quite
straightforward.
To
just
add
it.
If
we
want
it,
we
should
probably
discuss
that
sometime,
but
it
should
be
in
the
roadmap.
I
think
it.
D
D
B
Okay,
python
wants
quite
a
readme
yeah.
Okay,.
B
Yeah
sorry
I
didn't,
while
they're
in
the
right
color
this
way-
and
this
is
a
SDK,
go
question:
how
do
we
represent
the
transformation
in
between
difficult
event
in
a
city
event.
B
No
I
think
he
refers
to
probably
to
the
object.
This
is
an
SDK
question,
so
if
you're,
if
you
receive,
if
you
receive
a
cloud
event
or
you
can
convert
it
into
a
city,
that's
object.
Probably:
okay,
okay,
I
guess
the.
B
I
know
celebrities
experimenting
with
the
SDK
to
go
and
parsing
City
events,
how
to
see
so
receiving
CD
events
for
the
SDK
military
is
any
issue.
Let
me
check.
B
Yeah,
this
is
lean
up.
C
B
B
D
Is
what
we
should
do
today
to
do
Define
a
scope
for
zero
two
or
if
we
should
have
a
technical
discussion
on
some
of
the
topics
General?
Maybe
we
should
ask
Eric
if
you
have
any
preference
what
you
would
like
to
get
most
from
this
meeting.
D
A
D
D
B
D
C
B
I
agree
with
your
initial
statement:
I
think
it's
this
early
in
the
project
is
probably
there
is
no
need
to
have
like
regular
Cadence,
but
I
also
agree
last
thing
that
you
mentioned
that
maybe
having
at
least
some
kind
of
time
frame
helps
us,
you
know
kind
of
moving
towards
the
target.
B
Otherwise
it's
maybe
harder
to
to
move
forward.
B
But
yeah,
so
we
don't
we
don't
have
to,
but
maybe
we
we
could
try
to
set
an
indicative
time.
Thinking
I
think
you
is
April.
B
Would
it
make
sense
to
try
and
Target
something
like
March
or
end
of
March
2023
for
this
back
and
delivering
the
update
of
the
sdks
so
that
when
we
are
in
April
May,
we
we
have
something
to
to
show
okay.
D
Yeah,
yes,
he's
updated
yeah
to
not
lose
interest
from
from
our
surrounding
interested
stakeholders,
so
we'll
just
call
them
I
think
we
need
to
have
some
kind
of
release.
I
would
say
every
quarter
would
be
good,
but
at
least
I'll
be
half
a
year.
D
A
I
think
so
too,
I
think
and
also,
as
we
mentioned
before,
like
the
I'm.
Definitely
the
kind
of
person
who
works
best
with
some
sort
of
deadline.
I,
don't
work
really
well,
either
but
or
anyway,
but
the
best
with
the
deadline
so
having
semi-frequent
deadlines
and
I
think
every
quarter
is
a
reasonable.
We
don't
need
to
set
a
fixed
Cadence,
but
we
have
like
a
rough
roughly
every
quarter,
something
but.
B
D
B
B
B
So
November,
so
it
would
be
then
earlier
we
are
looking
at
something
like
end
of
January,
but
yeah
I,
don't
know
with
Christmas
holidays
and
everything.
Okay,
yeah.
D
Probably
end
of
February
at
least
it
would
be
okay,
I
mean
if
you
would
have
something
end
of
February
and
then
maybe
with
a
stretch.
We
could
have
the
zero
to
three
before
the
that
there
will
be
some
kind
of
see
this
Summit
I
think
in
May
with
the
open
source
Summit
in.
D
C
B
B
D
D
C
B
A
A
D
I
have
a
question
that
related
to
this
top
three
assignment
so
top
three
that
we
said
there.
If
someone
looks
at
our
top
three
list
and
sees
that,
oh,
that
ticket
is
already
taken
by
Eric.
Will
that
mean
that
they
don't
want
to
to
contribute
I,
think
or
what?
How
will
people
see?
That's
the
link
or
will.
A
C
B
B
I
I
mean
we
can't
clarify
I
guess
this
is
just
an
initial
attempt.
The
idea
is
when
we
maybe
did
you
see-
to
provide
a
kind
of
template
or
format
for
for
projects
to
provide
this
information.
I
think
it
would
be
good
to
like
contact
person
associated
to
the
issue,
so
at
least
some
of
the
wants
to
contribute.
They
know
who
to
talk
to
and
ASMR
they
can
reach
out
reach
out
to
and
say.
Okay
I
would
like
to
contribute
to
these
I
mean,
of
course
they
can
contribute
to
that.
B
A
Pretty
well
in
October
or
hacktoberfest
that
worked
pretty
well,
because
I
had
some
people
reach
out
to
me
to
help
with
some
part
of
the
Python
SDK.
D
A
D
But
couldn't
we
have
to
do
it?
The
simple
way
to
say:
I
mean
in
text,
along
with
the
table
or
whatever,
where
these
top
three
tickets
are
shown
on
some
CDF
site
that
could
it
could
be
said
that
if
you
want
to
contribute
and
the
ticket
is
already
assigned
to
someone,
please
reach
out
to
that
person
to
see
how
you
can
help
out.
B
D
Because
I
think
it's
still
good,
that
Louis
is
not
as
on
top
of
this,
since
you
have
started
it
and
since
you
have
the
ideas
on
how
to
structure
it.
Yes,.
C
D
C
C
B
Yeah,
that's
not
I'm,
not
sure
it's
something
I'm
put
on
the
top
of
my
priorities.
This
is
an
issue
I
created
a
time
ago.
B
Yeah
I
think
the
the
the
the
idea
was
to
do.
We
want
to
to
have
like
some
format
specification
for
the
source,
something
more
strict
and
that
we
have.
D
Today
but
that's.
B
D
D
B
D
B
Okay,
all
right
abbreviations
for
all
event,
types.
D
Maybe
if
we
wanted
that
level
or
are
these
not
that
maybe
there's
another
ticket
in
the
safe
area,
maybe
that's
because
this
is
more
for
a
build.
We
already
called
it.
So
maybe
this
is
not
that
and
then.
B
I
mean
hell
aligning
with
the
work
of
the
other.
Six
does
not
give
us
much
value
in
terms
of
pictures.
We
can
provide
with
a
CS
with
a
spec,
but
there's.
B
D
Yeah
and
I'm
not
sure
that
the
last
word
is
said
in
its
interpretability
document
either
I
mean
it's
as
small
as
yesterday
proposal
from
from
one
person
which
has
been
reviewed,
of
course
by
some
persons,
but
there's
no
real
consensus
in
the
CD
Foundation
that
these
are
the
actual
names
we
should
use
for
everything,
so
they
might
change
again
when
that
discussion
is
brought
up
the
next
time,
maybe,
but
at
the
same
time,
of
course,
the
later
we
do
this,
the
more
places
we
need
to
change
in
I
mean
Beyond
hdk
code
and
wherever
maybe,
which
might
be
hard
later
on.
B
I
I
guess
at
least
staying
on
top
of
this
trying
to
answer
this
question
on
a
regular
basis.
It's
probably
something
that
we
should
do.
You
know
it's
part
of
every
milestone.
D
Yeah
I
believe
real
estate
is
something
in
a
documentation
saying
that
we
aim
to
be
aligned,
but
we
might
not
be
yet
something
like
that.
We
have
stated
in
the
documentation
or-
and
that's
still
true,
but
it's
not
enforced,
neither
from
us
nor
from
seek
interoperability,
but
it
needs
to
be
fully
aligned.
Yet.
B
Okay,
so
is
it
okay
to
keep
this
in
to
remind
us
about
completely
checking
this,
and
we
can
check
on
a
regular
basis
and
decide
whether
we
keep
it
on
this
Milestone
and
move
it.
D
B
Okay,
so
let's
let's
switch
to
0.3,
then
I
think
so.
Okay,
so
incident
at
least
a
certain
initial
level
of
specification.
That's
something
that
I
would
really
like
to
to
to
have
in
for
the
Dora
metrics,
so
I
I'm
happy
to
put
my
name.
C
B
And
keep
getting
there
so
at
the
repository,
including
last
change,
to
build
events.
B
B
Yeah,
it
depends
I
I,
don't
think
there
is
any
pressing
to
address
this
specifically
right
now,
so
I
will
remove
it.
Yes,.
B
Secure
software
supply
chain
aspect:
it's
definitely
something
interesting
to
have
not
something
that
I
would
be
able
to
work
on,
probably
within
a
0.2
time
frame.
Unless
someone
is
because
I
said
in
taking
this
up.
D
B
Something
but
I
think
it
makes
sense
to
do
it
if
we
kind
of
have
a
POC
to
there's
some
kind
of
even.
C
C
B
C
B
That
looks
when
the
pipe
the
build
is
done
and
it
goes
and
signs
the
artifacts,
and
then
it
adds
some
annotations
to
the
the
build
information
to
say:
okay
yeah
this
is
signed
now,
and
so
what
I
want
to
do
there
is
to
send
an
event
so
that
someone
could
capture
that
event
and
react
to
that,
as
opposed
as
reacting
to
the
artifact
was
built
because
yeah
you,
if
you
want
to
assign
an
artifact,
you
want
to
react
to
those.
So
that's
something
that
I
was.
C
B
But
the
time
frame
for
that
would
be
I
mean
I
can
I
can
try
to
keep
it
in
0.2
tentatively.
D
Yeah,
it's
probably
higher
not
highest
priority
for
zero
two,
but
we
could
try
to
have
something.
Maybe
it's
zero,
two
I
guess
this
would
be
like,
as
I
said
before,
like
an
epic
level
thing
which
could
contain
sub
it's
sub
issues
and
some
sub
issues
might
be
sold
in
this
area,
but
for
sure
not
the
whole
thing.
B
D
Gosh
predict.
D
B
All
right,
foreign.
B
C
B
Yeah:
okay,
there's
one
minute
left.
B
You
find
different
type
of
tests
tests
in
City
events,
so
this
is
also
partially
related
to
software
supply
chain
aspects.
We
have
anything
events
like
security,
scans
and
so
forth,
but
there
are
also
other
type
of
events
like
unit
tests,
end-to-end
tests
and
classic
test
and
so
forth,
and
maybe
there's
some
chat
with
a
cube
test.
Folks,
if
you're
interested
in
what
City
events
could
do
for
them,
but
there's
been
no
no
follow-up.
After
the
initial
discussion.
B
C
B
At
nine
now
do
we
want
to
continue
this
going
going
for
this
for
the
next
meeting?
Maybe
we
could
use
some
time
from
the
sick
events
meeting.
If
you
don't
have
anything
else
in
schedule,
yeah.
D
It's
fine
for
me
and
I
think
once
we
have
a
fixed
list
of
things,
we
want
to
work
on
towards
serial
two.
It's
also
easier
to
to
sell
that
so
to
the
community
or
to
to
publish
that
so
that
other
other
people
can
see
where
they
can
contribute
if
they
want
to
help
out
in
zero.
Two,
so
I
think
it's
valuable
that
we
do
this
now
or
not.
Today,
then,
of
course,
obviously,
but
maybe
continuing
on
the
Sig
meeting
on
Monday.