►
From YouTube: 2021 01 21 Docs Office Hours
Description
Jenkins Documentation Office Hours Jan 21, 2021
A
Welcome
to
google
or
google
to
jenkins
documentation
office
hours,
it's
the
21st
of
january
2021.,
thanks
for
being
here.
Let's,
let's
go
ahead
and
talk
to
the
topics,
so
I
wanted
to
solicit
comments
on
a
proposal
I
just
created
for
a
jenkins
contributor
summit,
and
so
that
was
when
I
would
love
to
invite
kristin
you
and
xena
both
to
comment
on
it
to
give
me
insights,
to
suggest
ideas,
etc.
A
A
A
C
A
A
A
contributor
summit
is
an
event
that
we've
held
once
a
year
to
encourage
people
to
contribute
to
jenkins
to
meet
together
to
talk
about
what
jenkins
should
be
doing
in
the
coming
year.
We
used
to
do
it
regularly
at
fosdem
an
open
source
conference
in
belgium,
but
that
conference
will
be
all
online
this
year,
so
instead
we're
going
to
do
this
as
an
online
event.
A
The
idea
is
we'll
take
three
days,
we'll
start
with
a
combined
everyone
in
the
session
90
minute
session
on
day.
One
identify
the
topics
during
that
90
minute
session
and
who
the
session
leaders
are
for
the
set
the
topic
sessions
and
then,
during
the
next
two
days,
we
will
have
subsets
of
the
group
meet
for
topic.
Specific
discussions
then
gather
everyone
back
together
for
a
a
full
group
session
to
hear
the
summary
of
what
happened
so
start
together.
A
A
C
A
B
A
It
is
it's
trying
to
invite
every
sig
and
jenkins
to
every
sig
and
every
basically
everything
it
starts
with
officers.
So
the
security
officer,
the
security
topic
infrastructure
and
releases
then
goes
into
sigs,
and
what
we'd
like
to
do
is
invite
all
of
them
to
come
now,
some
of
them
some
of
them,
may
not
be
there.
You
know
this
will
be
based
on
who's,
interested
and
who's,
not
sure,
but.
A
D
A
A
If
you've
got
experiences
in
your
work,
scheduling
the
she
code
af
she
codes
africa
sessions.
I
would
love
to
get
insights
on
hey.
How
do
you
schedule
groups
effectively
so
that
they
actually
meet
successfully
etc?
I
put
some
ideas
in
that
document,
but
I
have
relatively
little
experience
doing
that.
Well,
so
we'd
love
your
insights.
A
All
right
so
then,
let's
talk
about
pull,
request
progress
so
now
it's
time
for
the
embarrassment
phase,
where
I
haven't
reviewed
a
pull
request.
That's
been
opened
for
two
weeks
and
that's
terrible
sorry
about
that
zenob.
Thank
you
very
much
for
creating
it,
so
images
and
text
ready
to
go
ready
for
a
way
to
show.
Oh,
this
looks
looks
like
great
work.
Thank
you.
A
C
C
A
A
Asked
he
asked
a
very
good
question
or
made
a
very
keen
observation.
His
his
question
was
hey
mark.
Is
there
any
work
to
make
the
jenkins
documentation
more
structured
and
more
organized
than
than
the
current
collection
of
things
that
are
starting
to
adopt
it's
starting
to
feel
more
disorganized
than
it
was
two
years
ago,
for
instance,
what's
happening
is
new
content
is
arriving,
but
at
an
uneven
pace.
A
A
C
A
Well,
and-
and
this
one
I
think
I
think
office
hours
here-
this
session
is
perfect,
because
hearing
hearing
kristen
from
you
and
from
zenob
on
hey
these
ideas
work
well
together.
No,
these
not
so
much.
That's
that's
a
great
way
for
us
to
collaborate
and
identify
okay,
which
things
are
more
interesting
or
which
are
less
so.
How
about
we
take
the
following
mark
to
start
something
and
share
with
others
for
more.
A
Right
right
well!
Well,
because
I
had
as
an
example,
I
had
a
flawed
concept
that
oh,
we
should
split
the
documentation
into
user
guide
and
admin
guide,
but
now
that
I've
looked
at
it
after
two
years,
I
think
I've
realized.
I
can't
tell
the
difference
between
user
guide
and
admin
guide,
and
I
look
at
the
freebsd
handbook
and
they
have
only
one
it's
for
users
and
admins
and
so
we're
and
we're
modeled
after
that.
A
C
A
C
A
A
A
Super
now
the
next
topic
was:
we
know
that
there's
a
big
gap
for
kubernetes
documentation
still
right.
There's
the
the
world
can't
get
enough
of
kubernetes
documentation
in
general,
there's
just
so
much
so
much
of
interesting
happening
in
that
space
with
openshift
and
with
various
kubernetes
releases
and
the
transition
from
using
official
docker
images
to
using
container
images
that
are
docker
compatible,
but
not
necessarily
generated
by
docker.
You
know
all
sorts
of
interesting
things
there
xena
are
there
specific
areas
where
you
say
ooh.
B
A
I
like
that,
I
like
that
a
lot
so
more
advanced
use
cases
are,
are
very
interesting
right
and,
and
they
certainly
are,
we-
we
know
that
there
there
are
people
who
are
looking
for
those.
You
cited
that
very
good
example
of
the
user,
who
said
hey
that
the
initial
documentation
is
great,
but
it's
mini
cube.
Centered
and
most
most
production
installations
will
be
using
something
much
bigger
than
minicube.
A
C
B
So
you're
right
because
I
actually
had
to
reply
to
it-
and
I
just
made
mention
that
considering
the
fact
that
we
didn't
have
any
content
on
jenkins
on
kubernetes
before
it
made
sense
to
actually
start
from
the
basics,
then
go
right
up
to
more
advanced
content
and
that's
why
it's
that
way.
But
obviously
it's
in
changes.
Documentation,
roadmap
to
have
more
advanced
content
as
time
goes
on.
A
A
Are
there
other
things
like
that,
for
instance,
I
don't
know
is
it
is
one
scaling
decisions
when
to
split
and
when
to
and
when
to
combine
and-
and
that's
not
really-
that's
not
really
kubernetes
specific,
even
that's
more
of
hey.
When
is
your
jenkins
controller,
so
big
that
you
should
split
it
out,
kristin,
any
other
insights,
you
could
offer
there
on
likely
hot
topic
areas.
A
C
C
B
In
particular,
the
only
observation
he
mentioned
was
that
it's,
the
documentation
was
mostly
centered
on
using
mini
cube,
yeah,
exactly
which
would
obviously
be
used
in
a
production
environment.
So
I
think
the
solution
to
that
treat
would
be
probably
releasing
an
alternative
to
miniature
production
environment.
C
So
this
be
a
good
case
for
building
out
more
of
those
solution
pages
so
like.
I
know
that
this
is
working
on
the
amazon.
Yes,
it's
like.
Oh
here's
like
getting
started
and
then
great
now
that
you
see
how
it
works.
You,
like
the
basics
here,
here's
how
to
get
it.
You
know:
here's
the
amazon
page,
like
here's,
google,
here's
openshift
just
like
anything,
we're
just
kind
of
continue
to
work
down
or.
A
C
Yeah,
like
just
in
case,
there's
anything
like
a
gotcha
or
unit
for
each
of
the
environments,
because
right,
like
the
basics
of
the
kubernetes,
like
how
kubernetes
works,
it's
going
to
be
the
same
everywhere,
but
it's
like.
Oh
here
are
some
tweaks
that
we
had
here
like
something,
and
especially
this
is
a
good
chance
to
get
from
experts,
and
you
know,
people
in
the
community
who
are
using
it
in
these
environments
to
chime
in.
A
C
A
That,
well
I
I
so
hey,
we've
we've
actually
got
when
we
have
entry
pages
like
that.
We've
got
this
thing
that
it's
not
terribly
well
highlighted,
but,
for
instance,
if
I
look
at
the
installing
jenkins
page
and
let's
look
at
kubernetes,
if
I
jump
to
the
bottom
of
this
page,
there's
the
improve
this
page
link.
A
C
A
Yeah,
okay,
very
good,
so
I
love
you
saying
that
zena!
Thank
you!
That
was
excellent.
How
did
you
get
there?
Okay,
so
what
I
did
was
I
went
to
the
the
installing
kubernetes
page
right.
So
here
here
is
one
of
our
pages
and
it
could
be
any
page,
but
one
of
our
pages-
and
if
I
go
to
the
very
bottom
of
the
page.
A
A
If
I
remember
right,
there
are
some
some
hidden
complexities
in
the
in
in
this
particular
one,
because
we've
got
some
reusable
content
that
we're
doing
right
here,
right,
we're
doing
content,
reuse
and
because
we're
doing
content
reuse,
they
may
say.
Oh,
I
didn't
find
the
page.
I
wanted,
because
it's
inside
the
reused
content
so
but
but
nonetheless
there
is
something
to
be
said
for
hey,
if
you
just
actually,
maybe
that
maybe
I
just
described
it.
A
A
A
A
B
D
B
I
said
this
now
and
at
least
from
all
these
mapped
outs.
I
I
kind
of
like
have
it
already
to
find
out
more
what
content
should
be
useful
in
the
documentation,
then
also,
I
think
the
solution
page
also
would
really
help
with
this
because
checking
existing
solution
pages,
I
could
see
that
there
are
also
links
to
other
resources
outside
jenkins
documentation
that
could
help
users
without
also
including
something
we
could
use
to.
A
A
A
A
B
A
Okay,
next
topic
was
jenkins
roadmap
and
I
wanted
to
take
a
quick
look.
It's
been
a
while,
since
I've
looked
at
the
docs
roadmap-
and
I
I'm
it's
embarrassing
to
admit
that
it's
been
a
while
since
I've
looked,
but
if
we
look
at
so
jenkins
on
kubernetes
is
current
project
admin
guide,
overhaul
user
guide
improvements
and
solution
pages.
Okay,
so
we've
talked
about
all
those
topics,
good
all
right.
So
that's
really
good.
A
A
A
A
A
A
A
A
Let's
see
so,
the
the
the
other
parts
of
that
plan
are
when
do
we
migrate
and
turn
the
thing
off
and
and
that
I'm
less
concerned
about,
because
it
it's
a
lot
of
work
to
turn
it
off
and
make
sure
that
everything
redirects
correctly
and
not
a
lot
of
gain,
because
we
don't
actually
spend
that
much
energy
maintaining
this
server.
So
it's
cheap
to
maintain
right
now
and
expensive
to
stop.
A
B
That
pretty
much
explains
the
steps
and
probably
links
to
this
good
map
for
people
to
be
able
to
see
okay.
This
is
what
we're
currently
doing
in
the
presentation.
This
is
where
we
have
plans
what
these
are
things
we
need
to
achieve,
because
it's
also
very
important
to
try
and
have
this
information,
if
not
in
one
place,
but
in
close
proximity.
So
whoever
wants
to
contribute
to
the
documentation
can
easily
get
all
the
information
they
need
without
getting
discouraged
from
having
to
look
around
and
try
and
find
their
way.
B
A
Good,
okay,
good
point
yeah,
so
so,
let's
I
mean
we,
we
certainly
know
one
of
the
experiences
from
your
experience.
Cnob
was
that
contributing
to
documentation
is
not
as
fluid
for
a
windows
user.
It
just
isn't.
We
need
to
improve
that,
and
so
that's
that's
a
good
one
for
us.
Let's
go
to,
we
do
have.
A
We
do
have
the
participate
page
here.
That
is
the
our
entry
point.
Oh
whoops
participate.
It
would
help
if
I
could
spell
correctly
there.
So
so
this
page
has
document
on
it,
and
this
takes
us
here.
However,
I
suspect
there
are
still
well,
for
instance,
featured
projects
probably
needs
an
update.
Newcomers
likely
needs
more.
I
bet
that
this
takes
us
to
oh,
no
good.
It
does
take
us
to
github
not
to
the
wake
wiki
that
or
not
to
the
jira
site.
A
So
good
insight
we
need
to,
we
need
to
improve
and-
and
that's
actually
part
of
the
part
of
one
of
the
things
that
the
jenkins
governing
board
has
expressed
concern
about
in
their
most
recent
meeting
was:
let's
improve
the
new
contributor
experience
now,
z,
knob
you
mentioned
you
mentioned
what
tasks
might
a
new
contributor
take
is?
Would
you
be
willing
to
test
drive
with
your
eyes
to
see
if,
if
this
material
is
a
good
recommendation
of
things
they
might
take
or
is.
B
Sure
I
won't
so
I
think
one
thing
that
I
really
need
to
add
to
the
contributor
talk
is
how
to
actually
set
up
jenkinson,
because
I'm
not
really
sure
that
information
is
really
explicit
anyway.
It
shows
how
to
on,
I
think
when
you
read
me
file
or
something
and
github,
it
shows
how
to
run
macron
and
all
that,
but
it
doesn't
really
go
explicitly
into
details
as
to
how
to
set
it
up
and
all
that,
if
you
don't
have
it.
A
A
A
So
there's
windows
users,
I
think
of
others
like
me:
freebsd
users
or
mac
os
users
or
the
and
and
some
of
those.
The
answer
may
just
be
sorry.
You
can't
do
that
because,
right
now
it
uses
a.
If
I
remember
right,
we
use
a
docker
image
and
that
works
for
windows
and
it
works
for
linux,
but
it
won't
work
for
these
others.