►
From YouTube: CDEvents Working Group (EMEA/APAC) - March 13, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
Yeah
I,
don't
know.
I
know
Evan,
wanted
to
add
something
on
the
agenda
about
the
Java
SDK
uh-huh,
okay,
but
I,
don't
know
if
it
was
for
today's
meeting
or
maybe
future
one
okay.
B
Yes,
we
can,
we
can
get
started
and
I
mean
people
join
us
along
the
way.
I
think
it's
fine
yeah,
that's
good!
Maybe
just.
E
B
Course,
yeah,
no,
no,
no,
no
I
mean
if
they're
special
topics
you
would
like
to
add
to
the
agenda
feel
free
to
do
so
as
well.
D
Nothing
at
the
moment,
as
I
said,
I
think
we're
we're
proceeding
ahead
with
the
integration
with
the
existing
latest
spec
on
the
plugin
that
we're
building
and
again
I
know
from
my
previous
discussions.
Andre
I
just
wanted
to
get
more
plugged
in
and,
as
I
said,
I
have
some
of
the
squad
available
to
help
with
some
low
hanging
through
but
yeah.
We
want
to
get
more
involved
now
that
we're
sort
of
a
bit
better
set
up
on
our
side.
D
So
it's
just
really
re-establishing
communication
within
these
meetings
and
seeing
what's
going
on
with
the
latest
roadmap
as
well.
A
D
We're
going
through
the
re-hosting
process,
I
think
the
basically
there's
the
Jenkins
Cloud
events
plugin.
We
basically
we're
looking
do
we
adopt
the
Plugin
or
re-host
it
and
it
looks
like
they
want
to
re-host
the
the
plugin.
So
that's
the
process,
that's
going
on
in
the
sides,
but
internally,
where
we're
building
out
the
the
Baseline
that
we
can
put
forward
for
the
obviously
the
the
required
reviews
and
just
establishing
a
new
project
effectively
for
that.
A
D
As
I
have
anything
that
we
can
tie
to
an
issue,
Emil
I'll
I'll
pass
that
back
with
you.
B
Okay
yeah,
so
we
have
this
project
in
another
city,
events
with
links
to
different
tickets
or
different
tools;
integration.
So
if
you
have
something
for
free
to
to
pull
it
in
here
or
share
it
here,
and
then
I
will
let
it
as
well
perfect.
D
B
B
So
for
the
agenda
today,
I
had
like
incident
events
and
then
review
the
robot
for
the
Jordan
2
SDK,
updates,
testing
events
and
well
tools,
integration.
We
I
guess
we
spoke
about
it
already.
D
B
So
we
have
an
incident
which
can
be
detected,
reported
and
resolved
and
we
have
the
corresponding
schemas
here
and
we
for
incident.
We
started
also
adding
examples
and
that's
something
that
we
need
to
bring
up
for
the
rest
of
the
events,
to
to
have
examples,
I
think
for
for
every
type
of
event,.
B
So
next
steps
for
this
would
be
to
I
guess
include
include
them
in
an
SDK
to
cut
a
release
of
the
specs,
and
maybe
they
order.
These
two
should
be
reverse
I
guess
we
might
need
to
cut
the
release
of
the
specters
and
then
include
them
with
the
SDK
or
we
could
work
on
them
parallel
and
the
other
thing
I
will
need
to
update
the
website
right
now.
We
have
here
this
groups,
so
we
need
to
have
an
extra
one
for
continuous
operations.
B
Yeah
and
I.
Think
that's
that's
about
it.
I
mean
there's
more.
We
can
do.
Of
course,
I
mean
there
is
we
can
build
the
pocs
we're
using
it.
These
events
in
terms
of
having
the
events
available,
I
think
these
are
the
main
next
steps.
B
Create
one-
and
there
is
not
a
yet
so
yeah-
that
would
be
great
thanks.
D
And
just
just
for
the
SDK
updates
is
there,
do
you
just
create
specific
I
know
you
got
to
go
the
Python
and
the
Java
one
I
know.
Sometimes
some
are
maybe
more
ahead
and
others
is
it?
Is
it
just
creating
a
specific
issue
for
that
and
allowing
the
community
pick
it
up
or
how
is
there
a
way
a
hard
one,
and
then
you
I
just
wanted
to
know
that
process
just
so.
B
Yeah,
we
don't
like
have
a
very
formal
process
right
now,
but
I
think
yeah
so
create
an
issue
for
each
SDK
and
yeah.
Let's.
D
B
Right
anything
else
on
the
incident
events,
the
question
yeah:
okay,
moving
forward,
I
I
wanted
to
look
at
the
002
world
map.
B
Since
I
think
we
are
already
at
the
day
that
we
plan
to
have
a
release
and
I
moved
a
few
other
things
that
we
know
that
we
are
not
going
to
do
out
of
the
0.2,
so
I
updated
this
0.3
table,
and
you
see
things
like
secure
software
supply
chain
aspect
and
connecting
events
are
now
under
0.3
I
hope,
that's
fine.
We
discussed
previously.
That
is
not
going
to
happen
in
0.2,
so
what
is
left
for
0.2,
apart
from
doing
the
release
itself?
B
B
In
terms
of
spec,
we
have
the
abbreviations
for
all
event
types
and
I
wanted
to
check
with
uml.
If
that's
something
still
that
you
would
like
to
have
in
this
or
we
should
move
it,
we.
A
Can
move
it
away?
I
would
like
to
have
it,
but
no
there's
no
rush
for
it.
So
let's
move
it
to
the
next
one.
Again.
Sorry.
B
No
worries
and
that's,
then
we
have
the
payload
them
versioning
I
linked
a
few
of
the
PRS
that
I
think
implemented.
This
from
my
point
of
view,
so
I
need
to
to
bring
back
the
question
to
the
band
whether
it's
fine
with
the
current
implementation,
and
we
can
close
this
or
is
any
other
issue
that
we
need
to
create,
but
I
think
from
my
point
of
view
at
least
the
scope
that
we
want
to
cover
of
the
other.
Two
of
these
item
is
is
done.
B
Available
so
I
don't
think
there
is
any
extra
work
to
be
done
in
0.2.
From
my
point
of
view
on
this
one.
B
B
Basically,
the
idea
here
is
just
to
give
an
overview
as
to
make
it
more
clear
in
that
in
the
tables
for
all
the
events,
what
the
standard
fields
are
for
the
subjects
which
is
IDE
source
and
type
so
to
Pro,
to
link
them
to
the
core,
sorry
to
the
spec
empty
so
to
the
general
specification
and
to
make
sure
the
type
is
there.
B
B
Okay,
oops
sorry
back
to
the
old
map,
I.
E
B
Right
so
and
that's
it
for
the
spec,
and
then
we
have
some
proof
of
concept
items
like
the
Torah,
metrics,
Plus
or
proof
of
concept
that
we
need
to
extend
to
include
these
events
and
also
updating
existing
POC
with
more
recent
traditional
CD
events.
B
So
to
me
this
is
kind
of
follow-up
work.
I,
don't
see
this
as
blocking
for
cutting
the
release
and.
D
B
And
then
we
have
a
bunch
of
things
in
the
SDK
areas
and
so
create
the
python
SDK
I
guess
this
is
marked
as
in
progress
and
similarly
for
the
python.
C
You
probably
should
I
will
say
this:
podcast
has
been
open
for
a
little
bit
like
for
several
months
and
I
think.
Actually
it
is
ready
to
oh
six
months.
Gosh
I
think
it's
ready
to
be
merged.
Actually
it
looks
really
clean.
C
B
B
I
think
Evelyn,
you
probably
referring
to
this
yeah
right
aligned
with
go
SDK.
C
B
B
So
I
wonder
then,
since
we
have
this
issue
on
this
side,
aligned
with
go
SDK,
yes
back
I
have
a
vote
for
closing
this
one
actually
and
saying:
let's
get
well,
the
the
SDK
has
been
created.
So
we
need
to
update
it
now,
but.
B
B
E
C
I'd
love
to
let
me
double
check
to
see
what
he
completed.
I
didn't
read
the
readme
yet,
but
I'll
put
that
I
prioritize
it
with
the
pedantic
I
was
going
to
do
that.
But
I'll
happily
was
going
to
read
me
just
a
fair
warning:
I'm,
a
terrible
speller
I
will
have
my
wife
read
over
it,
but
also
if
you
could
double
check,
I
I
kid,
you
not
ask
Jamie
I'm,
a
terrible
scholar.
You
might
just
double
check
on
the
reading,
but
I
will
happily
work
on
it.
B
Sure
no
worries
I
mean
what
we
can
do
also
I
think
on
the
go
SDK
we
have
some
linter
enabled
some
give
me
yourself
some
standard
linter
from
GitHub,
so
we
could
probably
set
it
up
for
the
python
SDK
as
well.
To
make
sure
you
know
we
we
catch
those
kind
of
things
in
CI.
B
C
Create
an
issue
actually
I
will
say
this
I
just
saw
his
current
board
request
and
the
readme
actually
looks
really
good
I'll
go
through
and
read
the
go,
SDK,
okay,
but
it
looks
really
great.
You
did
such
an
awesome
job.
C
Do
you
mind
if
everything
works
good
on
his
board
request
by
approve
and
merge
it
since
he's
the
only
maintainer
for
the
python
one
I,
don't
know
how
you
want
to
go
about
that.
D
A
E
E
D
B
C
B
So,
thanks
to
that,
even
so,
yeah
looking
forward
to
the
updates
on
the
python
SDK
and
it's.
B
And
one
thing
that
is
still
open
is
like
document
General
required
features
for
the
SDK
and
I'll.
Try
to
do
some
work
around
that
I
think
what
I
would
like
to
make
sure
is
that
you're
kind
of
consistent
across
sdks
all
right.
B
So
if
you
like
write
a
generate
a
message
with
the
go
SDK,
you
can
parse
it
with
a
Java,
SDK
and
or
the
python
SDK
and
they're
all
consistent
and
nice,
and
so
there
is
some
work
to
be
done
on
this
and
I'll
try
to
figure
out
at
least
some
basic
testing
requirement
that
we
could
have
put
in
place
that
we
could
try
to
comply
in
the
upcoming
releases
of
the
sdks.
A
I
just
had
a
note
there
in
the
tissue
Andrea
as
well
I'm
thinking
about
now
when
we
reach
0.2
what
should
be
I
guess
when,
when
creating
events,
the
SDK
is
fine
to
just
create
the
latest
version,
always
but
I
assume
that
the
consumers
of
the
events
I
mean
when
you
interpret
an
event
that
comes
on
the
channel,
you
will
need
to
be
able
to
translate
or
to
interpret
both
series
one
and
zero,
two
versions
right
now,
so
that
we
documented
somewhere
how
we
handle
those
versions.
A
B
A
A
C
Could
the
version
that
produces
the
event
and
then
whoever
consumes
it
maybe
go
to
Java,
maybe
throw
the
warning
says:
hey
this
isn't
supported,
but
we
can
extract
these
fields.
So
you
know
for
your
SDK,
older
versions
have
these
fields
if
a
field
changes
or
goes
away,
you
just
give
them
a
warning
and
then
fail
or
something
like
that.
I
don't
know.
A
Intend
to
be
backwards
compatible
between
releases,
but
now
before
we
reach
1.0,
we
might
not
see
that
was
compatible,
always
I,
think
this
release
is
compatible
with
the
older,
the
previous
one,
so
I
would
say
that
the
consumer
that
currently
only
understands
0.1
would
also
understand
CO2
releases,
I
expect
or
maybe
I
shouldn't
say.
Maybe,
since
I
haven't
written
on
the
SDK,
maybe
you
should
say
Andrea.
If
that's
the
case
or
not,
they
go
SDK.
For
example,
how
would
it
handle
an
incident
event,
for
example?
Now,
if
it
comes.
A
B
I
think
so
I
don't
remember
on
the
top
of
my
head,
but
yeah.
So
when
there
there
is
a
list
of
valid
types,
so
let
me
see
if
I
can
find
out.
B
A
B
E
B
A
A
A
B
Yeah,
but
that's
a
very
good
point:
I
mean
we
should
probably
be
consistent
across
sdks
on
on
this
Behavior
at
least
I
think
we
need
to
decide
whether
we
want
to
Parish
the
event
as
much
as
possible.
D
C
I
completely
agree,
I
think
you
should
try
to
read
it.
One
thing
I'd
recommend,
though,
is
instead
of
ignoring
trying
to
create
some
type
of
stamp
identification
where
in
the
line
it
broke.
So
when
we're
trying
to
going
back
to
last
week's
meeting
linking
events
if
you
broke
on
the
third
parsing,
so
let's
say
you
know
you
go
Java,
go
python.
Let's
say
you
broke
on
the
third
somehow
saying:
hey
I
broke
at
this
point.
C
So
if
we're
not
able
to
read
it
instead
of
ignoring
it,
just
you
know
putting
some
type
of
response
in
there
as
that
field
could
be
an
idea.
Now
that
could
be
really
complicated,
but
I
don't
know
trying
to
think
of
linking.
So
if
a
devops
engineer
is
trying
to
go
back
in
and
figure
out
where
it
broke,
it
might
help
them
navigate.
You
know,
between
the
second
and
third
event
or
at
platforms.
Maybe.
B
B
Yeah,
that's
interesting,
I
think
we
we
don't
type
until
now
any
special
concept
of
reply
messages
right.
So
we
only
have
like
the
request
messages.
We
have
not
anything
specified
for
in
terms
of
responses,
but
I
think
at
least
Cloud
events
is
by
the
cloud
event
binding.
We
use
they
do
as
some
requirements
in
terms
of
responses,
so
we
could
think
about
including
context
in
in
there
for
for
people
to
to
find
out
more
about
what,
if
I'm,
not
able
to
parse
a
message
or
so.
D
E
B
I
think
that
feels
like
yeah
there's
quite
some
work
to
be
done
in
this
area.
A
A
A
B
B
Okay,
I
would
then
move
it
to
0.3,
but
I
think
it's
something
that
should
be
yeah
I
in
the
priority,
especially
now
that
we're
you
know
starting
to
to
integrate
as
CD
events
or
these
sdks
into
into
tools.
B
B
All
right,
okay,
so
with
all
this
I
think
what
is
left
then
just
to
summarize,
is
the
the
schema
link
is
broken.
That
needs
to
be
fixed,
I.
Guess:
updating,
updates
on
the
pr
that
I
made
already
for
the
subject
field
and
yeah
I,
guess
merging
the
python
SDK,
and
that
should
be
it
in
terms
of
doing
the
the
0.2
release.
Is
there
anything
else.
C
B
A
Do
on
the
website
four
zero
to
for
releasing
with
a
versions
and
such.
B
Ees
I
think
there
are
things
that
needs
to
be
done
there
and
also
I
just
noticed
that
right
now,
for
instance,
if
we.
E
B
To
this
point,
zero
zero
dot,
zero
zero.1.1
yeah,
but
it
should
be
0.1.2
because
we
have
a
0.2,
open
and
I
guess.
When
we
do
a
release
zero
to
release.
It
then
should
point
to
the
0.2
release,
but
we
don't
have
anything
I
guess
we
have
this
releases.
A
E
C
B
Good,
so
like
the
approach
we
we
have
right
now
is
basically
we
only
show
on
the
website
the
latest
one
and
everything
else
goes
in
the
links
here
and
the
link
just
links
to
Gita
with
attack.
So
we
need
to
move
the
old
ones
to
these
links
and
then
add
the
new
one
there.
Okay,
so
going
back
to
the
spec
I
wanted
to
decide,
then,
on
a
date,
because
currently
the
Meister
is
marked
as
due
for
March
14th,
which
is
today.
A
E
C
C
I
think
I
can
get
the
python
stuff
done
in
a
week.
It's
nothing
major.
So
the
setting
up
the
basic
CI
for
linting
that
Gap
checks,
I,
might
need
or
yeah
might
take
a
little
bit
of
time,
but
I
think
I
can
get
most
of
the
Python
stuff
done
in
a
week.
B
Well,
we
can
still
move
it
forward.
If
we
don't
make
it
next
week,
then,
but
yeah
I
want
to
try
and
keep
it
not
too
far
away
in
the
future.
Then
we
can
still
try
and
get
a
0.3
version
before
the
city
con.
It
was
the
original
plan.
B
Okay,
I
do.
C
Have
one
more
question
so
I
couldn't
do
about
this
and
I
will
get
the
Java
maintainers
with
SDK
on.
But
one
thing
I
was
hoping
to
do.
Maybe
for
0.2
or
0.3
is
to
have
the
Java
SDK
be
put
in
the
maven
Central
repository,
because
the
work's
already
been
done
when
we
do
release
the
Java,
the
Jenkins
plugin,
having
that
in
a
maven
Central
repository,
so
people
can
compile
the
file
and
they'll
upload
to
the
tool.
The
Jenkins
tool
would
be
critical.
B
B
C
B
Is
there
any
decision
or
anything
that
we
need
to
be
concerned
about
as
a
as
a
project
in
general
I
mean?
Do
we
need
to
decide
things
like
what
the
name
of
the
SDK
will
be
in
the
center
repository
here?
Is
there
any
security
key
token
things
like
that
that
we
need
to
store
somewhere?
Yes,.
C
So
there's
the
security
token
that
I
think
you
brought
up
this.
The
sport
request
was
open
six
months
ago.
That
needs
to
be
stored
in
GitHub.
The
name
of
the
like
how
the
artifact
essentially
will
be
stored
in
Maven
is
based
off
the
pom
pile.
So
you
all
have
done
dev.cd
events
as
the
a
higher
name,
I
forget
what
it's
called
Maven
and
then
the
actual
artifact
name,
parent,
I,
think
it's
parent
and
then
artifact.
It's
like
Java
SDK,
CD
events
or
something
like
that.
C
So
that'll
be
driven
off
of
the
kind
of
the
Palm
file,
but
generally
I
think
he
covered
most
of
the
stuff.
But
yeah
there
are
tokens.
D
B
Okay,
so
is
this
something
that
we
need
to
generate.
B
C
I
think
we
just
needed
to
have
the
discussion
about
the
generating
and
storing
of
the
keys
I
know
you
can
do
that
on
GitHub
I
believe,
but
that
was
part
of
the
conversation
they'd
happen.
If
this
can't
be
released
to
like
zero
three
zero
four,
that
would
be
fine.
B
B
Just
wondering
if
we
need
to
do
something
like
a
tool
where
we
can
store
Secrets
accessible
to
the
team.
Is
that
something
like
a
tool
like
one
password
would
help
with?
Or
do
you
think
we
should
just
store
it
as
I
need
to
and
took
it
up.
C
I
would
have
researched
that
this
I,
we,
our
my
experience
to
GitHub,
has
only
been
in
the
past
six
months.
So
I
don't
know
about
storing
credentials.
I
I
could
have
sworn
if
I
remember
correctly.
He
did
and
the
poor
request
talk
about,
storing
it
there,
but
it
might
be
better
stored
in
an
external
tool.
A
B
Yeah
so
they're,
like
in
in
GitHub
you're
of
like
this
secret
and
variables
that
you
can
store
and
then
pick
them
up
from
basically
GitHub
actions.
B
Excellent,
but
you
know
so
there
could
be
a
starting
point,
but
I
don't
know
if
someone
it
might
be
worth
having
like
yeah
some
external
tool
where
we
put
secrets
that
are.
C
C
And
it
depends
on
the
tool
too,
you
know
this
is
the
release
to
the
standard
release
manager
for
Java.
It's
going
to
be
different
for
Python
and
go
so.
It
might
be
good
to
have
an
external
tool.
C
And
then
can
you
tell
me
one
more
time
it
was
called
one
secret.
What
was
the
one
that
you
liked.
B
There
is
one
password:
it's
a
password
manager,
perfect
I
just
mentioned
this
because
I
think
there's
that's
what
CDF
uses
okay
and
they
we
started
using
it
now
in
tecton
as
well,
because
they
they
have
kind
of
free
license
for
open
source
projects.
Oh
cool,
so
you
can
yeah.
There
is
a
small
process
to
follow,
but
basically
you
you
submit
your
project
name
to
a
page
and
one
password
site,
and
then
you
get
basically
very
licensed
and
something
like
that.
C
B
Password
manager,
so
you
can
use
it
to
store
Secrets
the
different
kinds,
but
that's
yeah,
so
I
don't
know
what
kind
of
Integrations
they
they
have
or
apis
to
to
pull
those
Secrets
automatically,
but
at
least
they
could
be
available
for
release
manager
to
copy
paste.
In
the
worst
case,
yeah.
C
I
mean
if
it's
just
copy
and
paste
and
then
maybe
we
create
action
that
runs
like
a
show
or
API
call
to
then
pull
them
in
to
automate
release
orchestration
absolutely
that
later,
but
that
works
for
me.
I
will
make
a
post
on
slack
and
then
tag
the
Java
maintainers
and
get
Avic
medium.
But
saying
this
is
all
first
use
this
and
maybe
just
start
some
fun
conversational.
A
I'm
thinking
I
want
to
talk
about
Navy
and
there
for
JavaScript
should
we
have
the
same
for
python,
so
we
have
a
Pi,
Pi,
publishing
or
python
as
well.
B
All
right
and
for
go
I!
Guess
it's!
It's
automated!
It's
done
by
the
tooling!
They
go
to
link
directly,
so
you
don't
have
to
do
any
anything
extra
there.
So
that
makes
life
a
bit
easier.
A
D
C
B
Right,
it
might
be
missing
so
thanks
for
bringing
that
up.
So
if
you
want
to
edit
I
think
we
do
have
the
license,
let
me.
B
Yeah,
so
we
do
have
a
license
in
the
spec,
which
is
the
Apache
license,
and
so
what
we
discussed
in
the
beginning
is
to
to
use
the
battery
license
for
everything
within
the
CD
events:
project,
okay,
cool,
I,
guess,
except
for.
If
we
create
content,
we
may
want
to
use
Creative,
Commons
and
those
kind
of
things,
but
or
specification
and
code
we're
thinking
to
to
stick
to
the
Apache
2..
B
So
if
you
see
that
missing
yeah
feel
free
to
create
a
PR,
provided
it
would
be.
C
Yeah
I
would
love
to
do
that.
Does
it
differ
per
so
again,
I'm,
not
a
lawyer,
I,
don't
know
licenses
very
well.
Do
I
need
to
State
and
I'll.
Look
it
up
if
I
need
to
does
this
work
Java
this
is
for
python.
Does
that
make
sense
for
the.
B
License,
no,
it's
it's
a
general,
so
you
just
copy
the
file
as
it
is.
You
don't
need
to
worry
about.
C
D
Know
we're
adding
some
items
here,
I'm
sure
you
guys
are
shooting
toward.
Like
you
mentioned
the
meal,
some
of
the
releases
you
want
for
CD,
con
and
I
think
once
our
Baseline
plugins
in
place
as
well
with
the
existing
splack,
will
be
again,
hopefully
have
more
horsepower
to
pick
away
at
some
of
these
items
as
well.
B
No
I
mean
this
is
great,
I
mean
we
have
not
had
the
the
bandwidth
or
the
demand
power
to
end
a
lot
of
this.
This
thing,
so
it's
great
to
have
you
know:
you're
bored
you're,
asking
all
these
questions
because
yeah
we
need
to
fix
all
this
aspects.