►
From YouTube: CDF - TOC Meeting 2021-01-19
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
A
A
C
D
E
D
Okay,
we
have
up
to
12
people,
so
we
can
probably
get
started.
Please
sign
in
here
in
the
agenda.
I
pasted
it
into
chat
I'll.
Do
it
one
more
time,
because
I
think
it
only
goes
to
people
that
are
in
chat
once
it
goes
out
all
right,
yeah,
please
sign
in
at
the
top,
and
then
we
can
jump
in
thanks
tracy
for
adding
these
agenda
items
just
to
confirm.
Tracy
reagan
said
that
we'd
be
doing
the
events
sig
chartered
today.
I
hadn't
seen
it
before
this,
so
is.
G
D
A
Yeah
now
super
happy
to
just
do
a
follow-up
update
from
last
time.
So
if
you
go
ahead
and
click
on
that,
so
we
have
an
end
user
council
and
they're
pretty
actively
kind
of
driving
what
they
want
from
the
cdf.
A
So
we've
put
together
this
plan.
So
if
you
want
to
scroll
through
it
and
I'll,
please
feel
free
to
read
in
detail,
but
I'll
give
you
kind
of
the
overview.
A
So
at
the
top
level,
the
goals
for
this
group
are
to
help
drive
adoption
at
their
own
organizations
as
well
as
they
want
to
kind
of
use
cdf
as
a
place.
They
can
come
together
and
you
know,
advance
the
state
of
art
for
continuous
delivery
in
the
industry
or
just
push
for
for
greater
adoption,
so
done
if
you
scroll
down
to
the
goals.
A
A
How
can
we
kind
of
work
out
if,
if
you're
on
the
right
track
and
one
of
the
ways
is
sort
of
saying
okay,
they
can
speak
to
their
continuous
improvement
journey
and
also
they
can
create
assets
or
collateral
that
other
teams
or
the
greater
industry
references
so
yep,
pretty
ambitious,
but
yeah
we're
seeing
if
we
can
kind
of
bring
people
together
in
a
focused
way,
so
they
have
set
out
an
editorial
calendar
which
consists
of
four
topics
so
the
first
one
for
this
quarter
is
all
around
measuring
devops
success.
A
A
So
if
you
say
okay,
what
does
it
mean?
Those
are
pretty
huge
topics:
we've
kind
of
set
out
a
structured
workflow
of
how
we'll
tackle
them.
So
first
of
all,
the
group
gets
together
and
we
have
a
kind
of
brainstorming
session
where
we
sort
of
say:
okay,
what
are
all
the
different
components
of
this
topic
and
then
typically,
each
topic
is
pretty
huge.
So
then
we
agree
on
okay,
which
subset
can
we
focus
on
that
will
kind
of
give
us
the
biggest
bang
for
the
buck.
A
Then
we
are
hoping
to
kind
of
get
encourage
those
teams
to
share
what
they're
actually
doing
and
perhaps
run
some
surveys
with
our
communities
to
kind
of
get
a
a
current
state
of
what
you
know,
whether
it's
measuring
devops
or
developer
experience
how
how
that
topic
is
perceived
then
once
we've
well.
Actually,
these
steps
are
not
necessarily
linear,
but
we
also
want
to
kind
of
go
out
to
sorry
stick
with
those
steps
we
want
to
go
out
to
the
community-
and
I
know
some
folks
have
already
reached
out
so
we'll
be
asking.
A
Then
people
who
are
doing
cutting-edge
work
to
talk
about
that,
put
those
ideas
all
together
and
then
the
expectation
is
that
each
quarter,
we
finish
off,
writing
a
white
paper
or
whatever
assets
or
collateral.
It
might
be
an
api
or
something
we
work
with
interoperability
group.
I'm
trying
not
to
prescribe
it
too
much.
A
Okay.
So
if
you
go
to
the
next
bit
so
roughly
when
we're
working
on
sharing
a
calendar
of
all
the
different
events,
so
we'll
have
a
content
plan.
Where
we'll
have
these
meetings
we'll
have
the
round
tables
for
the
wider
cdf
community?
A
We
want
to
have
webcasts
on
the
topic
and
we
want
to
host
a
podcast,
and
then
we
also
expect
to
kind
of
have
an
analyst
briefing
and
ideally
finish
with
a
discussion
forum
where
we
sort
of
share
everything.
That's
been
learned
with
the
wider
community,
okay
and
then
the
last
bit
is
just
a
few
details
of
the
end
user
console.
A
A
Sorry,
it's
escaping
me,
okay,
so
the
first.
The
first
thing
we
are
mapping
out
is
measuring
devops
success
and
it
looks
like
the
focus
area,
for
this
will
be
kind
of
the
the
dora
metrics
and
the
four
keys
pro
so
the
four
keys
and
working
out
you
know
how
are
people
measuring
this?
How
are
they
measuring
it?
What
are
good
practices?
What
what
are
different
aspects
of
that?
A
A
So
on
the
first
one
like
the
literature
survey,
that's
where
we're
collecting
all
the
links
we
might
have
to
folks
who
have
written
about
measuring
devops
success.
So
we
referenced
that
you
know
accelerate,
has
a
very
good
chapter
on
that.
But
then
there
might
be
other
elements,
different
articles
that
that
great
talk
from
cdcon,
for
instance,
we'll
put
in
there
and
not
maybe
not
just
dorametrics
but
other
ways
of
evaluating
whether
your
teams
are
happy.
A
Yes
to
the
in
practice,
so
this
is
the
show-and-tell
bit
so,
in
addition
to
the
conversations
we'll
be
having
with
the
end
users
we're
trying
to
open
it
up,
so
anybody
who
also
wants
to
improve
their
team
can
start
by
just
taking
a
snapshot
of
where
they
are
so
just
sharing.
What
is
the
reality?
What
are
you
doing
in
practice?
Do
you
know
kind
of
what
your
four
key
metrics
look
like
for
your
team?
A
Do
you
have
additional
context?
Is
your
team
aligned
on
them?
You
know
anything
on
this
topic.
That
is,
you
know,
not
theoretical,
but
it
is
practical
reality
for
a
specific
for
anybody
who
wants
to
kind
of
critically
examine
it
and
improve
it.
A
Okay,
so
actions,
I
will
encourage
you
to
jump
in
on
those
threads.
They
will
probably
be
other
ones
started
by
end
user
folks
and
then
the
other
action
is,
if
you
have
an
event
that
should
feature
as
part
of
our
calendar
or
if
you
want
to
be
involved
in
the
roundtable.
I
know
some
of
you
have
already
reached
out
and
I'll
be
following
up,
but
we're
prepping
the
calendar
of
events,
so
we're
going
to
say
when
each
of
the
the
things
in
the
content
plan
will
happen
this
quarter
and
yeah.
A
Just
please
please,
please.
Let
me
know
we're
really
trying
to
bring
everyone
together
on
this
topic
and
try
to
see
it
from
multiple
different
perspectives
and
and
see
what
we
can
learn
by
all
working
together
and
I'd
like
to
yeah,
maybe
just
open
it
up
for
a
little
bit
off
q,
a
and
also
some
other
thoughts.
So,
first
of
all
any
questions
or
comments.
D
I'll
just
start,
I
love
the
content
train,
I
love
building.
I
think
the
quarterly
cadence
is
going
to
be
great,
especially
with
the
podcast
and
analyst
conversations
and
everything.
A
A
So
one
of
the
things
oh
go
ahead:
steve.
H
Yeah,
this
is
very
similar
to
a
a
trade
show
you
used
to
go
to,
which
is
called
all
things
delivered
where
they
would
have
it's
mainly
end-user-focused.
So
what
you're
putting
together
is
very,
very
similar,
and
I
know
that
was
very
successful,
so
I
think
this
is
well
worth
it.
H
No
problem,
the
one
thing
I
was
wondering
I
don't
know
where
this
would
fit
would
be,
and
I
hate
to
call
it
a
maturity
make
matrix,
but
maybe
a
success
matrix
if
that
would
fit
into
this
as
well.
So
people
can.
B
A
Yeah
absolutely-
and
I
think
it's
that's
a
thought
that
keeps
coming
up.
I
think
the
preferred
language
folks
uses
is
the
capability
matrix
just
to
get
away
from
the
baggage,
with
maturity
models
exactly
yeah.
A
I
think
that
is
I'm
going
to
make
a
note,
because
I
think,
for
each
topic,
giving
folks
a
way
to
self-assess
in
in
a
in
a
practical
way
that
leads
to
improvement
would
would
be
really
nice
because
yeah,
I
think,
at
the
end
of
the
day,
we're
just
trying
to
help
you
get
better
know
put
yourself
in
context
of
of
the
industry.
Perhaps
so
you
know
if,
where
you
stand,
I
like
that.
A
A
I'd
almost
love
to
see
if
we
could
get
each
open
source
project
to
speak
to
its
role
it
plays
in
in
let's
say
dorametric
so
like
checked
tacton,
you
know,
could
link
to
to
that
project
by
dina
portman
and
say:
hey
here's
how
you
could
instantly
automate
all
these
metrics,
but
you
know,
is
there
that
option
for
spinnaker
or
jenkins,
or
you
know
what?
If
people
were
using
those
tools?
How
should
they
be
thinking
about
doing
measuring
devops
with
them?
A
So
I
don't
know
if
that's
too
much
of
a
stretch
reasonable
or
what
that
looks
like
so
you're
open
to
to
any
thoughts.
A
Maybe
just
then
I'll
put
you
in
the
spot
any
like.
If
I
had
to
say
hey
you
know,
could
screw
drivers
speak
to
how
you
might
use
it
with
to
measure
dora
metrics
any
thoughts
on
that.
C
Not
quite
I
think,
we'll
have
to
think
through
how
we
can
convert
this
into
some
sort
of
a
specific
metric,
because
we
look
at
devops.
There
are
different
ways
in
which
a
tool
is
used
for
various
different
use.
Cases
used
for
deployments
for
building
ci,
don't
know
if
we
can
convert
this
to
a
common
metric.
Where
we
can
say,
maybe
do
some
surveys
to
see
how
you
how
the
tool
is
working
out.
D
I
think
some
of
the
metrics
would
be
pretty
easy
for
most
of
the
projects
like
the
deployment,
frequency
and
maybe
even
lead
time
for
changes,
but
the
other
ones
start
to
get
a
little
trickier
like
I'm
just
looking
at
them.
Now
like
the
time
to
recover
and
change
failure
rate,
I'm
not
sure
we
have
too
many
tools
to
kind
of
cross
into
the
operations
and
alerting
space
to
really
have
all
that
information.
H
Yeah
and
even
going
back
the
other
direction
to
you
know
when
something
is
is
added
to
a
sprint.
You
know
and
requirements
are
gathered.
H
You
know
that
comes
into
this
whole
metrics
as
well,
when
you
know
when,
when,
if
something
is
added
as
a
new
request
for
a
new
feature,
how
long
does
it
take
for
that
feature
to
get
to
production
that
going
to
that
those
requirements?
Gathering
tools
is
kind
of
out
of
the
cdf
scope,
but
there
still
is
a
a
tie
that
needs
to
be
made
there
and,
like
you
said
dan
on
to
the
other
side
onto
the
operation
side.
You
know
the
tools
exist,
but
not
in
our
and
not
in
the
cdf
world.
E
I
mean
it
was
used
in
the
original
talk,
so
I
guess
it
is
possible
to
conduct
metrics.
Of
course,
tecton
is
by
itself
very
non-opinionated,
so
you
can
do
a
lot
of
different
things
with
tecton,
but
I
guess
one
of
the
things
that
we
started
considering
this
maybe
to
have
some
stories
and
how
you
could
use
tekton
for
doing
specific
things
and
yeah.
I
guess
this
could
fit
in
that
that
area
so
I'll
definitely
bring
it
up
with
the
with
the
rest
of
the
team.
B
And
I
think
jenkins
x
is
probably
a
bit
more
end
to
end
than
some
of
the
the
other
projects,
so
it
may
be.
This
is
a
better
fit
for
for
us
to
look
at
some
of
that
and
see
how
we
can
help
support
them.
B
H
I
would
say
that
the
the
projects
would
look
at
the
low-hanging
fruit
like
dan
said
around.
You
know
frequency
those,
those
ones
that
we
know
that
are
there
and
then
work
our
way
outwards.
D
Yeah,
it
seems
like
it
could
be
pretty
at
least
with
technon.
It
seems
it
could
be
pretty
simple
to
set
up
like
a
deployment
frequency
metric
over
time
and
then
see
if
you're
getting
better
or
worse
it's
in
the
absence
of
knowing
what
your
rate
frequency
should
be.
At
least
you
know,
if
you're
going
up
or
down,
I
could
see
imagine
setting
that
up
pretty
quickly.
A
A
Okay,
yeah!
No
thanks
for
those
thoughts
and
yeah,
definitely
chewing
on
this
all
quarter,
so
we'll
try
to
think
maybe
either
how
to
set
up
the
right
discussions
to
bring
folks
together
to
to
push
it
forward
or
just
yeah
just
capturing
what
people
are
doing
and
spreading
the
word
about
what
what
is
possible
and
and
dress
driving
again
that
industry,
clarity,
great
yeah,
feel
free
to.
Let
me
know
if
any
thoughts
after
after
the
meeting
or
whenever
on
this.
D
Awesome
all
right
time
for
the
events
charter.
Do
you
want
to
take
over
presenting
and
sharing
email.
F
Yeah,
I
can
do
that,
no
problem,
I
hope.
Actually.
Last
time
I
tried
to
share
my
screen
through
soon
I
failed.
B
F
F
Perfect
so
yeah,
I'm
here
representing
the
the
work
stream
that
is
called
currently
events
in
ci
cd,
which
is
work
stream
within
the
interoperability
sig,
and
we
we
were
asked
here
to
to
let
us
come
here
to
present
our
our
work
and
our
charger
and
with
the
intent
to
propose
this
work
stream
to
become
a
proper
sig
of
its
own
and
of
course,
why?
Why
would
we
like
to
be
a
sig?
F
I
guess
there
are
multiple
reasons
for
that,
but
one
is
the
scale
of
it
when
we
were
forming
our
work
stream,
we
were,
I
think,
representing
four
different
organizations
or
tools
in
the
city
landscape,
but
since
then
it
has
grown
quite
a
lot,
so
we
are
now
at
least
double
that
figure.
I
believe
we
are
attracting
quite
quite
a
lot
of
people
and
we
we
want
to
to
be
able
to
do
some
more
some
more
hands-on
work,
which
you
think
will
be
enabled
if
we.
F
Lifted
to
become
a
proper
sig
of
its
own
with
with
working
groups
underneath
so
so
what
you
see
now
is
the
the
charter
that
we've
been
working
on.
It's
currently
work
in
progress,
I'm
about
to
create
a
pull
request,
to
add
this
to
our
github
repository,
but
this
is
the
the
working
document
that
we
have
so
for
introduction
there
to
begin
with.
F
We
are,
if
you
scroll
up
to
the
top
again
yeah
yeah,
you
see.
We.
We
think
that
the
studio
city
systems
of
today
they
don't
talk
to
each
other
in
a
very
but
a
good
standardized
way.
There
are
point-to-point
communications
going
on
between
all
tools,
but
we
foresee
that
there
is
a
need
for
having
a
stylized
way
of
communicating
between
these
systems.
F
And
that's,
of
course,
the
topic
in
the
interoperability
area.
That's
why
we
are
have
emerged
from
the
interoperability
sig.
I
believe,
and
now
this
group
is
looking
into
how
events
can
help
to
create
csud
systems
with
decoupled
architecture
which
is
easy
to
scale
and
which
makes
it
resilient
to
failures.
F
F
F
So
it's
a
data
record
as
it
says
here
representing
or
expressing
an
occurrence
and
the
content
of
that
occurrence.
So
that's
what
we
mean
with
an
event.
It's
it's!
In
line
with
what
cloud
events
says
about
events,
the
cncf
product
cloud,
events
yeah:
we
can
go
back
again
to
the
charter.
F
We
have
outlined
some
bullets
on
what
we
intend
to
to
discuss
in
this
in
this
group.
What
to
currently
discuss
and
what
we
aim
to
continue
discussing
when
to
use
events
and
how
to
use
them
best
practices
and
how
to
orchestrate
workflows
using
events
and
a
lot
of
other
things
for
tracing
auditing,
graphing,
visualizing
and
metrics.
And
things.
F
D
Awesome
building
off
of
tracy's
last
discussion
point
I
can
imagine
using
these
standardized
events
to
come
up
with
standardized
ways
to
calculate
things
like
the
dorametrics.
If
there's
a
standard
way
to
represent
a
deployment
or
a
rollback
or
a
change
or
anything,
make
it
much
easier
for
people
to
track
those
across
all
the
different
tools.
F
I
Yep
guys
this
is
tracy
and
steve,
we're
dialing
in
the
old
school
way,
because
our
internet
crashed
again
we're
having
a
big
storm
in
new
mexico.
So
that
may
be
the.
E
F
D
Question
it
looks
like
you've
done
most
of
the
work
here
on
a
proposal.
I
think
the
next
step
according
to
charter
and
everything
is
to
submit
that
as
a
pull
request
to
the
talk
repo.
There
might
be
some
minor
changes
as
you
converted
it
into
markdown,
but
I
can
find
the
link
and
send
you
the
template
for
how
these
get
proposed.
I
And
then
dan
does
the
talk
vote
on
it.
D
Yes,
yeah,
we
would
review
the
pull
request.
Sorry
go
ahead.
A
G
I
I
can't
tell
who's
on
right.
A
D
No,
we
are
missing
a
few
people
today,
so
don't
let
that
get
in
the
way.
I
guess
I'm
sure.
J
A
A
I
think
that's
great
and
we
can
get
the
ball
rolling.
I
would
say
on
the
kind
of
announcement
side,
if
we
want
to
just
use
that
as
a
way
to
push
for
visibility
and
reignite
the
interest
in
and
get
people
in
the
wider
community
to
come
to
come,
attend
the
meetings
so.
I
Who
was
the
the
sponsor
for
the
interoperability.
I
A
Yeah,
who
are
in
the
proposal
have
we
identified,
who
the
chairs
or
co-chairs
are
for
the
group.
F
No,
we
haven't
discussed
that
yet
so
that
remains
to
be
discussed
within
our
group.
I
guess
to
propose
something
in
the
request.
A
Yeah,
no,
I
think
that
would
be
great
just
they.
We
tend
to
give
the
the
co-chairs
a
bit
of
greater
access
in
terms
of
the
the
github
repos.
The
calendar
invites
so
just
a
yeah,
a
small
thing
to
have
those
folks
identified,
so
they
can
play
a
a
greater
role
in
structuring
and
managing
the
calendar,
etc.
I
We
need
to
identify
a
code,
a
co-chair
and
we
need
to
find
a
talk
liaison.
D
Yeah
there
might
be,
I
mean
you've,
done
the
hard
work
of
explaining
what
this
thing
is
going
to
do
and
all
that
stuff,
the
pull
request
might
just
have
a
couple
of
their
little
eyes
to
dot
and
everything,
as
you
start
filling
up
the
template.
But
that
should
be
the
easy
part.
I
D
D
K
D
J
Jacqueline
was
going
to
and
she
did
sweet
so
we've
got
so.
I
guess
I
signed
up
for
this
again.
We
were
trying
to
pull
together
something
for
g
sock
for
the
last
newsletter
and
one
of
the
things
we
discovered
is.
We
didn't
have
enough
organization
around
closing
artifacts
recordings
presentations
and
it
turns
out,
I
need
to
circle
back
around
with
some
of
the
project
owners,
but
we
had
projects
that
were
marked
as
complete
but
didn't
actually
get
merged.
J
So
so
there's
some
logistical
things
in
there
that
that
we'll
need
to
learn
from
for
2021
but
yeah
stuff
kicking
off.
I'm
hoping
that
we'll
get
good
representation
from
all
of
the
projects
for
this
go
around.
H
Yeah,
so
just
to
let
you
know,
ortulius
put
a
pull
request
into
the
sock,
repo
and
also
there's
the
jenkins
update
is
out
there.
So
there's
two
pr's
out
there
to
update
around
the
project
ideas
that
okay.
H
They're,
both
pretty
simple
just
you
know,
read
me
updates.
So
it's
not
like
there's
a
lot
of
files
they're,
both
in
both
both
pr's
against
the
readme.
D
So
we
have
to
finalize
this:
we
have
about
a
month,
I
guess
exactly
a
month.
Is
that
correct?
Something
like
that
february
19th
here.
A
And
tara,
just
let
you
know,
I
don't
think
cara
de
la
marc
is
on
the
call,
but
she
confirmed
she'll,
be
the
admin
for
jenkins,
as
well
as
her,
along
with
the
james's
struck
and
enrolling,
will
be
contact
points
for
jacking
insects
and
yeah,
and
she
she
can
also
says
she's
happy
to
help
on
as
the
gsoc
admin.
If
you
want
to
work.
J
Would
be
lovely
yeah
that
would
be
great
and
I'm
assuming
oleg
is
going
to
be
running
the
actual
project
oversight
again
or.
A
A
J
Yeah
and
I'll
follow
up
with
rosalind
and
isaac
for
armory.
Let's
see
dan,
do
you
know
what
christie
and
company
are
planning
if
anything.
D
I
don't
know
okay,
I
will
give
her.
H
H
We
did
have
one
question
from
a
person
that
wants
to
participate
from
the
student
side.
They
just
graduated
graduate
school
just
recently
and
they're
wondering
if
they
could
participate
or
since
they're
no
longer
in
university
that
they're
they
don't
qualify.
J
That's
a
good
question.
I.
J
J
Okay,
well,
what
well
I'll
I'll
see
if
I
can
get
clarification
on
that
it
may
be
that
it's
a
matter
of,
even
if,
if
it's
okay,
it
may
be
a
matter
of
stack,
ranking
your
potential
contributors,
because
we're
only
going
to
get
so
many
slots
that
will
have
to
divvy
up.
So
that's
another
thing
to
keep
in
mind.
So
cdf
in
its
entirety
got
three
slots
last
time,
for
example,
we're
combining
with
jenkins
this
year
and
we've
already
reached
out
to
confirm
that
they
recognize
jenkins.
J
You
know,
hopefully
we'll
get
some
some
grandfathering
in
as
far
as
participation,
but
at
the
end
of
the
day,
we'll
we'll
get
as
many
slots
as
we
get.
C
D
Yeah,
maybe
so
I
know
part
of
the
you
mentioned
tact
on.
You
know
part
of
the
reason
technology
involved
last
summer
was
they
took
on
a
whole
bunch
of
other
interns,
so
not
through,
like
the
g
sock
program,
right.
B
D
You
know
red
hat
hosted,
I
think,
like
a
dozen
or
something
in
terms
of
techton
and
google
had
a
couple
as
well.
Maybe
you
know
when
we
do
the
wrap
up
post
next
year
or
something
it'd
be
good
to
just
kind
of
point
out
all
the
different
student
programs
that
cdf
projects
are
involved
in
and
not
just
focus
on
gsoc
to
kind
of
get
a
more
holistic
view.
D
D
Awesome
yeah
I'll,
follow
up
with
them
too,
to
see
exactly
what
they're
planning
for
this
summer.
D
All
right
end
user
console
update.
We
oh
wait.
Sorry,
I
scrolled
too
far
we're
switching
tabs
newsletter
updates.
Yes,
so
we
skipped
the
last
one
for
projects
because
did
a
good
job
taking
a
holiday
break
this
time,
not
too
many
releases
or
updates
happened
over
december,
but
this
is
just
a
kind
of
reminder
to
get
your
project
updates
into
that
dock
for
the
next
one.
So
we
can
get
that
going
again.
It
was
pretty
popular
in
the
newsletter
to
see
all
the
different
kind
of
high-level
things
from
each
project.
A
Just
to
build
on
that
one,
I
know
jackie
mentioned,
she
got
kicked
off
the
call
thanks
to
to
the
storm
but
she's,
pulling
together
the
annual
report,
so
we're
hoping
to
share
that
either
end
of
this
week
or
early
next
week.
So
thanks
everybody
for
all
your
input.
A
I
had
a
a
a
brief
preview
of
it
and
it's
looking
really
good
and
then
yeah
on
the
newsletter
we
decided
with
to
skip
the
the
january
one
as
folks
are
getting
back
into
things.
But
if
you
share
your
project
updates,
we'll
have
those
in
the
one
going
out
early
february.
D
Awesome,
it's
great
to
see
all
the
different
updates
and
stuff
going
out
each
month.
A
Oh,
oh,
the
last
thing
I
will
say
is
actually
cdcon
call
for
papers
is
open.
We
already
have
about
15
talks
in
progress
and
we
know
500
folks
have
registered
for
the
event
already.
So
please
submit
your
talks
on
all
the
exciting
work,
you're
doing
and
yeah
looking
forward
to
a
really
good
event.
Later
this
year
in
june,
virtual.