►
From YouTube: CDEvents Working Group - Aug 17, 2020
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
C
A
A
B
B
B
C
A
B
B
There
is
a
section
about
the
city
event
project
that
is
not
filled
in
yet
and
then
how
to
get
involved.
This
is
basically
copied
from
the
document
we
currently
have
on
spec,
so
reach
out
a
working
group.
So
I
put
the
link
to
the
two
working
group
now
links
to
contributing
and
governance
information.
B
C
C
C
B
C
B
Sure
what
sorry
I
was
thinking
to
fill
in
the
cd
event
project
with
some
context
about
the
project,
and
that
is
the
main
thing
I
was
thinking
of
having
us
under
construction.
Maybe
setting
up
some
ci
with
the
linter
for
the
pages
yeah.
Or
do
you
see
any
other
thing
that
we
should
have
in
there
before
we.
C
C
For
sure
I
think
we
should
probably
have
something
written
on
where
to
place
issues
I
mean
now,
since
we
have
a
community
project,
we
should
probably
move
some
of
the
issues
from
other
vehicles.
Here,
for
example,
we
should
maybe
say
something
about
what
kind
of
issues
should
be
in
what
kind
of
rate
points
from.
B
B
B
And
then
we
can
add
more
things
I
mean
I
can
imagine
like
in
the
community
recruitment.
We
would
be
good
to
things
links
to
to
work
as
we
do
with
other
communities
as
well,
so
we
could
have
links
to
the
work
that
we
do
with
the
various
projects
implementing
city
events,
things
like
that,
but
that's
something
that
we
cannot
implement
it
yeah.
B
B
B
I've
added
the
cloud
events
binding
and
also
a
binding
that
allows
to
format
an
entire
event
as
a
json
string,
which
is
handy
because
then
it
allows
basically
to
use
the
sdk
to
produce
adjacent.
It
can
be
compared
with
what
is
in
the
spec,
and
I
created
some
tests
where,
for
instance,
I
take
things
like
entire
json
and
load
it
into
a
cd
event
and
then
verify
that
it
matches
the
cd
event
that
I
created
separately.
B
B
In
this
case
the
spec
says
we
need
a
pipeline
name
and
pipeline
url,
so
the
end
which
I
require,
so
this
must
be
set
and
then
to
send
it.
There
is
this
s
cloud
event
helper
that
returns
an
object
from
the
cloud
event
sdk,
which
is
the
ce
and
then
from
there.
This
the
rest
of
the
code
is
the
same
that
it
would
be
within
any
cloud
event.
So
it's
basically
using
the
cloud
event
sdk
to
set
the
sync
and
set
some
config
and
send
the
event.
B
How
to
receive
your
first
cd
event
as
cloud
event?
It
should
be
possible
with
existing
code,
but
maybe
I
need
to
add
another
helper
function
and
also
need
to
add
some
validation
functions
so
that
that
before
we
send
an
event,
maybe
we
could
call
the
validate
to
make
sure
that
all
the
mandatory
fields
are
required.
B
B
B
A
B
B
Yeah
anyway,
if
you
can
still
hear
me,
I
think
that's
that's
about
it.
What
so,
if
you,
if
you
have
some
time
to
look
into
the
sdk,
if
you
want
to
add
some
comments,
if
there
is
no
strong
concern,
I
would
merge
the
pr
sooner
rather
than
later,
and
then
continue
to
writing
on
it.
So
we
have
a
usable,
sdk,
google
as
well.
C
Sounds
good
I'm
thinking
about.
I
think
we
talked
about
it
some
time
if
we
should
ever
come
on
some
kind
of
common
guidelines
for
all
our
sdks,
I'm
not
sure
how
much
of
a
common
look
and
feel
we
would
like
on
github,
for
example,
when
we
describe
the
sdks,
but
I
guess
for
0.1
they
can
differ
some
that
that's
no
problem,
but
maybe
in
the
long
run
we
should
have
some
kind
of
common.
C
B
Yeah,
I
think,
but
I
I
agree-
maybe
the
documentation
look
and
feel
of
the
repos,
but
I
think
what
we
discussed
last
time
is
also
that
at
least
the
way
to
consume
the
sdk
should
be
aligned
with
what
the
language
specific
best
standards
are,
as
opposed
to
strive
for
having
an
aligned
api
across
the
languages,
because
if
I'm
a
co-developer
or
java
developer,
I
have
certain
expectations
when
I
use
an
sdk
and
they
will
not
be
the
same
control
or
python,
of
course.
So
that's
the
only
way.
A
B
A
A
C
B
B
B
C
C
C
B
A
B
A
A
A
B
B
B
B
B
C
B
B
Next
for
the
quarters
pack,
I
think
we
the
the
main,
so
we
have
one
item
which
is
expand:
the
packets
back
the
documents,
which
is
a
very
broad
one.
It's
assigned
to
me
right
now
and
I've
been
doing
some
reformatting
of
the
spec
in
in
this
context,
but
yeah,
I
think
that's
where
we
we
need
there
is
most
probably
most
or
the
the
most
important
work.
So
I
was
thinking.
Maybe
we
can
split
this
up
a
little
bit.
I
can
create
some
some
items,
because
this
is
basically
about
expanding
the
data
model.
B
B
B
C
C
B
C
I
guess
it
could
be
updated
later,
as
well
as
matthias
wrote
there
down
there
there's
in
eiffel,
we
have
a
full
object
of
the
source,
so
it's
more.
There
are
more
fields
than
just
the
uri,
so
you
can
see
if
there's
a
person
behind
it
and
if
there's
some
host
name
behind
it
and
other
things
in
there,
so
more
properties
of
the
source
are
possible
to
provide
through
an
iphone.
If
you
like
to.
B
C
B
A
B
A
B
So
for
backward
compatibility
strategies,
I
think
this
is
in
progress.
It's
almost
done,
yeah
this
that
experiment
about
binary
mode
which
we
agreed.
We
we're
not
going
to
do
so.
I
need
to
finish
refreshing
this
back
based
on
that
and
specify
the
data
field
so
that
we
can
have
extra
vendor-specific
data
in
there
in
that
payload
yeah.
That's
a
to-do
item
on
my
site,
but
yeah
I'll
continue
to
progress
on
this
one.
B
B
C
A
A
C
A
C
C
That's
a
documentation
thing
mostly,
I
would
say
it's
also
good
to
have
these
abbreviations.
When
we
talk
about
events,
they
are
quite
long,
some
of
them
and
it's
it
might
be
easier,
at
least
when
you
draw
pictures,
if
you
will
draw
pictures
with
the
events
to
have
abbreviations
to
use
and
also
it
may
be
in
some
fluent
texts
somewhere.
Maybe
it's
not
early,
I
shouldn't
say
it's
mandatory
for
the
release
either,
but
at
the
same
time
it
shouldn't
be
a
big
thing
to
do
it
either.
C
B
C
B
C
Mention
there
is
some
discussion
or
has
been
some
discussions
during
the
summer
about
this
reference
architecture
and
in
that
work
I
know
that
at
least
tracy
reagan
wrote
the
the
issue
about
that.
We
might
not
be
aligned
all
over
see
the
different
cdf
working
groups,
so
I
mean
we
have
the
vocabulary
initiative
in
seeking
drop
and
we
have
this
spec
in
our
repositories
and
then
there
is
the
reference
architecture,
which
is,
which
is
somehow
also
quite
related
now
to
to
vocabulary
and
how
to
how
we
set
up
things
and
call
things.
C
B
B
B
B
C
B
B
B
Now
the
idea
was
due
to
something
that
translates
a
gita
web
book
into
the
city
event,
which
I
think
is
something
that
I'm
planning
to
to
work
on
a
bit
for
the
dollar
matrix.
If
I'm
getting
web
books
from
from
github
or
another
alternative,
there
would
be
to
use
gt.
For
instance,
I
started
looking
into
that
yeah,
just
also
based
on
some
previous
discussion.
Maybe
it's
good
to
try
and
not
include
things
that
are
too
vendor
specific
in
the
scope
for
first
release.
C
I'm
thinking
more
generally
when
it
comes
to
proof
of
concepts
and
whether
they
should
be
part
of
the
release
or
not,
really
isn't
it
more
so
that
we
actually
want
a
some
kind
of
reference
implementation
as
part
of
the
release
and
well.
A
proof
of
concept
could,
of
course
be
such
a
reference
implementation,
but
I
guess
if
we
would
have
a
reference
invitation,
it
should
also
follow
the
spec
and
be
updated
whenever
new
things
come
into
the
spec.
C
B
B
A
A
B
When
we
do
0.2,
I
think
we
we
could
have
like
a
0.1,
spec,
mison
and
an
overall
sorry
and
0.2
spec
milestone
and
maybe
an
overall
0.2
milestone
which
includes
the
sdk.
So
we
would
then
first
make
a
0.2
version
of
the
spec
and
then
in
parallel
we
would
work
on
the
s6
case,
but
the
sdks
would
be
released
maybe
shortly
after
the
spec
is
released
because
well
the
respect
needs
to
be
finalized.
First.
C
Yeah,
of
course-
and
it
could
also
be
so
that
some
sdks
might
only
support
up
to
certain
level
and
we
want
to
stop
supporting
them
or
we
don't
intend
to
continue
supporting
them,
maybe
or
well.
Some
sdks
are
more
important
than
others,
and
therefore
we
prioritize
those
some
release,
those
before
the
other
ones
or
whatever.
We
don't
need
to
release
them
all
in
a
bunch.
A
A
C
A
This
I
I
could
also
do
a
bit
of
wood
chopping,
so
a
lot
of
the
things
are
related
to
the
release.
Maybe
these
little
things
around
that
don't
necessarily
have
to
be
to
the
release,
or
you
know,
like
you,
mentioned
ci
pipelines
for
the
go,
and
I
could
probably
do
a
bit
of
that
stuff
as
well.
If
you
want
or
any
golang
or
yeah
anything
really.