►
From YouTube: SIG Events Meeting - Jan 11, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
C
D
D
Okay,
do
you
think
we
should
wait
for
him
or
no,
I
don't
know
if
he
will
join,
but
if
he
does
join
he
might
be
a
bit
late.
So
let's
just
start.
A
D
D
No
though
what
me
and
andre
are
working
on
is
the
four
stem
presentation
which
needs
to
be
recorded
and
uploaded
by
next
monday.
So
that's
the
current
focus
and
there
are
some
some
some
things
that
might
be
interesting
to
get
feedback
on.
I
don't
need
to
walk
through
the
whole
presentation
with
you.
I
think
that
will
be
a
waste
of
your
time,
but
some
some
things
that
could
be
discussed-
maybe
I
think
one
is-
is
what
from
a
cd
events
project
perspective,
so.
A
So
well,
we
can
have
a
round
table
as
well
for
adam
but
adam.
You
can
start
just
telling
us
who
you
are
and
what
your
your
intention
is
joining
us.
B
So
I'm
adam,
I'm
just
a
graduate
developer
for
est
and
I
just
joined
the
ctel
team
to
work
on
mostly
spinnaker
and
I'm
working
with
jillander
and
fatty.
If
he's
oh
he's
not
here
right
now,
but
yeah,
that's
pretty
much
it
for
now,
I'm
pretty
new
to
open
source,
and
all
of
this
so
be
patient
with
me.
If
I
don't
know
anything,
I
guess
thank.
A
You
you're
you're,
very
welcome,
so
est
is
the
company
that
fatty
also
works
for
the
ericsson
software
technology.
So
aaron
will
be
a
developer
in
that
company,
helping
out
developing
open
source
stuff.
D
A
Yeah
sounds
like
that
and
maybe
then
we
should
present
ourselves.
We
are
some
of
us
for
the
most
of
us,
the
usual
suspects
here,
so
I'm
emil
beckmark.
Both
you
are
yolanda
and
adam.
You
met
me
before
I
work
very
soon.
D
E
Steve
taylor,
I'm
with
deploy
hub
and
part
of
the
ortillius
open
source
project
as
well.
That's
underneath
the
cd
foundation.
C
F
Yep
go
next
matthias,
working
together
with
emily
in
erickson,
open
source.
A
Good
and
I
think
that
was
all
right
yeah-
I
can
also
mention
that
andrea
and
I
are
the
ones
sharing
the
the
sig
especially
interest
group,
which
this
meeting
belongs
to
that's
the
current
status,
at
least
okay.
So
now
eric
please
go
on
and
let's
try.
D
D
D
So
one
thing
I
think
that
tracy
has
brought
up.
This
is
yeah.
Basically,
we
need
need
people
from
the
other
big
players
in
the
continuous
delivery
area
to
help
the
line
on
on
events,
but
I
don't
think
we
can
just
say
say
that
in
a
presentation
say
we're
mainly
looking
for
people
who
are
already
in
big
continuous
delivery
projects
because-
and
I
don't
think-
that's
necessarily
the
only
truth
either.
A
Yeah,
just
to
frame
the
context
a
bit
the
foster
conference
is
is
stated
to
be
by
developers
and
for
developers.
So
it's
it's
mostly
developers
attending
the
conference.
It's
not
as
much
business
owners
or
managers,
so
that
kind
of
people
it's
it's
mostly
actually
developers
there
and
of
course
they
could
be
in
any
any
area.
The
continuous
integration
community
deployment
or
delivery
is
just
one
area,
and
I
guess
the
the
room
there,
the
is
it
called
dev
room
is,
is
called
ci
cd
right.
Is
it.
D
D
Yeah
right
now,
one
of
the
big
focuses
of
the
presentation,
or
one
of
the
underlying
message
is
that
using
or
when
cd
events
is
in
place,
there
will
be
less
work.
Writing
a
lot
of
glue
code
to
make
things
fit
together,
because
we
will
support
that
sort
of
or
projects
can
use
the
cd
event
specification
to
support
out
of
the
box
interoperability,
so
that
should
hopefully
be
appealing
to
to
developers
unless
they
are
more
found
than
I
am
of
writing
glue
code.
D
Yeah,
I
saw
andrea
had
a
fantastic
picture
that
I
really
liked
from
a
previous
presentation
where
there
was
a
bunch
of
logos
for
different
tools
and
they
were
differently
colored
differently,
styled
arrows
everywhere,
and
that
seemed
like
yeah.
It
basically
seemed
like
glue
code.
In
some
sense,
you
have
to
do
different
things
to
make
things
fit
together,
and
our
message
should
be
no.
We
can
actually,
we
can
enable
a
future
where
you
use
one
communication
tech
to
make,
but
yeah
it's
a
good
point
with
pushing
more
for
interoperability.
E
So
I
was
thinking
that
we
could
almost
kind
of
reach
out
to
folks
to
find
out
what
their
cicd
world
looks
like
you
know
what
what
are
all?
What's
your
diagram?
E
You
know
you
know
so
because
that
would
be
one
of
the
things
that
will
really
help
us
to
narrow
in
when
we
start
looking
at
the
next
events
to
do.
If
we
can
find
a
a
common
area
between
different
companies,
cicd
process
that
you
know,
maybe
it's
around
the
the
build,
for
example,
or
maybe
it's
around
deployments,
or
you
know
whatever
that
we
can
we
if
we
can
kind
of
collect.
D
E
Exactly
record
your
story,
you
know
that
would
be
interesting
and
I
know
some
folks
won't
want
to
divulge
the
company,
because
companies
don't
want
to
divulge
how
either
bad
they're
doing
or
good
they're
doing
because
of
different
reasons.
But
you
know
somehow,
if
we
can
make
it
more,
allow
them
to
be
more
generic.
C
D
Yeah,
I
think,
just
having
like
one
question
in
that
form:
can
you
just
list
some
of
the
tools
that
you
use
together
and
then
get
that
gives
us
really
good
input
for
like
okay,
what
what
problems
do
or
what?
What
use
cases
do
we
have
for
different
tools
that
that
people
need
to
have
interoperable.
D
E
A
Yeah
exactly
and
I
think
making
them
push.
Information
to
us
might
be
a
bit
hard
if
it's
a
very
complicated
form
where
they
need
to
write
a
white
paper
or
something
of
the
use
case.
So
maybe
it's
better
to
that.
We
pull
the
information
from
them.
So
if
we
can
more
or
less
get
some
contact,
just
a
name
from
them
and
mail
address
or
whatever
yeah.
D
D
We
can
even
skip
that
part,
but
I
think
I
have
a
feeling
that
people
would
be
slightly
more
willing
to
give
their
contact
information
if
we
also
asked
at
least
one
question
that
they
thought
was
relevant.
Otherwise
it
would
be
like
subscribing
to
a
an
anonymous
email
list
and
nobody
wants
to
do
that
so,
but
yeah,
it's
a
good
point,
make
the
form
easy.
That's
really
good.
D
A
So
as
long
as
you
have
a
name,
I
guess
during
the
conference
anyway,
I
guess
it's
possible
to
reach
out
to
people
in
the
conference.
E
Yeah
yeah
yeah
conference
communication
in
the
conference
shouldn't
be
a
problem
because
everybody
would
have
signed
the
appropriate
legal
stuff.
A
E
So
let
me
share
what
we've
we're
working
on
with
the
artelius
and
our
kind
of
flow
diagram
for
our
get-ups
model.
So
this
is
one
of
the
things
one
of
our
folks
is
putting
together.
It
uses
the
diagrams.net
and
it
basically
gives
you
the
flow
who's
doing
what
at
that
level.
E
E
So
we
have
captain
argo
and
ortelius
and
github
all
kind
of
plumbed
together
at
this
level,
and
it's
amazing
how
complicated
get
ups
becomes
at
scale.
A
Yeah,
I
think
if
people
find
your
presentation
interesting,
they
they
will
probably
be
interested
in
what
is
booking
a
follow-up
session
with
one
of
us
and
one
of
them
in
a
later
time
slot.
So
I
hope
that
that
should
actually
be
the
way
forward
here.
E
And
I
think,
like
andrea
was
saying,
maybe
just
a
simple
form,
to
kind
of
list
what
tools
people
are
using
a
google
form.
Maybe
we
we
pre-populate
it
and
let
people
check
you
know
which
tools
that
they
are
having
their
ci
cd
pipeline,
just
as
a
starting
point
to
collect
some
high
level
information.
E
And
then
you
know
we
can
then,
like
you,
said,
drive
into
some
more
detail.
It'd
be
great
to
be
able
to
get
get
pictures
of
people's
pipelines.
If
there's
an
easy
way
to
do
that,
to
understand
what
tools
doing
what
in
the
pipeline.
D
Yeah
yeah,
that's
something
to
think
about.
I
think
from
a
timing
perspective.
Since
again
the
the
recording
has
to
be
done
by
monday.
D
D
Yes,
yes,
that
is
true
or
we
can
create.
I
guess
we
can
create
a
short
link
that
we
can
later
re-point
to
something
else.
That's
a
good
point
very
good
point.
A
D
Yeah
then,
yes,
so
one
takeaway
that
we
want
people
to
have
done
is
what
we've
just
talked
about.
We
want
their
input
on
on
like
what
what
the
priorities
for
getting
things
to
work
together
and
how
their
flows
look.
Are
there
any.
B
E
Like
you
said
at
the
beginning,
working
on
the
the
glue
you
know,
so
one
is
getting
the
information
about
what
people
are
doing
then,
second,
is
how
we
take
that
information
and
implement
it
in
the
event
side,
and
so
it's
kind
of
twofold
one
is
fact
more,
the
other
ones
like
how
do
you
contribute
in
what
are
what
are
the
different
areas?
You
can
contribute.
E
So
those
would
be
the
two
main
topics
I
would.
I
would
consider
for
the
presentation.
Well,
third
topic
is
explain
what
it
is.
What
we're
doing
you
know
that
would
be
so.
Those
are
kind
of
like
the
three
high
level
bullet
points,
explain
what
we're
doing,
what
we
need
from
you
and
how
you
can
contribute.
C
Yeah
yeah
and
I
think,
on
the
how
to
contribute,
of
course,
if
someone
is
available
or
willing
to
do
it,
I
think
we
should
mention
that
we
are
always
open
to
presentations
in
the
sick
events.
I
mean,
if.
E
That
could
be
a
good
instead
of
people.
E
D
Yeah,
definitely
that
could
be
an
offer
as
well.
It
might
scare
some
people-
or
at
least
I
know
a
whole
bunch
of
people
who
are
really
not
fond
of
coming
into
an
unknown
group
and
presenting
stuff.
I
used
to
be
that
way.
Myself
perhaps
still
am,
but
some
people
will
really
enjoy
it.
I
think
we
can
offer
that
as
well.
E
Yeah-
and
I
think
what
we've
found
with
like
ortillius
is,
if
you
provide
a
a
calendar
link
to
get
on
somebody's
calendar
to
just
to
talk
about
some
just
15
minutes
to
talk
about
the
project
and
and
get
some
more
one-on-one
time.
I
found
that
that
works
really
well
and
we
use
one.
It's
called
once
hub.com
and
you
can.
D
Speaking
of
things
like
that,
it
would
be
good,
I
think,
to
update
the
see
the
events
github
repository
readme,
not
reaper
with
me.
The
organization
read
me
to
include
contact
information
that
is
not
already
there.
I
didn't
really
see
it,
but
like
come
talk
to
us
on
slack
or
join
the
github
discussion
or
whatever
channel
we
want
to
have
for
people
who
just
stumble
onto
the
github
project,
because
that
link
we
will
present
in
the
presentation,
and
it
would
be
good
if
that
can
be
like
the
starting
point
for
finding
everything
else.
D
C
D
A
D
D
We
we
mentioned
last
year
that
by
say
february
some
points
we
would
like
to
have
something
in
place
so
that
we
can
go
out
more
strongly
to
a
wider
audience,
and
I
think
we
discussed
a
little
bit
what
we
wanted
to
have
in
place
for
that.
But
I
don't
remember
that
much.
There
were
some
use
cases
that
we
wanted
to
enable,
I
think,
or
at
least
have
written
down.
D
I
don't
have
any
other
things
in
mind.
Basically,
the
structure
would
be
where
they're
already
intended
structure.
We
will
start
with
storytelling,
then
go
on
to
introductions
talk
about
what
is
continuous
delivery
events.
What
is
cd
events,
some
use
cases
and
then
what
cd
events
can
do
for
you
and
the
way
forward
and
wrapping
up
with
some
key
takeaways
and
questions.
C
Maybe
one
question
I
mean
we,
I
think
we
plan
to
show
two
use
cases
and
my
idea
would
be
to
to
maybe
have
one
use
cases
with
this,
which
is
specifically
related
to
interoperability,
between
tools,
so
tool,
x,
y
z,
talking
together
and
the
other
use
case
more
about
like
collecting
information
consistently
across
different
tools
which
are
not
necessarily
talking
to
each
other,
like
the
the
four
keys
or
metrics
type
of
use
case.
If
you
will
right.
A
Yeah,
I
think
it's
good
to
have
those
both
both
those
points
in
the
presentation
makes
sense.
It's
only
the
first
one.
I
guess
it's
so
well.
The
first
one
is
more
about
interoperability
than
the
other
one,
but
in
some
sense
it's
interoperability
as
well
between
a
reporter
environment
or
csd
system
and
its
metrics,
collector
or
visualizer,
or
whatever,
that's
in
some
sense
interpretability
as
well.
D
I
guess
for
for
kubecon
it
it's
more
likely
that,
since
it
is
the
the
dora
metric
so
to
say
for
this
one,
I
I
don't
have
a
strong
opinion
on
it.
It
might
be
easy,
but
we
could
also
say
that
basically
anything,
but
that
we
want
to
understand
about
what
the
system
is
doing
or
where
we
are
in
the
catalog.
A
A
E
A
January
28th,
so
if
you
want
the
first
track
to
get
accepted,
it
should
be
done
by
the
end
of
january.
A
E
And
I
think
we
could
reuse
what
we're
I
don't
think
we're
going
to
need
to
stray
from
what
we
just
did.
What
we're
planning
to
do
for
fosdem.
E
For
another
meeting
but
looks
like
we're
moving
along
pretty
good.
A
A
Yes,
oh
well,
there
is
a
ticket,
the
github
ticket
for
it.
I
can.
I
found
it
right
yesterday,
yeah,
I
don't
need
to
see
it.
I
just
want
to
make
sure
someone
is
on
top
of
it.
Oh
well,
I'm
not
sure
anyone
has
to
take
it
on
the
task
to
actually
do
it,
but
I
saw
that
there
is
a
ticket
for
it.
It
was
created
by
oleg.
A
A
D
Yeah,
at
least
we
will
we'll
want
one
logo
to
have
in
the
presentation.
We
can
pick
the
closest
one
that
you
think
is
going
to
win,
but
if
we
can
settle
it
before,
then
that
would
of
course
be
pretty
nice
as
well.
A
H
A
A
A
D
My
issue
with
the
third
er
or
to
write
to
the
third
row
is
that
that
out
the
leftmost
wave
and
the
c
they
form
together
the
side
profile
of
a
head
to
me.
You
have
the
upper
top
of
the
head
and
then
the
ear
at
the
bottom,
which
might
be
good
or
bad.
But
that's
the
only
thing
I
can
see
when
I
look
at
that
combination.
D
A
C
A
I
think
we
also
requested
a
version
with
with
just
the
cd
and
not
the
events
at
all.
I
mean
more
or
less
just
an
icon
without
any,
but
the
cd
is
there
because
it's
part
of
the
so
I
think
I
see
you
andrea,
did
a
comment
in
in
the
in
the
request
earlier.
A
D
It
might
end
up
being
horribly
unbalanced
if
we
only
have
text
to
the
right.
Sorry
to
the
left
of
the
stem
of
the
d.
What
I
did
just
for
for
my
own
experimentation's
sake
is
I
kept
the
cd
and
I
kept
the
e
for
events,
but
I
made
it
bold
and
I
also
stretched
it
out
a
bit.
It
doesn't
look
good
to
have
a
stretched
e,
but
at
least
it
balances
the
whole
whole
logo,
so
it
doesn't
tip
over
to
one
side.
I'm
not
sure
if
something
clever
can
be
done
there
in
some
way.
D
Will
the
plan
for
for
the
next
couple
of
months
be
to
have
this
meeting
as
a
cd
events,
project
meeting
or
by
la
city
event
spec
meeting,
I
guess
in
some
sense
and
to
have
the
other
meeting
as
a
sig
events
meeting,
or
should
we
set
up
a
different
cd
events
project
meeting
as
well?
Just
so
we
don't
so
nothing
forced
between
the
chairs,
as
you
say,.
A
Yeah,
I
think
we
at
least
said
that
the
initial,
like
bootstrap
committee
for
the
cd
events
project
will
be
the
sig.
In
some
sense.
Maybe
it
should
be
for
more
formal
with
some
persons
allocated
to
it
really
not
just
me
and
andrea
stairs
or
something,
but
some
more
people
actually.
A
A
So
for
the
rest,
it
hasn't
been
there
today,
but
where
we
discuss
the
protocol
more
in
in
detail,
so
we
don't
stop
evolving
the
protocol
at
the
same
time,
yeah,
that's
ask
us,
as
we've
seen
today,
it's
it's
very
easy
to
take
all
the
time
to
discuss
smallest
administrative
things
and.
A
A
C
D
I
think
it
would
be
really
interesting
to
see
that,
however,
that
would
look
and
it
could
definitely
be
a
contender,
I
think,
as
well
yeah.
I
think
that
it
seemed
like
the
the
the
designer
would
appreciate
exactly
what
you're
giving
now
like
very
concrete
ideas
and
yeah
take
this.
Do
this
this
this
and
this.
So
if
we
can
give
them
that
they
might
be
able
to
come
back
a
bit
quicker
than
last
time,.
A
D
I
I
voted
for,
or
I
suggested,
having
one
where
the
waves
are
thinner,
just
to
see
how
that
would
work,
but
we
maybe
those
two-
can
form
the
base
of
a
new
set
of
proposals
that
would
allow
us
to
take
things
even
further
and
of
course
I
mean
we
cannot
always
change
the
logo
later.
It's
not
like
we're
going
to
print
the
thousand
business
cards
tomorrow.
So
it's
it's
reasonably
easy
to
switch
things
out.
If
it's
just
small
small
changes.
A
A
A
F
Should
we
put
in
some
kind
of
example,
for
a
stacked
version,
so
they
know
what
we're
talking
about.
F
F
Yeah,
because,
if
you're,
if
you
remove
mts
from
the
from
the
end,
you
get
cdb.
A
D
C
B
F
Yeah,
that's
from
one
that
I
I
was
trying
to
do
something,
but
I
didn't
manage
there.
A
F
And
the
that
other
one,
where
you
remove
half
of
the
stuff.
F
Yeah
and
if
we're
supposed
to
follow,
I
know,
there's
been
logos,
redone
and
people
have
complained
so
much
about
them
because
they're
so
simple
and
but
maybe
as
an
icon
and
if
you're,
if
you're
having
it
small,
then
it
might
be
easier
having
it
very
stylish.
B
A
D
My
colleagues
suggested
having
yeah
keeping
the
e
making
it
the
same
size
and
and
weight
as
the
other
letters
to
the
left
and
then
nudging
it
slightly
to
the
right.
So
it
feels
a
bit
more
balanced.
I
can
give
that
a
shot
at
some
point
to
see
how
that
would
work,
but.
A
And
again,
I'm
not
really
sure
what
the
cde
would
be.
Then
we
should
maybe
start
using
that
abbreviation
as
well
somewhere
or
say
that
it's
an
official
abbreviation.
G
A
A
C
Okay,
do
you
want
to
put
some
of
these
ideas
for
a
stacked
version
in
the
github
issue
as
well?
C
Just
see
I
mean,
I
think
at
least
we.
We
have
a
good
feeling
about
this
font
and
this
color
polite.
C
F
Yeah
I
mean
we
could
give
like
two
of
the
versions,
maybe
the
second
and
the
last
one
or
something
and
then
say
the
second
one
is
more
fuller,
but
it's
unbalanced
and
the
last
one
feels
more
balanced.
But
it's
not.
F
F
But
I
agree
that
the
the
big
pro
with
the
last
one
is
the
stylishness
in
it
it's
simple
and
stylish,
and
I
think
it
would
do
a
great
deal
as
a
icon,
because
it's
so
simple.
C
B
C
Okay,
anyone
do
you
want
to
consolidate
this
feedback
email,
maybe
on
the
ticket
or.
A
F
The
landscape
picture,
and
do
you
want
to
use
one
of
them
as
preliminary
one?
So
we
just
have
a
logo
and
we
can
publish
last
picture
or
do
we
want
to
wait
until
we
have
the
final
version.
A
I
think
there's
always
a
risk
of
publishing
some
imageware
and
people
will
start
copying
it
and
using
it
and
whatever
all
over,
not
least
the
cdf
themselves.
I
think
we'll
start
using
this
logo.
If
they
just
get
get
get
their
hands
on
one
of
them
preliminary,
they
will
start
using
it,
and
then
we
will
have
a
hard
time
updating
all
those
sites
later
on
with
the
correct
logo,
I'm
afraid.
F
Or
ask
ask
cara
if
she
has
some
ideas
around
there's
this
routine
from
adding
a
perimeter
logo.
A
Yeah,
I
see
we're
out
of
time
for
today
we
spent
the
whole
meeting
or
half
of
meeting
discussing
the
logo,
but
it's
a
could
sound
useless,
but
I
think
it's
quite
important
to
have
a
good
logo.
Actually
I
think
it
was
worth
it
so
okay,
so
I
will
note
something
about
this
in
the
issue
tomorrow
and
if
you
have
any
more
follow-up
or
if
you
don't
agree
or
whatever
you
can
comment
on
it
and
of
course
we
should
reach
out
in
slack
as
well
and
pick
here.