►
From YouTube: CDF SIG Best Practices - Dec 13, 2021
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
C
So
I
did
try
setting
up
with
netify
so
upside.
Is
that
it's
hooked
up
with
the
github
repo
and
the
idea
is
that
if
something
then
so
the
way
it's
supposed
to
work
is.
If
someone
opens
a
pr,
then
it
will.
If
and
if
you
are
like
a
member
of
of
this
account,
then
you'd
be
able
to
do
a
preview
of
your
commit
and
then
once
things
are
committed,
it
will
then
build
it.
C
So
some
nice,
auto
deployment
stuff,
build
and
deploy
it's,
because
it's
this
model
where
a
free
tier
is
one
account
the
only
user
on
it
is
me,
so
I
think
the
model
we'd
have
to
work
with.
If
this
is
the
deployment
route
we
go
with,
is
that
people
could
preview
locally
with
with
dot
with
docker
compose
and
then
open
the
pr-
and
you
know
once
it's
submitted,
then
it
could
update
this
site
and
we
can
map
this
to
a
proper
domain
if
we
wanted
to.
So
that's
that's
sort
of
the
easy
route.
C
B
C
It's
no.
This
is
building
off
the
cdf
best
practices
repo.
So
I
committed
I
committed
that
first
sort
of
skeleton
set
of
source.
The
last
time
we
met.
I
I
did
that
that
day
and
and
tara
did
a
review
and
yeah
pr
so
yeah.
If
we
could
get
the
setup
with
the
same
account,
I
can
send
you
the
instructions
that
I
use
to
set
this
up
with
netlify,
so
that
the
same
kind
of
configuration
can
be
used
and
then
yeah.
Then
then
we
could
work
with
it.
That
way,.
B
A
C
That
was
my
main
update
if
so
yeah
and
once
we
get
into
the
new
year,
I'm
probably
going
to
get
busier,
so
I
I
will
certainly
be
able
to
help
you
know
if
you
need.
If
you
need
some
consultation,
I
can
still
come
to
the
meetings,
but
I
don't
know
how
much
time
I'll
be
able
to
sink
into
this
once
we
get
into
new
year.
C
A
B
C
Tracy,
do
you
have
instructions
for
how
contributors
to
the
landscape
update
the
docs
so
that
we
could
use
a
similar
model
because
right
now
the
the
information
on
this
sort
of
skeleton
site
is,
you
know,
preview
locally
with
docker,
then
there's
a
sort
of
boilerplate
for
the
netlify
instructions
that
I
haven't
updated.
But
if
we
have
sort
of
process
already,
then
it
might
be
nice
to
copy
that
over
here.
B
Yeah,
I
think
the
the
landscape
does.
What
it's
not
explicit
about
is
just
who
who
reviews
it,
because
at
one
point
it
was
a
few
people
on
the
toc
and
then
they
stopped
maintaining
it.
So
now
it's
it's
pretty
much
cara
and
a
couple
of
other
folks,
but
yeah.
The
steps
are
there
and
what
I'd
recommend
is
we're
just
a
bit
more
clear
on
who
the
folks
are
who
like
seek
best
practices
group,
and
I
think
that's
a
good
excuse
to
get
that
all
kind
of
tidied
up.
B
C
B
B
Right
and
then
maybe
since
we
have
justin
here,
we're
talking
about
the
assessment
side,
because
now
I
know
justin
you're,
pretty
interested
in
doing
some
work
or
well
you're,
actively.
Looking
at
how
teams
can
assess
themselves
and
did
you
have
any
thoughts
you
wanted
to
share
or
tell
us
more
of
what
you've
been
thinking
through.
E
B
E
E
B
Great
yeah,
let
us
know
how
we
can
help
and
yeah.
I've
got
some
thoughts
around
capabilities
and
different
ways
of
things.
I
might
try
doing
a
write-up
of
of
the
ones.
We've
thought
through
a
bit
or,
I
think,
are
clearer
than
others.
Some
are
some
to
me
are
more
straightforward
than
others
in
terms
of
what
people
should
be
doing.
B
Okay,
there's
a
certain
school
of
people
who
are
turned
off
by
the
idea
of
the
term
best
practices
itself,
so
they
either
want
to
call
it
good
practices
or
emerging
practices
or
something
about
there's.
No
such
thing
as
best,
and
so
in
this
whole
spirit
of
saying
you
know:
how
could
we
brand
it
effectively
or
what's
a
good
way
to
make
it
distinct
is
just
interested
if
anyone
has
any
similar
takes.
I've
heard
anything
around
that
of
are
these
really
best
practices
or
yeah?
How
how?
How
firmly
do
we
want
to
stand
behind
that.
A
D
D
B
Great
yeah,
let
me
think
about
that,
but
yeah.
The
good
thing
is
nicola,
like
I
think
we
were
looking
for
something
to
point
people
out
and-
and
this
is
really
useful
because
up
to
now
it's
been
pretty
abstract
and
I
know
those
folks
who
want
to
help
or
want
to
give
feedback
but
yeah.
We
just
need
to.
I
think
let
me
do
that
work
on
the
contribution
guide
and
then
we
can
start
pointing
them
at
it,
and
I
think
we
can
yeah.
It
will
start
to
build
and
pick
up
some
pace.
E
B
C
B
Yeah,
so
I
guess
we
should
get
to
a
point
where
we
can
move
a
lot
of
the
useful
content
from
that
doc
into
github
and
then
deprecate
that
doc.
So
then,
all
comments
start
to
happen
on
the
website
and
we
get
some
consistency
because
yeah,
as
you
said,
it
was
a
dump
in
terms
of
lots
of
different
things
evolved
in
different
ways,
so
that
that
might
be
another
goal
as
well
just
get
rid
of
that
as
a
any
source
of
truth.
But
yeah.
Let's
take
a
look
at
those
comments.
C
If
the
content
isn't
going
to
go
through
a
lot
of
change
in
terms
of
you
know,
points
that
are
being
made
added
to
the
doc.
If
you're
interested
in
me
taking
a
pass
and
maybe
trying
to
like
make
it
not
so
long
or
maybe
it
makes
some
things
a
little
more
clear.
I
I
I
can
possibly
do
that
if
there
is
a
rush
to
get
into
github.
C
B
A
I
I
would
suggest
that
we
take
what
we've
got
and
get
it
across
into
the
the
new
format
so
that
it's
under
version
control
and
and
then
start
to
iterate
through
it
and
refine
it,
because
that
when
we,
when
we
start
to
split
it
up
and
move
it
into
separate
sections,
we're
going
to
want
to
restructure
it
as
we
do
that
so
having
the
content.
Stay
as
it
is
at
the
moment,
doesn't
really
matter
because
it's
a
it's
a
big
long,
linear
document
at
the
moment.
B
I'll
take
a
look
at
that
and
what
we
need
to
get
to
a
proper
sort
of
minimum
viable
version,
which
maybe
we
can
schedule
an
announcement
around
next
year
and
just
give
us
a
kind
of
a
focus
like
by
this
date.
Let's
try
and
have
all
the
automation
in
place.
The
contributor
guide
in
place
a
first
set
of
the
text
in
various
sections,
some
basic
assessment
and
then
there's
something
a
milestone
we
could
work
towards
next
year.
A
So
I
think
the
first
key
milestone
is
getting
to
the
point
where
we
can
say
to
everyone
in
in
this
team:
okay,
here's
the
working
document
it's
now
available
for
you
to
start
contributing
to
here's,
how
you
log
into
it.
Here's
how
you
add
stuff,
here's
the
review
process,
so
once
we've
got
that
milestone,
then
we
go
back
to
where
we
were
before,
which
was
incrementally
building
on
on
stuff
and
putting
it
in
place.