►
From YouTube: Hacktoberfest: Docs and more
Description
Jenkins Online Meetup for Hacktoberfest 2020. Includes suggestions for areas to contribute including code, documentation, and more. Provides a demonstration of building the jenkins.io site locally for development, examples of submitting pull requests from github.com, and a migration of plugin documentation from the Jenkins wiki to GitHub.
A
So
welcome
everyone.
This
is
the
jenkins
online
meetup,
it's
the
14th
of
october
and
we're
celebrating
hacktoberfest
this
month.
This
is
the
docs
and
more
presentation
we're
going
to
share
with
you
how
you
can
contribute
to
jenkins
as
part
of
hacktoberfest.
A
A
First,
we've
got
omega.
Oleg
isn't
based
in
switzerland.
It's
an
international
community
today
presenting
he's
a
jenkins
contributor
he's
a
member
of
the
jenkins
governing
board.
He's
been
involved
with
jenkins
for
many
many
years
and
has
contributed
significantly
in
many
many
different
ways.
I'm
mark
waite,
I'm
based
in
colorado
in
the
united
states.
I've
been
involved
in
jenkins
for
a
number
of
years
as
well.
We've
also
got
jonathan
morais
with
us
from
brazil.
A
Jonathan
is
a
contributor
to
the
documentation
special
interest
group
with
interest
in
code
and
how
to
do
effective
documentation
as
code
he's
been
a
great
help
in
the
doc
special
interest
group.
We're
so
grateful
for
him.
We've
also
got
vlad
silverman
joining
us.
Vlad
is
here
from
california
and
we're
looking
forward
to
his
presentation
as
well.
A
It's
great
to
have
all
all
of
our
presenters
here.
We
love
hacktoberfest
and
are
grateful
for
it.
It's
good
thing
for
us.
It's
a
good
thing
for
you,
thanks
for
being
willing
to
help
us
now
today's
agenda,
we're
going
to
have
me.
Do
these
brief,
intros
and
then
oleg's
going
to
share
several
different
ways
that
you
can
contribute
to
jenkins
and
hacktoberfest
jonathan
is
going
to
then
highlight
some
of
the
things
we
did
to
prepare
for
hacktoberfest,
so
that
you
would
have
a
good
experience
after
that.
A
Vlad
will
talk
about
how
to
build
the
jenkins
site
locally
so
that
you
can
do
documentation
test
and
evaluation
on
your
own
computer,
and
I've
got
some
session
ready
to
show
how
you
could
do
plug-in
documentation,
migration
from
the
wiki
to
github
and,
at
the
end,
we'll
do
question
and
answer
now.
What
we'd
like
to
do
is
encourage
you
to
ask
your
questions
using
the
webinar
q,
a
system
that
helps
us
so
that
we
can
answer
questions
we'll
choose
to
answer
them
live
or
answer
them
in
chat.
A
B
B
Okay,
let
me
just
cover
it
so
yeah
october,
1st
2020
is
quite
an
exceptional
year,
because
this
year
the
vast
majority
of
october
first
happens
online
due
to
obvious
reasons.
B
Even
before
oktoberfest
was
a
worldwide
event
during
one
month
the
hundreds
of
various
events
happening
across
the
world
and
everyone
was
able
to
contribute
remotely
as
well
this
year.
The
main
focus
is
on
remote
and
basically
the
framework
remains
the
same,
so
you
can
submit
four
pull
requests
and
after
that
you
get
a
t-shirt
or
now
you
can
plant
the
tree
or
somebody
transfer
the
tree
for
you
very
cool
correctly.
B
So
it's
your
choice,
and
but
the
idea
is
quite
simple,
so
you
can
just
click
a
button
start
hacking
register
by
signing
up
with
your
github
account,
in
my
case,
I'm
already
logged
into
github.
So
for
me
it
will
show
my
profile.
I
guess.
But
if
you
go
here
for
you
yeah
for
you,
it
will
show
the
signup
form
where
you
can
register
and
after
that
you
can
start
contributing.
B
Basically,
that's
it,
though
there
is
some
specific
central
use
for
this
year.
We
will
talk
about
it
later.
B
Okay:
let's
talk
about
the
the
genghis
project,
specifically
so
jenkins,
as
many
other
projects
participates
in
oktoberfest,
we
started
participating
actively
in
2016
when
we
published
a
special
page
for
october.
That's
when
we
started
preparing
newcomer
friendly
issues
and
promoting
the
event,
and
since
that
the
project
has
been
successfully
participating.
B
Your
experience
with
jenkins
doesn't
matter.
There
is
a
lot
of
newcomer
friendly
issues.
The
result
of
pacquiao
is
focused
not
only
on
court
or
documentation,
but
many
other
activities.
Basically
anything
you
can
submit
as
a
pull
request
that
qualifies
for
breakfast.
B
Any
repository
which
is
public
on
github
is
a
digital
for
oktoberfest
if
it's
configured
properly
so
what
it
means
that
all
the
code,
the
communication
and
also
many
escort
instances,
for
example,
infrastructures
code
documentation,
is
called
and
many
other
areas
which
you
can
represent
as
code
and
find
on
github.
They
are
also
eligible
for
photographers.
There
is
no
specific
differentiation
for
that.
In
the
case
of
the
jenkins
project,
almost
everything
is
stored
in
github
repositories,
so,
basically,
all
content.
We
have
design
wall
artwork,
of
course,
all
the
code
test
units
etc.
B
All
of
that
is
available
as
code,
and
hence
you
can
contribute
many
perceived
jenkins
as
java
project
and,
yes,
the
most
of
jenkins
is
written
in
java,
but
actually
it's
not
only
about
java.
There
is
a
lot
of
other
technologies.
You
could
work
on
if
you're
interested
last
year,
together
with
smart,
we
did
a
presentation
about
contributing
to
jenkins,
and
if
you
want
you
can
go
to
that.
It's
probably.
B
I
can
share
the
link
in
the
chat
later
and
there
you
can
find
a
lot
of
information
about
what
actually
interests
you
and
for
jenkins.
We
use
it's
a
robust
system
with
hundreds
of
plugins
with
mining
infrastructure
repositories.
B
If
you
want
to
try
front-end
or
if
you
want
to
write
some
documentation,
you
can
find
something
interesting
for
you
and
if
you're
interested
in
a
particular
technology,
just
contact
us
and
we
will
be
able
to
provide
a
few
examples
today,
we
are
talking
mostly
about
the
documentation.
So
let's
go
quickly
to
the
documentation,
part,
okay,
so
yeah.
You
can
find
some
examples
here
in
this
slides
javascript
go
long,
many
other
languages
and
yeah.
Today
we
talk
about
the
implementation
so
for
documentation
in
the
jenkins
project
we
use
markdown
and
ask
doc.
B
We
have
a
lot
of
repositories
using
mark
down
as
github
flavor
markdown
as
a
documentation
language.
The
jenkins
website
is
allegedly
written
in
a
ski
doc.
I
believe
today
we
will
cover
both
technologies,
so
vlad
and
jonathan
I
will
talk
about
ascii
doc,
based
documentation.
Mark
will
talk
about
a
markdown
based
documentation,
so
yeah.
We
will
cover
that
in
addition
to
these
formats,
we
also
have
a
lot
of
embedded
documentation,
our
components
and
there
you
can
find
a
lot
to
play
in
text
plain
html
and
other
languages.
B
B
I
mentioned
multiple
times
that
any
repository
would
qualify,
and
yes,
that's
true,
but
at
the
same
time,
especially
for
newcomer
contributors,
it's
important
to
have
clear
guidelines,
issues
etc,
and
we
did
our
homework
before
the
heart
photographer
started,
and
we
prepared
a
number
of
newcomer
friendly
projects
to
which
you
could
contribute,
and
all
these
projects
are
considered
to
be
very
important
to
the
jenkins
project
and
the
community.
Many
of
them
are
represented
on
the
public
changes
throughout
the
month.
B
So
it's
not
like.
We
found
some
areas
where
a
newcomer
friendly,
I
think
it's
by
contributing
to
these
projects.
You
actually
contribute
to
the
changes,
project
goals
and
they
have
some
examples.
So
there
is
jenkins
website
with
a
lot
of
ongoing
documentation,
improvements
and
the
restructuring
that
is
jenkins
core,
which
basically
a
foundation
of
any
agent
instance
running.
Then
there
is
a
plugin
site
which
lists
information
and
documentation
for
all
the
plugins.
We
provide
from
the
jenkins
project
that
is
jenkins
file,
runner
portable
class
engine.
B
B
Also,
we
invite
everyone
to
participate
in
terminologically
now,
so
we
think
of
agent
controller
terminology
and
the
other
areas.
There
is
a
lot
of
quickbook
requests,
so
you
can
do
there
again.
It
helps
the
project.
Also,
if
your
designer
in
jenkins,
there
are
multiple
ways
just
to
improve
the
look
and
feel,
for
example,
you
can
just
contribute
artwork,
which
can
be
used
in
web
interfaces
on
the
jenkins
website
on
community
projects.
Also,
if
you
want
to
improve
the
existing
uis,
you
can
contribute
to
themes.
B
For
example,
there
is
a
recent
dark
theme
for
jenkins,
which
has
been
created
several
months
ago,
and
there
are
other
themes
or
you
could
just
contribute
to
core
jenkins
uis.
All
of
that
is
possible
and
yeah.
What
else
do
we
have
as
featured
projects?
If
you
are
one
of
kubernetes,
maybe
you
have
recently
moved
jenkins
home
charts
at
the
jenkins
organization.
B
It
has
been
available
even
during
the
previous
october
first
but
yeah.
There
is
still
hundreds
of
plugins
to
move,
so
we
will
appreciate
on
contributions
there.
So
all
these
projects
are
not
just
tables.
You
can
find
that
for
every
project
we
have
published
here,
we
have
clear
contributing
guidelines
list
of
good
first
issues.
You
started
working
on
and
also
a
list
of
other
open
issues
and
documentation
which
may
help
you
to
get
started.
So
you
can
take
any
project
which
is
interesting
to
you
and
just
start
working
on
that
for
new
common
contributors.
B
It
would
be
the
recommendation
just
start
from
one
of
these
projects.
If
you
want
to
find
more,
as
I
said,
not
everything
is
listed
as
featured
projects.
We
also
have
a
number
of
issue:
queries
where
you
can
find
issues
suggest
hot
photographers,
so,
for
example,
injectors
jira,
it's
the
old
box
writer
for
the
project.
You
can
find
oh
just
three
issues
marked
for
oktoberfest,
but
likely
we
will.
B
We
need
to
do
some
scrap
there,
but,
okay,
if
you
go
to
github
queries,
so
many
new
components
now
use
github
as
the
main
issue
tracker
here,
you
can
find
more
than
50
issues
focusing
on
different
areas,
so
you
can
see
that
there
are
some
plugins
which
haven't
been
listed,
for
example,
azure
keyword,
slack
plugin,
configurations,
code,
plugin
picture
client,
etc,
etc.
So
you
can
find
more
projects
where
you
can
contribute
here
and
also,
if
it's
not
enough,
there
is
a.
There
are
also
common
newcomer,
friendly
issues
which
haven't
been
solved
specifically
for
hardware
breakfast.
B
A
We
don't
have
any
questions
that
have
arrived
yet
now.
I
there
is
one
table
that
I've
enjoyed,
that
is
the
table
of
fresh
issues
for
or
of
new
of
newcomer
friendly
issues
on
jira.
That
shows
things
like
the
get
client
plug-in.
Has
a
newcomer,
friendly
issue
to
help
me
translate
tests
from
junit
3
to
junit
4,
so
you
had
noted
all
like
individual
plugins
may
not
say:
oh
I'm
a
featured
plugin,
but
they
they
are
still
very
welcoming
to
contributions
on
these
newcomer
friendly
issues.
B
B
So
if
you
have
any
questions,
if
you
are
stuck,
we
give
further
some
problems.
You
would
like
to
start
out.
For
example,
you
don't
get
reviews
etc.
Please
let
us
know
here
and
we
will
process
it
and
help
you
there
and
basically
that's
it.
You
start
contributing
for
contributing
again
any
request
to
any
github
request
repository
accounts,
but
this
year
there
were
some
changes
in
the
program
due
to
which
traffic
of
spambo
requests
coming
to
other
organizations.
B
So
how
to
professor
our
team
modified
the
process,
and
now
it's
opting
for
photographers
contributors
for
that
we
added
additional
process
so
that
when
you
create
a
pull
request,
we
need
to
know
that
it's
related
to
oktoberfest,
so
that
the
hackfaberfest
team
can
mark
it
properly
as
oktoberfest
accepted
pull
request
so
that
it
counts
towards
your
oktoberfest
goals.
B
I'll
show
you
how
this
process
works
again.
Let's
just
take
a
look
at
our
featured
projects,
I
want
to
do
something
quick,
but
at
the
same
time
useful
to
the
project,
and
I
think
that
terminology
cleanup
will
be
a
good
example.
So
here
you
can
see
that
there
is
a
link
to
epic
for
aging
terminology
cleanup
with
open
issues
and
contributor
guidance.
So
we
can
start
from
here-
and
here
there
are
a
number
of
newcomer
friendly
issues.
B
B
B
So
here
you
can
just
browse
from
through
that
and
we
can
find
a
component
which
we
would
like
to
update.
So,
for
example,
there
is
a
copy
to
slave
plugin.
So
let's
take
a
look
at
that
and
see.
What's
in
the
current
state,
so
there
is
a
short
page
here
which
basically
summarizes
what's
the
plugin
about,
and
that
is
also
a
wiki
page
and
I
guess
wiki
page
hasn't
been
getting
related
to
github,
so
something
mark
will
be
talking
about
later
so
yeah.
This
is
the
actual
documentation.
B
But
let's
imagine
that
we
want
to
clean
up
this
repository
because
it's
a
valid
request-
and
here
let's
take
a
look:
what's
the
current
model
plugin,
so
the
current
name
is
copy
to
slave.
We
can
assume
that
it
should
be
renamed
to
copy
to
agent.
B
B
Again,
I
will
be
just
using
the
github
web
interface,
so
no
id
needed
nothing
except
your
github
account.
So
here
you
basically
look
for
all
the
usages
of
slave
in
the
main
page
and
we
can
just
replace
all
of
them,
so
this
one
we
can
attach,
because
for
this
weekend
this
one,
I
guess
we
can
just
remove
it,
because
it's
220.
B
B
Okay,
so
this
is
my
first
patch
just
submitted
and
create
full
request
automatically
so
here
so
we
need
to
mark
it
for
oktoberfest
so
that
we
can
discover
it
on
the
organization
level.
So
I
just
put
charcoal
first
vlog
and
I
guess
that's
it.
B
B
B
So
I
created
this
request
and
yeah,
basically,
this
already
a
contribution
which
may
help
users
visiting
this
page,
and
we
can
assume
that
it's
a
valid
hardware
first
contribution.
So
what
will
happen?
It's
not
you
doing
that.
It's
orcadmin
handling
that
we
put
oktoberfest
accepted,
pull
request
so
that
the
pull
request
becomes
legible
for
hardcover
and
that's
it.
So
we
have
created
our
first
request,
which
does
something
very
useful.
Obviously
you
can
find
much
more
examples
for
that
in
your
plugins.
I
just
wanted
to
show
a
concept
of
how
you
could
do
that.
B
B
Let's
see,
there
are
more
ways
to
contribute.
We
talked
about
featured
projects,
we
talked
about
queries,
but
actually
we
are
not
limited
to
that.
There
is
a
page
called
jenkins,
ios
participate,
it
integrates
information
about
always
to
contribute
to
the
project
and
if
you
are
looking
for
more
opportunities,
please
refer
to
this
page.
B
So
there
are
more
arrays
where
you
can
contribute
to,
and
you
can
explore
to
these
guidelines
to
find
these
projects
or
you
can
just
ask
us
in
the
github
chat,
and
we
will
be
happy
to
help
you,
okay,
more
advanced
projects,
basically
any
pull
request
to
any
jenkins
github
organization
accounts.
Also,
you
can
contribute
to
upstream
projects.
Jenkins
uses
hundreds
of
different
upstream
projects,
honorable
mention
apache
mavian,
including
tools
also
many
other
apache
projects
we
use
in
our
code
base,
basically
for
many
other
projects
which
are
part
of
fujavaca
system.
B
Also,
if
you
want
to
develop
dotnet
code,
we
don't
have
dotnet
code
right
inside
the
junkies
organization,
but
that
are
projects
we
use
like
windows
service
drivers
for
managing
windows
services.
So
you
can
take
a
look
at
that.
You
can
also
work
on
your
own
repositories,
for
example,
just
create
a
demos
for
jenkins
do
some
more
experiments.
For
example,
this
jenkins
configuration
is
code,
his
helm,
charts
series,
kubernetes
separator
and
these
other
new
technologies
available
in
the
jinx,
and
you
can
mark
this
repositories
for
helpful
very
first.
B
B
In
addition
to
that
there
are
cdf
projects,
you
can
also
take
a
look
at
them.
So
thank
you.
Is
the
liberty
foundation
operative
space
and
hardware
test
as
well,
and
if
you
want
to
find
more
information,
please
hear
links
for
all
the
cdf
projects,
so
here
you
can
find
the
guidelines
etc
for
all
of
them.
B
A
D
So
guys
hi
everyone
and
my
eyes
on
this
view
and
software
developer,
and
I
I
love
when
my
daily
tasks
can
run
for
themselves.
So
because,
then
you
are
jenkins
and
I
have
been
able
to
hear
jenkins
fights
since
early
2020.
D
So
I'm
quite
new
here
too,
as
you
I
started
just
a
few
times
ago,
and
I'm
here
today
to
show
you
how
we
prepare
everything
to
offer
you
a
better
experience
than
actual
respect.
Okay,
so
first
everything
I
would
like
to
say
thank
you
for
you
all
and
we
already
received
several
pr's
and
a
lot
of
new
makers
joined
to
our
community
and
this
month,
and
they
those
pr,
has
really
helped
us
to
improve
our
documentation
and
offer
a
better
experience
to
our
members
community
too.
D
Okay,
so
just
to
show
you
a
big
picture
about
our
preparation,
I
will
show
you
some
charts.
So,
as
you
can
see,
the
yellow,
big,
yellow
slice
of
the
chart
show
all
issues
we
have
to
work
early
august,
okay,
so
we
mark
and
others
map
all
issues
for
all
pages
from
the
older
week.
We
we
have
and
how
they
are
important
for
their
own
visit,
page
okay,
so
once
market
we
work
hard
to
open
all
issues
or
github,
so
can
move
for
the
next
shortly.
A
D
Oh,
this
is
the
one
now
yeah
in
the
news
chart
that
you
can
see
and
what
we
work
to
finish
some
issues,
so
the
green
ones
show
every
issues
we
already
migrate
for
the
new
site.
The
jx.io
and
the
orange
slide
shows
how
of
many
available
issues
we
have
so
five
august
to
now.
We
have
almost
150
issues
to
work
on
it
and
maybe
left
now,
because
we
already
closed
on
them
because
they,
after
after
request,
but
the
most
important,
is
almost
50
items
as.
D
Issue,
so
there
is
two
important
points
here.
The
good
first
issue
is
it's
where
you
should
start
to
contribute
to
gender
okay.
So
if
you
need
to
learn
how
github
works,
so
if
you
need
to
learn
about
process-
and
you
want
to
know
how
changes
work
and
how
get
best
from
the
software
and
the
documentation
is
that
that's
a
start
point
to
you,
okay,
yeah.
So
for
that
reason
I
start
work
on
jake's
documentation
too.
I'm
a
software
developer.
D
I
can
work
for
another
plugins
developers
and
other
things,
but
I
choose
documentations
because,
yes,
okay,
it's
a
good
way
to
feedback
for
community
for
everything
documentation
we
already
see
on
the
internet.
So
it's
good
to
you
with
a
good
place
to
stay
and
switch
back.
D
Okay,
so
just
go
to
github
so
to
go
to
the
main
poster
of
jenkins:
go
to
jenkins
dot,
io
eclipse
click
on
issues,
tab,
okay,
so
there
you
can
see
all
issues
we
have
available
to
work
and
click
on
the
blue
one
inside
then,
which
is
right
a
good
first
issue
to
start
okay.
So
here,
in
that
slide,
we
have
have
a
a
print
for
a
software
issue.
Okay,
so
once
you
click
on
issue
to
set
us
work
on
them,
you
just
write
a
comment,
so
just
say
on
comments
I
work
on.
D
I
would
like
to
work
okay,
so
there
is
a
lot
of
good
content
there.
So
when
you
pick
an
issue
yeah
all
you
need
to
start
work
with
all
that,
but
if
you
need
some
more
assistance
feel
free
to
to
ask
for
help.
We
stay
there
to
help
you,
okay,
so
inside
this
each
issue
has
a
video
required
by
mark
where
you
can
find
how
to
work
on
documentation
and
how
to
be
great,
a
page
from
the
old
site
to
new
one.
Okay.
D
There
is
a
lot
of
other
information
too
so
take
time
to
your
time
to
read
on
them.
If
you
find
any
questions
just
sent
over,
so
the
issue
is
good.
First,
one
is
your
start
point.
Okay,
another
important
thing
to
know
is
the
another
on
other
issues:
it's
more
complex,
but
not
so
complex
at
all.
So
once
you
watch
the
videos
by
the
issue
you
are,
you
are
ready
to
work
on
jenkins,
documentation
and
migrate.
The
the
page,
the
only
difference
before
between
the
first
good
first
issue
is
a
normal
issue.
D
It's
because
some
of
our
contents
are
it's
it's
not
up
to
date,
so
we
need
to
rewrite
the
documentation,
update
the
content.
So
in
that
moment,
so
you
will
learn
more
about
jenkins
and
contribute
with
communities.
Okay.
So
to
do
that,
you
need
to
set
your
environment,
and
this
as
a
vlad,
will
show
you
the
next
session,
how
to
set
your
environment,
how
to
create
your
first
vr
and
how
work
engage
documentation.
D
So
everything
you
need
to
know
to
start
vlad
usual
to
you.
Well,
so
at
the
end,
I
hope
you
all
reach
out
new
40
years
to
to
earn
you
the
shirt
or
even
better,
to
first
to
place
a
new
tree
on
forward
and
it's
important.
They
are
alert
about
nature
and
a
lot
of
things.
D
A
B
Jonathan
wanted
to
briefly
highlight
the
contributing
guide
to
answer
the
question
in
the
chat,
so
the
most
of
information
we
present
today
is
already
available
as
contributing
guidelines,
for
example,
for
jenkins
website.
That
is
contributing
a
dog
name
inside
the
repository,
and
here
you
can
find
all
the
information
about
how
to
contribute
how
to
address
particular
use
cases,
for
example,
writing
documentation.
B
A
C
C
See
if
I
can
do
this,
let
me
know
if
you
can
see
my
screen.
C
Well,
let
me
show
well,
this
is
a
visual
code.
This
is
id
one
of
the
popular
ids
which
people
are
using,
but
nothing
that
I
will
show
will
depend
on
this
ide.
So
nothing
is
depends
on
this
specific
development
environment
and
if
you
have
just
terminal,
if
you
have
just
windows
command
screen
like
you
feel
free
to
use
this,
it
is
just
convenience
to
have
in
one
developed
environment,
editor
and
terminal
thing.
C
So
for
my
own
benefits,
I
prepared
this
file,
which
is
in
markdown
syntax,
and
it
is
just
convenient
for
me
not
to
forget
everything
that
I
would
like
to
talk
to
you
about,
and
it
is
possible
to
view
this
in
like
like
in
the
web.
Well,
the
first
thing
that
you
want
to
do
when
started
contributing,
of
course,
and
that
are
talking
about
just
contributing
to
documentation.
C
You
go
to
our
documentation
website,
which
is
jenkins.org
jenkins,
infra
organization,
and
you
look
for
issues
and
well.
I
specifically
for
this
demonstration
picked
up
one
of
the
issues
which
created
myself
and
it
is
fixed
terminology,
one
of
the
projects
which
are
oleg
highlighted
in
his
presentation,
but
it
regarding
only
documentation
part.
So
you
click
on
this
issue
and
it
describes
exactly
what
needs
to
be
done.
It
needs
to
change
white
list
to
allow
list.
C
This
is
new
terminology
that
we
are
using
in
a
developer
section
of
documentation
and
it
presents
all
files
that
needs
to
be
changed.
Links
to
all
these
previous
presentations.
You
can
go
through
this
and
browse
them
as
well,
and
it
mentions
very
important
feature
thing.
It
is
accepted
that
documentation
changed
may
proceed
the
user
interface
or
code
changes,
so
you
can
change
documentation
without
worrying
that
the
code
is
not
changed
yet
because
as
well.
Some
people
may
know
that
code
little
bit
more
difficult
to
change
that
documentation.
C
Sometimes
so,
let's
watch
in
case,
if
you
hadn't
done
this
before,
let
me
bit
shift
my
screen.
First
thing:
is:
you
need
to
fork,
of
course,
if
you
haven't
done
this
before
for
this
repository
too,
I
had
four
this
before
so
and
after
that,
after
you've
worked
this,
you
just
need
to
clone
this
documentation
to
your
own
repository.
This
is
the
copy
button
you
just
copy
this
and
you
can
use
different
well
methods
protocol
right
now.
C
It
is
available
using
github
cli,
which
we
have
recently
introduced,
but
just
ssh
is
also
possible
to
use
and
you
copy
this
well
copy
this
string,
and
after
that
you
just
let
me
see
you
just
use
git
clone
and
after
that,
just
cut
and
paste
this
copy
copy,
sshd
command,
and
I
had
done
this
before
so
I
am
just
not
doing
this
and
after
that
ucd
to
jenkins
dot
io,
and
this
is
the
quantitation
website
and
if
exactly
well,
I'm
doing
exactly
what
is
written
in
this
3d
file,
which
in
case
if
people
want.
C
I
can
share
this,
but
this
started
specific
to
this
after
fixing
this
issue
regarding
terminology,
now
what
is
important-
and
this
is
usually
what
I'm
doing
when
I'm
looking
at
this,
I
would
like
to
be
in
sync
with
the
master
branch,
my
own
repository,
and
this
branch
is
even
with
jenkins,
infra
master
in
case.
If
it
is
not
well,
there
are
two
simple
commands
which
I
organized
in
like
git
sync,.
C
Shell
script,
which
allow
you
to
make
sync
up
with
the
master
repository
very,
very
easy,
and
after
that,
what
you
want
to
do
is
just
let
me
see
in
which
branch
I
am
okay,
when
the
master
branch
and
so
what
we
can
do,
we
can
do
kit
check
out
minus,
b
and
well
x
del,
and
you
can
like
put
any
name
for
your
new
branch
and
just
try
to
match
what
you
are
going
to
do.
C
So
people
will
understand
easier
to
understand
for
those
who
review
your
contribution
basically,
and
your
kicks
and
minus
b
means
that
you
are
just
creating
right
now
and
it
will
copy
in
case.
If
you
have,
you
just
do
check
out,
so
we
are
switched
already
to
this
new
branch
and
we're
already
there.
Now
we
go
replace
whitelist
with
allow
list
for
every
file
in
the
selected
set
of
files
and,
of
course
well.
C
I
opened
all
these
files
in
my
editor,
and
here
they
are
and
again
just
to
make
sure
that
you
understand
we
are
taking
all
these
files
from
from
this
list,
because
this
is
very
detailed,
written
actually
issue.
Sometimes
it
is
not
so
detailed.
Sometimes
it
is
like
yeah,
but
it
depends
so
you
know
we're
going
to
this
specific
files.
C
C
It
is
modified
here,
we'll
go
to
another
file
and
just
do
the
same.
It
is
our
two
on
occurrences
of
this
just
replace
them
both
both
and
for
this
one,
the
police-
and
it
is
modified,
go
to
this
one
and
so
on.
Basically,
we
can
well
just
see
how
many
here
are
our
list,
and
you
see
this
is
everything
in
not
in
the
code.
It
is
in
the
communication
which
can
easily
be
replaced
and
well,
there
is
no
problem
in
doing
this,
so
we
will
replace
this
one
and
let's
go
to
this
action.
C
C
C
C
C
Most
of
this
is
related
to
the
code
and
well
you
can
see
that
it
is
like
the
name
of
the
file
java
file
here
and
well.
If
we
can
start
like
modifying
this
right
now,
it
is
little
bit
more
complex.
Well,
I
would
suggest,
since
we
are
talking
about
documentation-
let's
just
don't
touch
the
code
at
this
point
and
stay
with
documentation.
C
Let's
go
back
to
this
to
our
ide
and
we'll
make
sure
that
we
already
change
these
files
and
what
we
can
do
right
now,
we're
still
in
this
branch
we're
going
to
well
execute
this,
make
wrong
command
and
I'm
going
to
switch
back
to
back
to
my
review
file
here.
It
is
and
we're
going
to
make
run-
and
this
is
micron
in
this
make
file,
and
this
is
how
you
run
your
well
built
your
local
site
id.
C
So
it
will
create
build
the
entire
site
and
will
start
a
docker
container
instantiate
docker
container,
and
it
will
start
it
on
localhost
4242
and
you
can
like,
if
needed,
change
the
sport,
but
I
would
not
recommend
for
new
contributors
to
doing
this
and
go
inside,
because
this
was
written.
Make
file
but
really
smart
people,
and
so
they
knew
what
they
were
doing
so
you
just
can
use
as
it
is.
So
it
is
executing
this
pipeline
initial
jenkins
file
in
this
repository,
and
it
will
start
this.
C
C
And
we
can
see
that
we
have.
We
have
this
actual
our
own
site
localhost
and
we
have
it
here,
and
so
we
can.
For
instance,
let's
see
now
we
change
this
plugin
site
doc
and
I
guess
plug
inside
dock.
It
is
in
developer,
guide
and.
C
Tutorial
tutorial,
it
is
somewhere
else.
Probably
now,
let's
go
back,
let's
go
back,
let's
go
back
and
it
is
reference
the
quotation
maybe
plug
inside
here
and
let's
look
for
what
list
we
didn't
find
it.
What
about?
Allow
list
allow
list
here
we
go.
So
this
is
what
we
changed
and
we
can
again
just
click
on
this
and
see
that
it
works,
and
here
you
have
this
well,
it
goes
to
another
site,
a
brace
center
too
and
see
you
can
see
a
white
list
here
and
well.
C
It
gives
you
some
clue
of
what
can
be
done
next.
So
when
you
start
doing
some
changes
and
you
are
start
doing
some
requests,
you
will
get
understanding
well.
This
is
how
I
can
just
continue
contributing
and
it
is
very
easy.
So
well
it's
what's
interesting
about
this-
that
it
is
well
with
this
site.
It's
a
very
kind
of
interpretive
mode.
C
So
in
case,
if
you
will
change
anything
here,
it
will
modify
the
site
as
well,
and
so
you
will
just,
for
instance,
if
you
go
to
id,
and
you
want
to
change
look
like
inside,
and
you
want
to
change.
For
instance,
here
put
something
like
jenkins:
save
it
go
to
this
site,
refresh
it
and
you
will
see
jenkins
plug
inside,
and
so
it
is
very
easy.
You
will
see
what
kind
of
what
it
changes,
what
you
will
get
basically
and
you
don't
need
to
restart,
which
is
very,
very
variable.
C
Let's
like
go
back
and
remove
this
save
it
again.
So
we'll
restore
this
okay.
So
now
you
already
changed
the
verifiedly,
just
simple,
sending
the
test
and
all
files
well,
that
your
changes
work,
and
so
you
can
just
easily
after
that,
go
back
to
your
id.
Let's
stop
this!
Okay!
Let's
stop
this
for
now
we're
stopping
this
jogger
container,
which
was
executed
right
now
and
let's
go
to
so
we'll
not
forget
3d
file,
and
we
can
just
start
contributing
to
this.
C
So
we
will
do
is
get
starters,
it
will
show
what
are
we
edit?
So
we
can
just
hit
add
content
and
again,
do
you
get
starters,
for
instance,
so
all
our
four
files
have
been
added
and
we
can
just
do
git
commit
minus
am
and
we
can.
Oh,
I
put
fixed
terms
yeah,
so
we
fixed
terms
in
dev,
section.
C
Something
like
this
and
we'll
do
this,
and
after
that,
we'll
do
git
push.
Oh,
I
already
always
forget
how
you
need
to
do
this
correctly.
It
will
just
remind
us
and
you're
trying
to
push
it
to
your
to
your
own
repository
now.
After
that,
you
can
open
this.
It
will
show
you
what
to
open.
C
And
you
can
hear
just
it's
possible
to
mention
that
value
some
files
we
hadn't.
C
Because
of
our
code,
notification
is
a
little
bit
different
and
we
can
break
a
lot
of
links,
and
so
let's
not
do
this
right
now
so
just
you
mentioned
this,
create
pull
request
and
after
that,
well,
you
will
see
how,
like
everything,
is
automated
process
kind
of
except
reviewing.
C
Of
course,
you
will
just
basically
wait
and
see
what
is
the
problem
like
how
the
checks
given
or
what's
interesting,
that
some
checks
haven't
completed
yet,
but
there
is
process
already
going
on
and
your
testing
start
and
well,
you
know,
jennifer's
project
is
using
blue
ocean
plugin
and
just
you
can
go
inside
and
see
how
everything
is
well
given
the
process.
So,
basically,
after
that,
you
sit
and
wait
until
you
will
receive
approval
and
probably
most
likely,
you
will
receive
it
in
email
and
well.
C
I
just
go
inside
details
what
you
need
to
do
to
fix
one
specification.
I
haven't
shared
that
readme
file,
but
I
will
be
glad
to
do
this
in
case
if
needed,
so
you
well,
you
know
how
easy
it
is
to
do
how
easy
it
is
come
like
to
contribute
to
the
jenkins
project
in
the
communication
area.
Like
showed
in
different
other
areas,
mark
will
show
how
to
do
transformation
from
wiki
page.
So
you
are
welcome.
Please
start
contributing
and
well.
You
will
have
a
lot
of
fun
doing
this.
B
C
Do
you
want
me
to
answer
yeah
yeah?
Well,
I
prepared
it
just
for
my
presentation,
but
I
would
build
that
to
share
this
and
just
we
can
discuss
where
to
put
it,
and
I
will
be
glad,
of
course,
to
share
this.
No
just
yeah,
it's
not
private.
It
will
not
be
private.
B
B
So
there
are
two
answers.
Firstly,
indeed,
the
most
of
work
happens
in
the
plugins,
but
it's
not
just
because
the
junk
is
called
stable,
but
it's
because
of
that
the
most
of
the
junkies
functionalities
in
the
projects
jenkins,
has
a
framework
system
and
yeah
it's.
The
agency's
culture
is
related
to
small
implementation,
which
implements
core
foundation
and
apis
projections,
but
all
the
business
logic
all
features
the
most
of
wembley
interfaces,
etc.
They
happen
in
the
plugins.
A
Yeah
I
I
like
I
like
that
observation.
As
one
of
the
one
of
the
genius
elements
of
of
the
jenkins
project
is,
it's
got
lots
of
small
projects
where
individuals
can
contribute
very
effectively
with
without
worrying
about
disrupting
larger
organizations
or
big
monstrous
things
so
whole-hearted
agreement.
Plug-Ins
are
a
wonderful
way
for
you
to
contribute
and
help.
B
B
There
is
a
lot
of
ongoing
work,
for
example,
for
user
experience,
improvements
and
the
junkies
core
and
its
apis.
So
inside
this
component,
the
results
have
a
lot
of
work
happening
at
the
moment,
also
all
kinds
of
performance,
optimizations,
etc.
So
if
you
want
to
explore
genki
score,
it's
also
possible,
though
yeah
this.
The
code
based
on
junkies
core
is
just
it's
much.
Bigger
and
jenkins
has
15
years
of
history,
which
includes
binary
compatibility,
etc.
So
the
code
is
not
straightforward
in
many
cases,
just
because
we
have
to
retain
binary
compatibility
for
the
plugins.
B
A
Now
I,
like
the
question
from
naveen
navin
sundar
about
any
plugins
recommended
for
a
new
java
developer,
and,
and
so
I
have
a
shameless
self-promotion
technique,
contribute
tests
most
of
the
plugins
would
benefit
from
more
tests
and
if
you,
as
a
new
developer,
would
like
to
learn
something
about
the
development
experience
writing
a
test
inside
of
an
existing
plugin
is
often
a
very
good
way
to
explore.
Oh,
how
does
this
work
and
why
does
it
work
that
way?
A
B
All
right
there
are
many
newcomer
friendly
issues
submitted.
Also
there
is
a
lot
of
refactorings
available
because
yeah
jenkins,
we
literally
use
java
8
now
but
yeah.
A
lot
of
the
code
was
created
before
so.
There
are
improvements
you
could
make
there
or
maybe
contribute
to
static
analysis
of
cleanups,
but
yeah
writing
new
features.
Also,
there
is
a
lot
of
opportunities
check
out
the
existing
tickets.
A
Now
we've
got
we've
got
a
question.
Where
are
issues
that
I
can
work
on,
and
I
think
this
might
be
a
good
excuse
to
highlight
the
newcomer
friendly
issues
table
in
the
jenkins
in
the
jenkins
page.
Would
you
be
okay
if
I
shared
briefly
all
like
yeah
you're
doing
the
presentation
next
anyway?
Oh
good?
Okay,
so
let
me
let
me
do
that.
I
think
I
think
I
may
skip
that
presentation
that
I
was
thinking
of,
but
I
just
like
to
show
this
as
a
way
to
highlight
what
what
they
can
see
just
a
minute.
A
A
So
this
is
a
page
that
shows
the
newcomer
friendly
issues
in
the
jenkins
jira
bug,
tracker
and
you'll
see
here
there
are
63
bugs
listed
for
the
jenkins
core
that
are
newcomer
friendly.
There
are
14
listed
for
the
git
plug-in
27
for
warnings
ng
now.
Those
two
plug-ins
that
I
just
mentioned
have
very
high
usage
in
the
git
environment
in
the
jenkins
environment,
and
so,
if
you
contribute
a
fix
there,
you're
contributing
significantly
to
help
the
project.
A
Now
the
next
question
was:
is
anyone
available
to
guide
a
new
dev
and
the
answer
there
is:
we've
got
the
chat
channels
that
will
happily
help
new
developers.
We've
got
the
jenkins
dev
mailing
list
as
well.
Both
are
willing
and
ready
to
assist
now
holding
center
links
to
the
chat.
A
A
This
page
that
you
see
here
highlights
our
progress
and
I'm
I'm
very
pleased
to
show
that
we've
we've
completed
over
500
plug-in
migrations
in
the
last
year,
plus
that's
really
great,
but
we've
still
got
over
a
thousand
left
to
do
so.
There's
lots
of
work
to
do
to
get
the
plug-in
documentation
migrated
into
github,
so
that
maintainers
can
maintain
it
more
easily,
so
that
you
can.
We
can
update
it
so
that
we
can
deliver
it
with
new
releases.
A
So
how
do
we
do
that?
Well,
first
challenge
is:
let's
find
a
plug-in
that
hasn't
been
migrated
yet
you'll,
see
here
on
the
status
column
and
if
I
just
I'm,
I'm
kind
of
lazy
I'll,
just
page
down
and
find
a
row
that
has
there's
one
that
I
thought
I'd
like
to
try
this
one.
So
here
is
the
x-unit
plug-in.
It's
used.
It's
installed
in
over
19
000
installations,
I'd
like
to
migrate
that
so
I
open
up
the
jenkins
wiki
exporter,
jenkinswikiexporter.jenkins.io
and
paste
into
it.
A
The
url
to
that
plugin.
Now
that
plugins
wiki
documentation
looks
like
this.
It's
actually
quite
good.
It's
got
pictures
in
it.
It's
got
a
good
good
content
list,
different
insights,
multiple
levels
of
of
content,
it's
a
very
good
piece
of
documentation
on
the
wiki,
but
it
can't
be
edited
because
the
wiki
is
now
read
only
so
this
export
process.
When
I
click
that
convert
button,
it
will
generate,
it
will
read.
The
wiki
page
generate
a
zip
file
from
the
wiki
page.
That
includes
the
pictures
as
well.
A
Now
I
didn't
want
to
wait
for
this
for
purposes
of
our
demonstration,
so,
oh
and
there
it
is
so
when
I
open
the
zip
file
you're
going
to
see
it's
got
the
readme
and
it's
got
the
docs
images
that
are
my
pictures
so
there
it
is
helping
me
along
the
way.
Now.
What
I
did
then
was.
I
copied
that
up
to
my
development
location
and
let's
make
the
text
here
bigger
there,
we
go.
A
A
A
A
A
A
A
Where
we'll
find
my
branch
migrate
docs
to
github
and
if
we
look
at
the
readme
file
now
you'll
see
here
is
the
translated
documentation
that
a
readme
didn't
exist
for
this
repository
previously
and
now
here's
this
readme
that
has
hyperlinks
in
it.
It's
got
the
pictures,
it's
got
content
and
it
all
looks
actually
pretty
good.
Okay.
I
me
personally
I'd
want
to
get
rid
of
some
of
the
empty
space
here.
A
I'd
likely
make
a
make
an
initial
heading,
so
there
are
lots
of
things
that
I
might
do
to
further
improve
this,
but
this
is
already
a
pretty
good
first
effort
and
that
pretty
good
first
effort
has
transformed
the
documentation
from
read
only
on
a
wiki
page
to
being
able
to
read,
write
inside
the
github
repository
that
the
maintainers
will
be
able
to
care
for
so
we've
we've
made
maintainability
maintainability
improvement.
If
we
submit
this
pull
request,
just
as
it
is.
A
A
B
Then
yeah
on
the
right
side,
there
is
reviewers
on
the
top
still
in
progress.
Oh.
A
A
A
A
That
covered
the
part
that
I
wanted
to
talk
to,
and
I
think
I
can
stop
sharing
now.
We've
got
a
question
in
the
q.
A
about
hey.
Can
I
start
working
on
document
migration.
Absolutely
documentation.
Migration
is
a
is
a
topic
that
we
need.
We've
got
lots
of
issues
in
our
in
our
jenkins.io
site
in
github
issues
that
are
specifically
documentation,
migration
tasks.
A
Now
what
we
found
is
that
the
wiki
as
it's
evolved
over
the
15
years
or
the
10
years
it's
been
maintained,
is
not
always
current,
so
it's
not
as
not
always
a
simple
trivial
conversion
from
one
format
to
another.
It
requires
thought
and
consideration,
evaluation
and
improvement
as
you're
doing
a
migration
of
content
from
the
wiki
to
jenkins
demaio.
A
B
But
in
many
cases
it's
quite
straightforward
and
it's
generally
beneficial
for
the
project.
It's
not
just
moving
from
one
source
to
another,
for
plugin
documentation,
etc.
Removing
the
documentation
github
allows
us
to
follow
the
documentation.
This
code
approach
when
features
changes,
get
documented,
along
with
changes
themselves
which
helps
us
to
maintain
actual
and
version
documentation.
B
Plus
we
can
also
automate
the
release
flows
and
now,
if
you
go
to
documentation
of
existing
plugins,
you
can
see
that
the
documentation
of
these
also
referenced
in
the
change
logs
so
that
they
become
more
traceable
for
users
and
yeah.
Of
course,
it's
also
good
from
the
recognition
perspective,
but
yeah
yeah
main
purpose
said
that
you
know
it's
a
really
collaborative
format.
With
a
support
for
reviews.
We
support
for
versioning.
A
It
really
helps
everyone
in
the
project.
Documentationist
code
really
has
been
a
very
a
very
nice
positive.
The
things
that
I've
interacted
with
I
found
that
the
documentation
is
significantly
better
now
for
plug-ins
that
have
made
that
transition
from
wiki-based
documentation
into
github.
They
are
more
likely
to
update
it
more
likely
to
care
for
it
and
maintain
it
and
be
willing
to
accept
and
consider
pull
requests
that
correct
mistakes
in
it.
B
A
B
B
B
So
if
you
have
any
questions,
please
contact
us
in
this
guitar
channel
genki,
says
oktoberfest.
We
will
be
happy
to
answer
questions,
providing
you
guidance,
how
to
resolve
issues
debug,
something
if
needed
and
yeah
thanks
a
lot
for
your
interest
in
contributing
to
the
jenkins
project,
and
we
are
looking
forward
to
meet
you
in
the
community
channels,
so
have
fun.