►
From YouTube: SIG Events Meeting - 2021.12.14
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
A
A
C
C
B
C
A
B
A
A
B
C
I
was
wondering
about
it,
but
at
this
point
it's
a
bit
a
little
bit
late
and
I
would
probably
it
would
be
better
as
a
pair
because
they
almost
always
oh
andre,
is
not
coming
today.
Okay,
they're
almost,
I
think
they
prefer
pair
of
tops,
but
it's
a
little
late
in
the
in
the
day.
At
this
point
it's
been
a
bit
hectic,
so
I
don't
know,
let's
see
what
other
people
have
said
and
no
one's
responded
to
your
call.
That
was
good
to
do.
No.
A
B
A
C
C
A
C
A
B
C
C
C
A
A
C
No,
no,
I
think
I
think
that
it
happens
often
when
we're
trying
to
announce
a
new
initiative
or
a
project,
because
it
it's
much
more
interesting
than
marketing
coffee.
Obviously-
and
it
sounds
much
more-
you
know
engaging
and
precise
and
it's
nice
to
let
the
people
who
are
building
out
the
technologies
to
speak
and
explain
what
they're
excited
about.
I
think
that
is
both
more
informative
and
just
generally
lands
better.
So
that
is
what
we're
looking
for.
Does
that
make
sense.
C
A
C
Have
a
number,
and
especially
for
a
project
launch,
because
we
definitely
want
people
to
be
aware
of
how
much
involvement
there
already
is
how
much
enthusiasm
there
is
for
the
project-
and
you
know
we
kind
of
want
to
like
drum
up
a
sense
of
real
movement
and
engagement,
and
I
think
that
helps
draw
on
even
more
people.
So
we
definitely
want
it
on
there.
A
C
C
A
D
A
C
C
A
A
C
C
A
C
I
mean
I
I
think,
actually
that
would
be
a
great
showing
of
the
use
case,
because
from
my
understanding,
when
creating
the
four
keys
project,
they
had
to
do
a
lot
of
mapping
between
the
different
tools
they
were
looking
at,
for
showing
the
metrics
and
for
making
the
metrics
make
sense,
and
I
think
if
we
had
more
standardized
data
than
that
using
the
four
keys
and
comparing
between
would
be
much
smoother.
So
it
would
almost
be
a
back
end
thing
for
the
four
keys,
but
it
would
be
great
for
that
project.
A
C
C
C
C
A
D
C
A
A
Statistics
connections
and
we
are
well
as
starting
to
use
it
as
not
not
yet
machine
learning
basis,
but
at
least
collecting
a
lot
of
data
from
the
ci
cd
flows,
both
for
statistical
reasons
and
then
for
different
analysis
and
for
visualization.
So
this
association
is
a
big
use
case
where
we
can
follow
like
a
commit
through
the
flow,
how
it
passes
through
different
steps
and
so
on.
C
C
A
We
use
eiffel
a
lot,
so
if
it's
what
we
use
for
events
today,
but
we
look
forward
to
replacing
it,
I
guess
would
see
the
events
eventually
when,
when
it
becomes
mature
and
complete
enough
okay
and
for
sure,
when
the
tools
that
we
use
have
native
support
for
seed
events,
that's
of
course
a
very
big
business
case
for
bringing
that
in
right.
So
we
don't
need
to
have
our
own
adapters
on
top
of
existing
groups.
C
A
I
mean
that's
the
hope,
at
least
for
from
us,
yes,
me
and
matias
community,
otherwise
we
shouldn't
really
probably
be
here,
but
it
remains
to
be
seen.
Of
course,
if
the
city
events
will
fly
and
it
will
be
implemented
as
a
native
thing
in
all
all
tools
yeah,
because
if
it
won't
then
of
course
there's
no,
maybe
no
major
reason
to
to
migrate
from
eiffel
to
something
else.
That
is
not
supported
anyway.
A
A
I
don't
think
it
would
be
such
a
huge
thing
to
do,
but
at
the
same
time
we
might
not
focus
on
that.
Since
cd
events
is
coming
or
seems
to
be
coming
at
least
so
I
guess
we
will
stick
with
what
we
have.
We
haven't
really
seen
so
far
that
the
big
benefits
to
using
cloud
events
as
an
infrastructure
part.
B
C
A
C
A
Was
it
like
a
year
ago
or
something
that
it
was
released
in
the
1.0
version
or
maybe
even
earlier,
or
maybe
it
was
even
three
years
ago
yeah.
It
has
been
around
for
some
while
and
I
think
quite
a
lot
of
tools,
support
cloud
events
nowadays.
So
still,
I
think
that's
that's
the
future,
but
that's
we
also
discussed
in
the
city
against
groups
that
we
have
that
we
don't
want
to
tie
ourselves
too
hard
into
cloud
events
either.
A
B
A
Only
an
event
framework
I
would
say
so.
Of
course
you
get
some
some
meta
data
prepared
and
defined,
but
the
whole
data
bodies
are
undefined
in
cloud
events
and
that's
what
we
now
will
do
with
city
events
on
top
of
cloud
events,
to
define
the
data
bodies
for
different
different
items
to
have
in
these
events
and
that's
the
crucial
part
of
eifel
as
well
to
to
actually
standardize
on
the
data
parts.
So
we
use
the
same
parameters
all
over
and
without
that
there's
not
much
there's
not
really
standardization.
A
So
there
are,
of
course,
some
maybe
event
names
and
parameter
names
in
the
afl
standard
that
are
more
dedicated
to
non-cloud
systems,
and
that's
also
one
reason
for
marketing
away
from
it,
because
we
see
that
the
cloud
is
is
the
future
also
for
ericsson
products
and
therefore
it's
it's
good
to
be
aligned
with
the
the
ways
of
working
in
the
cloud
world
to
say.
Also
when.
D
C
A
C
Right,
no,
I
I
because,
when
I
switched
from
club
east
to
cdf
my
role
changed
and
my
involvement
with
the
jenkins
project
kind
of
necessarily
reduced.
I'm
no
more
involved
with
that
than
any
of
the
other
projects
and
in
fact,
my
role
for
two
months.
I've
only
been
here
two
months,
but
my
role
has
not
been
that
project
engaged
except.
I
said
that
I
well
I.
C
I
think
we
all
believe
that
cd
events
as
a
project
is
really
interesting
and
it's
grown
out
of
the
cdf
and
it
kind
of
shows
the
sort
of
work
that
you
should
be
doing
in
open
source
foundations,
and
we
hope
that
it
will
make
a
great
impact
and
protocol
will
be
widely
adopted
and
all
these
things.
So
I
volunteered
to
to
do
what
I
could
to
help
with
the
professional
launch
and
things
like
that.
B
A
C
I
I
think
I
assumed
it
was
developer
relations
more
because
that
that
is
usually
what
I
am
recruited
for,
but
but
actually
it
turns
out.
Ecosystem
advocate
means
a
lot
more
communication
with
member
companies
and
and
that
that's
been
really
interesting,
and
certainly
I
would
hope
to
involve
our
member
companies
as
much
as
possible
in
in
our
open
source
projects
and
there's
a
lot
of
interest
there
too,
so
that
that
kind
of
works
really
well.
You
know
that
kind
of
a
of
movement
works
well
and
feels
natural
for
me.
A
A
C
A
C
But
you
know
it'll
be
one
of
those
quiet
indoors
christmas
and
have
just
a
nice
tree
and
lots
of
cookies
and,
and
that
will
be
it-
I
I
don't
think
I'll
be
going
to
many
gatherings
and
in
fact
like,
like
you
have
mentioned
in
all
likelihood,
there'll
be
additional
restrictions
either
they're
hoping
not
to
do
it
for
christmas
itself,
because
they
don't
want
to
disappoint
people.
Essentially
that's
a
completely
political
decision,
but
they
think
that,
right
after
christmas,
they're
gonna
do
a
snap
shut
down,
so
we'll
see
we'll
see
how
it
evolves.
They.
C
C
I
think
it's
pretty
much
what
they
did
last
year,
more
or
less,
but
it
will
be
more
open.
I
think
their
hope
is.
It
will
be
more
open
for
christmas
and
and
then
there
will
be
they've
already
hinted
in
the
press
and
it's
funny
because
I
usually
hint
in
the
press
like
three
days
out
and
I'm
like
wow.
That's
that's
pretty
far
in
advance.
If
that's
what
you're
planning
on
doing,
but
I
don't
know
we'll
see,
yeah.
C
A
C
Was
almost
impossible
to
take
a
flight
or
seem
like
a
very
bad
idea,
and
the
last
thing
I
wanted
to
do
was
you
know,
bring
this
to
my
parents
accidentally
that
would
have
been
awkward
yeah,
but
hopefully
it
all
get
better
get
better.
You
know
more
vaccines,
more
treatments.
Eventually
this
will.
This
will
get
better.
A
A
A
A
A
C
It
sooner
sure
it
opens
in
the
beginning
of
january
january.
10Th,
I
believe,
is
our
is
our
date
we're
aiming
for,
so
those
tracks
are
being
finalized
right
now
and
then
the
cfp
opens
january
10th
and
we
definitely
want
you
all
to
submit
very
very
excited.
We
want
to
do
a
big
push
for
cd
events
so
and
submit
on
other
topics
as
well,
but
it
should
be
a
great
conference,
I'm
very
happy
it's
going
to
be
in
person
and
we'll
do
a
hybrid
in
person
and
virtual
so
covering
all
use
cases.
There.
C
C
And
actually
I
don't
know
if
that's
of
interest
to
you
at
all,
but
your
tickets
for
one
conference
will
be
accepted
at
both
conferences,
so
that's
quite
fun
and
we're
hoping
to
do
at
least
one
joint
track.
It
won't
show
in
the
cfps
but
we'll
have
similar
space
covered
in
the
cfes
and
then
we'll
see
how
the
talks
you
know
the
submissions
we
get,
but
the
aspiration
is
to
do
a
joint
track
on
automation
and
testing
and
and
or
security
and
supply
chain
security.
So
we'll
see.
A
C
Okay,
so
we
had
we
had
some
actual
track
ideas,
but
it
just
became
a
little
bit.
Well
I'll
get
your
feedback.
These
were
the
track
ideas
we
had
developed
so
far
a
leadership
track.
We
had
that
last
year.
We
want
to
keep
it
a
community
and
culture
track.
We
had
a
community
track
last
year,
but
we
wanted
to
be
not
just
about
open
source
community,
but
also
internal
team
culture.
C
There's
a
little
bit
of
an
interoperability,
maybe
element
pulling
on
from
what
santiago
was
saying
in
his
presentation
on
in
toto
in
the
interoperability
sig
that
there's
kind
of
a
movement
where
security
initiatives
were
kind
of
transforming
them
from
the
point
of
view
of
of
devops
of
users
into
into
policy
concerns
which
is
kind
of
like
you
know,
codifying
it
and
making
it
a
policy
concern
which
is
kind
of
an
interesting
way.
To
think
about
that,
so
there's
kind
of
a
security
angle.
C
There
too
developer
experience
track,
and
this
is
where
we
were
thinking
of
putting
cd
events,
because
we
think
it
really
improves
developer
experience,
as
does
interoperability
in
all
sorts
of
forms,
but
I
I
did.
I
did
actually
mention
this
in
a
previous
one.
Maybe
it
was
the
stake
events
meeting,
but
you're
welcome
to
give
feedback.
If
you
think
that
is
not
the
right
track
or
high
not
properly
surfaced
enough
case
studies
will
be
sprinkled
throughout.
C
And
and
more
so
cloud
native
cd
get
elves
progressive
delivery,
observability
mlaps,
like
so
many
things
missing,
so
we
did
think.
Oh
well,
maybe,
instead
of
trying
to
group
things
into
tracks,
because,
essentially
what
submitters
look
at
you
know,
they
know
what
they
want
to
talk
about.
They
have
their
abstract
and
by
and
large,
not
everyone,
but
by
and
large
and
and
they'll
find
the
track
when
they're
filling
out
the
form
that
best
fits
it.
So
what
we
just
want
to
do
is
give
the
track
search
is
meant
to
be
guidance
like
in
general.
C
This
is
what
we're
looking
for.
You
have
a
better
chance
of
acceptance.
If
you
are
in
these
categories,
so
it
may
be
an
easier
way
to
do
it
and
it
may
be
covers.
A
broader
range
is
similar
to
the
way
that
kubecon
does
it
where
they
have
bullet
points.
Actually-
and
I
have
I
have
that
here
so
you
know
they
have
a
topic
now
to
narrow
down
the
focus
and
you
choose,
you
know
in
general,
one
of
them.
C
I
think
that's,
I
don't
know
okay,
so
these
are
the
ones
we
were
thinking
of
for
us.
It's
the
101
101s
leadership,
community
and
culture,
cloud
native
cd,
get
ops,
progressive
delivery,
best
practices
in
the
lab
security,
emerald,
ops,
observability
performance
security,
developer
experience
and
productivity
policy
and
governance,
automation
and
testing,
and
but
if
you
can
think
of
another
one,
you
know
off
your
top
top
of
your
head
right
now.
A
C
C
D
Because
one
of
the
things
I
noticed
is
that
when
you
go
through
the
once,
it's
not
clear,
at
least
for
me.
Where
would
you
put
in
like
seed
events
yeah
so
more
like
it's
maybe
too
broad
but
interruptability
category,
because
that's
probably
where
seed
events
would
be
easier
fit
into,
but
maybe
in
the.
C
Where
is
it
it
might
be
on
another?
It
might
be
on
the
stock
for
cd
events.
I
just
want
you
to
know.
We
have
put
it
right
here,
alphabetical
order,
so
you're
right
on
top,
so
I'm
pretty
excited.
So
there
will
be
a
section
for
submitters
to
say
which
of
the
projects.
They're
talk
relates
to
or
they
can
choose
another,
and
you
know
I
guess
I'll
be
text
box.
C
I
can
write
in
what
what
it
would
be
so
cd
events
will
be
certainly
within
the
format
to
choose,
and
this
will
be
seen
on
the
website
as
well,
but
yeah.
It's
interesting
where
to
put
it's
interesting
where
to
put
interoperability,
because
I
think
I
think
tracy
was
thinking
developer
experience
is
where
she
would
have
put
that
and
kind
of
also
see
the
events
within
that,
but
it
is,
it
is,
I
think,
quite
fun
to
surface
a
little
bit
more.
A
C
A
C
So
there's
a
little
bit
of
a
movement
against
having
that
happen
so
having
virtual
speakers,
but
you
could
do
a
virtual
live,
although
that
just
seems
like
difficult
for
the
more
difficult
for
the
speaker
without
that
much
more
of
a
benefit.
It's
my
personal
opinion
on
that
one.
But
given
that
we've
had
that
feedback,
I
think
there
is
a
movement
to
try
and
have-
I
guess
in
person.
C
Speaker
live
speakers
instead
of
pre-recorded
talks,
which
I
realized
does
make
it
difficult
because
one
you
have
to
fly
over
and
that's
that's
a
whole
effort
and
then
also
you
know
there
is
an
ongoing
pandemic.
So
I
guess
to
a
certain
extent,
we'll
play
it
by
ear,
but
I
would
imagine,
given
that
I've
been
given
that
that's
been
spoken
of,
I
would
imagine
that's
going
to
show
up
in
the
cfp
that
you
know
in
an
ideal
world.
We
want
the
speakers
to
be
live
so.
A
C
I've
had
that
experience
where,
but
I
was
a
virtual
attendee,
so
I
was
watching
like
a
conference
recording
you
know
someone's
standing
on
stage
and
then
sometimes
we
would
switch
to
a
pre-recorded
talk,
so
I
wasn't
in
the
room
experiencing
it
and
for
someone
sitting
on
a
couch
at
home.
That
was
fine.
I
didn't
care,
but
I
could
see
how,
if
you
yourself
have
flown
there
and
were
in
the
event,
you
would
prefer
the
speakers
to
be
live
rather
than
sitting
in.
You
know
a
room
in
a
different
country
and
watching
a
pre-recorded
talk.
A
Yes,
if
you
are
a
speaker
in
person,
you
would
of
course
also
want
an
audience
with
more
than
10
people
in
it
or
something
physically,
I
mean
10
people
in
the
room
and
thousand
online
is
not
optimal
either
when
you're
when
you're
there
physically.
Yes,
so
it's
hard
to
get
that
balance
yeah
before.
Of
course,
you
don't
have
to
know
where
you
will
end
up.
C
A
I
will
say
either
observability
or
interoperability.
Of
course.
Of
course
it
will
fit
in
interoperability.
That's
no
question
if
interoperability
would
exist
and
that
would
be
a
generic
enough
fit
for
all
kinds
of
events
discussions,
but
maybe,
as
we
talked
about
in
the
beginning,
the
the
use
cases
for
events
could
be
quite
different.
It
could
be
both
for
just
observability,
like
the
four
keys
and
other
things
I
think
could
be
also
for
driving
continuous
delivery,
which
is
more
of
orchestration,
which
is
something
totally
different.
Maybe
more
developer
experience
than
or
something
like
that.
C
A
C
A
D
C
But
that's
great
because
that
means
whatever
cd
events
talk.
One
wish
to
give
there
would
be
an
easy
box.
You
have
boxes
to
take
that
fit,
which
is
great,
because
this
is
basically
just
a
way
to
give
clear
indications
to
speakers
on
what
we're
really
looking
for.
You
know
what
we're
hoping
to
get
and
then,
depending
on
submissions,
we
would
then
form
the
tracks
from
that.
So
yeah.
A
But
but
I
think
also
if
you
would
like
to
give
a
presentation
on
seed
events
generally
on
any
kind
of
events
in
incidents,
then
of
course
it
could
be
a
bit
harder
to
find
the
right
place
to
put
it.
But
then
you
might
want
to
put
it
in
introverted
interoperability
just
to
be
to
be
generic
enough
right.
B
C
C
I
think
the
idea
was
that
we
are
thinking
in
the
cdf
of
having
a
little
more
emphasis
on
improving
developer
experience
is
something
that's
an
area
where
we
could
contribute
and
we're
thinking
that
cd
events,
because
they
improve
interoperability
and
reduce
friction
in
that
way,
they're
more
positive
for
developer
experience.
Does
that
make
sense.
C
D
D
Yeah,
maybe
a
feedback,
there
could
be
developer
experience
and
productivity.
That's
some!
You
state
more
detail
what
means
by
developer
experience,
but
maybe
that's
not
too.
I
mean
if,
if
you
have
a
category
you
place
it
and
and
u.s
committee
feels
like
okay.
This
is
bit
off,
but
we
still
want
it
in.
You
could
probably
move
it
around
so
then
it
might
not
be
that
much
of
a
problem.
C
C
A
Could
be
could
be
like
what
we
call
inner
loop
or
the
when
you
try
the
software
yourself
before
it's
committed
to
a
sem
system
that
this
developer
experience,
which
would
anyway
fit
in
your
ci
cd
context.
Otherwise,
the
developer
experience
you
could
get
the
impression
that
it's
about
ides
and
I
don't
know-
that's
not
really
cicd.
B
C
A
C
Yeah,
I
think
we
were
looking
at
it
more
in
terms
of
reducing
friction,
increasing
automation.
You
know
making
it
easier
for
developers
to
be
more
productive.
I
guess,
and
have
a
have,
a
smoother
time
with
that,
rather
than
yeah
it
kind
of
bleeds
out
more
than
cicd,
but
still
relevant
for
the
cicd
space.
I
would
think.