►
From YouTube: CDF SIG Best Practices - Feb 7 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
E
D
D
Okay,
so
I
had
a
couple
of
things
so
one
I
merged
your
change,
terry,
I
don't
know
if
you
saw
that.
D
I
figured
it
you
know
no
sense
not
to,
and
when
I
was
talking
to
nikola,
she
didn't
have
any
violent
objections.
So
what
went
ahead
and
got
that
going?
Do
we
have
a
maurizio
today?
Did
he
come
by?
Doesn't
no,
it
doesn't
look
like
it
too
bad.
D
So
the
other
thing
was
he's
got
those
contributions
that
he'd
like
to
make
so
figuring
out
how
to
incorporate
those
in
a
reasonable
way.
Wow.
My
your
background,
terry,
is
like
triggering
my
adhd
to
keep
looking.
D
D
One
is
stuff
like
mauricio's,
which
is
an
implementation
in
theory
of
a
best
practice.
Actually
I
haven't
looked
at
it
yet
I'm
assuming
that
it
is,
and
then
the
other
oops,
the
oh
and
then
the
other
thing
is
the
vendor-specific
stuff.
D
But
I
was
looking
at
the
resources
tab
in
the
or
the
resources
area
and
the
think
in
the
thinking
that
this
is
where
all
such
things
like
that
would
go.
D
Sorry,
as
far
as
like
you
know,
any
any
early
guidances
that
we
want
to
keep
in
mind,
as
we
start
to
put
stuff
in
here,.
C
Yeah,
I
think
that
aligns
to
what
we
we
said
previously,
that
we
would.
We
would
put
that
sort
of
stuff
in
in
this
section
and
mark
it
out,
so
that
it
was
invisibly
different
from
the
the
core
practices.
D
F
Too,
I
don't
have
super
strong
feelings
about
it,
so
in
the
learn
section
it
has
its
own
sort
of
dedicated
table
of
contents.
So
when
you're
in
that
section,
that
would
be
the
table
of
contents
that
you
see-
and
you
would
have
that
context,
but
it
could
be
meaningful
to
have
a
different
color,
for
you
know,
maybe
in
the
top
and
bottom
bar,
for
example,
like
the
header
and
footer,
to
designate
the
stuff.
That
is
implementation
specific.
F
F
They
aren't
really
like
specific
implementations,
but
they're
like
going
down
that
rabbit
hole,
is
kind
of
beyond
the
scope
of
the
best
practice
core
stuff
we
have
so
that
resources
page
was
really
more
about
about
that
and
like
pointing
and
pointing
to
like
christy
wilson's
book
and
and
the
other
book
that
got
mentioned.
So
it
was
more
like
hey.
You
know
here
are
the
rabbit
holes.
You
can
go
down
to
like
explore
even
more,
whereas
this
section
was
going
to
be
yeah
like
if
we
had
cdf
members
who
wanted
to
put
things
here.
F
This
would
be
the
section
we
could
do
that
and
so
yeah
we
have
like
this
blue
header.
On
top,
we
could
have
a
different
header.
We
could
make
the
maybe
make
the
table
of
contents
a
different
color
like
there
are
different
options.
There.
D
B
C
I
think
my
feeling
on
this
one
is
that,
if
you're
coming
to
it
as
a
as
someone
looking
to
use
this
as
a
facility,
you
might
make
the
assumption
that
community
was
about
shared
experiences
and
if
you
were
looking
for
actual
examples,
you'd
probably
look
in
the
resources
section,
because
that's
a
fairly
common
pattern
across
other
sites.
C
We,
what
we
originally
were
going
to
do
with
that
section,
was
to
use
it
for
individual
projects,
so
so
that
you
could
get
examples
of
here's.
How
you
would
use
jenkins
x
to
to
do
this
or
here's
how
you
would
use
jenkins,
etc,
etc.
C
C
D
Right,
okay,
so
it
could
just
be
a
matter
of
how
things
are
referenced
so
that,
regardless
of
which
one
you
go
into
first,
you
end
up
in
the
right
place.
Does
the
community
have
a
distinct
table
of
contents
from
resources?
Currently?
Is
that
the.
F
I
I
didn't
imagine
the
resources
was
going
to
be
a
huge
long
thing,
so
it
doesn't
have
a
table
of
contents
right
now,
but
I
can
change
the
template,
but
this
one.
Yes,
it
has
its
own
table
contents.
It
says
community
at
the
top
on
the
top
left
there,
so
that
heading
would
stay
there
to
show
that
this
is
a
community
table
of
contents
and
so
yeah.
This
would
be
independent
from
the
stuff
under
learn,
which
is
the
best
practices
stuff
yeah.
C
I
think
what
we
need
to
bear
in
mind
with
the
with
this
particular
point
is
that
the
examples
are
effectively
a
reference
to
somebody
else's
book,
so
we
don't
have
any
control
over
the
content
of
that
and
we
don't
necessarily
endorse
everything.
That's
in
it,
but,
like
dora,
you
know
if
there's
value.
G
G
A
D
D
Two,
I'm
sorry,
I
poured
the
coffee,
I
have
not
drunk
the
coffee,
yet
you
know
how
it
is
okay,
so
going
back
to
the
maurizio
example,
he's
got
a
couple
of
example:
repos.
He
wants
to
donate
and
just
have
them
be
part
of
this,
which
needs
to
be
reviewed.
D
C
Yeah
we're
going
to
need
to
make
it
very
simple
for
him
to
maintain
that
code
base
independent
of
the
rest
of
what's
going
on,
so
we
should
probably
just
have
a
little
bit
of
think
about
whether
we
directly
link
it
into
the
hierarchy
or
if
we
we
put
it
somewhere
slightly
different
and
then
reference
it
through
internal
links
in
in
the
doxy
setup
right.
D
Well,
what
I'd
love
to
have
is
that
any
example
that
was
wherever
it
was
possible
to
put
like
a
like
a
really
quick
github
action,
ci
test
on
it,
so
that,
if
it
didn't,
if
it
stopped
working
we'd
know
because
the
worst
thing
in
the
world
is
to
have
example,
code,
that's
broken,
and
in
that
regard
a
separate
repo
might
be
easier
to
manage.
D
D
D
G
D
Or
use
cases
more,
I
I
think
the
general
concept
is
that
we
want
there
to
be
as
there's
like
the
set
of
principles
best
practice
you
learn
about
and
then
whatever
additional
resources
and
support
of
those
we
can
provide.
So
it
might
be
a
case
study.
It
might
be
an
actual
example
so
trying
to
figure
out
and
then
for
vendor
specific
stuff.
We
want
to
be
able
to
do
that
too.
We
just
need
to
be
able
to
make
sure
people
know
that
we're
not
necessarily
endorsing
we're
just
reflecting
right.
C
C
Then
everyone
gets
to
contribute
their.
You
know
particular
advantages
for
for
their
given
tool
set
and
we
get
the
benefits
of
both
worlds.
Exactly.
G
D
Wait
so
debate
just
to
confirm
this
will
go
under
resources
or
under
community.
No,
let's
go
to
community.
D
And
then,
ideally,
we
can.
D
D
D
D
D
D
F
D
F
I
believe
it
is
by
page,
I
don't
think
it's
more
granular
than
that,
but
you
can
assign
multiple
tags
to
a
particular
page.
Okay,
I
mean
that
that
goes
back
to
the
question
of
you
know:
how
big
do
we
make
your
page.
D
D
G
C
G
D
D
There's
nothing
that
says
that
we
can't
change
our
minds
if
we
decide
that
other
formats
might
work
better,
yeah.
Okay,
and
do
you
have
access
to
the
repo.
D
G
D
Yes,
okay,
all
right!
Okay,
then!
Yes,
please,
please
be
our
guinea
pig
for
this.
This
would
be
great
and
then
nicola.
I
don't
know
if
we
wanted
to
if
you
wanted
to,
or
we
wanted
to
recruit
someone
to
do
something
similar
for
for
google,
and
we
should
also
get
get
it
christy
to
see
if
we
could
get
a
tech
time,
someone
to
contribute
a
tecton
example.
If
that
wasn't
you.
F
Yeah
I
know
when
I
asked
the
da's
someone
got
tagged.
I
I
haven't
heard
anything
yet,
but
there
was
there
was
a
da
that
got
tagged
about
whether
they'd
be
interested
in
contributing.
So
I
can
follow
up
on
that.
A
D
Who
was
that?
Oh
great
anthony
and
it
was
anthony-
and
there
was
two
fidelities.
D
Juan
juan
juan
flores,
okay,
where
did
anthony
go.
C
C
D
I
can
take
a
stab
I
was.
I
was
starting
to
go,
look
to
see
what
stuff
we
were
missing
and
then
I
realized
that
we
hadn't
reviewed
terry's
pr
yet
so
I
switched
to
work
on
that.
Instead.
E
E
E
I'm
sorry
who
did
that
niece
and
oh
nest
next
yeah,
so
yeah,
it's
just
super
cool.
D
We
may
want
to
break
this
down
a
bit
functions
yeah
into
into
functional
areas.
Yeah.
E
Now
I
can
have
a
stab
at
trying
that,
for
let's
say
software
security
and
see
what
it
looks
like
just
pull
out:
salsa
and
misguide
lines
and
yeah.
D
D
So
s
assess
I'm
sorry,
we've
got
some
stuff
in
here.
D
D
Did
you
want
to
once
you
got
your
example
landed?
Did
you
want
to
throw
this
on
your
backlog.
G
E
Yeah
there's
a
couple
of
other
fidelity
folks,
nick
benson
and
jimmy
mcnamara,
who
might
be
able
to
and
nick's
been
doing
a
lot
of
writing
blog
posts.
So
I
can
reach
out
to
him.
D
D
It's
right
there
right
there,
oh
nicola
tecton's,
not
you
right.
F
One
of
the
other
sstp
writers
is
on
that
so
yeah
jerry
jerry.
This
is
the
way
to
protect
home.
D
That's
what
I
was
trying
to
think
of
okay,
so
google
has
some
from
a
documentation
perspective.
Google
has
a
couple
of
of
types
of
docs
that
are
dually
published.
So,
for
example,
we
have
google
documentation
that
also
gets
published
to
spring
boot,
for
example.
D
Similarly
terraform
right,
and
so
this
makes
it
easier
to
be
able
to
share
doc
content
for
for
the
writing
team
more
broadly,
without
having
to
individually
publish
to
each
thing.
So
would
we
consider
a
would
we
consider
it
a
reasonable
thing
to
say
hey
if
you
wanted
to
co-publish,
you
know
a
set
of
pre-reviewed
examples
here.
Here
are
the
things
that
you
would
do
to
do
that.
D
C
D
That,
I
don't
know
you
know
is,
is
terraform
and
spring
boots,
some
of
the
other
sites
they're
doing.
Are
they
using
the
same
format
or
is
there
some
kind
of
info
we
had
to
set
up
like
that?
I
don't
know,
but
I
think
if
we
could
say,
hey
we'll
work
with
you
to
help
help
it
so
that
you
can
publish
to
this.
I
think
that
might
be
not
a
bad
story
to
sell.
B
E
D
For
terraform,
it's
the
same,
I
think,
and
it's
it's
kind
of
like
a
big
huge
thing
like
it's.
Just
all
of
the
terraform
stuff
it
gets
is
getting
sucked
into
google
somewhere.
I
wasn't
part
of
that
project,
but
I
know
who
was
on
it,
so
I
could
find
out
how
that
was
working.
I'm
not
sure
what
went
into
that.
I
don't
know
about
spring
boot.
F
E
Yeah-
and
I
think
that
could
be
potentially
quite
nice
and
it
just
eases
the
maintenance
burden.
I
I
think
scoping
it
in
in
some
way
will
be
useful
but
yeah
in
general,
plus
one.
D
Okay,
you
can't
think
of
any.
I
know
you're
technically
no
longer
in
the
world,
but
you
can't
think
of
any
like
legal
reasons
why
that
would
be
a
bad
thing.
I
couldn't
think
of
anything
but
okay.
D
D
To
see
what
to
get
more
details
about
what
google
is
doing
and
then
maybe
there's
some
kind
of
I
don't
know
a
hook
or
a
validator
that
we
could
like.
If
you
triggered
her
pr
with
a
particular
tag,
we
could
make
sure
that
it
wasn't
going
to
break
the
site
if
it
came
in
okay.
I
think
that
was
the
last
thing
that
I
was
thinking
of
any
other
topics:
concepts.
D
D
Tracy,
do
we
have
somebody
who
should
we
talk
to
about
actually
publishing
the
thing
we
still
have
to
have
the
branding
conversation?
E
E
Either
yeah,
I
think,
depending
on
what
it
is
different
people,
so
cara
can
help
connect
us
in
to
like
the
the
creative
services
folks,
like
she
just
channels,
issues
to
them
and
reports
back
and
and
then
chris
and
check
for
anything
url,
and
he
can
connect
us
to
the
right
person.
Who'll
help
on
that.
E
Yeah,
logos
and
stuff,
I
think,
you're
good
they're,
all
already
under
the
artwork
folder
with
the
guidelines.
So
do
you
know
where
that
is
they
find
it?
If
you
could.
F
Tracy,
the
other
thing
that
came
up
last
time
we
met
was
just
around
the
netlify
account
and
one
of
the
things
I
had
looked
up.
I
don't
know
if
you
saw,
but
one
of
the
things
I
had
looked
up
was
that
if
someone
is
added
as
a
reviewer
that
they
would
be
able
to
they'd
be
able
to
see
the
the
deployment
previews,
which.
F
Come
up,
I
think
in
the
pr
is
when
they
get
submitted,
but
you're
allowed
to
have
an
unlimited
number
of
reviewers
in
a
netflix
project.
So
if
there
were
people
that
we
wanted
to
add
as
reviewers.
F
E
So
yeah
and
I
think
we
can
add
folks
in
as
reviewers
as
needed,
so
I
just
need
email
addresses
and
happy
to.
I
think
I
can
do
that
for
the
site,
as
can
tara.
Maybe
terry.
D
F
Yeah
on
netlify,
I
was
looking
at
the
permissions
and
it
didn't
look
like
anybody
other
than
you,
and
I
think
chris
and
chris
yeah
yeah.
E
D
I'm
sorry
so
for
creative
services,
that's
just
things
like
final
review
and
publishing
so
the
url
and
that
kind
of
stuff,
or
would
that
be
a
crisp
question?
Sorry,
I
was
just
trying
to.
E
E
F
Sorry,
no
just
stuff
about
the
reviews.
I
wanted
to
make
sure
I
got
in
okay.
C
All
right,
so,
from
my
perspective
couple
of
quick
things,
I
I
noticed
that
we've
we've
got
those
sort
of
use
cases
the
the
user
stories
that
that
we
wrote.
C
I
was
wondering
whether
we
should
do
a
separate
section
of
you
know.
Why
should
I
read
this
where
we
could
just
put
in
a
bunch
of
those
things
to
just
to
see
if
that
resonates
with
people
and
helps
them
to
to
draw
them
into
the
the
documentation,
and
we
might
also
be
able
to
then
start
to
branch
out
so
for
people
with
particular
areas
of
interest,
we
could
lead
them
into
particular
sections
of
the
documentation.
D
So,
like
a
user
journey
kind
of
like
what
problems
am
I
trying
to
solve?
Oh,
this
sounds
like
my
problem.
That
kind
of
thing
yeah.
C
So
so
you
know
initially,
let's
just
capture
the
the
things
that
we've
got
them
put
them
somewhere
fairly
visible
and
then
let's
have
a
think
about
how
we
might
use
that
as
a
starting
point
for
different
user
journeys.
Through
the
information.
D
Sure
I
was
did
we
lose
the
doc?
I
thought
I
thought
there
was
a
link
to
the
google
doc
here.
D
A
C
Okay
and
and
then
just
a
a
general
point
from
from
this
month's
toc
meeting,
the
the
various
sigs
and
project
teams
are
all
a
bit
styloid
at
the
moment
and
we're
not
doing
a
very
good
job
of
communicating
across
all
the
activities
that
are
going
on
and
without
tracy
being
the
link
between
everything.
That's
happening
right
now.
C
We're
being
asked
to
look
at
ways
of
improving
that
situation,
so
the
expectation
is
that
somebody
will
be
asked
to
join
from
each
of
the
the
six
into
the
tse
meeting
once
a
month
to
to
feed
back
on
activities
that
way,
but
then
we're
also
looking
at
different
ways
to
get
information
flowing
the
other
way,
so
that
people
know
what's
what's
happening
at
a
detail
level
and
and
can
collaborate
a
bit
more
across
the
various
streams.
D
I
mean
I
know:
cdcon
is
gonna.
Well
the
attempt
it's
going
to
be
attempted
in
person
this
year.
We
shall
see
yeah,
I
I
am.
I
am
tentatively
going
to
be
apparently
emceeing,
which
is
kind
of
cool,
but
I
put
a
big
caveat
on
it
because.
D
Sense
if
we
do
end
up
having
it
in
person,
because
a
miracle
occurs,
which
would
be
amazing,
a
you
know,
maybe
like
a
sig,
an
all
sig
birds
of
a
feather
or
some
other
form
of
like
mini
summit,
could
be
kind
of
a
fun
thing
to
to
shoot
for
if
we
could
get
everybody
in
on
site
yeah,
that's
not
amazing
wow.
It
sounds
incomprehensible.
C
C
If,
if
we're
going
to
do
something,
I
think
the
request
has
gone
out
for
that
this
week.
So
so
we
we
we
need
to
be
getting
involved
in
and
offering
ideas
imminently.
D
D
D
E
E
Oh
yeah,
no,
it's
just
saying
it
does
seem
like
we
are
in
a
better
place.
Now,
as
things
are
shaping
up,
it
seems
more
effective
to
be
taking
it
to
show
other
people
what's
happening
and
get
them
involved,
because
we
can
guide
them
to
more
clear
voice
to
contribute
so
yeah.
That's
that's.