►
From YouTube: Best Practices SIG - June 28, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
C
C
B
B
That's
so
good!
Well,
we
are
having
our
probably
most
serious
bout
of
Canadian
Wildfire,
bad
air.
B
It's
been
intermittent
like
there
was
earlier
this
month.
It
was,
it
wasn't
great,
but
it
was
okay.
I
think
today,
like
the
air
quality
is
somewhere
in
the
like
160
or
one
night.
It's
almost
200.,
which
is
in
the
unhealthy
range,
which
was
entirely
different
yesterday,
was
really
good.
So
it's
just
kind
of
hit
here
today,
pretty
bad
foreign.
B
E
I'm
going
to
get
the
notes
up
here,
unless
you
already
have
them
Terry.
C
E
E
E
We
had
the
preliminary
sort
of
outline
for
the
Mainframe
doc.
I
put
some
comments
in
there
come
on
now.
E
I
haven't
had
a
chance
to
see
if
those
comments
had
been
addressed.
If
there's,
if
we
wanted
to
identify,
you
know
a
a
set
of
future
actions
if
we
wanted
to
start
to
transition
this
into
a
preliminary
pull
request
and
start
editing
from
that
perspective,
you
know
how
are
people
feeling
as
far
as
wanting
to
proceed
in
order
to
move
the
needle
on
this.
C
E
E
Right,
my
question
was
more
logistical:
I
was
like.
Do
we
want
to
leave
this
in
a
Google
doc
form,
or
do
we
want
to?
You
know,
have
a
branch
to
to
to
have
sections.
You
know
where
how
what
what
can
facilitate
better
contributions
at
this
point
for
what
we
did
for
this
the
secure
supply
chain,
we
basically
did
the
white
paper
in
Google
doc,
but
that
was
driven
by
David
bendery.
E
So
this
seems
to
be
a
little
bit
more
of
a
crowdsourced
effort.
B
E
So
so
I
think
where
we're
at
then
is
you
know
who's
going
to
take
principal
authorship
to
to
drive
the
content.
To
get
to
the
point
where
we
can
finalize
review
and
then
get
it
published.
I
think
is,
is
the
key
thing
and
how
can
we
support
you
know?
What
can
we
do
to
support
that
that
person
or
persons.
D
Right
so
from
from
my
perspective,
I'm
happy
to
continue
with
helping
with
the
effort.
I,
don't
know
that
I
have
capacity
to
write
away
paper
to
be
to
be
honest
at
this
time,
but
also
transitioned
into
a
new
role
within
my
organization,
which
is
you
know,
additional
challenges,
because
I
have
more
more
of
my
day-to-day
workload
on
that.
D
Not
that
I
so
like
I'm
willing
to
contribute
to
this
as
I
as
I
can
and
leave
comments,
but
even
when
you
know,
if
I
had
principal
ownership,
there's
a
few
a
few
issues
here
that
are
preventing
us
from
from
moving
forward,
one
is
engagement
from
others
on
the
Mainframe
side
to
contribute
to
this
document.
Perhaps
that
can
be
driven
through
open
Mainframe
Tac
would
be
my
suggestion
if
others
could
be
engaged.
D
Two
is
folks,
have
you
know
even
heard
it
on
on
this
call
a
little
bit
about
opinions
on
strategically
the
angle
at
which
the
white
paper
would
be
written
and
we
could
write
a
white
paper.
D
In
fact,
if
the
white
paper
was
written,
the
way
it's
written
now,
it'd
be
it'd,
be
in
opposition
sort
of
to
Terry's
comments
about
showing
how
it's
different
for
the
Mainframe,
because
really
the
the
story
that
the
draft
was
intended
to
tell
was
how
Mainframe
can
be
integrated
into
the
space
and
it's
like
any
other
platform,
not
focused
on
any
differences,
more
focused
on
similarities.
So,
if
you
were
doing
the
deployment
of
an
application
that
was
full
stack,
it
could
be
very
similar
across
Mainframe
and
distributed.
E
Sense
I
mean
if
it's
truly
not
different,
then
do
we
need
the
white
paper.
I
guess
is
the
question
but
I
think
there's
probably
a
category
I
think
what
Terry's
driving
as
though
there's
a
category
of
things
that
need
to
be
accounted
for,
but
that,
once
you
have
those
things,
then
it
is
as
everything
else
and
as
as
the
narrative
that
you're
trying
to
drive
towards
if.
D
You
had
like
a
baseline
white
paper
on
how
it's
done
in
the
distributed
World
from
the
CD
Foundation.
We
could
compare
and
contrast
I
think
I
had
asked
for
that
document.
I'm,
not
sure
if
it
ever
ever
came
up
but
that'd
be
another
angle.
You
know
I
think
in
general,
it's
more
of
an
information
lacking
information
in
the
general
world.
D
Right
I
mean
you
go
to
you,
go
to
these
client
shops
and
they're
running
a
distributed
team
and
they're
running
a
Mainframe
team,
and
you
can
now
use
Jenkins
on
the
distributed
side,
for
example,
to
drive
Mainframe
workload
and
there's
a
lot
of
initiatives
where,
like
the
Mainframe
portion
of
the
organization
they're
just
left
out,
because
oh
it's
Mainframe,
we
don't
understand
Mainframe
right,
it
can't
be
connected,
but
I
mean
it's
API
enabled
and
you
can
drive
stuff
over
there.
It's
just
left
out
of
the
that's
more
of
what
I've
seen
when
I
visited
places.
D
Is
this
left
out
of
the
conversation
is
this
is
the
problem
because
folks
don't
have
experience
in
Mainframe,
they
don't
know
about
it,
so
they
don't
pull
it
into
their
their
initiatives,
which
you'll
see
similar
things
happening
here
on,
like
the
software
supply
chain
security
side,
you
mentioned
I
just
bring
that
up.
You
mentioned
a
white
paper
was
written
written
for
that
right.
There's,
there's
web
servers
that
run
on
USS
on
the
Mainframe
and
they
should
be
subject
to
the
same
software
supply
chain.
D
They
also
have
the
same
thing
like
as
far
as
even
Beyond,
like
just
software
supply
chain.
Security
was
like
dependencies
and
things.
You
also
have
things
like
you
know.
Has
this
particular
asset
that
I'm
going
to
deploy
to
my
system?
Has
it
been
tampered
with?
Has
somebody
modified
the
files?
Well,
it's
been
sitting
there
before
I
actually
deploy
the
software
right
same
principles.
D
That
being
adopted
in
the
distributed
world
and
like
from
the
results
of
the
recent
executive
order
on
software
supply
chain
security,
they're
also
relevant
to
the
to
the
Mainframe
space,
but
I
think
if
we
don't
bring
Focus
to
it,
because
there's
you
know
in
general,
in
the
industry
right
there's
a
little
less
attention
to
Mainframe
for
the
overall
Workforce
there's
this
folks
working
on
Mainframe,
even
though
it
supports
a
lot
of
economic
activity.
So
we
just
highlight
how
those
things
are.
D
Are
you
know
really
applicable
to
applicable
to
Mainframe
I?
Think
I,
think
that
would
be
good.
You
know,
I'd
say
if
you
go
look
at
the
state
of
Mainframe
today
across
the
ecosystem.
You
probably
see
more
manual
activities
just
because
it
wasn't
brought
into
this.
You
know
automation,
first,
culture,
that
we
have
on
the
distributed
side,
but
I
think
we're
turning
the
corner
on
that.
A
little
bit
I
see
that
changing,
certainly
certainly
within
in
broadcom.
It's
changed.
We
do
a
lot,
a
lot
of
automation,
first
type
approaches
I.
E
Mean
another
another
key
aspect
of
the
narrative
is
also
is
that
there
it's
often
a
hybrid
scenario,
right
I
mean
you
can
I.
Think
IBM
Cloud
now
enables
access
to
power
mainframes
in
in
cloud
form,
which
is
kind
of
cool.
They
can't
do
that
for
Z
series
right
for
as
an
example,
so
I
think
there's
that
that's
another
aspect
that
if
you're
in
this
realm,
it's
a
hybrid
scenario
and
here
in
the
hybrid,
whether
it's
Mainframe
or
not.
If
it's
you
know
local
data
center
or
whatever,
there's
there's
some
overlap
there.
B
Might
be
actually
an
interesting
way
to
think
about
it
because
I
mean
kind
of
hearing
from
what
I'm
hearing
from
this
group
here
a
lot
of
the
initial
onus,
it
sounds
like
around
a
potential
weight
paper.
Collaboration
is
a
differences
aspect
and
I.
Think
and
Michael
correct
me
if
I'm
wrong
and
I
think
I
heard
this.
What
you're
saying
a
real
bitter,
interesting
focus,
at
least
from
a
Mainframe
perspective,
is
a
similarities,
because
the
the
common
narrative
is
they're
just
completely
different
animals.
You
can't
use
the
same
tools.
B
You
can't
use
the
same
processes,
and
this
is
driven
through
pretty
much
any
Enterprise,
that's
using
mainframes,
except
for
a
handful
of
very
forward-thinking
ones
and
the
more
that
it
can
be
driven
from
an
education
not
just
from
the
Mainframe
side,
because
I
think
a
lot
of
those
people
will
get
it,
but
from
the
broader
it
in
which
is
where
I
think.
The
validation
from
a
group
like
this
and
the
CD
Foundation
really
come
in
handy
is
a
way
to
sort
of
move.
B
That
narrative
forward
is
they're
not
different,
and
the
hybrid
approach
is
where
these
organizations
tend
to
be
willing
to
go
because
you
want
to
have
sort
of
a
similar.
You
know
deployment
environment
for
an
entire
application
that
might
have
like
multiple
tiers
of
distributed.
Iot
cloud-
and
you
know,
Mainframe
as
well
and
I-
guess
Michael
correct
if
I'm
wrong
on
any
of
that.
That's
sort
of
what
I've
captured
from
previous
yeah.
D
It
won't
be
there
day
one
you
had
containerization
on
distributed
platforms
for
a
while,
starting
to
see
containerization
on
Z
OS
like
different
specific
Technologies,
if
I
mean,
but
my
understanding
of
the
way
paper
two
as
far
as
similar
in
differences,
it
was
really
talking
about
the
flow
it
was
abstracted
away
from
the
Technologies.
So
as
far
as
the
flow
I
think
yeah
they're,
pretty
similar
can
be
pretty
similar.
C
C
So
for
most
of
that,
we
we
aren't
differentiating
between
any
given
Target
platform.
So
we're
just
saying
you
know
this
is
how
you
think
about
the
problem.
This
is
how
you
need
to
decompose
what
the
work
that
you're
doing
in
order
to
follow
a
continuous
delivery
methodology,
but
then,
at
some
point
we
want
to
be
able
to
call
out
specific
functional
domains
where
you
might
have
questions
about.
Well.
How
does
this
apply
to
me
in
my
situation
with
this
technology
stack?
C
So
that's.
Why
we're
thinking
about
taking
the
Mainframe
staff
and
any
other
of
these
context
specific
things?
A
good
example
is
AI
and
machine
learning,
because
that's
another
area
where
everybody
thinks
it's
completely
different
and
no
it's
not
it's
mostly
the
same,
but
there
are
additional
challenges
that
exist
in
that
space
that
you
have
to
take
account
of
in
order
to
be
able
to
integrate
into
a
single
overarching
methodology.
C
So
so
I
think
that's
where,
where
we
are
with
this
is
we're
saying:
how
can
we
take
this
subject
matter
and
then
knit
that
into
The
Narrative
for
best
practices
without
needing
to
at
every
stage,
specifically
call
out
open,
Mainframe
or
any
other
given
technology
and
how
you
would
do
it
in
in
that
context,
so
I
think
it
makes
sense
from
our
perspective
to
say,
look,
here's
the
overarching
methodology,
but
then
here's
the
domain,
specific
stuff,
where
you've
got
challenges
that
you
need
to
be
aware
of,
but
which
are
not
necessarily
big
issues.
E
Yeah,
it's
making
me
wonder
going
back
to
Michael's
point
I,
don't
know
that
we
actually
have
a
unified,
PDF
white
paper.
In
that
way,
it's
kind
of
it's
It's.
The
website
right.
This
kind
of
represents
all
of
the
things
that
we're
working
on,
but
I'm
wondering
if
you
know
we
continue
to
kind
of
enhance
that
and
and
the
Mainframe
stuff
becomes
more
of
the
community
example
build
up
like
Michael.
You
were
saying
like,
oh
you
can.
You
know,
use
Jenkins
to
manage
these
workloads
in
either
a
sole
Mainframe
or
in
a
hybrid
scenario.
E
It's
like.
We
could
get
a
case
study
that
documents.
Here's
what
here's,
how
that
was
set
up
right.
We've
been
wanting
to
do
that
for
a
while.
We
haven't
been
very
successful
in
getting
people
willing
to
contribute
their
example
workload.
So
maybe
that's
a
better
approach
that
you
know
kind
of
takes
those
two
things
in
conjunction.
C
C
So
it's
a
case
of
saying
you
know:
here's
how
you
would
do
continuous
delivery
with
Jenkins
X,
and
so
that
would
be
an
opportunity
to
do
say
an
open,
rainframe
specific
piece
in
in
there.
C
But
then
we
also
have
the
domain
specific
section
under
learn,
which
is
where
we
want
to
say:
here's,
here's,
an
application
domain,
that's
a
little
bit
different,
and
so
here
are
the
challenges
and
the
ways
that
you
need
to
think
about
this
generically
in
in
that
space,
without
referring
to
specific
projects
or
Technologies.
So
so,
if
you
like
anything,
that's
in
the
domain.
Specific
part
is
part
of
our
core.
Our
best
practices.
E
E
Okay,
I'm
capturing
some
some
action
items
here
and
my
I
think
Michael
or
John.
One
of
you
mentioned
there
was
an
open,
Mainframe,
Tech
I'm,
assuming
it's
a
technical
meeting
is:
do
we
have
information
on
when
those
are.
B
They're
on
the
second
and
fourth
Tuesdays
of
the
month,
I
mean
we're
happy
to
you
know
if
you
all
would
want
to
come
and
kind
of
present
a
little
bit
of
the
idea
of
what
you'd
want
to
do.
We
can
get
you
on
the
agenda
for
that,
but
that's
basically
sort
of
think
of
that,
as
sort
of
our
technical
oversight
group
across,
like
all
of
our
projects
and
other
sort
of
technical
work,.
E
Yeah
so
I'm
just
trying
to
think
you
know
from
from
Michael's
Point
he
doesn't,
you
know,
doesn't
have
the
capacity
to
to
take
lead
on
this.
So
it's
you
know
it's
engaged
and
see
if
we
can
get
somebody
else
that
we
can
partner
with
and
bring
on
board
I'm
happy
to
I'm
I,
don't
know
where
the
meetings
are
I'm
North,
America
Terry
is
a
may.
E
D
A
Just
I
want
to
I
want
to
add
something
about
the
PDF.
Why
I
am
talking
about
PDF
a
lot,
because
this
is
a
feedback
I
directly
received
from
few
people,
like
mainly
the
people
on
management
positions,
they
are
happier
if
they
can
download
PDF
put
on
their
iPads
and
read
them
on
airplanes,
rather
than
looking
at
websites
or
GitHub
repos
and
so
on.
That's
why
there's
a
feedback
I
heard
a
few
times
from
different
people
so
and
for
me
frame
so
I
guess
such
people
are
part
of
our
target
audience.
E
Yeah
no,
and
it
certainly
wasn't
suggesting
that
we
don't
do.
One
I
was
just
saying
that,
where
we're
starting
to
go
for
some
of
these
things
are
not
white
paper
friendly
and
we'd
have
to
create
an
additional
formatted
document.
John.
Do
you
have
a
link
that
you
could
drop
in
the
chat,
maybe
for
for
the
open,
Mainframe
meetings.
B
Yes,
I
can
I
can
yeah.
B
B
Join
the
club,
yeah
I'll,
put
a
link
here
that
has
some
of
the
information
about
it.
Hey.
D
One
one
other
thought
here
too
John
is
like
the
attack
would
get
us
to
leadership
in
certain
areas.
Yes,
but
the
I
almost
wonder
if
this
goes
eventually
to
like
the
Zoe
technical
steering
committee,
where
you
get
access
to
folks,
who
are
a
little
bit
a
little
bit
closer
to
the
code
and
and
talk
about
some
of
some
of
this
a
little
bit
in
more
detail.
That.
B
D
Or
or
whichever
I
just
mentioned,
that
because
I
brought
this
up
on
the
attack
a
couple
months
ago
and
the
I
didn't
get
much
much
engagement,
I
assume!
That's
because
folks
capacities
are
full
there,
so
I
wonder
if
we
got
to
a
TSC,
we
might
have
more
luck
in
finding
folks
who
had
had
available
capacity.
I.
B
B
I
think
you
know
I
know
you
know
we
can
also
kind
of
help.
Will
really
you
know,
get
some
interest.
I
mean
from
my
perspective
on
these
things,
the
heart,
the
the
even
though
it
sounds
terribly,
the
easiest
thing
is
to
get
writing
support.
You
know
because
either
you
know
we
have.
You
know
marketing
folks
on
our
side
that
can
help
with
writing.
We
have
resources
that
can
help
with
ad.
The
hard
thing
is
the
SME
support.
B
So
if
we
can
find
ways
to
at
least
Leverage
The
smes
in
such
a
way
that,
like
we
can
Garner
that
insight
and
then
we
can
kind
of
help
work
to
tell
the
story
and
things
around
it,
I
think
that
would
be
best
and
if
you
all
sort
of
have
a
I,
don't
know
it
sounds
like
from
what
we're
creating
here.
It's
not
necessarily
of
the
template
that
we
viewed.
E
Mean
the
important
thing
is
that
we
get
the
content
and
then
it's
just
a
matter
of
formatting,
right
and
organization.
So
you
know
we
start
with
getting
that
that
Google
doc
fleshed
out
and
then
we
can
figure
out
what
to
do
with
it.
So
I
think
and
I
think
there's
again,
there's
two
things
there,
which
is
you
know
kind
of
this
over
where
I
just
lost
this
stupid
thing
again
there
it
is,
there's
the
you
know,
I
think
Terry
made
a
great
suggestion
about.
E
You
know
having
something:
that's
in
our
learn
hierarchy
and
then
you
know
maybe
start
to
identify
some
potential
for
the
community,
the
project
contributions
or
the
you
know
the
implementation
contributions,
and
then
we
can
have
like
a
you
know,
a
secondary
that
you
know
takes
all
of
those
chunks
puts
them
together
to
the
white
paper
for
for
the
plane
ride
for
Fati,
and
that's
that's
just
a
matter
of
you
know:
content
work,
okay,
so
and
John
you're,
you're,
gonna,
try
and
dig
that
up
for
me.
B
Yeah
I
will
look
here
in
the
background.
I
should
be
able
to
I
should
be
able
to
hook
you
up
there.
E
Okay,
all.
D
Right
I'm
also,
if
you
have
those
on
calls,
John
I,
have
capacity
to
join
those
and
help
with
positioning
I
also
have
capacity
to
help
with
the
SME
bit
somewhat
I
can
make
that
happen.
I
just
don't
have
the
capacity
to
write
the
whole
white
paper,
yeah
I.
E
B
B
C
I'm
trying
to
manage
here
is
the
overall
amount
of
effort,
because
if
we,
if
we're
going
to
explain
continuous
delivery
in
the
context
of
Mainframe
well,
first
you've
got
to
explain
continuous
delivery.
C
So
if
we're
going
to
host
that,
then
that
part
needs
to
be
in
line
with
the
best
practices
that
we're
publishing.
So
what
I'm
trying
to
avoid
is
a
situation
where
we
write
a
white
paper
about
continuous
delivery
and
then
have
to
go
through
and
spend
two
or
three
months.
Editing
it
to
make
it
a
line
to
to
best
practice
is
if
actually,
all
we
really
need
to
do
is
focus
in
on.
C
What's
what's
the
really
important
stuff
for
Mainframe,
and
then
we
can
think
about
how
we
potentially
do
an
export
of
our
overarching
information
package
to
to
give
that
view
of
what
our
best
practices
methodology
is,
plus
how
that
has
implications
on
Mainframe,
because
that
should
be
a
you
know.
A
lot
smaller
chunk
to
bite
off,
as
if
we
just
focus
on
the
the
Mainframe
bit.
E
Under
learn,
we
have
a
category
we
haven't
fleshed
out
yet,
which
is
the
domain
specific
practices?
I,
don't
know
Michael
if
you've
had
a
chance
to
kind
of
go
through
some
of
that
content.
Here
it's
let
me
drop
the
link,
notes.
E
E
E
You
know
any
sort
of
Mainframe,
specific
things
or
or
maybe
it'll
be
an
opportunity
to
do
a
hybrid
discussion
of
which
Mainframe
would
would
be
able
to
benefit
from
depending
on
how
we
want
to
label
it,
and
then
the
white
paper
could
basically
be
a
dump
of
all
the
content
into
a
single
document
that
we
could
PDF
right.
So
something
like
that.
C
Yeah
and
you
know
from
our
perspective,
usually
those
those
sub
sections
are
typically
one
to
two
hours
worth
of
work
and
a
little
bit
of
review.
So
it's
it's.
It's
not
a
major
piece
of
writing
and
editing
work.
It's
it's!
A
very
straightforward
couple
of
smes,
giving
a
brain
dump
in
in
that
section.
So.
E
All
right,
okay,
so
we
have
some
preliminary
action
items.
D
C
E
E
Okay,
we
hit
the
30
minute
Mark,
we
have
some
action
items
for
Mainframe.
Is
there
any
lingering
any
any
lingering
things
that
we
want
to
make
sure
to
touch
on,
because
otherwise
I
want
to
make
sure
we
have
a
chance
to
to
talk
translations.
B
B
All
kind
of
helping
get
this
back
on
the
agenda
here
definitely
excited
to
work
with
you
all
and
drive
this
yeah.
E
It's
I
apologize,
poor
Terry
has
been
kind
of
carrying
the
load
a
bit
so
I'm,
trying
to
step
back
up
and
provide
more
more
help
here.
E
Yeah,
let's,
let's
plan
on
touching,
let's,
let's
plan
on
getting
some
engagement
with
the
open,
Mainframe
project
sleeping
gets
more
solicitation
for
resources
in
touch
base
next
time,
or
maybe
maybe
a
month
out,
if
we
think
given
everybody's
schedules.
Maybe
two
weeks
is
too
fast
to
report
back
on
this,
but
let's
plan
on
within
the
next
month,
seeing
if
we
can
identify
some
contributors.
E
D
Sorry
perfect,
thank
you
and
then,
if
we're
all
done
with
Mainframe
I
think
I'll
I'll
drop
off
the
line.
Then.
E
B
B
The
got
the
whole
Old
Mac
collection,
going
on
all
100
working
too.
B
E
D
The
one
on
the
one
on
our
left
here,
right
that
was
in
our
lab
in
high
school,
it's
called
the
Mac
lab-
is.
D
B
E
E
Lovely
to
meet
you
I
see,
we
also
have
Oscar
and
Victor.
Okay,
so
I
want
to
make
sure
everybody.
So
we
have
the
branch.
Currently,
the
l10n
branch
for
localization
I
wanted
to
make
sure
everybody
had
had
a
chance
to
clone
that
and
if
you
were
able
to
start
playing
around
with
it
I
again,
I
was
struggling
with
that
toml
file
and
in
my
local
attempts
to
run
a
local
Hugo
server,
I
wasn't
seeing
the
I
have
that
test
Spanish
about
page
that
I
put
in
there
and
I
wasn't
seeing
it
accessible.
G
Yeah
on
my
side,
I
I
was
the
and
I
try
to
set
up
the
on
my
local
local
laptops
on
my
local
computer
and
so
far
is
not
working
actually
I'm,
trying
to
figure
out
what
what
happened.
Looks
like
it's,
like
a
configuration
and
also
I
use
this
this
issue
to
document
how
to
set
up
how
to
onboard
when
you
try
to
to
contribute
on
the
on
the
transmission
so
on
this
on
this
website.
G
If
you
need
to
contribute
so
undocumented,
and
maybe
I'm
gonna
create
one
one
page
to
explain
how
to
set
up
your
computer
and
how
to
onboard
it
and
I
got
two
people
to
contribute
on
it
in
French,
but
last
week
I
launched
them,
but
there
is
no
reply,
so
I'm
gonna
try
to
oh.
E
E
With
with
your
updates,
because
that
would
be
fabulous
if
there's
if
this
is
insufficient
or
has
inaccuracies
for
for
getting
started
with
the
platform
yeah.
E
I
found
and
and
to
be,
and
just
to
be
fair
like
for
me,
I'm,
not
sure
what
Terry,
which
system
that
you're
using
I
found
the
most
success,
doing
the
Hugo
server
version
of
it,
but
there's
like
three
different
ways
that
you
can
do
this
and
different
people
have
have
done
different
things
with
it.
So
it's
like
Pearl,
you
know
there's
more
than
one
way
to
do.
It.
C
Yeah,
so
we
we
need
to
make
sure
that
we're
on
roughly
similar
versions
of
Hugo
and
Doxie,
because
there
are
some
incompatibilities
so
I'm,
not
sure
how
the
the
docker
image
is
being
created
and
whether
we're
keeping
it
in
sync
with.
E
E
Okay,
yeah
I,
haven't
I,
haven't
taken
a
pic
peek
at
that,
okay,
so
yeah.
Let
me
see
if
you
could
take
a
peek
and
and
then
you
know
feel
free
to
open
PRS
against
that
document
for
any
additions.
That
would
be
super
helpful,
Oscar
and
Victor.
How
are
you
all
going
with
your
setup.
E
F
But
I
had
a
lot
of
the
idea
of
the
continuous
contributes
to
the
Spanish
translation
in
every
repo
on
in
every
project.
I
think
in
we
need
I
love
this
information.
They
continue
delivering
foundation
in
Spanish
and
we
need
this
information
yes
and
I
can
help
and
compelling
the
processes.
It
relates.
E
E
And
and
if
you
want
to
go
ahead
and
put
any
changes
to
that
contribution
guide
in
the
same
Branch,
we
can
just
all
work
in
that
branch
and
and
then
start
merging
things
over
as
we
as
we
get
to
good
points
and
I
I
have
limited
availability
but
I
try
and
check
the
channel
a
couple
times
a
week
and
I'll
try
to
be
better
about
it
and
I
know.
Terry
keeps
an
eye
on
it
periodically.
So
we'll
try
and
get
questions
answered
as
you're
progressing
Victor.
H
Setting
up
I
have
been
tried
so
actually,
because
I
I
was
working
on
the
translation
of
the
cncs,
the
the
Distributing
model,
how
the
translation
work
as
well
as
well,
and
then
they
actually
have
a
way
to
have
a
separate
language.
You
can
add,
like
a
language
module
and
then
clone
clone
a
language
module
and
merge
back
all
from
GitHub
itself.
I
can
post
that
link.
How
is
that
down?
H
There
I
think
that
might
be
it's
using
and
I'll
post
that
in
there
easy
way
to
to
merge
the
changes.
E
E
C
E
So
in
Victor,
what
language
are
you
representing.
E
A
Like
once
this,
you
know
way
of
working
settles,
I
will
give
a
try
to
Turkish,
because
turkey
is
a
bit
lagging
behind,
so
it
comes
continuous
delivery.
So
I
am
also
going
to
contribute
I'm
just
observing
to
learn.
G
E
G
Time
I
saw
on
the
I
saw
on
the
the
depot,
the
slash
es
for
the
Spanish.
Is
it
the
way
to
male
translation,
so
just
create
a
new
repository?
Stop
for
that
and
put
the
language
inside
there
or
put
all
the
other
signs.
Are
there
so.
E
That
was
that
was
the
the
formatting
that
I
was
following
based
on
the
the
doxy
documentation,
and
you
know
setting
up
the
config
Como
and
all
that,
but,
like
I
said
it
still
struggling
a
little
bit
to
get
to
to
get
it
to
where
I
think
it's
working.
The
way
we
expect,
but
it
sounds
like
Victor
may
have
another
option
that
he'd
like
us
to
investigate
which
I
am
totally
open
to.
So,
if
there's
there's
things
that
you've
done,
that,
like
hey
doing
it,
this
way
is
going
to
make
it
really
simple.
E
G
F
E
F
D
E
H
E
H
Have
posted
the
the
GitHub
issue
at
least
relates
to
how
it
was
done
in
that
right
now,
it's
only
German
I,
already
I
already,
actually
posted
the
the
same
thing,
so,
basically
that
after
cloning
with
this
setup
after
cloning,
the
the
original
repo
you'll
be
able
to
just
make
a
few
changes,
and
you
get
a
create
a
subdirectory
for
your
language,
and
this.
H
You
don't
have
to
one
is
being
committed.
It
can
be
the
whole
thing
back
into
the
main
branch.
This
way,
it's
it's
a
lot
easier
to
merge
different
languages
into
the
original
module,
no
need
to
make
the
change
to
the
to
the
original
English
version
yeah.
So
so
this
way
it's
a
okay.
C
Yeah
so
so
you
have
there's
only
a
single
language
in
here
at
the
moment,
which
is
English.
H
Well
already
merges
German
I
did
English
Chinese
already,
but
not
not
merged.
Yet.
E
Yeah
I
mean
I
think
that
this
looks
very
similar
to
what
we
were
trying
to
do.
As
far
as
the
the
language
definitions,
the
the
thing
that
for
me
that
wasn't
working
was
once
I
was
running
the
the
site
locally.
On
my
laptop,
you
know,
I
couldn't
find
any
any
anchor
that
allowed
me
to
switch
the
localization
so
like
for.
E
E
C
E
Whatever
the
top
leading
is,
which
should
be
English
right,
okay,
so
that
was
just
me
misunderstanding
whatever
that
documentation
was
that
I
was
reading.
Okay,
so
I
can
go
test
that
and
make
sure
that
that's
no
I
can't,
because
that's
all
on
my
workstation,
that's
at
home,
all
right
I'll
have
to
set
up
a
new
environment
on
this
laptop.
E
Okay,
all
right
so
y'all
are
going
to
continue
working
on
getting
setups,
we'll
update
the
Contra,
the
contributor's
guide
as
necessary.
I
always
set
up
my
local
environment
yeah.
Let's
get
some
get,
some
files
landed
and
we
can
check
back
in
a
couple
of
weeks.
H
Yeah
so
the
way
that
that
group
done
at
least
that
I
did
it
that
way
is
there's
no
need
to
set
up
anything.
My
laptop
I,
just
I,
just
GitHub,
make
a
clone
and
make
changes
and
merge
back
all
these
in
the
GitHub.
E
Okay,
well,
I
I.
Definitely
I
think
we
want
to
be
able
to
do
both.
C
Yeah,
so
so
the
only
what
you
need
the
local
set
up
for
is
so
that
you
can
actually
test
in
the
in
the
Hugo
environment.
On
your
laptop,
you
can
see
what
it's
actually
rendering
as
yeah
you
can.
You
can
edit
and
push
that
push
dust
but
I
think
and
you
you
can
obviously
then
look
at
the
look
at
a
PR
and
and
check
the
pr
version
to
just
to
see
if
the
preview
is
rendering
correct.
C
But
it's
just
that
little
bit
easier
to
be
able
to
do
it
live
on
your
local
machine.
So
as
you're
editing,
you
can
see
the
changes
in
the
browser
locally.
E
And
I
think
you
know
once
we
have
more
of
the
stuff
in
place
Victor,
your
your
suggestion
will
become
that
much
more
useful
because
it
won't
require
the
overhead
but
I
suspect.
There's,
probably
some.
You
know,
since
we're
just
getting
going
being
able
to
make
sure
we
can
test
everything
locally
before
the
merges
happen
is
going
to
be
super
helpful.
C
I
I
suspect,
we'll
probably
hit
some
rendering
problems
where
we're
working
in
languages
that
are
in
a
different
rendering
sequence
to
to
the
English.
We've
got
so
far
so
yeah
so
I
expect
we
might
get
some
layout
bugs.
E
F
E
E
Okay,
so
check
status.
The
docker
container
review
contributor
guide
for
correctness
update,
is
necessary,
then
confirm
for
local
testing
that
localizations
with
browser
setting
updates
work
right.
Any
other
thing
that
are
our
localizers
need.