►
From YouTube: CDF - SIG Events Meeting - 2021.06.07
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
D
A
A
E
A
Let's
see,
let's
just
go
through
the
protocol
from
last
time,
then,
if
there's
anything
there,
any
actions
we
should
look
into
eric
should
have
made
appear
about
what
the
changes-
and
I
believe
you
did.
A
A
A
Further
down,
we
will
come
to
the
blog
post
for
the
silicon
buff
session
later
in
the
the
minutes.
So
in
the
agenda
good
and.
A
Then
I
guess
it's
time
for
some
updates
on
the
sig
itself
and
as
I
guess,
I
hope
you've
seen
that
andrea
sent
out
the
poll
for
the
name
of
our
protocol.
A
E
Sure
yeah,
I
included
the
the
list.
E
Yes,
okay,
so
we've
got
six
answers,
oops,
no,
seven!
Yes,
six!
Six
answers
the
first.
One
is
just
beginning
and
different
proposals.
So
thanks
for
all
the
answers,
I
try
to.
E
E
E
A
So
I
guess
many
of
those
just
as
you
said,
are
referring
to
cdf
or
cd
or
rc,
or
something
like
that
and,
of
course
that's
that's
an
obvious
proposal.
I
guess
to
have
it
very
much
related
to
the
actual
say,
project
we
are
performing
here
or
whatever.
A
A
Maybe
my
first
thought
thing
could
be
that
I
would
like
us
to
not
be
the
protocol
to
not
be
really
hard
connected
to
the
current
name
of
our
sig
or
of
the
organization
we
work
in
cdf,
but
rather
something
that
tells
the
world
what
this
protocol
is
about
or
more
about
the
content
of
the
protocol
than
how
it's
driven
or
important
in
what
project
scope
it's
created
or
whatever.
A
If
that
makes
sense,
yes,
I
would.
B
Organizations
change
and
as
well
so
it
should
be
more
focused
on
what
it
is
rather
than
who
built
it.
A
Yeah
exactly
if
we
would
imagine
that
the
protocol
might
move
from,
I
don't
know,
hopefully
not
from
cdf
to
some
some
other
hosting
site
or
whatever
hosting
organization,
and
it
it
needs
to
change
name.
Of
course,
if
that's
happened,
and
we
have
cdf
in
the
name
anyway,
but
of
course
cd
as
continuous
delivery
is,
of
course,
what
we
are
aiming
at
at
least
right
now,
I'm
not
sure
if
that
could
be
considered
to
a
limitation
to
what
the
protocol
could
contain
or
if
we
think
that's
a
broad
enough
term.
F
Delivery
does
make
sense,
so
the
other
thing
that
we
keep
hearing
about
the
delivery
is
more
also
on
supply
chain,
that's
also
being
commonly
used
now
so
supply
chain
events
or
something
related
to
software
supply
chain
from
code
to
deployment.
G
I
think
the
I
personally
think
the
cd
is
too
limiting,
because
if
you
start
pushing
the
events
back
to
the
ci
process,
then
the
name's
not
reflecting
that
and
like
you're,
the
other
person
saying
like
supply
chain
down
the
road
you
know,
needs
to
come
into
play
as
well.
When
you
bring
in
devsecops
and
other
pieces
to
that
pro.
That
puzzle.
H
F
Is
now
also
includes
a
ci,
so
so
we
could
think
of
that
in
that
direction.
All
the
tools
that
are
used
in
software
dead
world.
G
I
You
also
was
going
to
ask
I
mean
I
I
get
that
we
don't
want
to
name
anything
based
on
a
foundation
or
ownership,
but
I
andrei
don't.
Were
you
using
the
term
continuous
delivery,
not
as
like
the
continuous
delivery
foundation,
but
continuous
delivery
as
a
process?
Yeah.
E
Yeah
yeah
I
mean
you
could
see
continuous
integration
or
everything
related
to
continuous
integration,
continuous
deployments
and
continuous
delivery
as
part
of
a
broad
term.
Continuous
delivery,
which
I
think
is
what
the
continuous
liberty
foundation
is
also
made
continuously
very
far.
I
Right
right,
so
I
think
the
only
one
that
you
really.
I
So
should
we
be
aligning
some
of
these
this
these
these
kind
of
these
event
buckets?
Should
we
try
to
align
it
with
what
the
landscape
represents,
so
we
would
have,
for
example,
orchestration
events,
and
we
would
have
security
events
and
we
would
have
new
feature
events.
I
D
I
E
Yeah,
but
I
think,
apart
from
the
names
of
the
packets
tracy,
I
think
what
we
were
trying
to
just
to
come
up
here
is
with
a
name
for
the
overall
protocol,
like
a
brand
name
that
we
could
use
to
refer
to
the
protocol
instead
of
yeah
the
protocol
produced
by
the
cdf
event,
I
get
it.
A
C
Captain
sorry,
but
just
want
to
say
in
in
captain
we
have
most
of
the
events
we
currently
have
are
around
continuous
delivery,
but
we
also
have
events
that
are
more
in
the
bucket
of
operations,
so
this
is
also
in
in
I
heard
earlier.
I
think
it
was
steve
that
we
also
have
the
the
bucket
of
ci,
so
I
think
it
makes
sense
to
open
up
the
name.
C
Also,
although
I
really
like
the
name
cd
events,
but
if
we
consider
that
an
event
starts,
let's
say
in
continuous
integration
or
even
at
the
at
the
developer
and
goes
all
the
way
to
production.
Maybe
even
if
there's
a
problem
with
his
his
or
her
code
change,
then
all
these
events,
they
should
spend
the
whole
the
whole
flow,
and
then
it's
not
only
cb
anymore,
but
it
starts
in
ci
and
goes
all
the
way
to
operation.
I
Right
and
I
almost
feel
like
you
know,
continuous
delivery,
as
we
know
it
today,
we
are,
we
are
ourselves
in
this
event.
Discussion
is
disrupting
it,
so
it
it's
would
be
great
if
we
could
come
up
with
a
broader
term
to
take
it
so
that
if
we
disrupt
continuous
delivery-
and
that
becomes
old-fashioned,
we
didn't
we
didn't
use
that
name.
I
But
I
don't
know
what
a
better
name
is
to
it's
hard,
it's
hard
to
rebrand
and
it's
hard
to
come
up
with
your
own
kind
of
this
name.
I
was
working
on
the
application,
enablement
working
group
from
the
cncf
side
and
what
they're
trying
to
do
is
come
up
with
some
patterns
for
deploying
infrastructure
and
database
components
and
application
components
all
at
the
same
time
in
application
enablement.
They
were
struggling
with
that,
so
I
gave
them
the
name
of
cooperative
delivery,
which
is
a
great
description
of
what
they're
trying
to
do.
I
I
don't
know
if
they're
going
to
use
it,
but
it
still
is
a
cd,
so
can't
get
rid
of
the
c.
You
know
c's
and
d's
deployments
deliveries
continuous
cooperative,
so
I
do
feel
like
we
should
come
up
with
it,
and
maybe
we
go
back
to
terms
like
life
cycle
events,
whoa.
A
Yeah,
I
think
this
debate-
this
is
quite
infected
and
a
lot
of
people
have
different
understandings
of
what
continuous
x
is-
and
I
guess
that's
one
of
the
reasons
I
actually
propose
this
cmu
as
a
name,
something
that
is
does
not
related
at
all
to
anything
we
talked
about,
but
just
just
a
name.
That
anyway,
makes
some
some
sense
of
form
its
meaning.
I
mean
the
cemu
is
a
greek
word
that
talks
about
how
to
notify
around
activities
and
other
related
stuff.
I
And
then,
if
we
do
disrupt,
you
know
go
five
years
from
now,
when
most
tools
are
really
event-based.
Potentially
that
could
happen
and
they're
not
taught
we're
not
talking
about
continuous
delivery.
We
have
not
retired
a
name
that
we
can.
We
started
using.
I
think
that's
the
biggest
challenge.
E
I
was
going
to
say
that
I
really
like
the
cloud
events
name,
that
it's
simple
sketchy
and
it
might
be.
Maybe
I
don't
know
I
don't
know
if
it
covers
all
the
use
cases
that
it
pains
for,
but
at
least
it's
from
the
name.
You
can
get
an
idea
of
what
it
relates
to
and
I
think
that's
an
advantage,
even
if
the
name
is
not
like
a
full,
perfect
description
of
what
they're
trying
to
do,
or
maybe
it
is
in
their
case,
it's
a
bit
easier,
but
I
would
like
to
for
me.
E
I
think
it's
important
to
have
a
name
which
is
also
like
a
reasonable
brand.
So
it's
not
too
complex
and
long,
and
it's
also
relates
to
what
it
is
about.
I
like
the
the
cemu's
name,
but
it's
the
only
concern
I
have
with
that
that
if
just
by
the
name
you
don't
know
what
it
is
about.
I
G
I
A
Yeah
I
I
kind
of
agree.
I
mean
we
could,
or
maybe
I
would
say
that
we
have
scared
some
embedded
developers
when
when
are
we,
but
when
the
cloud
events
term
was
initiated,
I
mean
also
such
events
are
also
interesting,
interesting
for
embedded
developers,
I
would
say
not
just
kubernetes
or
cloud
based
developers,
so
I
actually
have
a
problem
with
the
cloud
part
of
cloud
events,
because
it's
not
only
about
cloud
at
this.
That
is
not
to
me.
A
B
Speaking
of
cloud
events,
I
guess
there
is
nothing
really
keeping
us
to
following
the
cloud
events
standard
for
all
future.
We
could
switch
to
another
one
or
branch
out
to
multiple
ones
or
whatever
is
suitable,
so
it
might
be.
For
that
reason
reasonable,
not
to
include
cloud
events
in
the
purple
name.
It
really
has
not
very
much
with.
J
I
agree
with
that,
because
we
are
mostly
using
cloud
events
for
kind
of
structuring
our
events
and
stuff,
but
what
is
different
different
in
this
case
is
the
actual
vocabulary
that
we
are
creating
around
it,
so
something
that
kind
of
reflects
more,
though
more
about
what
the
vocabulary
is,
what
we
are
bringing
to
cloud
events.
I
G
Us
through
this
around
here
how
about
continuous
transformation.
I
Events
emil,
could
you
bring
up
the
original
our
original
definition
from
our
working
group
when
we
we
were
in
a
working
group
and
we
were
pushing
to
be
a
sig?
I
just
want
to
see
what
terms
we
use
to
describe
ourselves.
I
A
D
I
I
You
know
you
slap
things
around,
my
mother
was
jewish,
and
that
was
one
of
those
yiddish
where
she
kept
around.
Are
you
just
slept
around
things
carrying
things
around?
I
A
I
I
K
Yeah
thinking
about
the
same
problem,
what
is
the
life
cycle
of
what
of
an
application
of
software
of
hardware?
This
is,
I
mean,
maybe
it's
just
one
additional
word
for
classifying
what
lifecycle
stands
for
would
be
needed
from
my
point
of
view.
C
E
Course
so
what
what
I
can
do
I
mean
I
can
take
these
options
and
make
a
new
hole,
and
then
people
can
vote
to
comment
further.
D
E
Or
yeah
or
I
can
start
a
github
discussion,
I
mean
to
see
people
wants
to
comment.
We
want
to
continue
the
discussion
until
we
find
the
right
one.
I
don't
know
if
we
are
going
to
find
it.
If
we
continue,
I
mean
we.
If
we
continue
today,
I
mean
we
can
continue
discussing
on
the
name.
I
I
B
I
G
I
Well,
that's
funny
that
you
should
mention
that
particular
image,
because
I
am
doing
a
presentation
and
I
brought
up
events
in
my
presentation
for
like
like
high
level
c
c
level
and
director
level,
and
I
was
looking
at
the
infinity
symbol
and
I
was
like
you
know
what
that
doesn't
describe
events,
and
so
I
started
thinking
about
what
describes
events
and
I
used
a
tibetan
knot.
Instead,.
I
I
F
Right,
so
if,
if
you're
looking
at
that,
then
I
I
think
what
we
are
looking
at
is
something
sitting
on
top
of
that
eight
right
infinity.
We
are
basically
extracting
all
the
events
or,
what's
going
on
with
this
a
and
then
trying
to
build
a
context
on
top.
F
I
That's
that
describes
more
what
we're
doing
with
events
than
a
than
an
infinity
symbol,
because
it's
all
happening
it
could
potentially
all
be
happening
at
the
same
time,
and
it
actually
is
always
listening.
You
know
it's
not
it's
not
a
pipeline
anymore.
Where
that's
why
I
keep
saying
we're
we're
kind
of
disrupting
that
this
the
concepts
of
continuous
delivery,
and
so
the
names
are
kind
of
important.
If
we
can
come
up
with
something
that
really
has
a
reference
to.
A
I
A
Yeah,
I
think
we're
getting
somewhere
now.
At
least
I
mean
it's
good
that
we
start
the
discussions
and
the
people
start
thinking
and
be
creative,
and
I
think
we
need
this,
and
I
I
agree
with
tracy.
We
shouldn't
really
rush
this
too
much
and
just
decide
on
something
in
a
hurry.
Now
until
I'm
here
that
there
was
an
intention
that
we
should
have
this
name
represented
in
the
event
protocol
pr
now,
but
of
course
that
could
hopefully
change
as
well.
A
E
Absolutely
that's
a
draft
and
that's
for
the
poc,
so
I
mean
we
could
stick
with
something
like
cd
events
just
for
the
pse
and
doesn't
have
to
be
our
final
name
like
authority
on
that
yeah.
A
A
B
Creative
bonus
points
from
me:
if
it's
something
everyone
can
pronounce
I've
run
into
those
problems
before
like
jira,
for
instance,
or
gyro,
whatever
other
pronunciations
people
have.
E
What
sorry
a
recursive
acronym
like
yaml
or
gnu
or
like
yaml,
is
yet
another
markup
language.
No.
A
E
E
H
I
A
B
Andrea,
just
to
re,
restore
your
honor
yaml
is
a
recursive
acronym.
It's
short
for
yaml
ain't,
markup
language,
oh.
B
It
might
have
been,
but
now
it's
changed
to
yamaha
change
to
recursive
one.
That's
like
the.
I
K
A
D
A
A
B
Some
really
good
discussions
regarding
the
proof
of
concept
work
basically
specifying
in
much
more
detail
what
exactly
it
contains.
So
we,
I
think
we
have
people
from
from
captain
techton
and
all
other
involved
parties
and
mauricio
for
their
library.
B
So
I
don't
remember
how
much
notes
we
took.
I
posted
some
stuff
in
slack,
I
know
as
an
outcome,
so
we
were
talking
like
yeah
discussing
what
events
exactly
attacked
them
will
send
and
how
kept
them
will
pick
it
up
and
translation
layers
and
stuff
like
that.
So
it's
looking
good,
that's
my
recollection,
at
least
from
the
meeting.
D
A
B
A
C
I
also
agree
we
had
a
very
good
discussion
and
I
think
one
of
the
next
step
could
be
that
we
pick
those
events
that
are
the
most
important
one
for
the
park
and
define
those
and
then,
in
the
long
run.
Of
course
we
won't
want
we.
We
don't
want
to
high
check
this,
but
it
was
a
very
productive
meeting
last
week.
So
if
we
can
keep
this
technical
focus
on
the
clock,
that
would
help,
in
my
opinion,.
E
Yeah,
I
totally
agree.
I
think
it's
really
helpful-
to
have
the
blog
move
forward
and
also
to
keep
like
the
scope
contained
until
we,
you
know,
have
something
that
we
can
show
to
the
world
and
that
we
can
start
expanding
from
there.
A
A
And
that's
for
all
of
you
both
for
this
siege
event
for
the
vocabulary,
sorry,
for
this
sig
events
meeting
and
for
the
vocabulary
meeting,
we
can
add
you
as
as
participants
in
that
calendar
entry,
if
you
like
so.
A
A
A
I
I
think
there's
enough,
I'm
hoping
that
it
becomes
more
organic
anyway,
and
people
ask
you
know
whatever
questions
they
feel
works,
but
I
think
that
that
we'll
get
that'll
get
us
started.
A
B
I
spoke
with
the
jennifer
just
inappropriately
before
just
before,
setting
up
the
training.
So
there
is
an
questions
for
us
to
share
something
and
as
far
as
I
understood
from
jennifer,
the
sharing
doesn't
like
automatically
take
over
anything.
So
we
could
just
have
that
sort
of
on
the
side
and
people
can
choose
to
to
look
at
something.
So
if
we
want
to
prepare
or
yeah,
if
we
want
to
present
something,
then
we
should
prepare
it
and
have
the
be
ready
to
share
it,
but
I'm
not
sure
what
that
would
be.
B
I
I
And
then
did
we
hear
anything
back
so
there
was
a
suggestion
that
we
actually
changed
the
time,
because
it
is
that
what
they
I
don't
know
why
they
did
it,
but
they
put
all
the
buffs
at
the
same
time,
which
means
that
jenkins
x,
for
example,
is
at
the
same
time
as
this
one
as
ours.
I
I
I
didn't
have
to
email
and
kara,
I
pushed
it
or
fati
and
kara
pushed
it
up.
The
kind
of
the
food
chain.
D
I
So
I
I
can
send
a
note,
though,
to
jennifer
crowley
and
let
her
know
that
at
least
those
of
us
who
have
committed
to
being
at
that
particular
buff
are
okay,
with
changing
that
and
putting
it
at
a
different
time.
A
D
I
Is
it
is
at
11,
15
eastern
daylight
time
and
yes,
it's
exactly
at
the
same
time
as
jenkins,
x
and
ml
ops,
and
then
they
have
another
group
of
them
that
are
at
two
o'clock
eastern
time
and
there's
ortilius.
And
then
there
is
feature
flags.
And
then
there
is.
I
I
I
don't
know
how
many
rooms
they
have.
I
Like
at
10
45,
there's
a
ton
of
talks
and
then
at
11
15,
there's
just
three
bo
there's
just
three
buffs,
I'm
wondering
if
we
ask
that
we
can
yeah,
I
don't
know
they're
gonna,
they're
gonna
have
to
sort
it
out,
we'll
leave
it
leave
it
up
to
them,
they're
the
experts,
but
I
can
tell
them
that
we're
okay
with
changing
the
time
if
they
do
yeah.
A
I
The
james's
will
be
hosting
the
the
jenkins
ex
baffia.
I
I
I
I
think
kara
would
have
a
problem:
she'd
have
to
choose
one
or
the
other.
A
And
I'll,
just
as
fatty
mention
on
the
interrupt
meeting
last,
the
buff
session
is
supposed
to
be
an
interactive
session
and
therefore
it's
not
as
interesting
to
watch
it
afterwards.
Right.
I
I
Tekton
is
on
the
24th
and
spinnaker
is
on
the
24th
and
then
there's
another
jenkins,
one
on
the
24th.
B
I
don't
know
about
our
boss,
like
what
is
the
main
message
that
we
want
people
to
take
away.
I
just
took
a
course
in
strategy
communications
and
now
I
need
to
ask
those
kind
of
questions
of
myself,
but
is
it
like?
We
want
people
to
join
the
sig
or
we
want
to
keep
people
to
keep
an
eye
on
the
events
or
we
want
people
to
in
general,
think
event
based
systems
or
what's
what's
their
main
takeaway,
so
to
say.
I
Well,
if
you
look
at
the
questions,
I
kept
the
questions
really
around
almost
an
introduction
to
who
we
are
and
what
events
are
most
people.
This
will
be
a
brand
new,
a
brand
new
world
for
them
to
think
about
a
cd
pipeline
in
in
terms
of
an
event
mesh,
as
opposed
to
a
very
linear
process.
I
D
A
I
see
now
that
time
is
running.
If
we
should
try
to
finish
the
agenda,
we
need
to
proceed
if
that's
okay
with
everyone
yeah.
So
we
should
mention
that
there
are
at
least
one
kubecon
submission,
andrea
you
and
who
was
it?
Was
it
mauricio
or.
E
Yes,
it's
me
and
mary,
so
we
submitted
a
presentation
for
kubecon
titled
using
cloud
events
to
create
an
interoperable
ci
cd
ecosystem,
which
is
about
the
work
that
we're
doing
here
in
the
sea,
so
creating
like
a
lingua
franca,
so
the
two
kind
of
language
for
cicd
system
to
talk
to
each
other
and
yeah.
Let's
see
if
it's.
I
C
I
know
the
captain
team
submitted,
but
it's
not
so
much
about
the
technical
part
around
events
or
around
interoperability,
but
more
on
the
on
the
use
case,
like
as
a
low-paced
quality
gates
and
these
kind
of
things.
I
I
I
I
A
Okay
and
then
going
on
to
presentations
and
there
I
thought
it
would
be
great
to
get
someone
from
argo
or
intivit
into
our
sig
to
present
how
arco
events
nor
the
thoughts
around
events
in
the
org
events
tool.
So
does
anyone
here
on
the
call
have
any
contact
with
anyone
from
argo?
I
guess
there
was
some
from
dietrich.
C
Previously,
we
do
have
some
context
to
to
argo
or
into
it.
Unfortunately,
I
know
that
sumit
he
was
our
like
first-hand
contact
to
intuit
and
argue,
but
he
left
argo.
He
left
into
it,
but
we
are
in
contact
with
others
from
the
argo
team,
but
more
on
the
argo
ct
team
and
not
so
much
argo
events
but
reach
out
to
them
and
ask
them.
A
Yeah,
I
believe
we
had
a
presentation.
Was
it
on
the
interrupt
sig
some
time
ago
about
argo
rollouts.
I
believe
it
was
by
them,
but
we
haven't
heard
much
about
the
argo
events
project
which
would
be
more
relevant
to
us
in
this
cig.
So
if
it's
possible
for
any
one
of
you
to
reach
out
to
them
to
see
if
they
would
like
to
join
or
even
make
a
presentation
for
us
on
there,
our
events
that
would
be
great
yeah.
C
I
I
will
ask
my
my
my
contacts
from
argo
cd.
If
they
have
someone
from
argo
events
joining
yeah,
I
can
do
that.
I
I
A
So
at
least
we
tried
that
some
time
ago
yeah
it
would
be
good
to
attract
them
actually
to
the
silicon
conference
as
well.
C
In
the
email
just
for
for
clarification,
they
should
be
invited
to
the
sick
or
to
the
or
to
the
cdcon.
A
A
A
A
Okay,
going
on
last
minute,
there
is
a
blog
post
now
tracy.
Thank
you
very
much
for
writing
that
one.
A
D
A
A
I
Yeah
we
they
have
been
roxanne
who
manages
their
social
media
she's
done,
she's
pushed
it
out
several
times,
so
it's
out
there.
I
know
that.
I
I
Hopefully
the
tiffany,
the
news
outreach
chairperson,
is
working
on
getting
a
new
website
up.
We've
got
we've
budgeted
funds
for
it.