►
From YouTube: CDF - SIG Events Meeting - 2021.04.19
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
Us
just
a
second
now
I
think
I
can
hear
you.
B
I'm
switching
switching
gears,
I
mean
I'm
just
installing
a
new
microphone
and
speaker.
That's
why?
B
Okay,
so
we're
three
people
here
who
couldn't
join.
I
think
mauricio
couldn't
join
right
and
neither
andreas
and.
A
A
Yeah
he
has
a
conflict.
I
wonder
if
we
should
send
a
survey,
maybe.
A
B
Sake
is
still
no
one
up
there
this
that
we
changed
the
schedule
from
twice
a
month
right
every
second
week
to
twice
a
month.
Maybe
it
wasn't
such
a
good
decision
after
all,
and
so
it
might
be
so
that
we
should
go
back
to
having
actually
every
second
week
unless
the
best
practices
equal,
we'll
join
the
same
schedule
as
we
do.
A
C
B
A
B
A
I
I
will
check,
I
mean
I
can
ping
christy,
maybe
later
after
the
meeting
and
ask
her
directly
yeah.
B
And
here
we
are
canada
as
well.
I
cannot
tracy
great.
B
B
A
A
B
A
Yes,
I
I
put
a
template
in.
We
can
use
it
for
the
for
these
meetings.
It's
yes
just
action
point
from
last
week
updates
for
the
sake
updates
from
the
work
streams
and
then,
depending
on
the
day.
There
is
anything
to
talk
about
in
terms
of
media
conferences,
not
post
any
presentation
that
might
happen
and
any
pr
design
discussion.
B
Yeah
sounds
good,
so
I
guess
last
time
we
we
thought
that
we
today
would
have
a
presentation
from
matthias
on
the
the
eiffel
protocol
with
the
event
linking
and
other
related
topics.
But
that's
that's
really.
The
on
the
next
meeting
is
that
it's
postponed
the
next
location.
So
we
don't
have
that
presentation
today.
So
the
agenda
for
today
is,
I
guess,
quite
thin.
B
B
B
B
E
Know
it
it
was
steve,
steve
taylor
chatted
with
him
about
it.
I
don't
recall
what
the
what
the
discussion,
what
was
really
discussed
to
be
honest,
but
I
do
think
steve.
Taylor
probably
knows
what
license
that
the
toc
was
thinking
about.
Unfortunately,
he
has
a
customer
call
right
now,
but
I
can
ask
him
to
send
an
email
or
update
this
doc.
B
Yeah,
let's
see
if
we
have
the
this
is
not
updated,
there's
another.
They
have
another
meeting
in
its
right
now.
D
B
A
Yes,
try
to
remember
as
well
if
you
came
to
any
conclusion,
but
I.
E
E
I
was
looking
at
the
last
toc.
Let
me
look
at
the.
A
I
think
so
I
think
it
was
the
last
one.
B
E
Just
says
yeah,
it
says
any
any
guy
from
the
linux
foundation,
any
osi
approved
license
is
okay.
B
E
That's
all
they
say,
and
then
they
do
say
that
for
clas,
if
we
have
code
artifacts,
we
could
we.
We
could
name
them
and
move
them
to
a
dedicated
repo
under
under
cla
checks.
A
Yeah,
I
think
so
I
think
eventually
yeah.
It
would
be
good
to
to
get
like
a
name
for
a
protocol
and
get
a
dns
name
allocated,
so
we
can
use
it
in
our
events
as
well.
A
A
B
Yeah,
so
I
guess
it's
a
bit
premature,
maybe
to
to
decide
on
something
here
now
for
the
licensing,
and
I
guess
what
we
do
now
I
mean
we
only
create
drafts
and
we
discuss
things
on
github.
We
discuss
it
of
course
publicly
and
I'm
not
sure.
If
what
we
discussed
there
is
considered
something
that
we
should
have
licenses
for
those
documents,
those
working
documents
that
we
have
but
before
I
guess
we
release
anything
on
this
protocol.
We
should
of
course
make
sure
it's
licensed
correctly
and
so
on.
E
I
know
the
dynatrace
folks
are
pretty
excited
about
this
sig,
I'm
sorry
that
nobody's
on
the
call
from
dyna
to
trace
today,
but
you
know
we
have
some
potential
to
work
with
them
to
bring
over
parts
of
captain,
possibly
so
I
feel
like
if
we
have
the.
If
we
have.
This
are
kind
of
our
ducks
in
a
row,
it'll
be
easier
to
move.
D
E
E
Them
you
know,
I've
looked
at
licenses
so
many
times
and
I
absolutely
hate
this
project.
When
I
was
on
the
eclipse
foundation,
we
spent
over
a
year
writing
the
the
the
eclipse
license
and
there's
so
many
out
there.
I
wish
the
toc.
Maybe
we
could
just
ask
the
toc
to
suggest
one.
B
E
That's
what
apache
ii
is
what
artilleus
is
under.
E
I
think
we
should
do
that.
Maybe
we
should
just
put
it
out
there
and
make
sure
everybody
on
this.
Do
we
do
do
we
have
a
mailing
list
for
this
yeah?
We
do.
E
C
E
Before
we
actually,
if
we
had
a
product
that
we
were
going
to
release,
we
if
we
changed
it,
then,
but
I'm
guessing
that
apache
2
is
going
to
be
fine.
B
Yeah.
Okay,
so
let's
assume
that,
but
it's
good
that
we
should
maybe
present
it
on
the
media,
still
say
that
we
intend
to
do
this.
E
E
And
you
know
email
you
probably
can
bring
it
up
at
the
toc
the
next
call
and
find
out.
If
anybody
there
has
any
concerns
about
that,
it
doesn't.
E
And
then
I
didn't,
I
wasn't
here
two
weeks
ago
because
I
had
a
conflict.
How
how
are
we
doing
did
we
get?
Have
we
got
anything?
I
haven't
looked
at
the
our
doctor
shared
document
in
a
while.
E
D
E
Okay
and
I
have
just
a
on
a
site
on
a
side
note,
I
have
joined
the
cncf's
app
delivery,
sig,
trying
to
kind
of
listen
in
on
what
they're
working
on
and
they're,
not
they're,
really
working
on
right
now,
the
definition
of
an
application
which
fits
far
more
into
the
ortilius
realm
than
anything
else
that
we
do
because
it's
like
is
infrastructure
part
of
the
application.
What's
an
application
package
in
a
native
environment,
it's
no
longer
an
msi.
What
is
it?
E
Those
are
the
kinds
of
discussions
they're
having,
but
I'm
still,
I'm
still
I've
still
joined
it
so
I'll.
So
I
can
try
to
cross-pollinate
between
us
and
what
they're
doing.
E
And
that
is
what
has
spawned
the
get
op
sig.
E
So
I'm
trying
to
keep
on
top
of
what
is
happening
on
the
cncf
side
of
the
house
with.
E
Think
that
dyna
trace
is
eager
to
work
with
us
in
defining.
You
know
the
protocols
defining
the
you
know
the
structure
and
potentially
bringing
over
parts
of
kept
in
if
they
can.
B
Great,
so
what
about
andrea,
bringing
it
to
the
toc
as
well?
Should
we
add
that,
as
an
ap,
then.
B
E
And
I
know
I'm
bouncing
and
I
tend
to
do
that
emily.
You
said
you
thought
we
needed
to
come
up
with
a
name,
a
name
for
a
potential
platform
or
whatever
we're
calling
it.
E
Did
oh,
what
are
you
guys
thinking?
What
are
you
thinking
in
the
long
term
where
this
is
going
to
go?
Do
you
think
we'll
have
like
a
a
listener
or
a
control
plane?
Is
that
what
we
want
to
do?
I'm
just
curious.
B
E
A
I
mean
at
the
transport
level
if
you
are
transported
by
cloud
events,
we,
you
can
already
use
the
code
events
sdks
to
generate
events
and
receive
events,
but
you
might
want
to
have
a
higher
higher
layer
or
higher
level
of
sdk
on
top
to
make
it
easier
to
produce
events
or
receive
events
that
are
compliant
with
what
we
define.
B
I
don't
know
if
it's
time
now,
but
we
had
on
the
interoperability
last
week
you
were
there,
I
guess
most
of
you.
We
talked
about
this
spd-x
metadata
specification
or
standard.
That
is
there
and
we
should
consider
if,
if
this
event
protocol
that
we
intend
to
provide
should
use
should
be
kind
of,
it
should
be
based
on
spdx
somehow
or
should
should
be
an
extensions
spdx
or
the
metadata
part
of
it
exists
and
not
the
vocabulary
or
the
I
don't
know.
E
Yes
and
I
hate
to
push
it
off
to
steve,
but
he
has
been
pretty
involved
in
working
with
spdx
because
we're
starting
to
integrate
with
that
from
the
ortillius
open
source
side,
they're
going
to
start
bringing
that
data
in
and
aggregating
it
up
at
an
application
level
based
on
a
collection
of
services.
E
So
I
think
he'll
have
some.
He
has
been
working
with
it,
so
I
think
he'll
have
and
cyclone.
I
think
cyclone
is
what
we're
actually
going
to
integrate
with
to
get
the
spdx
information.
But
I
think
he'll
have
some
insights
in
how
if
there
is
something
that
we
should
be
doing
with
spdx,
certainly
you
know
we
can
make
it
easier
for
people
to
integrate
or
have
an
event
that
calls
spdx.
That
would
be
really
good
because
I
don't
think
most
people
running
builds
right
now
are
thinking
about
s-bombs
too
much,
but
in.
E
A
Yeah
yeah,
I
think,
we'll
have
to
see
whether
it's
something
that
we
want
to
include
natively
in
the
protocol,
or
it
could
be
one
of
the
attachment
types
to
have
this
spdx
information.
When
you
do
a
build
and
send
an
event,
I
don't
know
the
build
is
finished.
What
do
you
want
to
do?
You
want
to
have
the
bill
of
materials
attached
as
part
of
the
events
or
you
want
to
have
a
link
to
do
it
so
that
it
can
be
downloaded
or
something
like
that.
E
And
I
I
think
that
I
think
her
name
is
kate.
Stewart
would
be
pretty
open
to
helping
pull
together
some
kind
of
an
event
stream
for
spdx.
If
we
chose
to
go
that
direction.
B
Yeah
and
I
think
we
could
of
course,
probably
leverage
from
what
they
already
have
in
there,
and
I
mean
if
we
would
be
made
an
extension
somehow
to
to
the
spx
standard.
We
will
have
get
it
out
for
free,
I
guess,
but
we
will
also
be
maybe
limited
to
what
we
could
do
a
bit,
but
anyway,
we
shouldn't
of
course
forget
about
that
option.
So
we
need
to
consider
that
in
some
way
and
someone
should
in
some
way
investigate
it
further
how
we
should
proceed
with
spdx.
E
A
C
I
know
that
last
time
to
build
the
sig
katie
has
talked
about
that
they
were
gonna,
do
in
3.0,
work,
something
they
call
pedigree,
and
provence
and
pedigree
sounded
more
like
precisely
in
this
area
that
we're
doing
so.
I
took
a
look
at
their
notes,
trying
to
figure
out
more
of
it,
but
it
sounded
like
they
haven't,
really
started
anything
there
yet,
but
it
would
be
kind
of
good
to
see
if
we
can
link
into
their
discussion
about
it
and
see
what
they're
thinking
if
we
can
use
anything
there
for
free.
E
I
haven't
yeah
and
can't
remember
the
pedigree
was
the
ownership
and
the
province
was
the
life
cycle
or
where
it's
where
it's
at?
E
B
D
E
I
thought
I
had
it
when
she
was
talking
about
it
then
now
you
ask,
I
don't
remember,
I
must
have
committed
it
to
short-term
memory,
but
I
know
one
of
them.
I
was
like,
oh
that's
something
that's
in
the
life
cycle.
That
might
be
something
that
we
want
to
be
thinking
about
for
events
and
that's
as
far
as
I
got,
and
I
know
that
one
was
ownership.
C
C
Development
releases,
pedigree
and
upstream
and
downstream,
and
so
on,
that
is
providence.
B
B
E
Probably
will
start
depending
on
his
time
requirements
I
he
he
may
start
checking
out
on
this
particular
sig
or
project.
However,.
E
Meet
with
her,
we
have
a
meeting
with
her
coming
up
sometime
next
week
to
chat
about
sbdx
and
ortillius
and
ortelius.
Storing
some
of
this
because
remember
ortelius
is
just
a
massive
we're:
a
data
hoard,
we're
storing
data,
we're
starting
metadata
about
deployments
and
that's
why
he's
been
working
with
it
initially
to
find
to
add
to
that,
to
that
data
store.
B
D
D
B
D
D
B
Okay,
are
we
done
with
the
guess
so
on
the
dictionary
work
stream?
I
don't
know
if
there
are
we
we
had
a
very
short
meeting.
B
Was
it
two
weeks
ago,
very
few
people
ended
up
there
wouldn't
really
say
much
more
than
that.
At
that
meeting
people
hadn't
had
the
time
to
to
work
on
any
of
the
github
discussions
that
were
put
up
and
neither
on
the
pull
requests.
So
there
wasn't
much
to
discuss
actually
in
the
meeting.
I
believe
I
remember
so.
C
C
B
E
E
B
So
I
don't
know
if
we
should
discuss
that
decision
point
here.
The
discussion,
but
I
guess
my
take
on
it-
is
that
we
we
could
in
that
work
group
could
make
some
some
easy
decisions
and
then
but
then
they
need
to
be
based.
I
sort
of
present
it
to
the
sig,
I
guess
and
if,
if
needed,
then
it
can
of
course
be
reverted,
but
we
shouldn't
stop
the
vocabulary
group
from
progressing
proceeding
by
putting
a
strong
process
on
them.
E
B
D
E
E
So
I
can
why
don't
I
make?
Why
don't
I
do
this?
Why
don't
I
send
as
the
cdf
board
member
rep,
let
me
send
out
to
the
general
member
the
problem
with
the
general
member
list.
Is
that
a
lot
of
marketing
people
on
it,
but
I
can
send
out
to
the
general
member
list
of
a
a
description
of
what
we're
working
on
and
what
kind
of
help
we're
looking
for.
E
Let's
see
if
we
get
any
takers
there,
maybe
there
may
be
folks
from
harness
that
would
get
involved.
I
think
there's
might
be
folks
from
ops
that
we
get
involved
love
to
get
some
folks
from
snake
involved.
We
don't
see
them
hardly
in
anything,
so
I
I
we
can
do
that
and
see.
If
we
can't
get
some
more
conversation
around
this,
I
think
it'll
make
a.
I
think,
we'll
be
in
a
better
place.
If
we
do
do
that,
if
we
can
get
some
more
voices
in
it.
E
A
E
I
do
that,
what
what
link
should
I
send
to
them?
Should
I,
if
I
look
at
the
vocabulary,
where
is
the
vocabulary.
A
E
All
right,
I
will
send
him
that
and
the
and
the
discussions.
E
And
I
think
we
could
also,
we
can
also
ask
roxanne
to
push
it
out
on
the
on
twitter.
That
tends
to
get
more
feedback
and,
of
course,
we
can
put
it
on
on
slack.
We
can
put
on
the
general
channel
on
slack.
A
Good
yeah,
I
think,
with
the
with
the
early
days
as
well,
we
slow
down
a
bit,
so
hopefully
we
can
start
getting
back
to
the
discussion
within
this
group
as
well.
I
I
had
a
talk
to
prepare
as
well,
so
yeah.
There
are
things
getting
in
in
the
way
of
making
more
progress,
but
I
think
we
did
make
progress
so
hopefully
we
can
continue.
If
we
get
more
contribution,
that's
even.
A
Something
that
I
wanted
to
mention
is
that,
from
the
meeting
we
had
in
the
dictionary
meeting
we
had
think
was
on
the
23rd,
so
the
one
yeah
before
this
is
some
action
points
to
create
some
github
discussions
and
not
all
of
them
are
done
yet,
but
yeah,
a
good
amount
of
them
are
done,
but
there's
still
some
pending.
A
So
we
we
we
give
more
discussions
like
the
4k
specific
one
or
the
one
about
deployments
and
version.
Analysts
brought
up.
C
Yeah,
I
noticed
that
you
linked
to
the
github
version
of
it,
not
the
hack
md,
so
you
couldn't
click
on
those
links,
but.
B
B
A
Yep,
okay,
yeah!
I
can
take
next
session
so
for
me
type
conferences.
I
just
put
here
link.
We
will
have
a
virtual
header
and
ap
cdcon.
B
E
B
I
think
that
there's
no
drawback
is
it
I
mean
we
could.
The
belt
could
still
be
kind
of
a
panel
if
we
would
like
to.
E
A
D
E
A
Okay,
do
we
want
to
some
discussion
about
this
in
the
next
meeting,
or
do
we
want
to
set
up
a
dedicated
chat
or.
B
E
I
think
yes,
I
think
I
think
a
good
way
to
do.
That
would
be
to
come
up
with
different
topics,
and
I
can
we
can
treat
it
like
a
panel.
I
can
ask
the
questions
and
try
to
push
the
conversation
if
we
want
to
you
know,
we've
got
some
time
here,
but
if
we
want
to
start
a
shared
google
doc
and
start
just
thinking
about
the
questions
that
we
want
to
ask
ourselves
so
to
speak,
and
then
on
that
day
I
can
just
basically
work
from
the
shared
doc.
A
A
E
I'll
send
a
I'll
send
a
link
to
to
everybody
on
this.
A
Thanks
yeah,
I
guess
the
advantage,
maybe
being
it
above
is
that
we
can
do
the
panel-like
discussion.
We
can
have
our
answers,
but
also
other
people
will
be
able
to
join
in
and
we'll
have,
I
think,
two
hours
time
slot.
So
we
can
yeah.
D
E
A
A
D
B
B
E
There
are,
there
are
potential
spa.
I
know
that
there
are
stuff
that
the
the
day
zero
events
at
kubecon
there
are
still
openings
for
that
and
I'm
not
sure
what
those
day
zero
events,
but
kate
was
talking
about
something
as
well.
I
thought
on
the
spdx
side.
E
B
E
E
E
I
don't
know
if
we
should
submit
a
panel
or
if
we
should
have
one
of
you
submit
something.
I
really
don't
know
I've.
Never
I've
never
been
successful
at
getting
talks
accepted
at
kubecon,
but
that
doesn't
mean
we
wouldn't
be
able
to
it
just
means
I
haven't
been
able
to
so
I
don't
know
what
we
should.
The
reason
why
I
phrase
it.
That
way
is
because,
since
I
have
not
been
successful,
I
don't.
I
can't
even
think
what
we
would
pitch
unless
we
just
have
kubecon's
not
until
october.
E
If
we
try
to
get
our
if
we
say
we
want
to
have
our
initial
draft
of
our
vocabulary
done
by
end
of
third
quarter,
that
that
gives
us
quite
a
bit
of
time.
We
could
present
the
the
first
draft
of
the
vocabulary
and
that
might
get
accepted.
A
D
E
E
E
E
A
C
C
C
A
E
A
A
E
A
I
think
there
is
a
month,
so
we
could
still
discuss
it
next
next
meeting,
maybe
also
with
a
wider
audience
and
let's
see
if
we
want
to
do,
we
want
to
try
the
panel
what
we
want
to
do.
We
can
have
multiple
submissions
as
well,
so
I
mean
we
can
try
to
have
a
few,
and
hopefully
one
of
them
will
be
accepted
so
that
we
we
get
some
kind
of
representation
from
the
group.
D
A
Okay,
I
think
we
only
have
three
minutes
left
all
right,
so
if
there
is
anything
that
we
missed
the
discussion,
otherwise
maybe
we
could
close
it
here
for
today.
A
All
right,
oh
this
one
something
I
wanted
to
mention
so
as
I've
seen
gabe
is
her
name
she's
on
vacation,
so
hopefully,
when
she's
back
we'll
get
some
updates
about
the
recording
from
this
meetings.