►
From YouTube: 2020 10 12 GSoD Office Hours
Description
Google Season of Docs office hours from OCt 12, 2020 for the Jenkins on Kubernetes documentation project. Topics included pull request review, example placement, and documentation structure.
A
B
A
A
A
C
Okay,
it's
for
reference,
so
say,
for
instance,
section
those
sections
where
I
the
contents
of
this
copy.
This
content
put
it
in
a
file.
We
just
add
a
link
to
that
particular
file
on
jenkins.io,
so
they
can
actually
see
what
the
structure
looks
like
what
the
yaml
file
looks
like
exactly
because
for
some
issues
for
some
people
there
might
be
issues
with
copy
and
paste
and
all
that
right.
A
D
D
B
A
A
A
A
A
A
A
C
A
C
A
A
A
And-
and
that's
that's
fine
for
something
that
fits
on
my
screen.
But
now,
if
we
look
at
at
the
example
here,
this
does
not
fit
on
my
screen
and
the
odds
are
that
I'm
going
to
make
some
mistake,
like
I
just
did
now
and
miss
the
first
character
or
the
last
character
so
like
okay
is.
Is
that
the
the
concern?
Then?
A
A
What
what
if
we,
I
wonder,
what
if
we
tried
putting
it
as
a
separate
file
here
separate
file
and
then
import
it
into
this,
so
that
so
that
we
would
only
have
one
copy
of
the
data
and
we
could
point
them
to
the
file
in
the
in
the
jenkins.io
actual
source
tree.
Would
that
be
okay?
I
I
guess
marky
and
kristen,
give
me
your
opinions
on
what
do
you
think
is
best
for
the
reader
of
this?
B
B
A
B
You
just
make
a
what
we
also
do
in
kubernetes
is
and
spinnaker
is,
we
will
say,
we'll
put
a
little
blurp
in
the
dock.
That
says
this
is
the
link
to
this
code
like
you're,
letting
them
know,
as
opposed
to
because
sometimes
they'll
miss
the
hyper
they'll
miss
the
link
as
well,
and
then
they'll
still
ask
the
question
like
where's
this
code.
B
A
A
Repository
and
I
assume
that
these
things
don't
make
sense
to
place
them
inside
the
jenkins
hamilt
or
the
jenkins
chart
repository
right.
These
are
really
examples
that
we
need
to
be
able
to
edit
and
modify
more
frequently
than
we
would
want
to
modify.
The
chart
itself
is.
Is
that
a
safe
assumption.
B
A
A
A
And
that
that
seems
perfectly
reasonable
to
me.
I
don't
see
any
other
obvious
place
where
I'd
say.
Oh
no,
okay,
let's
see
no,
that's
yeah!
I
don't
see
anything
else,
obvious
right,
say
ooh.
This
looks
like
a
place
where
we've
done
examples
elsewhere,
so
it
was
tutorials,
doc,
tutorials
and
then
a
subdirectory
of
that.
A
D
A
Yes
right
well,
and
in
fact
that's
that's
a
very
good
point
kristen,
because
in
reviewing
the
install
materials
there
are
times
when
in
order
to
indent
things
in
terms
of
a
numbered
list,
or
something
like
that,
we
end
up
using
leading
spaces.
But
leading
spaces
can
be
significant
in
these
yaml
files.
A
A
I
couldn't
couldn't
this
also
be
done
as
a
subsequent
pull
request.
I
mean
we
could
take
yeah.
I
at
least
I
don't
object
to
a
to
this,
not
being
yet,
but
we
get
the
if,
if
the
second
pr
is
ready
to
merge
and
the
first
pr
is
ready
to
merge,
I
don't
think
that
this
change
needs
to
happen
inside
either
of
those.
Unless
there's
something
xenophobia,
you'd
say:
oh,
no,
this
pr
will
be
the
second
one
will
be
much
better
if
we
do
this,
I'm
okay
with
that
being
a
later.
A
A
D
Right
so
I
think
we
might
have
already
covered
a
lot
of
this,
because
I
was
kind
of
wondering
what
we
were
planning
on
doing
with
the
order
of
the
pr's
or
like
making
sure
they
have
enough
reviews,
and
when
we
were
going
to
deliver,
I
the
other.
I
guess
the
other
point
that
I
had
was
about
the
yeah
that
was
kind
of,
but
it
kind
of
been
answered,
which
is
good.
I'm
very
happy
about
that.
I
guess
the
other.
The
last
remaining
outstanding
question
in
this
section
would
be
about
the
blog
post.
D
So
I
know
for
the
google
summer
of
code
each
coding
phase
that
we
required
them
to
have
a
blog
post
kind
of
about
what
happened.
I
don't
know
if
this
was
something
that
I
it.
This
is
a
completely
different.
You
know
program
where
it's
just.
It
takes
a
lot
longer
and
we're
already
doing
a
lot
of
writing.
But
I
didn't
know
if
there
was
also
some
if
we
were
gonna
do
some
requirement
or
like
talk
about
where
this
is
so
bad
that
it's
like,
where
x
number
of
weeks
in
or
like
something
it's
like
done.
D
These
different
sessions
we've
been
doing
this,
it's
kind
of
like
an
awareness
for
what's
been
happening.
I
I
don't
know
I
don't
know
this
might
be
a
thing
here.
We
throw
it
out
to
everybody,
see
if
it
makes
sense,
if
it's
too
much
more
writing
or
like
extra
work,
maybe
not,
and
then
we
just
continue
on,
but
I
didn't
know
if
it
was
a
good
chance
to
give
a
highlight
of
the
awesome
works.
You
know
that
you've
been
doing
and
also
to
maybe
get
some
extra
eyes.
D
D
A
And
it
was
just
a
link
to
the
new
install
guide:
hey
here.
It
is
kubernetes
or
or
we
if
we
can
stand
an
extra
day
or
two
before
the
blog
post.
We
refactor,
we
rework
the
install
page
to
use.
So
I
reworked
the
install
page
or
marquee
reworks
it.
Somebody
reworks
the
install
page
and
we
get
it
restructured
so
that
she
can
point
to
the
new
page
and
it
points
to
the
restructure
page
and
says:
hey
we've
made
it
easier
to
read
simpler
and
it's
got
kubernetes
in
it.
D
A
Great
okay!
So,
let's,
if,
if
everybody
is
okay,
I'm
going
to
take
that
that
action
item
work
on
the
restructuring
with
the
doc
sig
thinking
about
my
schedule,
I'm
doing
a
webinar
on
wednesday.
So
it
may
not
be
till
wednesday
that
I
get
I
get
at
this.
Is
that
okay
with
everybody,
or
is
that
too
too
long
a
delay?
And
we
need
it
sooner
than
that,
so
it
would
be
like
potentially
thursday
we'd
review
it
in
our
in
our
session.
D
A
D
F
B
B
C
C
B
I
also
wanted
to
add
one
other
thing
to
the
agenda
that
I
completely
forgot
and
I
am
going
to
wait
till
you're
done
typing
and
then
I
will
say
it
in
the
meantime.
I'm
also
going
to
ping
somebody
I'm
set
go
ahead:
the
transfer
of
org
admin
and
mentor
that
has
not
been
done
yet.
I'm
pinging
oleg,
I
kind
of
forgot
about
it
last
week
because
of
cd
con.