►
From YouTube: Documentation track 1 - 2021 02 24
Description
Jenkins Contributor Summit documentation track 1
A
A
Here
are
some:
the
the
intent
of
this
track
is
to
help
us
identify
things
that
should
be
on
the
jenkins
documentation
roadmap
for
the
next
12
months
and
and
things
on
the
documentation
roadmap
should
advance
the
state
of
the
documentation,
help
improve
it.
I've
got
some
ideas
here,
but
before
I
go
through
my
list
of
ideas,
zenob
or
christian
kristen,
were
there
any
ideas
that
you
wanted
to
add
to
the
list,
so
we
can
be
sure
that
they're
at
the
top
of
the
list.
A
C
A
A
A
A
Okay,
great,
so
then,
I
think
in
terms
of
sorting
things
so
that
we
assure
we
get
highest
priority
when
it's
done.
First,
I'm
going
to
put
site
search
the
docs
down
below,
just
because
we'll
review
that
one
in
the
west
coast
version
in
about
four
and
a
half
hours.
So
I
don't
think
it's
as
urgent
that
we
review
it
here
all
right.
So,
let's,
let's
talk
about
first
topic,
would
be.
I
think
we
should
put
on
our
roadmap
that
we
should
be
involved
jenkins
project
involved
with
c-code
africa.
A
A
Changes
many
of
the
screens,
and
it
would
be
a
good
excuse
to
visit
that
and
work
through
screenshot
read
retake
pipeline
examples
are
frequently
requested,
but
now
that
xenob,
I
don't
know
what
your
experience
is
with
these
contributors,
do
they
do.
They
likely
have
any
experience
with
jenkins
prior
to
coming
to
chica
africa.
I
assume
not.
B
So
I
I
can't
really
say,
but
I
know
we
have,
ladies
in
cloud
track
and
devo,
we
have
a
devops
channel,
but
I'm
not
really
sure
of
the
tools.
But
I
think
we
should
have,
ladies,
that
have
some
experience
with
jenkins,
but
I
can't
really
say
for
sure
I'll
have
to
find
out,
but
I
can
put
that
on
my
to-do
list
to
find
out
if
we
have,
ladies,
that
have
any
prior
experience
with
jenkins
or
not
so
we
can
know
what
project
ideas
would
be
more
suitable.
A
Well,
for
me,
this
one,
the
screenshots,
would
could
be
done
even
by
somebody
not
yet
terribly
experienced
if
they're
willing
to
go
a
little
slowly
through
the
process
of
hey.
Here
are
the
instructions
that
got
me
there.
Okay,
and
they
may
say,
oh,
I
need
to
update
the
documentation
because
they
didn't
get
me
to
that
screenshot,
okay
and
and
this
sec
this
last
one
document.
Examples
in
plugins
is
really
sort
of
the
same
as
yeah
see.
I'm
not
sure
that
I
think
those
things
are
the
same.
A
B
B
Well,
this
requires
someone
with
like
advanced
like
an
advanced
jenkins
user
or
probably
someone
if
the
person
just
has
probably
like
basic
knowledge
of
jenkins.
A
person
can
probably
go
through
like
knowledge
sharing
sessions
come
up
to
speed
or
the
person
has
to
be
someone
who
is
well
vast
with
jenkins,
who
is
like
knows
jenkins,
very
well
to
be
able
to
do
the
second
projector
here.
A
Yes,
so
the
second
one
here
is
is
probably
more
advanced
than
the
first
idea,
significantly
more
advanced
the
first.
I
think
I
can
see
how
it
could
be
done.
The
second
one,
at
least
for
me.
I
needed
a
job,
the
ability
to
compile
something
with
java
and
then
run
it
in
order
to
see
the
results
of
what
I
was
creating,
and
so
so
that's
relatively
more
advanced,
whereas
updating
the
screenshots,
that's
probably
just
a
matter
of
us
teaching
them.
How
do
you
create
a
jenkins.io
development
environment
and
update
your
pictures,
update
the
screenshot?
B
So
the
good
thing
about
this
boots
camp
is
that
is
not
just
for.
Ladies
within
chica
africa,
it's
for
all,
ladies
across
africa,
so
anyone
can
apply
whether
you're
part
of
chicago
africa,
community
or
not.
So
I
think
it
would
be
a
good
idea
to
put
out
because
you
can
put
out
more
than
one
project
idea,
so
it
would
be
a
good
idea
to
just
put
everything
out
there
to
select.
B
A
B
Yes,
so
in
march,
that's
when
we're
going
to
be
selecting
the
applicant
so
once
we're
able
to
agree
on
the
project,
ideas
I'll
share
a
google
form
with
you
to
fill
with
the
project
ideas.
So
that's
what
we're
going
to
use
in
selecting
the
participants
that
are
going
to
participate
in
this
bootcamp,
so
since
it's
not
just
for
ladies
within
cheaper
africa,
community,
hopefully
we'll
be
able
to
get.
B
A
D
A
C
B
C
Yeah,
that's
what
I
was
wondering
I
was
like.
Is
there
anything
that's
small
or
like
that?
That
is
like,
maybe
not
entirely
related
to
documentation
that
might
be
useful
here,
like
that,
just
like
a
like
something
that
can
be
self-contained
enough,
like
even
stuff
where
they
get
plug-in
mark.
I
know
you're
really
involved
in
that,
but,
like
that
could
be
helpful
here
as
well.
Yeah.
A
Some
tests
that
exist
today
are
written
for
junit
3
and
they
need
to
be
converted
to
junit
4,
and
this
project
has
been
ongoing
for
12
months
or
more
with
progress
only
as
students
in
google
summer
of
code
volunteer,
so
we're
making
some
new
progress
now,
but
there's
a
lot
yet
to
be
done,
so
this
one
might
be
a
possible
there.
Others
like
it
where
oh
learn
something
about
test
frameworks,
learn
something
about
writing
and
running
automated
tests
and
and
be
available.
Have
some
casual
mentoring
for
me
in
the.
D
A
Right
and-
and
I
think
I
I
think
it's
a
good
question-
that
I
don't
yet
know
the
answer,
but
I
think
it's
worth
asking
the
question
and
starting
it
the
the
docs
piece.
I
think
I
could
see
the
doc's
office
hours
easily,
covering
that
part
part
of
mentoring
right.
We
could
mentor
once
a
week
in
doc's
office
hours
with
that
and
and
quite
comfortably
the
get
client
plug-in
test.
Rework
I
could
probably
cover,
but
other
additional
areas.
We'd
need
to
bring
it
to
to
a
larger
group
and
promote
and
invite
others
to
help.
B
A
B
A
Okay,
hot
spot
for
me
and
zenob,
you
are
our
soda
sort
of
our
classic
example
of
this
contributor.
Onboarding
for
documentation
is
harder
than
it
should
be,
and,
and
we
need
we've
got
several
challenges
right.
One
is
developing
on
windows
is
not
as
easy
as
it
should
be,
and
and
z
knob.
In
your
case,
you
switch
to
a
a
linux
virtual
machine
on
your
windows,
computer
computer.
A
B
Yeah,
I
know
it's
possible,
but
I
was
having
issues
with
permissions
when
I
tried
using
ws01,
and
I
wasn't
able
to
resolve
it
so
because
of
time.
That
was
why
I
had
to
switch
to
the
lineups
vm,
but
I
think
it
would
be
a
good
idea
if
it
could
probably
have
like
maybe
documentation
or
articles
or
things
that
could
explain
this
all
these
available
processes
for
people
that
would
like
to
contribute
like
to
use
vm.
A
B
A
Now,
in
addition
to
that,
there's
we
have
pages.
We
have
pages
that
include
the
improve
this
page
link
and
those
are,
I
think
we
occasionally
do
receive
contributions
through
those.
So,
for
example,
if
we
go
into
the
jenkins
pipeline-
and
we
look
at
this
page-
we'll
see
at
the
bottom
of
the
page
improve
this
page
and
it
takes
us
to
a
page
where
I
can
actually
edit.
A
A
A
A
A
A
A
Yeah
I
mean
for
for
a
user
who
says:
oh
there's
a
misspelling
or
there's
an
error
or
just
something
just
wrong
in
this
text.
I
don't,
I
would
assume
they'll
they'll
want.
Oh,
where
do
I
go
to?
I
want
to
help
with
that.
Where
do
I
go
to
help
with
it,
and
the
answer
is:
go
deep
inside
the
git
plug-in
source
code
to
a
file
that
contains
the
word
url
in
its
name
and
and
it's
it's
a
long
ways
in.
C
D
C
Oh
bye
but
yeah.
I
think
that
that's
you're
right.
That
would
be
the
best
place
to
go,
and
then
also
maybe
that
would
encourage
people
to
fill
out
additional
help,
because
I
think
like
mark-
and
you
were
you
saw-
someone
had
tried
to
was
asking
to
quote
unquote
like
simply
update
something.
This
would
enable
them
to
be
able
to
go
and
do
it
themselves,
because
it's
not
dynamically
generating
something
is
going
to
make
it
difficult
to
do
simple,
update.
A
Right
so
so
the
the
concept,
then
I
think
that
would
mean
that
would
that
page
would
open
to
something
like
this
and
it's
yeah
finding
it
maybe
even
a
challenge.
It's
in
source,
main
resources,
probably
jenkins,
plugin
get
get
step.
Here
we
go
it's
this
file
right,
and
so
we
would
dream
of
a
time
when
url
here
would
have.
I
don't
know
a
hoverable
link
right
next
to
it
or
something
that
would
jump
to
this.
A
E
A
C
What
happens
yeah,
like
the
reason
how
it's
able
to
do
all
this?
Is
we
pretty
much
launch
a
jenkins
or
like
a
plug-in
manager,
instance
and
then
load
everything
into
the
plug-in
manager
and
then
use
plug-in
manager
or
like
use
class
like
the
information
in
the
classes
to
pull
descriptions
and
help
help
text?
C
So
it's
not
like
looking
at
the
classes
like
the
actual
lines
that
like
file
names,
so
I
don't
really
know
how
we'd
be
able
to
get
that
right
now
without
doing
some
digging
but
yeah
it
it.
It's
pretty
much
to
get
all
this
stuff.
We
create
a
plugin
manager
that
has
every
single
plugin
loaded
into
it
and
then
goes.
E
A
Good,
okay
yeah.
So
so
I
think
I
think
that's
a
that's
a
that
feels
like
that's,
probably
relatively
advanced,
because
it
would
mean
looking
at
the
pipeline
step
stock
generator
and
extending
it
somehow.
But
if,
if
we
have
someone
who
has
java
experience
and
we've,
we've
already
got
evidence
that
our
google
summer
of
code
students
are
able
to
make
progress
on
pipeline
step
stock
generator
right.
We've
got
at
least
one
who's
been
investigating
now
for
a
week
or
two
and
been
asking
very
good
questions
about
it
and
obviously
got
it
running.
A
F
C
F
A
C
Well,
it's
me
it's
like
if
we
could
consolidate
so
it's
easier
like
if
everything
is
kind
of
using
the
same
thing
it
it's
another
lowers
a
barrier
to
entry
to
development.
Right,
as
you
already
know,
one
would
be
easier
to
continue
to
contribute,
or
I
think
you
can
share.
It-
would
be
easier.
Maybe
it'd
be
easier
to
share
themes.
I
don't
know,
but.
A
D
A
C
D
It's
relevant
relevant
tool
because
well
you
can
build
the
website
on
windows
as
well,
why
you
cannot
build
it
easily?
It's
because
you
have
make
files
and
wrappers
which
are
designed
for
the
rest
environment.
So
these
flappers
do
not
work
correctly
on
windows,
but
they
work
correctly.
If
you
configure
it
properly
got
it.
So
it's
not
the
framework
itself.
It's
additional
environment.
We
use
automated
development.
A
D
A
D
I
think
that
we
should
be
doing
more
outreach
programs
and
we
should
be
creating
more
tasks,
because
historically
we
get
contributions
through
various
programs
and
outside
them.
There
are
not
so
many
activities,
so
what
could
be
done?
There
would
be
additional,
let's
say,
user
experience,
hackathons
or
that
could
be
ongoing.
Programs
like
you,
can
dedicate
some
budget
for
spark
and
say
that
hey
you
create
documentation
based
on
whatever
conditions
you
get
a
t-shirt,
so
something
like
that
could
be
doable.
A
D
A
A
D
A
D
A
D
It's
not
cdf,
so
basically,
cdf
has
no
its
own
legal
entity.
Okay,
then
they
use
a
linux
foundation
treasury
so
basically
for
all
linux
foundation
projects,
google
just
sent
money
to
the
same
account
and
then
there
should
be
additional
details
and
comments
for
payments
that
should
have
magically
redirected
it
to
community
breach.
This
magic
wouldn't
happen.
D
A
B
B
B
A
C
A
C
A
So,
and-
and
I
had
heard
several
already
in
just
in
sessions
recently
cloud
native
things
like
hey
more
details
on
how
you
use
the
operator
more
more
pipeline,
examples
is
certainly
an
a
a
frequent
request
from
the
feedback
on
our
sites.
Hey
give
me
another
example:
why
don't
you
have
an
example
of
this
and
of
that.
A
A
A
A
And
2021
project
ideas
are
here
and
the
automatic
specification
generator
is
very
much
about
documentation
right.
It's
its
goal
is
to
provide
a
rest
api
description
for
the
jenkins
rest
apis,
but
in
a
format
that
could
be
used
to
could
be
presented
through
things
that
present
things
that
comply
with
the
open
api.
A
C
C
A
C
A
Well,
and
and
okay-
there's
one
for
me
that
probably
I
I'm
guessing
just
looking
at.
Let's
look
at
those
project
ideas,
okay,
this
one
is
a
plug-in
that
will
probably
provide
a
pipeline
step.
Therefore,
that
pipeline
step
should
have
documentation
for
the
step
and
documentation
for
its
arguments
and
preferably
some
examples.
A
C
C
Yeah,
even
seeing
that
kubernetes
operator
one
I
was
like.
Oh,
this
is
perfect.
It
ties
right
into
the
documentation.
We
just
updated.
It's
a
it's
a
good
chance
for
them
to
the
student.
If
a
student
chooses
that
project
and
it
gets
accepted
for
them
to
make
sure
that
that
documentation
stays
up
to
date,.
A
Well,
and-
and
I
had
I-
we've
got
the
action
item
from
other
meetings
where
we
want
to
tutor
people
on
how
to
do
this,
how
to
provide
online
help.
I
liked
yours
of
hey,
identify
places,
identify
locations
in
existing
documentation
that
should
be
updated
right.
The
kubernetes
operator
one
makes
perfect
sense
to
do
an
update
to
jenkins
on
kubernetes.
C
B
C
E
A
C
D
C
C
D
C
A
A
A
A
All
right
next
one
is
wiki
migration
plan,
so
olivier
wants
to
wants
to
avoid
having
to
up
once
to
spare
us
the
update
update
of
the
current
wiki,
and
I
understand
that
right.
That's
that's
an
overhead
that
the
it's
read-only
not
giving
us
a
lot
of
value,
but
it
has.
It
contains
lots
of
useful
content
still.
A
A
D
D
D
A
D
F
F
F
A
F
F
A
A
Okay,
good
yeah-
and
I
think
I
think
that's
the
that
that
was
the
open
question
for
me.
I,
if
my
original
assumption
on
wiki
migration
had
been
not
that
the
goal
was
to
just
shut
down
confluence,
but
it
was
to
get
the
content
into
the
new
destination
and
validated,
but
that's
a
a
much
bigger
project,
and
I
don't
see
that
happening
reasonably
during
2021
not
being
complete
anyway,
and
so
so
this
idea
of
a
mechanical
transformation
or
of
a
of
us
converting
it
to
static
adopt
pages
has.
A
A
A
F
F
F
It
also
has
built-in
metrics
I'm
we're
only
using
the
back
inside
of
it,
but
it
also
can
do
front
and
side
as
well
so
right
now
we
can
get
a
list
of
like
what
words
are
being
searched
for
what
phrases,
how
many
results
are
returned
for
each
search
result
and
then,
as
mark
noticed
the
other
day,
it
actually
does
typo
correction,
which
is
really
cool.
So
if
you
have
a
common
word
that
you
typo
it'll
switch
over,
I
think
it
has
synonym
support.
F
A
F
That's
on
top
of
it's
actually
just
real
time,
fast
response
right,
so
you
can
like,
when
you're
typing
in
google,
you
can
get
results
right
away,
while
you're
still
typing
your
query.
Okay,
so
they
on
their
docs.
They
have
tons
of
demos
as
well.
So
you
have
to
see
some
of
this
in
practice
and
see
what
you
need.
I
just
hooked
up
the
basics
of
basic.
F
F
A
F
A
F
I
have
not
we've
only
been
running
this,
for
we
haven't
been
running,
not
even
24
hours
yet
so
there
are
limits.
The
free,
the
free
one
which
we'll
we'll
be
switching
over
to
soon
has
the
low
limits,
but
the
open
source
one
is
pretty
high
and
they
and
from
their
page
it
seems
like
they're,
pretty
open
to
whatever
you
want.
As
long
as
you
talk
to
them
about
it.
A
F
A
F
So
we're
in
so
we
used
in
our
we're
in
the
free
trial
plan
right
now,
we're
not
free
yet,
but
in
24
hours
we
use
five
units
which
includes
updating
indexes,
which
I
can
definitely
make
less
expensive
and
how
many
search
requests
we've
had
four
thousand
search
requests
in
the
last
and
then,
if
you
go
to
the
analytics
on
the
side,
you
can
see
people
who
you
know
what
the
searches
are.
The
fourth
one
so
yeah.
F
A
F
A
F
Yeah
yeah,
but
I
mean,
like
I
said
this
has
been
a
good
prototype.
Nothing
in
the
plug-in
site
is
committed
to
this,
yet
we
just
wanted
to
see.
If
it
worked,
I
mean
there's
no
reason
we
couldn't
do
another
trial
in
a
couple
weeks
with
elasticsearch.
If
we
wanted
to
go
that
route,
so
I
don't
know,
I
saw
that
you
had
notes
about
it.
I
don't
know
if
they
have
a
sas
product
as
well.
F
D
F
F
F
A
D
Right
search
engines,
so
in
our
case
we
can
take
whatever
we
want.
We
can
also
contact
google
to
see
whether
we
could
get
sponsorship
is
because
you
can
also
use
google
search
the
problem
that
by
default
it
will
show
you
promoted
links.
So,
for
example,
we
can
create
a
search
just
five
minutes
of
work,
but
then,
for
example,
you
will
get
a
paid
promotion
by
circle.
Ci,
you
know
search
layouts,
which
is
definitely
not
good.
E
D
F
D
A
F
A
A
F
E
F
F
A
F
F
F
So
right
now
we're
doing
a
back-end
search,
we're
just
doing
an
api
call,
but
we're
not
we're
not
tracking
to
see
any
of
the
actual.
Let's
say:
click
information
like
which
results
are
useful
for
them,
which
that
kind
of
thing,
so
that
would
be
essentially
a
little
bit
they'd,
be
injecting
a
little
bit
more
of
their
javascript
into
the
page,
which
means
they
potentially
could
track
all
kinds,
more
information
about
the
browser
and
everything
else.
A
A
Okay,
so,
but
I
would,
I
would
assume
it
would
be
okay
to
collect
the
same
kinds
of
information
with
algolia
that
we're
currently
collecting
with
google
analytics
it's
no.
If,
as
long
as
we
don't
make
it
worse
in
terms
of
the
information
we're
gathering,
is
that
a
safe
assumption
or
is
that
that
being
too
creative.
A
E
E
F
Would
hold
off
until
we
get
open
source
sponsorship
and
then
we
have
an
account
manager
and
we
ask
them
like
what
their
front-end
collect.
Data
collection
is
because,
if
it's
just
tracking
on
which
search
result
you
click
on,
then
I
don't
think
it's
an
issue
like
it
doesn't
if
it
doesn't
collect
metrics
about
the
user
and
just
collects
which
you
click
on.
That's
fine,
but
if
it
starts
collecting
about
saying
hey,
you
know
everyone
in
age,
five
clicks
on
this
link,
you're
like
that's,
not
what
we
want.
A
F
But
you
saw
the
stats
I
mean
we
know,
I
mean
they,
they
track
ip
requests
for
searches,
so
they
know
what
country
that's
basic
searching
and
we
know
how
many
searches
they
do
and
then
we
know
what
people
search
for,
because
just
the
nature
of
what
people
are
searching
for.
That's
good
enough
for
our
use.
I
think
right.
We
don't
really
care
if
they're,
you
know
on
a
phone
or
you
know
in
this
country,
doing
this
search
or
anything
else
like
that.
We're
just
curious
about
what
they're
searching
like.
F
F
A
F
A
A
I
don't
think
we
need
to
have
any
deep
discussion
here.
Just
noting
that
this
is
one
of
those
things
where
a
group
of
people
working
across
several
months
will
be
able
to
improve
what
our
final
result
is,
as
we
steadily
move
more
and
more
content
from
wiki
to
curating
it
and
then
putting
it
into
www.jenkins.io.