►
From YouTube: CDF SIG Best Practices - Nov 16, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
We're
always
glad
to
have
you
and
when
you
can
make
it.
B
Yeah
well,
I
I've
been
doing
a
lot
of
sort
of
crossover
work
really
connecting
with
the
other
sigs
and
some
of
the
project
teams
and
just
trying
to
make
sure
that
you
know
the
overarching
work.
That's
going
on
is
staying
somewhat
aligned
to
the
best
practices,
getting
people
to
use
the
common
vocabulary
and
notation,
and
you
know
generally
try
and
sync
things
up.
B
B
C
B
Event
stuff,
for
example,
I,
will
link
that
in
once,
we've
we've
got
that
website
up
scratch
and
that'll
connect
us
across
into
that
piece
of
work.
Hi
Tara,
good.
D
C
B
I
should
have
tipped
you
off
the
the
bosses
here
today,
so
we're
gonna
have
to
behave
ourselves.
C
B
Feel
free
to
I've
I've
I've
set
the
template
up,
but
okay
you're
welcome
to.
D
The
vaccine
gave
her
tachycardia.
It
was
really
scary,
so
I'm
trying
to
be
careful,
I
wasn't
able
to,
because
you
know
it
was
cold
and
the
outdoor
dining
stuff
has
gone
away.
So
I've
been
sleeping
in
our
RV
for
the
past
week
to
you
know
just
get
through
quarantine,
and
let
me
tell
you
California,
Northern
California
is
having
a
cold
snap.
E
B
So
key
update
from
me
yesterday,
I
I
joined
in
with
the
the
supply
chain
maturity
working
group.
We
have
very
interesting
discussion.
B
B
Yeah,
so
the
the
the
the
the
document
that
I
shared
with
you
yesterday
is
is
their
initial
working
document
and
it
overlaps
quite
neatly
with
the
chunk
of
what
we've
been
planning
to
do
for
a
while
now
in
terms
of
the
assessment
model.
B
B
They're,
looking
at
the
at
the
the
fine
detail
of
you
know
explicit
behaviors
in
the
engineering
delivery
sense.
B
D
Okay,
it
feels
yeah
I
started
going
through
it
last
night.
Thank
you
is
the
goal
that
this
would
eventually
be
hosted
on
the
website.
B
D
That's
good
we're
actually
working
on
this
right
now
at
the
beginnings
of
this
at
mongodp,
that's
perfect.
B
C
B
A
B
Of
self-assessment
survey
so
that
people
can
find
it
and
then
fill
it
out
and
get
get
some
information
about
there.
Their
current
maturity
in
a
space.
D
D
D
C
There
might
be
something
we
can
snag
there:
okay,
cool.
B
B
So
you
know
well
when
you're
looking
at
that
first
level
of
maturity,
really
what
you're
seeing
is,
what
are
the
key
things
that
you
absolutely
must
have
in
order
to
survive
for
any
period
of
time,
trying
to
do
continuous
delivery
and
then
at
the
next
level.
What
are
the
next
things
that
you
should
add
that
that
will
increase
your
odds
of
survivability
and
then,
as
you,
reach
the
higher
maturity
levels?
B
What
you're
talking
about
is
more
of
the
convenience
pieces
that
reduce
your
cognitive
load
and
improve
your
ability
to
be
efficient
and
effective,
and
hopefully
that
makes
it
easier
to
think
about.
C
D
D
Amazing,
so
does
it
was
there
discussion
about
how
to
measure
this
stuff?
So
one
of
the
things
we've
been
talking
about,
for
example,
isn't
it
with
with
my
team
is:
is
telemetry
and
instrumentation
like
all
right?
D
Well,
we
know,
you
know,
we
know
what
we
don't
know:
okay,
well,
let's
start
figuring
out
how
to
measure
that
and-
and
hopefully
out
of
that,
we'll
start
learning
other
things
that
we
don't
even
know
that
we
don't
know
to
measure
that
some
of
these
I
are
encapsulated
in
this,
but
a
lot
of
them
aren't
so
that
this
is
a
good
checklist
to
review
and
that
led
us
to
start
thinking
about
the
mechanics
of
instrumentation.
D
And
I
think
we
talked
about
this
before,
which
is
like
Cloud
events,
trace-based.
D
B
E
F
See
you
hi
I'm
here
Emily,
oh
yeah,
so
what
was
there
a
question
or
or
more
about
a
statement
that,
of
course,
yeah
events
could
be,
could
be
used
there
for
the
supply
chain
as
well
to
propagate
such
information?
Sure.
C
B
F
Okay,
go
ahead,
no
yeah,
sorry,
so
the
city
items
today,
it's
a
very
early
basis.
They
learn
better
the
stages
on
the
City
events
deck,
but
we
are
defining
a
number
of
well-defined
events
for
certain
occurrences
in
the
CIA
City
system
and
the
intended
start
of
such
well
chain
of
events
would
be
your
store,
change,
being
committed
or
or
merged
in
some
sort
of
called
repository
manager,
which
is
also
often
the
start
of
a
dual
Matrix
where
something
is
merged.
F
And
then
we
have
events
saying
that
the
north
track
is
built
rather
than
saying
that
the
test
is
performed
and
we
have
also
events
for
deployment.
So
when,
when
we
can,
when
a
system
would
emit
such
events
and
then
those
events
would
then
be
related
to
to
the
storage
unit,
that
was
actually
the
source
of
that
binary,
which
was
eventually
been
deployed.
We
could
then
calculate
the
lead
time
for
from
Storage
into
deployment,
and
we
have
events
coming
in
about
incidents
or
issues
whatever
we
want
to
call
them
now.
D
And
see
the
events
are
going
to
be
part
of
the
larger
Cloud
events
model
right,
I.
Think
that's
what
I
recall.
What
is.
F
C
F
Very
generic,
it's
more
or
less
just
defines
the
context,
the
the
frame
or
the
headers
so
say
all
the
the
event
itself.
But
then
the
payload
is
very
free.
It's
totally
free
and
you
can
see
in
Cloud
event,
sorry
and
then
what
we
do
in
CD
events
is
that
we,
we
Define
certain
specific
payload
structures
which
should
be
sent
into
inform
on
certain
occasions
from
the
cicd
pipeline,
and
currently
we
have
Cloud
events
as
the
binder
there.
F
B
I
think
this
isn't
one
of
those
areas
where
we
can
potentially
avoid
a
lot
of
duplicated
effort,
because
what
we're
going
to
be
doing
here
within
best
practices
and
in
the
supply
chain
maturity
model
is
drilling
into
the
requirements
for
the
things
that
we
need
to
measure
and
then,
if
we
can
feed
that
into
the
CD
events
work,
we
we
can.
You
know,
carry
a
lot
of
that
weight
and
and
help
to
provide
a
good
set
of
requirements
for
what.
E
F
The
artifacts
that
that
sort
of
notified
to
received
events
currently
this
these
events
are
very
thin,
still
very
small
in
size
and
don't
contain
much
information,
but
I
foresee
that
we
could
quite
soon
get
in
supply
chain.
Specifics
also
into
this
events,
notifying
about
an
artifact
for
example.
So
we
could,
for
example,
have
a
total
at
the
stations
there
or
signed
signatures
and
such
things
either
as
part
of
the
events
or
reference
from
the
events.
If
they
are
stored
elsewhere
and
also
s-bombs,
should
then
be
isama
reference
from
the
event.
F
D
C
F
So
so,
there's
the
website,
which
contains
the
which
actually
Terry,
is
working
on
as
well
the
refining
which
is
showing
the
documentation
for
the
current
events
that
we
have
the
specifications
but
the
proof
of
concept.
There
is
there's
one
proof
of
concept
which
was
made
over
a
year
ago,
last
summer,
more
or
less
of
a
very,
very
even
earlier,
this
stage
of
the
protocol,
which
modulus
showed
how
to
interpret
if
we
will
come
to
interoperate
as
soon
as
well
so
interoperate
between
these
different
tools
in
the
CLC,
the
domain.
F
So
given
examples
there
so
that
the
clock
deploys
some
different
tools,
techton
and
Captain
and
speed
hackers
lately
have
been
added
and
so
I
guess.
Those
were
the
first
tools
that
were
there,
and
so
those
events
just
show
how
to
trigger
actions
in
these
different
tools
without
them,
even
knowing
each
other
and
knowing
about
each
other.
F
But
then
there
is
also
there
was
I
think
the
just
before
the
summer.
It
was
a
talk
on,
or
was
it
in
Austin
right,
say,
Eric
and
Andrea
had
a
talk
on
Dora
metrics
with
City
events,
where
they
also
had
where
they
showed
a
book
for
that
part
where
they
didn't
show
all
these
four
dollar
metrics,
but
I
think
two
of
them
at
least,
were
were
shown
in
the
demo.
There.
C
D
B
And
I
I
think
that
medium
term,
this,
this
sort
of
standardized
metrics
problem,
may
actually
be
one
of
the
leading
drivers
for
CD
events
as
a
as
a
standard,
because
it
solves
a
a
problem
that
nobody
else
is
really
tackling
right
now
in
a
way
that
you'd
be
able
to
do
uniformly
across.
You
know
multiple
different
platforms,
so
I.
C
B
This
will
will
become
much
more
significant
as
we
dive
into
it
and
and
make
these
measuring
techniques
a
bit
more
visible
and
obvious.
F
D
B
D
D
F
I'm
about
to
open,
Telemetry
and
observability
I
think
we
haven't
really
come
into
any
detailed
discussions
there,
but
for
sure
I
see
that
we
also
need
to
have
some
way
to
reference
between
the
spans
or
Trace
IDs
provided
through
such
inter
such
yeah
yeah.
D
F
Foreign
working
on
on
the
spec
and
improving,
adding
some
more
event
types
being
more
well,
we
we,
we
do
add
more
than
types,
but
we
also
refactor
the
events
themselves.
Still
I
mean
we
haven't
reached
1.0
version
and
we'll
be
we're
still
evaluating.
What
is
the
best
way
to
do
this,
so
we
are
looking
into
different
specific
topics
but,
for
example,
on
how
how
to
reference
between
different
events
reference
one
event
to
another:
that's
one
topic
we
discussed
last
yesterday
last
so
it
was
actually
some
topic.
D
F
So
I
think
we
have
this
proof
of
concept
implementations
now
in
in
tecton
in
Jenkins
and
other
places
already.
But
of
course
they
are
just
proof
of
concept,
implementations
and
or
plugins,
or
what
you
should
call
them
there,
but
I
think
before
we
have
reached
the
1.0
version
of
this
spec
I.
Don't
think
that
any
of
those
tools
might
release
their
cities
and
support
officially
say
that
they
support
it.
F
That's
that's
my
guess
anyway,
but
maybe
some
Front
Runners
could
do
it
early
like
sector,
maybe,
and
maybe
some
work,
so
they
can
pave
the
way
for
others
to
come
in,
but
we
don't
know
which
of
these
tools.
That
will
be
the
first
text
on
this
one
obvious
candidate,
because
they
have
one
other
maintainers
when
they
take
the
maintainers
in
the
City
events
team
as
well,
and
he's
very
keen
on
getting
this
supported
by
take
them.
F
D
Yeah,
it's
chicken
and
egg
right.
Do
we
get
early
adoption
to
help
validate
the
1-0
release,
or
do
we
do?
We
call
it
1-0
and
then
try
to
get
adoption.
F
Yeah,
of
course
yeah,
so
so
we
can't
wait
of
course,
too
long
before
we
release
the
Wonder,
though
it
needs
to
be
at
least
within
a
year
or
something
I
mean
it
needs
to
happen
during
the
next
year,
I
think.
Otherwise
we
might
miss
the
chance.
B
But
I
think
there's
also
the
opportunity
here
for
us
to
be
driving
the
need
for
adoption
from
a
best
practices.
Standpoint.
D
F
D
At
one
of
those
companies
that
does
the
horrible
thing
where
our
fiscal
year
is
offset
by
11
months,
so
our
first
so
we're
about
to
come
to
the
end
of
fiscal
year,
2023
in
January,
and
it
just
my
brain
I,
just
I
hate
that
I
know
why
they
do
it
that
way.
But
it's
just
maddening
because
next
year
2024
wait.
What
okay
so
yeah!
That's
exactly
where
I
was
what
I
was
thinking
about
Terry,
which
is
you
know,
being
able
to
have
the
reference
implementations
available?
D
So
the
focus
should
be
then
I,
guess
your
to
your
earlier
point
to
try
to
ensure
that
the
measure,
the
metrics
measurement
and
the
spec
lines
up
as
strongly
as
as
can
be
done.
B
Yeah
and
again,
this
is
another
area
where
Jenkins
X
is
looking
to
implement,
and
this
would
tie
in
with
some
of
the
other
supply
chain
work
that
they've
been
doing.
So
you
know,
there's
plenty
of
opportunity
for
us
to
get
a
reference
implementation
out
there.
B
B
Yeah,
so
a
lot
of
this
is
is
closer
to
being
done
than
it
looks
because
you
know
the
there's
already
been
some
proof
of
concept,
work
done
with
captain
and
techton,
and
those
tools
are
available
within
Jank
his
ex.
So
it's
just
going
to
be
about
building
on.
What's
already
been
done
and
tying
it
together.
D
And
I
remember
when
the
captain
folks
reached
out
when
I
was
still
on
the
TOC,
it's
nice
to
see
them
doing
so
well,
okay,
this
is,
is
cool,
I
almost
feel
like
do
we
want
to
have
a
either
the
take
the
next
this
meeting
or
carve
out
a
separate
time
to
just
kind
of
Workshop
through
the
the
metrics
to
the
spec,
or
do
we
want
to
try
and
async
it
I
feel
like
it
might
go
faster
if
we
just
grab
some
more
time
to
just
start
chunking
through
it.
D
D
A
Yeah
the
next
topic
stuff,
so
some
of
you
might
remember,
we
started
writing
this
white
paper
very
early,
like
2012.
A
A
But
those
case
studies
may
be
more
complicated
enough
or
maybe
outdated,
or
we
need
to
go
and
ask
for
permission
from
those
people.
So
I
was
reading
the
paper
this
week,
I
removed
those
case
study
pieces
and
left
the
main
body
of
the
document
there
to
simplify
it
because
it's
been
there
for
two
years
and
we
should
really
get
this
out
of
the
door
and
those
case
the
departs
could
be
turned
into
actual
case
studies.
That
is
kind
of
the
this.
The
idea
and
this
topic
will
be
discussed
during
tomorrow's
interability
signeting.
D
That
sounds
great
I'm
thinking
about
Terry.
What
do
you
thinking
under
this
be
an
a
resource
or
because
we
probably
start
to
need
rethink
about
how
some
of
this
stuff
gets
gets?
Organized.
F
B
Under
resources,
but
it
sounds
like
this
might
be
something
that
fits
better
in
the
community
section.
B
As
a
you
know,
a
more
a
narrative
piece
of
work.
That's
you
know,
the
the
resource
stuff
tends
to
be
era,
pointers
to
other
things
that
you
might
find
useful,
whereas
the
community
section
is,
is
about
here's
stuff,
that's
actively
going
on
within
the
CDF
that
directly
impinges
on
best
practices
and
how
to
do
things
so
so
I
think
yeah
trying
to
incorporate
that
in
in
that
space
and
and
then
fill
it
out
with
some
more
white
papers
on
on
different
Niche
areas
around.
That
would
would
be
a
great
fit.
D
Okay,
I'd
be
happy
to
to
put
together
a
PR
to
and
and
Market
into
the
site.
Did
you
want
the
V1
published.
A
Because
we
want,
like
some
of
those
people
are
not
around
anymore
and
they
probably
are
not
working
for
those
companies.
So
again
this,
depending
on
what
Sig
interrupt
says
tomorrow,
the
idea
is
to
work
on
V2
and
once
we
finalize
it,
give
it
to
LF
creative
team,
put
it
on
PDF
and
then
publish
it
like
CDO
and
swipe
paper,
and
it's
probably
maybe
q1
200.3
without
vrx
nearly
done
with
this
year.
Okay,
okay,.
A
I
I
didn't
remember,
like
the
electronic
people,
contributing
this
slightly
well
really
like
it's
collaborative
effort.
We
should
have
published
it,
but
here
a
little
late
than
never.
C
A
That's
the
nearest
Parts,
a
lot
that
and
my
the
other
topic
I
include
there
if
on
this,
but
we
don't
have
any
other
questions
or
comments
about
white
people.
A
So
the
developer
proactive
this
build
test
practice
I've
been
looking
at
the
best
practice
website
and
I
I've
seen
some
items
under
content,
integration
and
continuous
testing
section
and
I
recently
read
a
short
book
like
about
100
pages,
around
developer
productivity
engine,
and
that's
reminded
me
some
of
the
work
I've
done
in
the
past
and
those
things
like
my
question
here
is
like
around
build
and
test
track,
which
is
how
detailed
can
me
be
with
those
best
practice,
for
example,
build
avoidance
type
of
stuff
I,
don't
remember,
seeing
it
on
best
practice
website.
A
Does
this
type
of
stuff
fit
into
best
practices
like
using
cash
or
spilling
up
to
builds
using
test
avoidance
or
skipping
tests,
for
example,
or
having
some
clear
analysis
to
see
what
parts
of
the
cloud
base
change?
So
you
can
skip
certain
test
cases
or
even
like
migrating
from
a
set
of
tools,
different
set
of
tools
to
improve
build
test
times
or
even
changing
the
hardware
infrastructure?
B
So
there's
there's
a
sort
of
threshold
here
in
terms
of
how
we
drill
down
into
this,
because
the
the
learn
section
the
best
practice
is,
is
intended
to
be
completely
generic.
So
the
things
that
we
discuss
in
there
should
be
applicable
to
all
systems.
B
B
And
so
the
original
intent
was
to
treat
those
things
as
case
studies
within
the
community
section
to
say:
okay,
if
you're
solving
this
problem
with
Jenkins,
here's
what's
best
practiced
for
using
Jenkins
and
here's
how
you
handle
those
those
very
fine
detail,
cases
that
are
applicable
to
you,
who
might
not
be
applicable
to
Jenkins
X,
because
it's
the
inverse
model
of
of
handling
your
your
event
system.
B
E
B
A
case
where
I
think
we're
we've
got
a
big
gap
in
the
community
section
where
the
intent
was
to
to
get
each
of
the
projects
to
start
to
write
about
best
practices
relating
to
their
individual
tool
sets
are,
but
the
the
challenge
has
been.
You
know
finding
people
with
the
time
and
inclination
to
to
document
rather
than
write
code
and.
D
And
I
think
there's
it's
kind
of
a
three-way
right,
so
it
I
think
there's
an
element
that
that
ties
this
to
the
the
measurements.
The
measures
right,
if
you
think
about
okay
you're
at
a
you're
at
and
what
did
you
call
it,
the
survivability,
the
survivable
level
of
investment?
What
does
that
mean?
Well,
it
probably
means
a
correctness.
How
do
you
measure
it
code
coverage?
Oh
thanks,
Emil.
D
How
do
you
measure
it
maybe
use
a
code
coverage
tool
and
then
maybe
there's
an
example
of
a
of
a
particular
project?
That's
using
something
along
those
lines
or
it's
like.
Oh,
if
you
have
like
a
security
Focus,
you
know.
Are
you
incorporating
like
snake
checks
or
or
similar
right
and
then
I
think
where
it
really
gets
interesting
with
developer
productivities
to
me
and
if
you
read
the
space
framework
yet
Fati,
that's.
D
Good
one
yeah,
where
it's
it's
really
about
optimizing
around
velocity
correctness
on
all
of
those
things
with
not
just
tooling
but
also
process,
enhancements,
communication
models.
D
All
of
those
things
in
aggregate
optimizing,
your
organization
in
a
more
holistic
way
right
and
then
measurement.
There
is
actually
a
combination
of
instrumented
telemetry.
D
So
I
think,
there's
I,
think
there's
a
lot
of
opportunity
here,
but
I
I,
I'm,
leaning
towards
the
case
study
model.
Just
because
you
know
there's
so
many
details
like
how
do
what?
What
are
the
build
systems
that'll
enable
you
to
do
decent
caching
great,
but
if
we
bring
it
into
prescriptively,
people
are
just
going
to
check
out,
because
you
know
the
the
uplift,
for
example,
to
switch.
D
Your
old
cmake
system
to
bazel
is
probably
not
one
that
many
companies
are
are
prepared
to
make
unless
there's
no
other
choice
right
that
kind
of
stuff.
It's
like
we
don't
want
to
really
get
into
the
business
of
prescription
at
that
level,
and
the
other
concern
that
I
have.
Is
that
a
lot
of
the
tools
in
the
space
as
you,
especially
for
testing,
start
to
get
very
commercial
like
there's,
not
a
lot
of
Open
Source
test
Frameworks,
and
so
how
do
we
want
to?
You
know?
D
I,
don't
think
anybody
is
against
us
talking
about
commercial
things,
but
if
we
do
it
in
any
way
other
than
this
is
just
an
example,
then
it
looks
like
we're
like
make.
You
know
potentially
making
recommendations
for
commercial
software,
which
is
not
what
we
want
to
do
so,
but.
C
D
Think
I
do
think
maybe
exploring
this
as
as
part
of
like
Community
case
study
is
definitely
a
cool
opportunity.
B
I
think
there
is
probably
also
an
opportunity
to
touch
on
some
of
this
in
the
reference
architecture
work
because
in
in
many
cases,
you're
getting
into
territory
here,
where
it's
a
trade-off
rather
than
a
best
practice,
and
so
oh,
for
example,
when,
when
you're
looking
at
caching,
you
can
reduce
your
workload
and
speed
up
part
of
your
software
delivery
process
by
caching
a
bunch
of
things
but
say
one
of
the
things
that
you're
caching
is
the
this
this
this
this
this
this
this
this
this
so
cve
checking,
for
example,
well,
the
cves
are
being
updated
on
a
real-time
basis,
but
daily,
so
the
more
caching
you
have,
the
more
likely
you
are
to
have
zero
days
going
out
in
your
code
base
because
you're
not
checking
the
code
base
every
time
you
build
it.
B
To
say
you
know
which
of
these
things
are
the
most
important
factors
and
therefore
here's
how
you
should
optimize
the
shape
of
this
process.
For
your
scenario-
and
that's
it's
not
a
case
that
there's
a
one-size-fits-all
best
practice.
It's
actually
once
you
get
to
this
level
of
the
granularity
you're
going
to
face
some
really
hard
decisions
and
those
decisions
may
not
hold
for
the
lifetime
of
your
product,
so
you
may
have
to
change
those
decisions
over
time.
D
I
love
that
example,
because
churn
introduces
its
own
challenges
right
so
and
we're
having
this
exact
conversation
right
now
with
my
team,
because
we
build
images
that
are
comprehensive.
They
include
the
OS
distro
and
a
tool
chain
or
two
answer
anytime,
something
changes.
We
have
to
rebuild
the
whole
thing.
It's
like.
We
need
to
break
this
out.
Do
we
need
to
separate
the
OS
from
the
tool
chain
and
do
we
actually
want
to
incorporate
the
tool
chain
or
do
we
want
to
mount
it?
Because
we
could
use
EFS
or
similar
right?
A
You
know
sick
as
for
them
as
a
place
for
them
to
come
and
talk
about
these
things
like
I
can
still
tell
them
yeah
they
can
come
and
talk
about
what
they
are
doing
there,
but
they
are
again
their
vendors,
as
you
highlighted
like
they
are
working
with
a
commercial
tool,
but
isn't
there
a
middle
ground
here?
Okay,
yeah.
D
That's
that's
exactly
where
we
have
the
community
section,
yeah
it
and
that's,
and
it's
just
to
make
sure
that
we
have
Clarity
like
this
is
a
a
use
case
or
a
case
study
set
distinct
from
this.
Is
the
CD
best
practice
taxonomy
right,
so
we
just
have
a
different
section
and
we
just
want
to
make
that,
and
that
was
how
we
meant
to
incorporate
that.
But
absolutely
like.
D
We
have
vendors
like
hey,
here's,
what
we're
doing,
and
ideally
here's
you
know
some
of
the
projects
or
sdks
or
whatever
that
we
have
and
we
can
tie
them
back
and
tag
it
in
such
a
way.
It's
like,
oh
well,
you're,
looking
at
someone
who's
really
in
investing
in
you
know
from
the
what's
the
the
learn,
the
learn
part
of
the
site
and
they're
looking
at
continuous
testing
and
then,
as
you
know,
in
your
case,
the
vendor
comes
in.
They
have
a
a
case
study.
D
A
D
Always
wanted
that
we
just
haven't
gotten
that
far
yet
yeah
and
we
can
help
them.
We
should
probably
like
make
a
template
or
something
to
figure
out.
I
mean
bug
Nicola
to
get
a
template
that
people
could
just
download,
fill
it
in
and
then
PR
it
just
to
make
sure
they're
conforming
to
the
site
rules.
Yeah.
C
D
A
A
That's
not
even
result
in
worse
things,
people
leaving
their
jobs
because
they
can't
make
things
happen.
It's
like
that's
how
I
was
thinking
like
playing
this
hope.
It's
the
best
practice
like
you
should
look
for
in
putting
your
build
time
before,
even
claiming
to
do
a
Content
inspiration
and
so
on
type
of
things.
But
I
I
will
hopefully
get
back
about
this
topic
with
that
person.
B
D
A
So
this
we
haven't
finalized
the
plans
yet,
but
we
nearly
identified
when,
where
how
the
next
silicone
is
happening,
so
we
plan
to
co-locate,
we
call
it
gitopscom,
so
they
will
run
together
to
you
know,
have
broader
coverage
around
CD
tops
type
of
stuff
and
it
will
take
place
on
May,
8th
and
9th
just
before
open
source
Summit
in
Vancouver
and
the
details
are
not
available
yet,
but
at
least
we
know
when
and
where
it
will
happen
and
it
will
be
hosted
by
both
cncf
and
CDF.
So
I
have
broader
reach,
atoms
or
commodities.
A
A
It's
like
this
design,
Summit
type
of
session
or
hack
sessions.
I
am
talking
device
team
to
have
a
room
or
two
for
this
type
of
you
know.
Focus
sessions
people
may
want
to
you
know,
come
together
and
hack
things
around
or
discuss
things
until
the
topics
about
that
and
so
on.
So
more
info
will
be
available
as
soon
as
Iran's
team.
Finalize
that
yeah.
B
C
A
D
D
The
next
one
we're
gonna,
try
and
get
David
and
and
try
and
map
up
events
to
to
metrics,
but
my
CSO
is
is
currently
in
Madrid.