►
From YouTube: CDF - SIG Events Meeting - 2021.09.27
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
C
A
C
Yes,
yes,
no
I've
not
done
that.
Yet
I
wanted
to
yeah
see
if
we
could
pick
a
name.
A
So
next
up
in
the
agenda
is
the
name
discussion.
We
think
we
thought
we
take
that
first
before
we
go
into
the
ordinary
agenda
items,
so
we
don't
miss,
miss
it
so
to
say
so.
The
results
are
as
andrea.
I
just
point
pasted
in
the
chat
as
well.
In
this
events
slack
channel,
we
only
have
five
replies
and
there
is
a
astonishing
majority
for
cd
events
in
that
one.
A
C
C
A
D
A
E
A
C
A
B
Yeah,
I
think
we
could.
I
would
follow
whatever
the
format
that
the
cd
foundation
is
using
for
themselves.
So
if
it's
cd.foundation
that
we
would
do
cd.events
or
if
they're
doing
something
with
cds,
then
a
space
then
foundation,
I
would
just
follow
whatever
that
format
that
they're
using
just
to
be
consistent.
A
So
a
domain
name
proposal
would
be
cd.events.
I
guess.
A
G
B
Yeah,
that's
the
way
the
cd
foundation
did
it
it
so
cd
foundation's
one
word:
I
think
we
should
just
do
cd
events.
One
word
at.
B
A
B
Right,
yeah,
that's
just
in
the
description
of
the
organization.
You
can
spell
it
out.
A
C
B
And
so
anybody
can
do
it,
it
doesn't
have
to
be
somebody
from
the
lanx
foundation
now
down
the
road
you
get
into
the
whole
security
thing.
You
know,
if
you're
using
teams,
which
seems
to
be
the
more
popular
route
to
set
up
teams
within
the
organization
that
gives
access,
but
initially
starting
you
just
give
everybody
access,
make
life
easy.
A
C
So
is
it
going
to
be
cd
event
or
cd
events,
because
in
the
poll
we
have
the
s
the
events.
C
B
To
start
out,
that's
the
easiest
until
you
can
go
and
substitute
that
down
the
road.
When
you
transfer
the
organization
to
the
linux
foundation,
I
think
they
would
go
into
the
organization
put
in
all
the
linux
foundation
stuff,
but
right
now
we
don't
have
to
worry
about
that.
A
Just
a
sec
because
I
believe
it's
best,
we
do
it
right
away.
So
do
you
see
my
screen
sharing
now
or
yeah?
You
do
right.
H
B
A
A
C
A
B
B
And
then
it'll
get
translated,
so
try
typing
in
capital,
c,
capital,
c
capital
d,
space.
A
A
Organization,
members,
okay,.
A
B
B
You
could
just
just
use
sb
taylor.
A
B
Either
way
you
can,
you
can
always
add
more
people
later.
So
it's
not
oh
there's
eric
has
his
on
the
phone.
G
A
And
we
should
have
some:
is
there
community
repo
first
or
what
should
we
have.
C
A
B
B
The
hurdle
of
having
the
organization
so
we're
good
on
that
front.
Yes,.
A
Yes,
so
we
can
maybe
I'm
not
sure
if
we
should
or
whatever
it's
there
now
so
what
about
the
name
then
name
then
has
someone
doing
the
time.
Looked
it
up
or.
E
A
A
B
What
what's
what
does
techton
use?
Is
it
a
dot,
io
or
dot
dot.
C
B
E
B
And
they
have
their
own
registry
and
stuff
like
that,
it's
so
it's
can
be
a
little
complicated,
but.
F
A
C
F
F
Sorry
in
the
wind
there
we
go.
That
should
be
better,
so
I
was
saying
if
we
want
to
follow
the
standard,
which
would
typically
say
that,
like
github.com
would
be
com.github.
If
you
want
to
turn
it
into
like
a
java
package
or
something,
then
it
would
probably
be
events.cd
that
we
want
to
follow
that
standard,
and
we
can
of
course
have
another
address
that
is
like
more
belonging
to
the
organization,
but
just
to
reserve
the
name
for
the
spec.
We
could
have
events.cd.
C
Yeah,
but
I
think
eric
has
a
point,
so
we,
if
we
decide
to
have
a
website
for
something
like
that
for
the
domain.
Sorry
for
the
website,
we
might
still
have
a
domain,
then
that
we
can
use
for
the
event
types,
because
the
cloud
spec
specification
says
that
your
event
type
should
be
the
reverse
of
dns
names
that
you
own.
So
then,
if
we,
if
we
own
the
events,
dot
cd
domain,
then
our
event
type
types
could
be
cd,
dot
events
dot.
Whatever
event,
it
is
right.
B
So
yeah
yeah-
that
does
make
sense.
I
would
see
I
I
think,
events
that
cd
make
sense
and
if
we.
A
F
First,
I
looked
at
the
iconic
south
africa
now
I'm
looking
at
webnet
africa
inside
and
now
it
comes
up
as
available.
So
I
guess
someone
just
needs
to
try
to
get
it
and
see
what
happens.
B
So
I
think
we
should
put
that
one
down
and
see
what
happens
we'll
have
to
open
an
issue
with
the
linux
foundation
to
have
them
grab
it
for
us.
Instead
of
us,
one
of
us
grabbing
it
and
trying
to
do
a
transfer,
then.
B
A
We
had
some
notes
on
that.
Didn't
we
some
time
ago.
C
A
B
So
I
think
the
there's
a
toc
meeting
tomorrow,
so
yeah
so
we'll
I'll
bring
up
at
the
toc
meeting
that
we've
decided
on
a
name
and
we've
created
an
organs,
just
kind
of
bring
them
up
to
speed.
And
let
them
know
that
that's
we're
moving
forward
and
getting
some
of
our
repo
reorganized.
C
B
On
the
they're
from
the
the
toc
side,
they're
reworking
some
of
the
there
are
some
stray
documents
that
were
around
about
becoming
a
project
under
the
cdf
and
we're
working
on
reorganizing
those
and
getting
some
templates
out
there.
So
I
have
to
find
out
if
that,
where
we
are
tomorrow
on
that
and
I
think
from
there,
we
should
then
look
at
the
the
next
steps
and
getting
a
a
project
proposal
in
front
of
the
the
toc.
B
It
probably
probably
be
like
at
least
a
month
or
so
out,
but
I
would
say,
we'd
want
to
shoot
for
year
end
to
have
the
events
be
a
project
under
the
cdf.
B
I
don't
think
we're
that
far
off,
but
I
think
we
just
need
to
make
sure
that
we
we
we
get
all
the
paperwork
sorted
out
correctly.
E
B
A
B
Exactly
that's
why
I
was
if,
when
you
put
the
two
of
them
next
to
each
other,
it
kind
of
that
I
mean
that
would
be
kind
of
cool.
So
if
we
had,
you
know
each
each
part
that
we
have
be
an
icon,
that
we
kind
of
string
together
and
tell
the
whole
full
story.
H
F
B
Yeah
those
aren't
as
crucial
with
the
twitter
handles,
I
mean
you
could
add,
dashes
and.
C
C
C
G
C
Yeah,
I
was
saying
I
think
in
any
case,
this
seems
like
the
the
the
main
things
that
come
to
mind.
At
least
we
have
to
address
the
name
I
mean
I
mean
we'll
need
to
when
we
move
the
spec
and
the
sdk
into
the
new
beta
r.
We
might
need
to
make
sure
that
all
the
naming
used
in
documents
as
a
aligned,
the
event
types
match,
and
I
think
we
have
cd
events
now
in
there,
if
I'm
not
mistaken,
so
that
should
work
quite
well.
B
B
Yeah,
the
only
other
thing
I
just
want
to
give
you
an
update
from
the
artilla
side
is
we're
working
with.
I
have
a
working
group
in
australia
and
they've
been
focusing
around
get
ops
and
argo
cd
and
captain.
So
from
the
artelia
side,
we
are
going
to
be
looking
at
events
for
between
kept
in
and
ortilius
and
we're
planning
to
write
those
in
a
cloud
event
structure.
So
just
to
give
you
a
heads
up,
that's
that's
we're
working
on
that.
Nothing
really
really
early
on.
B
So
once
we
have
more
I'll
I'll
share
that
with
the
group.
C
B
The
plan
is
to
so
in
the
the
the
captain
world:
they
have
a
concept
of
a
product
and
that
maps
over
to
be
in
the
ortilius
world,
what
we
call
an
application
and
then
they
have
stages.
You
know
stage
of
your
pipeline
and
we
call
them
environments.
B
So
there
is
a
a
good
map
between
the
captain
and
ortillius
other
than
some
wording,
but
the
idea
is
to
create
an
event
to
let
us
know
that
a
something's
been
built
and
that
we
need
to
register
that
service
in
the
ortelius
side
and
then
the
other
event
will
be
to
actually
deploy
so
in
captain
would
say,
deploy
this
product
to
this
stage,
which
translates
to
deploying
this
application
to
this
environment
in
the
ortilius
world,
so
that
there's
right
now
it
looks
like
there's
gonna,
be
two
event
types,
one
is
going
to
be
the
the
service
registration
and
then
the
second
is
going
to
be
the
deployment.
C
Have
than
a
plc
similar
to
what
we
have
done
with
pecton
and
captain
then
including
ortalia's
and
yeah.
So
if
we
can
even
align
on
the
type
of
messages
there
or
events
that
we
sent,
we
can.
B
Yeah,
it's
it's
early
on
so
once
I
know
more
what
the
exact
details
I'll
share
with
everybody.
A
Sounds
great
I'm
talking
about
the
lining
on
the
second
rope
meeting
last
week
or
last
time
there
was
a
presentation
on
the
jenkins
google
summer
code
project
for
cloud
events,
and
then
they
send
a
lot
of
events
from
there
now
and
they
said
they
got
some
inspiration
and
they
synced
with
some
of
us
in
the
sikh.
I
wasn't
part
of
it
myself,
but
I'm
pretty
sure
that
those
events
that
are
defined
there
are
not
exactly
what
we
have
defined
so
far
in
the
siege
protocol.
A
I
Yes,
yeah,
I
think,
in
terms
of
you
know
like
structuring
the
event
of
how
it
needs
to
look
like
it
needs
to
really
align
with
sick
team
and
like
you're
right
it
was.
You
know,
like
inspiration
more
in
terms
of
what
needs
to
be
sent
rather
like
than
the
structure,
and
I
think
that's
one
of
the
very
important
point
that
I
wanted
to
do
is
you
know
like
in
the
future
aligning
all
of
the
sort
of
that
event,
data
metadata
and
very
much
with
the
vocabulary.
A
So
what
is
the
status
of
the
the
plugin
right
now?
Is
it
like
it's
published
right,
so
it's
available.
I
Yeah
it's
published
as
so
right
now.
We
have
jenkins
as
a
source
of
card
events,
and
I've
been
working
on
jenkins
as
a
saying.
So
there
are
a
couple
of
things
with
consuming
events
from
jenkins,
which
you
know
again
is
a
bit
of
that
structure
issue,
because
if
the
events
were
more
standardized,
it
would
be
easier
to
find
what
or
how
do
we
want
to
filter
on
specific
attributes.
A
A
Yeah
I
like
sending
stick
events
from
or
to
captain
from
jenkins
or
to
jenkins
or
whatever
so
using
the
actual
cigarettes
that
we
define
and,
of
course,.
I
I
Because
there
already
is
a
similar
sort
of
like
the
the
poc
which
was
developed
for
by
andrea
and
also
mauricio,
for
using
captain
and
tucked
on
with
I'm
sorry
for
getting
my
wood.
So
we
can
like
move
that
similar
architecture
and
just
transform
that
vocabulary
using
our
calorie.
I
think
that
back
and
look,
I
believe.
I
A
A
A
C
Is
the
idea
for
the
sync
side
of
the
plugin
to
be
like
the
same?
Plugin
and
tank
is
basically
being
able
to
send
events
and
then
listen
to
answers
and
kind
of
orchestrate
the
events
sent
and
received
and
connect
them.
I
So
for
now
it's
you
just
sending
events,
but
this
was
one
of
the
point
that
came
up
with
also.
You
know
the
idea
that
you're
bringing
about
visualizing
and
holding
that
open
communication
between
the
receiver
and
the
sender,
so
that
that
is
something
that
I
I've
been
working
alongside
with
have.
Who
is
also
on
the
team
on
making
that
sort
of
architecture
for
both
the
source
and
the
same.
A
Okay,
so
to
not
drop
that
discussion
just
there,
what
would
be
the
next
steps,
I'm
sure
from
tectum
perspective,
andrea,
if
you
think,
is
something
that
you
can
be
part
of
or
someone
in
your
neighborhood
or
how?
How
should
we
drive
this.
C
Shouldn't
be
difficult
just
to
create
new
pocs,
I
mean
we
have
this
still
an
experimental
component
for
setting
cloud
events
in
the
cd
event
format.
So
it's
only
supports
the
the
events,
the
type
of
events
that
we
needed
for
the
poc,
but
if
we
need
different
kind
of
events,
you
should
be
pretty
straightforward
to
more.
F
C
A
C
Did
you
have
some
use
cases
for
the
summer
of
code
like
summer
of
code
that
you
worked
on.
I
Yes,
andre,
so
what
we
did
was
basically
because
we
had
the
first
part
working,
which
was
jenkins
and
the
sport
that
was
just
trying
out.
How
would
jenkins
send
events
to
like
a
broker
in
the
middle,
so
that
became
okay
native
and
then
we
were
sending
those
configurations.
So
then
was
extracting
all
that
information
from
event
data
and
just
you
know,
running
a
task
run
our
pipeline
run
depending
on
what
sort
of
information
is
received.
I
So
it
wasn't.
It's
not
a
very
like
a
detailed
plan.
It
was
just
to
sort
of
like
test
system
out,
but
but
maybe
this
is
something
that
we
can
build
on
top
of,
especially
in
terms
of
the
use
case.
You
know
if
we
want
to
trigger
something
in
intact
on
a
new
task
on
our
pipeliner
and
want
to
extract
certain
information
from
the
event
that's
sent
over
from
jenkins.
C
C
C
A
I
mean,
of
course
they
can
be,
they
could
maybe
be
updated
and
to
match
whatever
need.
The
jenkins
plugin
has
as
well.
I
Any
idea
yeah,
I
think
I
would
have
the
same
plugin
support
the
new
sort
of
cd
events,
events,
because
this
was
also
something
that
while
we
were
working
this
was.
I
I
think
this
was
important
for
me
since
the
start,
because
I
wanted
to
have
that
standardization,
so
I
was
very,
you
know
always
trying
to
figure
out
how
we
can
use
the
vocabulary.
So
I
I'm
going
to
probably
feel
better
that
if
we
integrate
it
into
the
same
event
plugin
rather
than
making
like
a
different
plugin,
because
that
will
have
to
support.
If,
if
that
is
going
to
support
cloud
events,
you
know
essentially
the
same
workflow,
but
just
using
the
events
vocabulary.
C
Yeah
yeah,
it
makes
sense.
I
agree,
I
don't
know
we
could.
C
We
could
maybe
try
and
continue
this
discussion
in
the
the
other
meeting
in
the
vocabulary
meeting.
F
C
A
D
A
A
A
A
Something
like
that,
oh
sorry,
yeah.
So
let's
keep
that
in
mind
for
next
yonder
as
well,
then
andrea.
I
can
put
an
ap
on
me
to
not
forget.
A
H
So
there
will
be
some
investigation
there
at
some
point,
but
the
focus
should
probably
be
actually
happening.
First,
yeah.
H
A
Just
a
few
minutes
left,
then
anything
we
should
mention
about
meetups
or
conferences.
Cubecon
is
approaching.
I
know
I've
already
placed
the
links
to
kubecon
before
anything
to
bring
up
there
tracy.
I
don't
know
about
the
or
something.
E
Not
yet
yeah,
we
still
have
that
booth
date.
I
haven't
gotten
anything
from
them.
Yet
in
terms
of
how
we
do
it,
let
me
shoot
an
email
over
to
tracy
miranda
or
jackie
to
find
out
for
those
events
how
we're
supposed,
because
I
have
three
of
them.
I
don't
know
if
we're
just
supposed
to
show
up
at
the
booth
and
we're
in
the
chat,
I'm
going
to
assume
that's
how
it's
going
to
be
done.
E
It's
october
13th
and
it's
10
am
mountain
time
which
would
be
noon
east
coast
time.
E
So
my
suggestion
is
to
just
jump
on.
I
don't
know
if
it
has
been
announced
yet,
but
kara
is,
I
believe,
starting
to
go
to
work
for
the
linux
foundation
shortly.
So
maybe
once
she
is
on
board,
we
will
see
more
activity
around
this
or
more
clarity.