►
From YouTube: 2021 03 01 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
welcome
to
jenkins
documentation
office
hours.
So
here
we
are
topics
that
I
had
on.
My
agenda
were
see
any
action
items
we
had
from
the
past.
No
okay,
good,
so
topics
I
had
included
site
search
for
plugins.jenkins.io
status,
report,
site,
search
for
jenkins.io,
documentation,
site.
A
Jenkins
contributor
summit,
just
a
bunch
of
action
items
there,
google
season
of
docs
there
we
need
to,
I
think,
determine
some
action
items
and
google
summer
of
code
anything
else
to
put
on
the
list.
Meg.
A
Good,
let's
put
it
on
the
list
so,
and
so,
let's,
let's
put
chico
africa,
contribute
on
how
about
and
then
we'll
talk
about
both
sponsorship
contribution,
sponsorship
and
and
project
ideas,
because
we
need
both
project
ideas,
mentors,
okay,
good,
all
right.
Let's
move
that
one
up
high,
because
that
one
is
is
good
to
have
and
much
of
less
about
status
and
more
about
what
we
need.
Okay,
anything.
B
Else,
that's
good
for
me.
A
All
right,
so
she
could
africa
contribute
on
it's
coming
in
april
and
sponsorship.
A
B
B
A
So
I
haven't
had
any
response
from
jim,
yet
alex
said:
yes,
he
would
go
ahead
and
ask,
and,
and
if
you're
aware
of
others
who
are
in
the
community,
that
might
be
might
be
worth
asking
them
to
ask
their
employers.
I
think
it's
worth
worth
us
considering
further.
B
A
Pipeline
examples
all
right,
pipeline
documentation
pipeline.
Let's
see
how
would
we
say
pipeline
argument,
help
slash
step
help
for
specific
plugins.
A
B
A
A
B
A
A
Oh,
that's,
that's
a
good
one.
Actually,
let's
take
that
one
friendly
issues.
A
B
A
So
the
it's
a
an
interesting
combination
of
if
they
don't
get
funding,
they
of
course
can't
pay
these
these
people
to
these
women
to
do
coding
and
part
of
the
crucial
exercise
here
is
they
they
are
paid
for
that
month
to
do
it.
B
A
B
A
Right,
right
and
and
that's
my
suspicion
is,
this
is
probably
very,
very
reasonable
rates.
That's
my
assumption.
B
B
B
And
people
who
would
like
to
mentor
you
get.
A
B
A
D
A
You
will
so
I'm
going
to
I'm
going
to
include
it
actually
in
this
recording.
So
let's
put
here
is
the
jenkins
plugin
site.
So
when
I
look
at
the
plugin
site,
it
has
a
browse
button
on
the
left
and
a
search
button
on
the
right
for
plugins.
If
I
browse
you'll
notice,
it
brings
up
the
list
of
all
1
800
plugins
and
a
search
by
algolia
icon.
E
A
Or
maybe
a
strategy
and
this
one's
a
nice
highlight
that
basic
build
strategies
build
basic
branch.
Build
strategies
is
not
the
word
strategy,
but
the
algolia
search
engine
knows
that
strategy
and
strategies
are
synonyms
for
each
other
wow.
So
very,
very
nice
yeah
and
it's
it
is.
It
is
every
bit
as
fast
as
it
was
before
and
it
supports
all
of
the
layouts.
You
know
so
it
works
just
great.
B
B
A
A
E
A
A
B
A
Us
non-profit
we
do,
we
do
have
their
permission
to
use
it,
they
have
granted
us
permission
to
use
it
as
an
open
source
organization
and
and
and
we're
using
it
and
they've
even
implemented.
The
they've
they've
already
started
the
indexing
of
the
doc
site
with
the
thing
they
call
doc
search.
A
So
they've
already
started
it
and
gavin
hopes
to
they've
provided
instructions.
B
A
B
I'm
trying
to
remember
I
haven't,
I
don't
pay
that
much
attention
to
that
and
I
should
I
tend
to
go
to
google,
but
but
this
looks
so
powerful
and
it
clearly
got
implemented
so
smoothly.
B
A
B
A
B
A
A
A
One
cara
de
la
mark
is
the
track
leader
for
cloud
native
and
she
or
I
need
to
create
that
and
then
oleg
nanashev
was
the
track
leader
for
securing
the
delivery
pipeline
and
don't
know
that
he's
going
to
be
available
to
do
it.
But
I
need
to
discuss
with
him
because
I
haven't
looked
at
the
details
of
their
results.
I
just
listened
to
the
summary
and
was
delighted.
A
A
D
A
B
A
B
A
From
google
season
of
of
docs-
oh
yeah,
there
are
some
it's
different
this
year
and
that
they're
having
the
organization
I.e
the
jenkins
project
pay
the
writer
instead
of
having
google
pay.
The
writer
I.
A
B
E
Hi,
so
there
is
no.
A
This
year
I
thought
it
was,
I
see
I
I
haven't
looked
to
be
sure
I
was
was
assuming
that.
A
So
so
this
is
our
intro
page
that
we've
already
got
and
we
publicize
that
and
then
for
yes,
so
this
looks
like
it's
using
a
similar
format
to
google
summer
of
code
in
that
each
each
documentation
id
is
a
separate
idea
and
then
statements
of
interest
are
received
from
technical
writers
that
are
interested
in
working
on
one
or
more
of
the
project.
Ideas.
D
Oh,
oh,
so
there
is
no
next
exclusion.
So
if
we
don't
send
any
prototype
of
ideas,
the
writers
can
send
their
own
for
us.
D
E
A
Well,
it
may
not
strictly
be,
but
the
the
reality
is.
If
we
don't
do
this,
the
likelihood
of
them
accepting
our
us
as
a
project
is,
is
much
lower
right.
Their
google
season
of
docs
will
whoops
we'll
look
at
what
we're
doing
and
they
say
if
you
don't
have
good
ideas,
it's
not
not
as
likely
you'll,
be
successful,
as
if
you
have
a
bunch
of
good
ideas
that
people
can
choose.
D
So
what
is
your
your
plan
for
this.
A
What
we'll
do
is
we'll
put
we'll
basically
go
here
and
follow
the
same
machinery
we
used
last
year
with
the
doc
sig,
where
we
had
documentation
is
here
and
if
we
look
at
google
season
of
docs
it's
here
and
we'll
extend
this
to
include
2021
using
this
google
season
of
docs
page
extend.
C
D
A
A
A
Everything
under
control
good
well
so
there
are.
There
are
certainly
if
what
we
need
to
do
is
assem
is
read
through
the
instructions
here
in
terms
of
the
organization
application
process
and
identify
issues
that
may
need
to
be
raised
to
attention.
For
instance,
the
complicated
one
is
this
one
right
here?
A
E
D
No,
no
okay!
So
it's
up
to
google
sent
the
money
for
jenkins
organization
and
jenkins
just
to
pick
the
out
the
winner
by
his
own
and
just
pay.
A
A
There
are
some
things
about
this
that
I'm
not
entirely
clear
on
yet,
so
we
may
need
to
ask
the
google
people
to
give
us
some
further
clarification
perfect,
because
I
assume
somewhere
in
the
middle
here.
Let's
look
at
the
timeline
somewhere.
There
is
a
a
a
date
where
they
announce
which
project
which
open
source
projects
have
been
submitted
or
have
been
accepted,
and
where
is
the
timeline
there?
It
is
okay.
A
B
A
It's
a
good
question:
how
about
we
just
put
an
action
in
there
review
the
notes
from
the
contributor
summit.
C
A
A
A
Okay
next
topic,
then
google,
summer
of
code
here
we've
got
so.
We've
got
a
project
idea
that
was
just
merged,
proposing
improvements
to
the
pipeline
step,
documentation
generator.
This
is
this
is
the
the
classic
wow.
That's
that's.
Barely
usable
experience
for
the
documentation.
So
when
I
open
pipeline
and
look
at
pipeline
steps
and
then
search
for
checkout.
A
B
A
And
now,
if
I
click
what
just
one
of
those
git
scm,
it
expands
into
this
other
huge
thing
with
still
more
expandable
things.
So
this-
and
this
is
already
a
dramatic
improvement
over
the
first
thing
that
we
release.
We
delivered
with
this
kind
of
layout
then-
and
this
is
apparently
not
even
the
worst
example.
Sh
bennett
knee
noted
that
properties.
A
D
A
A
And
so
so
it's
huge
so
begging
for
someone
to
split
it
into
individual
pages.
Instead
of
having
this
huge
single
page.
B
A
A
So
the
the
there's,
a
program
that
generates
this
page
and
all
the
pages
of
the
pipeline
steps
reference.
That's
this
pipeline
step
doc
generator
program
and
what
that
program
does.
Is
it
iterates
over
every
jenkins,
plug-in
loads,
the
plug-in
and
then
uses
a
reflection
to
see?
Is
there
a
pipeline
implementation
inside
it?
If
so
extract
the
documentation,
it
writes
it
to
static
html
files,
which
then
are
used
here.
So
this
page
is
actually
static,
html,
but
it's
static
html
that
is
generated
by
this
pipeline
step,
doc,
generator.
A
There
there
is-
and
we
have-
we
have
quite
strong
evidence
that
people
are
using
it,
because
here
is
the
result
that
comes
in
from
let's
go
to,
let's
see
this
page.
So
if
I
go
to
a
page
like
this
one
and
scroll
to
the
bottom,
there
is
this
link
right
here.
Was
this
page
helpful
yeah?
If
someone
clicks
that
it
asks
for
an
answer
that
answer
is
placed
into
this
sheet.
A
D
A
So
there
are
all
kinds
of
harsh
comments
that
come
into
these
things,
but
you
can
imagine
they
can
help
us
if
we're
willing
to
ignore
the
profanity
and
ignore
the
irritation,
we
can
actually
still
get
get
better
as
a
result
of
reading
them.
So,
for
example,
there
was
some
feedback
about
six
months
ago
about
the
get
plug-in
and
that
feedback
motivated
me
to
rewrite
the
documentation
to
be
more
useful,
and
it
turns
out
that
those
kind
of
harsh
comments
have
reduced
now
for
that
particular
set
of
documentation.
So
it
seems
to
have
helped.
B
How
much
do
other
plug-in
owners
get
this
feedback
periodically?
Do
we
just
send
them
a
link
and
say
you
might
want
to
check,
see.
A
They
do
not
I've
not
been
promoting
this
because,
because
some
of
it
is
so
indelicate
that
I
I
might
get
people
saying
hey
that
that
is
crassly
offensive.
Please
delete
that
sheet
entirely
and
and
then
there
are.
A
Very
offensive
right
there.
There
are
comments
that
if
I'd
said
those
in
my
mother's
presence,
there
have
been
serious
consequences.
A
B
A
We
certainly
could,
I
think,
I
think,
that's
worth
considering
if
we're
willing
to
teach
them
how
to
do
documentation
for
their
plugin.
One
of
the
I
think
one
of
the
common
outcomes
here
is
is,
for
instance,
it's
very
frequent
they'll
ask
for
an
example
and
the
reality
is
they
don't
need
an
example.
They
need
a
pointer
to
the
pipeline,
snippet
generator
and
and
telling
them
just
use
the
pipeline.
Snippet
generator
is
better
than
telling
giving
them
an
example.
B
A
B
A
Right
well,
and-
and
that's
that's
actually
a
good
candidate
for
the-
I
wonder
if
we
could
consider
that
for
the
st
pipeline
step,
doc
generator
or
something
else
that
would
say,
hey
we're
going
to
propose
empty
spaces
for
your
syntax
diet.
Now,
I'm
probably
not,
because
that
won't
be
much
better.
My
guess
is,
unless
the
maintainers
are
interested
in
improving
their
documentation,
which
they
probably
are
not
by
default,
then
giving
them
empty
stubs
may
not
help.
B
Could
we,
instead
of
automatically
doing
that
for
everything?
Would
it
be
possible
for
us
to
create
a
script
that
for
my
plugin
I
can
go
through
and
this
will
set
up
all
the
files?
I
need
and
then
give
me
instructions
for
filling
them
in
and
then
give
me
a
test
suite
that
tests
for
whatever
they
can
but
just
would
be
for
just
my
plugin.
A
Suspect
that
it's
it's
a
simple
matter
of
programming
and
the
basic
outline
is
right
here.
Yes,
inside
this,
the
pipeline
steps,
doc
generator
already
knows
how
to
load
the
plug-in
and
detect
pipeline
steps
and
arguments
to
those
steps.
Therefore,
I
think
what
you're
suggesting
must
be
imminently
doable,
it's
loaded,
the
plug-in.
Okay.
Therefore,
it
knows
the
plug-in
inside
the
plugins
palm
is
the
url
to
the
plugin
repository.
C
A
B
A
Okay,
so
let's
see
we
were
talking
google
summer
of
code.
I
don't
remember
why
we
got
onto
this.
Onto
this
example.
Jonathan
help
me
I've
gotten
lost
a
little
bit.
D
D
Oh,
listen,
no!
No!
Go
ahead!
So
you're,
just
saying
it's
useful
and
the
season
the
google
season
of
code,
it's
about
to
improve
how
the
documentation
is
just
generate,
but
you
say
the
the
pipeline
documentation
generator.
It's
based
on
reflection
due
to
to
get
the
data
about
the
the
each
pipeline.
A
A
D
A
No
certainly,
certainly
there
are
standard
ways
of
where
you
place
documentation.
There's
this
thing
called
the
jenkins.
The
jenkins
archetype
jenkins,
plug-in
archetypes.
Let's
get
this,
and
here
on
the
creating
a
new
plugin
page,
it
talks
about
how
you
use
maven
to
generate
a
skeleton
plug-in
for
yourself.
I
haven't
checked
to
see
if
that
skeleton
plug-in
has
a
has
a.
A
A
A
A
A
A
A
But
there
is
the
there
is
this
concept
of
a
jenkins
archetype
and
it
will
generate
an
empty
plug-in
for
you
and
then
there
are
places
in
that
where,
when
you
create
a
new
pipeline
step,
you
place
the
documentation
for
that
step
in
that
location.
So,
for
instance,
if
I
look
at,
I
think
it's
called
index.html
no
help.html.
A
We
can
see
in
the
git
plugin
where
its
help
is
so.
The
help
for
the
git
step
is
in
a
file
named
getstep
dot,
slash,
help,
dot,
html
the
file.
The
help
for
the
git
scm
step
is
in
a
file.
Git
scm,
slash
help.html,
so
the
names
of
the
files
are
pretty
simple,
but
a
very,
very
easily
known
pattern,
but
not
created
as
far
as
I
understand
it
by
default,
my
ide,
for
instance,
doesn't
create
those
I
had
to
realize.
Oh,
I
could
add
help
here
and
add
the
files
myself.
D
So
when
did
the
documentations
get
the
content
inside
the
html
file?
There
is
purge
and
clean
every
html
tag
and
create
anothers
or
search
just
put
everything
together
in
one
big
size,
hml
file.
You
have
that
information.
A
A
A
I
started
changing
how
I
how
I
approach
it
and
started
sort
of
nagging
the
user
to
do
things
differently,
so,
instead
of
giving
them
the
example
first
and
telling
them
this
is
how
you
do
it.
I
said:
use
the
snippet
generator
and
every
time
there
is
something
about
an
example,
use
the
snippet
generator
and
it
gets
naggy
about
that.
The
snippet
generator
generates
this
and
again
naggy.
It's
you
know,
gets
very
over
and
over
again
repeating
here's.
A
D
Maybe
an
interface
that
button,
it's
just
a
a
button
which
means
for
us
that
already
use
it,
maybe
a
a
description
side
of
the
button.
Just
saying
how
did
the
proposal
to
use
it.
D
Maybe
you
force
people
to
use
the
generator
instead
of
search
for
help,
interesting
ideas.
D
User
interface
problem,
and
not
the
you
know,
for
example,
go
go
back
for
that
screenshot,
you
just
show.
So
this
one
yeah,
where
is
the
the
green
bluetooth?
Oh
this
one,
is
that
what
you're
thinking
yeah
exactly
so,
for
example,
the
people
has
a
blank
field
and
a
green
build,
so
the
people
see
the
blank
field
and
oh,
I
have
no
idea
what
I
need
to
put
inside
this
field,
so
they
go
to
documentation
or
go
to
google
to
ask
for
help.
A
Yeah,
so
so
the
the
there's
already
something
quite
quite
similar
to
that
here,
where,
if
I,
if
I
go
into
any
one
of
these
pipeline
pipeline
jobs
here
on
the
left,
is
pipeline
syntax,
but
people
because
of
the
number
of
things
that
are
on
this
left
side
and
how
attached
they
are
to
certain
of
them
and
ignore
others.
They
don't
see
it,
and
so,
when
they
click
it
that
this
is
now
the
snippet
generator,
and
this
is
how
they
do
so.
The
thing
that
I
was
describing
earlier
is
this
right.
A
A
Where
is
the
option
exactly
and
that's
and
that's
why
the
idea
was
hey
start
just
shamelessly,
promoting
in
many
different
places
use
the
generator.
I
I
did
something
similar
here
in
the
in
a
plug-in
documentation
page
and
it's
it's
received.
So
I
did
something
here
where
this
this
image
pipeline
syntax
with
the
git
plugin,
is
actually
a
link
to
a
video
on
youtube
and,
oddly
enough
that
video
on
youtube
has
now
received
over
450
views,
since
it
was
created
just
under
a
month
ago.
B
A
Yeah,
so
so
obviously
this
is
this.
Is
there
are
people
who
are
willing
to
click
it
and
and
watch
it,
and
the
the
analytics
on
the
thing
are
quite
quite
interesting.
Actually,
that's
a
that's
a
thing
to
learn
here.
I've
I've
been
impressed
at
how
how
helpful
how
helpful
the
the
syntax
is
or
the
the
analytics.
So
if,
when
I
click
the
analytics
here,
it
shows
me
things
about
who's,
watching
the
video
and
how
they're
doing
it.
A
A
C
A
A
A
A
I'm
good
one,
I
guess,
was
on
the
docs
road
map,
docs
road
map,
review
or
inventory
and
review,
and
I
don't
have
anything
to
do
to
anything-
to
offer
today
and
proposed
doc
structure
right
so
where
to
put
the
existing
content.
A
D
D
D
D
Oh,
there
is
several
meg
and
the
yeah
and
with
the
new
features
you
know,
for
example,
the
then
can
that
could
help
us
to
to
offer
more
a
better
experience
to
readers.
D
So,
for
example,
you
have
we
can
use
tabs
or
reviews
to
the
pipeline
generators
everything,
but
I
think
some
things
that
the
out
our
structure
don't
offer
us.
D
So
I
asked
that
because,
for
example,
if
now
we
create
another
organization
for
our
documentation
and
and
move
the
page
for
the
new
place,
we
keep
with
the
usability
problems.
A
And
and
you're
correct
for
now
this
this
is
not
attempting
to
address
site
usability.
It's
it's
not
offering
versioned
support
right.
It's
still
saying
we
only
have
a
single
version
of
the
docs.
It's
not
offering
historical
rousing
of
the
docs.
It's
it's
just
intended
on.
Hey
we've
got
this
large
body
of
knowledge
on
the
wiki
as
we're
transforming
it.
Where
should
it
go?
D
A
A
Yeah
I
I
certainly
know
I
know,
organizations
that
have
switched
to
antora.
I've
had
requests
from
people
hey.
Would
you
consider?
I
think
it
was
hugo
others
like
that
so
yeah
there
are
certainly
multiple
site
generators
available
and
and
they
they
seem
to
generally
support
ascii
doc.
So
we
we
could
retain
the
content
in
the
adoc
format
that
we've
got
and
just
switch,
which
thing
does
the
generation.
D
Yeah,
because
if
you
choose
a
a
good
one
that
accept
ask
doc,
for
example,
we
can
solve
two
problems
with
one
action
we
we
can,
for
example,
just
planning
which
is
the
better
place
for
each
page,
and
once
we
just
map
everything
we
can.
Okay,
this
is
the
new
version
of
documentation.
It's
a
new
site
generation.
D
A
Agreed,
I
was
assuming
that,
even
if
we
switch
to
a
different
site
generator
that
the
existing
content
must
must
be
usable
in
that
new
site
generator
did.
I
misunderstand.
B
If
we
were
going
to
do
this
first
we'd
have
to
decide
which
one
we
wanted
to
go
to.
How
do
we
do
that
in
an
open
source
project?
Do
we
have
to
let
everybody
vote.
A
C
B
B
A
B
You're,
like
I
I'm
just
going
through
the
antora
conversion
and
there's
a
lot
of
things
that
I'm
fixing
up
because
it
looks
nicer
in
antora.
If
I
do
it
this
way,
but
the
old
stuff
was
there,
the
information
was
there,
it
was
readable.
I
just
didn't
like
it
as
well.
So
right
so
are
we
saying
we'd
like
to
put
this
onto
the
roadmap
for
2021
or
2022
or.
A
I'm
I'm
not
ready
to
put
it
on
the
roadmap,
because
I
don't
think
I
I
don't
see
where
we
would
get
enough
capacity
to
do
it
during
2021.,
I'm
open
to.
If
others
say.
Oh,
it's
going
to
be
mine
and
I'm
going
to
run
this
project
for
the
multiple
months
to
do
it.
I
won't
stop
that.
But
for
me
it's
it's.
I've
got
I'm
already
feeling
like
I've
got
more
on
my
roadmap
plate
than
I
have
time
to
do.