►
From YouTube: CDEvents Working Group (EMEA/AMERICAS) - June 27, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
B
E
E
C
A
C
Hi,
so
my
name
is
comit
I'm
from
J
frog
today
to
hear
a
bit
about
this
project
and
since
I've
read
this
bag.
I
had
some
questions
about
the
events,
the
the
more
important
for
us.
This
I
was
wondering
if
I
could
be
added.
D
Sure,
okay
yeah
welcome
everyone.
So
let
me
share
a
link
to
you
today
notes
that
everyone.
D
I
said
yeah,
so
I
put
a
few
a
few
things
on
on
the
agenda
but
feel
free
to
to
add.
E
E
D
Questions
so
let's
make
space
for
those
for
sure
so
feel
free
to
add
yourself
to
the
participant
list
as
well
and
yeah
for
the
agenda
for
today.
First
item
I
mean
new
attendees,
but
introduce
yourself
already
so
welcome
again.
Kermit
just
wanted
to
review
quickly
action
items
a
couple
of
updates
first
and
then
we
can
maybe
switch
to
the
discussion
about
events
for
our
artifactory.
D
So
the
only
action
item
I
had
from
last
time
was
about
selling
at
permitting
for
the
Spinnaker
folks
for
CD
events,
demo
I
don't
know
jalander
do
you
know
if
anything
happens
on
that
front,.
F
So
the
review
is
happening
like
the
Spinnaker
peers
are
getting
reviewed,
but
demo
is
not
scheduled.
Yet
so
I
will
ask
Ben
to
second
one
again,
so
probably
he's
he's
finding
the
people
right
people
to
have
set
up
set
up
the
meeting,
so
I'll
check
with
Ben.
E
E
E
D
D
F
F
Yeah
right
so
like
couple
of
events,
I
play
a
dip,
so
it
will
be
same
for
all
of
all
of
the
events
like
once
the
spr
is
reviewed,
so
we
are
good
to
have
this
generating
SDK
for
all
all
other
events,
yeah
and
I'll
I'll
update
with
this
different
releases,
then.
D
Okay,
then
I
just
wanted
to
provide
some
quick
updates
on
the
tools
adoption
threads
that
we
have
so
in
terms
of
Harbor
The
Proposal
is
out
there
and
it's
being
reviewed.
This
has
an
approval
already
and
I
went
ahead
and
made
a
implementation
for
that
and
I
plan
to
do
a
demo
today,
Arbor
working
group
tomorrow
show
how
that
that
works
and
in
terms
of
tactone
I
got
the
announcement
proposal
up.
D
So
it's
also
being
reviewed,
and
the
idea
is
to
move
the
current
experimental
implementation
to
the
official
tectum
Branch
and
in
terms
of
Argo
CD,
add
a
quick
thing
with
Michael
who
made
the
proposal
and
is
currently
working
on
an
Argo
City
release,
but
hopefully
next
week
we
will
resume
work
on
that
and
work
on
a
POC,
so
anything
from
Spinnaker.
We
already
got
an
update.
D
And
I
wanted
to
ask
if
anyone
had
any
news
on
the
test:
Cube
implementation,
because
I
remember
all
they
mentioned
that
the
implementation
was
done
some
time
ago
and
it
was
waiting
for
a
release.
But
I
haven't
heard
any
news
whether
the
release
was
made
and
if
that
is
available.
Yet
in
a
test
Cube
release,
if
not
I
will
reach
out
to
to
Orlando.
D
B
I,
just
added
that
so
or
Taylor.
We
have
been
working
with
the
guac
people
that
are
part
of
salsa
and
we
pitched
and
that's
a
company
called
kasari
software.
It's
a
handful
of
guys
from
Citibank.
B
They
we
are
going
to
reconnect
in
September
and
they're
going
to
reach
out
internally
if
they
would
like
to
work
with
the
artillius
team
to
start
building
out
the
use
cases
and
events
for
security.
There's
it's
going
to
be
a
pretty
it's
going
to
be
pretty
broad,
because
there's
a
lot
of
new
security
tools
that
we
need
to
include,
but
just
to
note
that
that
is
potentially
in
the
works
and
I'm
going
to
continue
working
on
getting
a
team
together
to
start
building
security.
Events.
D
Yeah
thanks
thanks
Tracy
yeah
I
mean
it
would
be
great
to
to
get
people
contributing
to
that.
B
B
Can
I'll
continue
working
with
the
tool
belt,
the
open,
ssf
tool
belt
on
that
topic.
B
B
D
Yeah
I
would
say
before
we
get
into
discussions
about
this
pack.
Maybe
it's
a
good
time
for
to
stop
us.
I
think
this
is
all
the
the
updates.
Unless
there
is
anything
else.
B
We
did
just
a
note.
We
did
do
our
CDF
online
Meetup
last
week,
the
test
Cube
folks
presented
and
they
did
several
slides
on
CD
events
in
their
work
there
and
that
is
uploaded
to
the
CDF
YouTube
channel
and
there
is
a
CD
of
online
Meetup
playlist
that
you
can
find
it
in
and
I
Roxanne's
been
pushing
it
out.
C
Okay,
thank
you
so
I
reviewed
this
spec
and
looked
at
the
the
different
events
that
were
defined.
B
C
So
and
most
of
this,
the
events
defined
seem
to
me
to
be
coming
from
a
Ci
or
a
CD,
or
two
and
I
wondered
if
we
could
add
events
that
happened
later
on
in
the
pros
in
the
process
in
the
change
management,
for
example,
if
you've
uploaded
a
few
artifacts
and
now
you
want
to
bundle
them
inside
a
release,
bundle
and
then
promote
that
release,
bundle
to
let's
say
an
environment
called
Dev
and
maybe
then
to
an
environment
called
staging
and
then
they
want
to
distribute
them
to
an
edge
node.
C
Can
these
be
events
that
are
defined
in
the
spec
I
mean
not
the
actual
environment
name,
but
just
the
event
of
promotion
of
the
of
a
release.
Candidate.
A
C
C
So
I
would
suggest
that
there
will
be
an
event
of
bundling
of
collecting
a
few
artifacts
and
defining
these
as
a
release
candidate.
For
us,
we
just
the
name
we
use
internal
is
released
bundle,
but
it's
a
release.
Candidate
can
be
called
during
this
candidate
also
and
then
promoting
it.
The
event
of
promotion,
the
and
the
distribution
and
then
I
guess
for
some
for
some
customers.
For
some
people
there
will
also
be
a
deployment
for
some.
It's
just
a
distribution,
and
at
least
maybe.
C
D
Yes,
I
think
a
few
of
these
with
we
discussed
in
the
past,
but
we
have
not
implemented
yet
so
I
think
we
discussed
about
handling
of
artifacts.
So
today,
even
we
have
deployment
type
of
events.
We
don't
have
release
type
of
events
and
in
those
deployment
events
we
only
refer
to
a
single
artifact,
but
we
knew
that
this
was
kind
of
artificial
limitation.
We
always
plan
to
introduce
the
concept
of
bundling
at
some
point,
so
that's
definitely
something
that
we
discussed
and
I
think
will
be
interesting
to
to
have.
D
We
didn't
specifically
discuss
about
bundling
events,
but
that
makes
sense
to
me
as
a
possibility
for
sure
promotion.
I,
don't
think
we
discussed
before,
but
I
agree
with
Emil
that
this
is
something
that
we
definitely
could
consider
and,
as
you
mentioned
car
may
not
everything
is
about
deployment,
it's
also
about
releases
and
so
I
guess
yeah.
Making
these
promotions
and
finally
releasing
artifacts
is
something
that
we
could
consider
yeah.
So
I
think
all
this
sounds
interesting,
I
guess.
D
As
a
first
step,
we
should
probably
track
this
into
into
some
GitHub
issue
so
that
we
can
then
continue
that
detailed
discussion
for
on
on
those
as
well.
Oh
sorry,
I
see
that
someone
is
there
and
raised.
H
At
kind
of
a
similar
vein
of
thought,
of
maybe
tagging
artifacts
with
some
sort
of
metadata
and
for
I
mean
maybe
thinking
back
to
the
previous
item
of
tagging,
an
artifact
with
the
security
vulnerability
for
fire
use
case.
We've
wanted
to
tag
artifacts
as
having
regressions
or
bugs,
and
so
I
was
wondering
if
it
sounds
like
not
exactly
the
same
as
what
Carmen
was
mentioning.
H
But
having
some
way
to
add
tags
to
artifacts
is
something
that
we've
already
been
thinking
about
and
sort
of
toying
within
our
side
and
I'm
wondering
if
that
is
similar
or
just
completely
different,
or
you
know
we're
using
the
same
words.
But
does
that
actually?
Could
it
be
part
of
this
kind
of
update.
C
So
for
us,
when
we
do
a
bundling
of
artifacts,
some
of
the
artifacts,
you
bundle
inside
the
release,
candidate
might
be
documentation
and
it
might
be
artifacts
is
that
just
for
metadata
on
on
them,
I
mean
for
the
factory.
We
have
properties,
of
course,
so
you
could
just
put
in
the
properties
they
will
be
bundled,
but
you
could
also
add
artifacts
that
are
metadata
describe,
describing
like
documentation
or
release,
notes
or
anything.
H
Yeah
I
mean
we
have
a
thought
line.
Sir
I
will
lower
my
hand
I
think
we
have
a
I
thought
like
a
particular
type
of
meta
data
tagging,
but
if
it
was
General
like
we
could
work
with
it
or
if
it
helps
to
be
more
specific,
we
can
maybe
just
outline
our
use
case
in
a
GitHub
issue,
and
then
we
can
talk
about
whether
it
should
be
more
general
or
more
specific.
D
So
one
one
question
from
from
me:
I
mean
about
this
type
of
events
and
artifacts.
Are
these
all
envisioned
as
events
that
would
be
generated
by
artifact
and
registry
or.
C
For
us
I
mean
it
will
probably
just
be
a
Web
book
or
some
kind
of
plugin
that
we
can
add
to
these
events,
because
these
events
are
important
within
the
scope
of
a
binary
repository.
So
foreign.
H
Use
case
it
would
be,
you
know
there
could
be
something
that's
creating
the
artifacts
and
then
something
else
that
is
doing
some
sort
of
verification
or
validation
and
then
from
there
wanting
to
tag
an
artifact
with
certain
properties.
C
Actually,
I
would
assume
that
the
event
will
not
include
any
tagging
or
properties,
but
just
say
this
is
the
event.
This
is,
these
are
the
included
artifacts
or
this
is
how
you
get
the
included
artifact
and
then
a
username,
a
consumer
can
use.
You
can
use
the
appropriate
apis
I'm
guessing
each
each
repository
will
have
its
own
apis
for
retrieving
any
tags
or
properties
or
anything
on
these
artifacts
or
on
the
release.
Bundle
as
a
whole.
C
So
what
I'm
saying
basically
is
I
think
it's
a
minimum.
The
these
events
need
to
say
what
are
the
artifacts
that
were
bundled
or
what
is
the
bundle
that
was
promoted
and
where
to
and
what
was
the
bundle
that
was
distributed
and
where
to
and
then
you
could
just
query
the
system.
Any
system
for
the
rest
of
the
information.
D
H
Distributed
and
then
at
some
later
point
it
would
be
that
you
know
later.
G
H
Someone
has
a
security
check
that
determines
that
the
artifact
contains
a
bug
or
contains
a
vulnerability,
and
so
I
I
don't
want
to
conflate
the
idea
as
if
it's
a
separate
thing,
it's
okay,
but
in
our
in
our
world
we
were
thinking
of
the
same
sort
of
word
of
the
artifact
being
tagged
as
with
some
property
that
can
be
in
different
subject.
If.
H
I
think
you're
coming
for
sure
we
can
maybe
describe
a
bunch
of
different
types
of
events
and
if
it's
easiest
to
be
very
general,
like
just
tagging,
a
artifact
with
some
kind
of
vulnerability.
That's
fine!
If
it's!
If
we
cannot
sort
of
determine
a
few
well-defined
use
cases
that
cover
a
lot
of
our
famous
needs
to
be
more
specific,
I'm
open
to
you.
There.
D
Yeah
I
know
some
I've
been
working
a
bit
with
the
harbor
registry.
I
know
that
they
have
a
concept
of
labels
there,
for
instance,
so
I
think
for
them
as
well.
They
might
be
possible
to
to
have
events
about
labels
being
added
or
removed
from
from
artifacts,
but
I
guess.
The
use
case
for
those
tables
is
mainly
also
again
security
oriented
the
way
that
is
used
to
to
tag
an
artifact
as
being
scanned,
or
things
like
that.
So.
D
Okay,
I
think
that's
that's
a
lot
of
input
a
lot
to
process,
but
it
sounds
very
interesting
to
me
so
I
think
today.
The
the
only
event
we
have
today
that
is
really
targeted
to
to
Registries
is
the
artifact
pushed
event.
D
I'm
I
think
it
would
be
definitely
good
to
to
have
some
some
more
of
these
events
for
things
like
releases
I
think
we
might
want
to
have
like
a
generic
event.
I'm
not
sure
we
should
have.
We
could
have
I
mean
we
will
need
to
discuss,
but
we
could
have
like
one
specific
to
the
artifact
repository
and
also
generic
release
event,
or
it
could
be
the
same.
E
A
Yeah
I
mean
I'm
thinking
a
bit
about
this.
This
bundling
what
that
really
is
in
general
terms,
I
I
realized
that
that's
what
is
called
in
a
factory
today,
so.
A
C
So
if
an
artifact
is
a
Docker
or
a
jar
file
or
a
name
PM
or
I
mean
a
bundle
will
include
all
of
these
and
the
helm
chart
that's
used
for
I
mean
it's
usually
what
we
see
with
the
customers,
especially
B
customers,
is
that
abandoning
will
contain
potentially
tens
of
artifacts
of
packages
of
our
artifacts
or
maximum
I
mean
the
maximum
I've.
Seen
that
I
think
is.
Legit
is
a
few
hundreds,
but
we
also
have
people
with,
like
thousands.
C
I,
just
if
I
could
not
suggest
normal
thing,
it's
for
me
when
I
looked
at
the
spec
I
was
missing
something
that,
as
a
consumer,
is
very
interesting
for
me.
If
I'm
looking
at
myself,
not
as
a
producer
but
as
a
consumer,
getting
a
transitions
of
tickets
like
jira
tickets,
this
something
that
I
think
I
would
love
to
subscribe
to
as
an
event.
C
For
example,
it
would
be
if
a
customer
has
a
jira
that
was
turned
into
a
release,
bundle
or
maybe
an
artifact
even
before
the
release
bundling,
and
there
is
Finance
person
that
clicks
on
this
is
approved
from
finance
and
I
know.
I
can
promote
it,
for
example.
So
that's
something
that's
that
I
think
is
an
interesting
event.
D
D
Yeah
issue,
tracking
events
is
also
something
we
can
come
that
has
come
up
before
Brad
brought
it
up
in
the
previous
meeting
and
I
think,
there's
also
a
collaboration
that
we
started
with
value
stream
management,
interoperability
group
and
they
are
interested
in
a
scope
slightly
broader
than
what
we
do
in
City
events
today.
D
So
for
them
from
their
point
of
view,
they're
interested
in
a
feature,
definition
that
goes
through
epics
features
and
then
implementation,
that
is
the
specific
PRS
and
then
all
the
way
to
being
something
being
in
production
and
producing
value.
As
closing
the
cycle
back
to
defining
new
features,
so
they're
they're
interested
as
well
in
having
a
way
of
modeling
things
like
issues
in
as
part
of
City
events
or
some
extensional
City
events
and
I
think
this
is
definitely
an
area
that
seems
to
be
interesting
for
for
us
as
a
project
to
to
be
addressing.
D
Yeah
so
I
think
we
discussed
it
until
now,
more
in
the
context
of
links
to
SCM
type
of
systems
so
being
able
to
associate
changes
in
the
code.
Two
issues
I
think
you've
understood
what
you
were
suggesting
from
it
correctly.
C
I
mean
I
mean
it's
not
an
easy
task
to
find
the
artifact
that
is
linked
to
a
jira
ID,
but
I
do
believe
it's
possible
to
s-bombs
building
cells
and
git
commits
and
stuff.
D
Yes,
yes,
so
the
definitely
one
one
of
the
things
that
we
would
like
to
to
be
able
to
do
is
to
to
be
able
to
kind
of
build
it
in
type
of
audit
trade
for
artifacts
to
to
track
to
connect
all
the
events
with
each
other,
so
that
you
start
with
a
certain,
maybe
issue
ID
but
yeah.
Then
you
have
VR
senior
system,
your
certain
tests,
Security
checks,
bills
that
are
executed.
All
these
will
produce
events.
D
You
have
artifacts
generated
and
stored
in
an
artifact
registry,
and
so
if
we
had
the
ability
of
connecting
all
these
events,
you
would
be
able
to
navigate
this
chain
of
events
and
so
associate
your
artifact
ID
with
it
specific
dress,
ideas
Associated
to
those.
So
there
is
one
bit
of
work
that
we
are
discussing.
That
is
the
main
chunk
of
work
that
we
are
planning
for
the
next
three
days,
which
is
the
ability
to
to
connect
events
with
each
other.
D
So
that's
something
that
we
are
working
with
banned
from
Apple
and
ml.
So
Ben,
unfortunately,
could
not
be
here
today
to
to
present
his
work
but
yeah.
So
just
the
next
item
of
the
agenda
is
about
connecting
events,
and
he
he
prepared
a
PR
for
for
us
to
review.
So
that's
also
something
if
you're
interested
in
in
this
and
everyone
in
this
group.
If
they're
interested
I
think
the
most
the
more
input
we
get
on
this
topic,
it
would
be,
it
would
be
great.
D
Okay,
yeah
I
tried
to
capture
the
discussion
here
in
the
notes,
but
I
think
it
would
be
great
then,
to
to
go
and
track
this
in
into
GitHub.
D
Is
that
something
you
would
be
interested
in
in
doing
maybe
Define
some
use
cases
or
some
of
these
ideas
in
GitHub
issues,
Kermit
or
I
can
also
start
and
creating
some
some
item
based
on
the
discussions
that
we
are
today
but
I
think
it
would
be
great
then,
to
to
have
some
further
feedback
and
continue
in
the
discussion
there.
C
If
you
could
send
me
something
initial,
I
can
work
with
you
on
refining
it.
So
I
want
to
close
the
inside.
C
So
it's
attitude
the
correct
places.
So
if
you'll
send
me
something,
I
can
help
and
add
date.
D
D
Okay,
but
thanks
a
lot,
I
think
this
is
really
helpful
for
for
us
to
the
more
use
cases
we
we
have
and
I
think
it's
really
useful
for
for
the
project
to
move
in
the
regular
Direction,
so
I'll
start
creating
some
of
these
issues.
We
also
had
one.
D
D
So
I
do
have
one
question
about
Registries.
If
you
don't
mind,
car
meets
inside
you
here,
so
I
was
looking
at
the.
D
What
Harbor
does
in
terms
of
events
as
I've
been
implementing
a
POC
for
the
for
those,
and
they
have
this
these
events,
so
they
have
events
for
Push
Pull
and
delete
artifact
scanning
completed
scanning
stops
scanning
failed,
so
events
about
quarters,
replication
and
tag
retention,
I
was
trying
to
figure
out
what
which
of
these
events
would
make
sense
in
general
to
bring
into
CD
events
as
a
specification
and
I
think
it
would
be
good
to
consider
events
that
are
relevant
or
most
registries.
D
C
The
deploy
the
push
is
significant.
Obviously
we
also
handle
when
we
handle
web
of
events,
so
we
also
allow
move
or
copy.
C
Of
course
there
is
distribution
which
I
think
is
called
replication.
Maybe
on
yeah
I
mean
it's
not
the
same.
Actually,
replication
isn't
the
same
like
distribution,
but
it's
my
thing.
I'm,
not
sure
application
is
General.
It's
it's
interesting
enough.
D
Yeah
I
think
they
allow
for
retention
rules
to
be
set,
and
so
this
is
about
the
retention
rule
being
processed
I.
Think.
C
C
C
Scanning
is
very
interesting,
but
it's
not
really
a
registry
event.
It's
a
security
product
event,
I
mean
if
we
would,
if
you
would
fire
such
a
scanning
event,
it
would
be
from
our
x-ray
product
not
from
the
artifact.
E
E
A
A
So
it's
more
like
the
tagging
of
events
that
I
think
Dan
was
into
as
a
post
operation
after
it
has
been
pushed
to
the
registry.
A
C
I
mean
you
wouldn't
even
know
if
an
artifact
was
scanned,
if
it's
a
third
party
that
just
downloads
the
artifact
scans
it
and
maybe
deleted,
you
wouldn't
know
that
it
was
scanned.
You
just
would
know
that
it
was
deleted.
For
example,.
C
About
the
tagging,
I
understand
the
requests
we
again
like
I
said
we
have
properties,
it's
just.
The
customers
will
push
like
tons
of
properties
on
an
artifact.
C
I
mean
retention
is
not
a
hardware
specific
retention,
And
archiving
is
I,
mean
I,
don't
know
about
retention,
but
archiving
for
sure.
It's
a
generic
event.
Question
is
if
it's
interesting.
C
D
There
there
are
two
two
main
goals
or
use
cases
that
we
consider.
One
is
more
in
interoperability
between
tools,
so
certain
tool
to
sending
an
event
and
another
tool
reacting
to
it
and
taking
actions
as
a
consequence
of
that,
for
instance,
with
registry.
There
is
a
use
case
from
detox
tools,
they're
interested
in
being
notified
about
the
new
tag
available
for
an
artifact,
because
then
they
can
react
by
sending
a
pull
request
to
get
updating
the
definition
of
the
deployment
and
preparing
a
deployment
as
a
consequence.
C
So,
okay,
so
if
you're
talking
in
audit
Trail
so
I
take
it
back,
archiving
seems
to
be
important
for
you,
because
I
was
I'm
more
focused
on
the
sdlc
and,
as
you'll
see
once
the
once,
there
was
a
deployment
and
what
I
carried
next
is
not
archiving
of
the
artifact
but
the
world
back
if
or
the
next
release.
E
C
C
E
D
D
D
I
mean
in
terms
of
implementation
of
these
events.
D
Okay,
so
we
start
creating
the
issues
and
just
trying
to
figure
out
what
the
next
step
or,
in
practice,
how
we
we
can.
We
can
work
on
this.
Is
that
something
that
you're
interested
in
then
bringing
in
or
implementing
or
building
a
POC
for
artifactory
in
the
form
of
a
Plugin
or
something
or
what
is
the
the
plan
and
trying
to
figure
out
how
we
can
best
collaborate
on
this
work?.
C
C
I
need
to
check
if
this
is
something
that's
that
I
can
get
time
for
or
that
somebody
could
get
assigned
to
doing
this.
A
Maybe
we
could
start
by
preparing
a
documents
for
events
related
to
to
Registries,
or
something
like
that
that
we
could
include,
of
course,
hardware
and
not
Factory
there,
and
maybe
others
as
well,
and
then
collaborate
on
that
document
stating
what
kind
of
events
we
should
have
and
what
they
should
contain
and
how
they
should
be
maybe
connected
to
other
events.
We
already
have
or
something
like
that
before
we
go
on
and
create
pull
requests
for
you
actually
adding
these
events
to
the
protocols.
A
D
That
said,
if
I
think
there
is
interest,
we
could
start
with
the
events
that
we
already
have
I
mean.
Today
we
have
artifact
gold
event
and
I
was
implementing
I've,
been
implementing
a
POC
for
for
Harbor
to
support
that
and
I
think.
If
he
has
some
use
cases
we
can.
We
want
to
showcase
that's
a
very
powerful
if
we
can
integrate
one
or
more
tools
for
these
events
and
Implement.
Some
yeah
demonstrate
some
workflow
or
use
case
I.
Think
it's.
C
Have
I
don't
have
approval
for
commitment
for
our
for
any
developer
or
me
to
to
do
this,
but
I
think
it.
A
Obviously,
yeah,
of
course,
to
propose
a
lightweight
process
around
this
I
guess
we
can
just
create
an
account
just
like
this
one
and
start
collaborating
there
and
maybe
also
create
a
stack
Channel
with
the
relevant
people
in
invited
to
it.
So
we
can
discuss
there
and
then
maybe
also
help
out
in
implementing
or
documenting
on
iqmd.
For
now,
foreign.
D
All
right
yeah,
we
we
have
yes,
only
eight
minutes
left.
D
So
maybe
just
wanted
to
go
quickly
through
the
last
few
things
on
the
on
the
agenda
for
today
and
then,
if
anyone
has
any
other
comments
or
questions,
they
would
like
you
to
bring
up.
D
D
In
terms
of
collaboration,
I
wanted
to
to
mention
that
we
had
the
initial
meeting
with
Steve
from
the
vsmi
today,
so
we
decided
on
a
new
monthly
Cadence
for
this
meeting.
So
we
every
month
we
will
meet
and
discuss
on
the
progress
of
CD
events
and
bsmi
collaboration.
D
So
I
put
a
link
to
the
meeting
notes
for
today,
Steve
already
presented
their
progress
on
the
vsmi,
topology
and
ontology,
which
I
thought
I
found.
I
was
rather
interesting,
so
they
have
a
kind
of
architecture
in
mind
about
different
type
of
events
or
more
like
real-time
events
and
more
like
data
stored
type
of
events,
and
they
have
seed
events
presented
as
part
of
the
picture
they
presented
their
ontology
as
well
and
I'll
ask
Steve
actually
if
he
can
share
the
slides.
D
So
we
can
put
a
link
in
here
but
I
think
a
lot
of
the
or
at
least
some
of
the
ideas
that
they
are
discussing.
They
match
a
similar
discussion
that
we're
arriving
on
City,
Event
side,
so
I'm
quite
positive
on
the
future
of
this
collaboration.
A
D
D
It
went
well
and
they,
one
of
the
items
we
discussed
was
the
possibility
of
taking
one
of
the
software
artifacts
they
produce,
which
is
the
this
bought
Potato
Head
application,
which
is
a
kind
of
demo
application
that
they
use
to
demonstrate
different
app
delivery
strategies
and
so
to
the
idea
was
to
to
build
a
version
of
this
bot
data
hack
based
on
CD
events,
to
demonstrate
how
CD
events
can
be
used
to
and
produce
softer
in
this
event
driven
approach.
D
So
we
are
looking
for
for
computers,
candidates
that
would
like
to
to
work
on
this
to
drive
this
work
or
to
contribute
to
it.
So
if
you
are
interested
or
know
someone
who
might
be
interested,
please
let
us
know
so
that
we
may
have
some
progress
on
this
in
in
the
meanwhile,
there's
cncf
app
delivery
tag.
D
They
learned
about
City
events
and
they
I
think
they
were
quite
enthusiastic
about
the
idea
and
they
will
continue
to
promote
the
the
project
and
promote
it
across
the
different
group
in
the
cncf.
So
that's
the
last
update
I
got
from
there.
So.
F
I
wanted
to
add
two
points
there,
like
like.
We
demoed
last
in
one
of
the
sea.
Givens
meets
the
two
types
of
visualizations
right
like
one
we
use
with
the
specific
CD
events
tool
and
other
with
generic
CD
events
tool
like
kind
of
promote
news
and
grafana.
F
So
we
wanted
to
like
just
ask
a
follow-up
discussion
on
this
topic,
mainly
to
decide
like
which
type
of
visualization
that
we
wanted
to
use
for
this
CD
events,
visualization
and-
and
we
can
propose
some
reference
architecture
and
then
we
can
work
on
the
pop
kind
of
thing
on
on
the
decided
one
we
can.
We
can
I
wouldn't
follow
up
discussion
from
the
previous
demonstration.
D
Yeah
and
thanks
again
for
the
demo
last
time,
my
understanding
is
that
that
there
is
a
kind
of
there
is
a
strong
dependency
between
this
and
the
the
connecting
events
topic.
But
I
guess
the
the
two
discussions
probably
can
progress
in
parallel.
D
I,
wonder
if
that's
something,
maybe
we
need
like
a
dedicated
working
group
to
discuss.
I
know.
Evans
was
interested
in
joining
this
discussion
as
well
or
we
should
we
just
try
to
to
use
the
space,
maybe
next
next
week
to
dedicate
some
time
to
the
visualization
topic.
G
Yeah
David
here
Andrea
will
keep
jalandra
and
ourselves
will
keep
an
eye
on
the
connected
events
discussion.
We
might
try
and
even
decouple
the
visualization
from
that,
so
that
you
could
could
pass
whatever
way
the
connected
events
happens
and
visualize
anyway.
So
that's
what
we
were
thinking
of
doing
so
we.
F
G
F
E
D
D
All
right
almost
time,
any
last
comment.
D
All
right,
and
thanks
for
joining
everyone
and
good
nice
to
meet
you,
carmet
and
yeah,
see
you
next
time.