►
From YouTube: Docs SIG 2019 09 13
Description
Jenkins documentation special interest group Sep 13, 2019. Topics include plugins site improvements demo, governance board, documentation officer, Hacktoberfest, and collaboration with other special interest groups
A
Welcome
everybody:
this
is
the
meeting
in
the
Jenkins
documentation
special
interest
group.
Let's
take
a
look
at
the
agenda
and
then
what
we'll
do
is
review
the
agenda
then
walk
through
the
pieces
that
are
on
the
agenda
sharing
my
screen
and
I've
got
report
on
previous
action
items.
A
brief
point
on
a
brief
point
on
collaboration
with
other
special
interest
groups.
A
A
Excellent
we've
got
a
topic
on
the
community
bridge
sub
project
for
docs.
That
should
be
discussed
further
and
then
unusual
pattern
I'd
like
to
go
over
the
stats
just
to
show
that
a
word
we're
keeping
track
of
things
and
we'll
talk
about
how
the
project
is
progressing.
Are
there
any
other
items
that
need
to
go
on
the
agenda
either
from
you
old
anchor
from
you
Marky.
C
A
A
So
previous
action
items
I've
started
the
pull
request
on
Doc's
project
ideas.
It's
a
large
effort.
I
will
continue
that
it
is
not
ready
for
review.
It's
not
ready
for
merge.
Yet
it
is
ready
for
review.
Thanks
Oleg
for
first
review,
much
appreciated
and
regular
summary
posts.
I
will
mark
to
post
I
will
post
one
to
the
mailing
list
today
when
I
send
out
the
agenda
from
this
meeting.
A
C
C
A
B
B
A
B
A
B
B
Don't
have
something
specific:
we
have
some
follow-ups
to
make
documentation.
Google
Summer
of
Code
respective
so
yeah.
There
is
usual
demand
some
clarity
about
contributing
guidelines,
other
things
Oh,
basically,
nothing
to
do
in
terms
of
feedback.
Okay,
maybe
we'll
do
another
out
of
the
communication
improvements
before
which
is
of
the
720.
A
So
the
we'd
discuss
two
weeks
ago,
the
possibility
of
hosting
the
Jenkins
REST
API
on
swagger
hub
with
a
proposal
from
Abuja
Sharma
I,
created
the
organization
and
asked
SmartBear
by
an
email
if
they
would
be
willing
to
host
it.
For
us,
we
are
now
very
near
the
end
of
our
14-day
period
and
no
response
so
and
I
have
not
posted
anything
on
my
own
I'll,
refresh
that
request
a
smart
bear
and
Mark
to
create
one
more
placeholder
documenting
the
idea
was
document
the
notify
commit
API
as
a
very
popular
API.
A
Yeah
I
can
try
it
today.
I've
got
god,
that's
a
good
idea,
very
good
idea.
Okay,
all
right,
so
then
I
think
we're
ready
to
talk
the
plug-in
site
to
github
integration
sub-project
or
like.
Would
you
like
to
go
ahead
and
give
an
overview?
I
am
so
thrilled
with
this
I,
like
already
what
two
plugins
I
maintain,
have
benefited
significantly
from
it
thanks
a
bunch.
Okay,.
B
B
Jinkies
resources
yeah-
and
there
was
also
a
lot
of
help
from
Hagen-
either
mean
is
infrastructure,
so
basically
I
just
did
some
little
code
and
precipitation
in
this
project.
So
yeah,
it's
not
just
my
work
but
yeah
I
want
to
share
the
story,
need
because
it's
really
important
to
the
community,
especially
to
the
documentation
special
assessment.
So
if
we
take
100
plug-in,
for
example,
what's
take.
B
Most
of
the
communication
is
available
nowadays
and
if
you
know
we
need
to
make
you
can
experience
combinations
like
loading
time
etc.
The
way
outs
are
not
always
built,
so
they
stay
out
is
always
okay,
it
might
be
a
bit
obsolete.
There
were
some
companies
like
message
from
Jenkins.
This
program
is
deprecated,
but
most
of
the
plug-in
yeah
and
the
unique
ESA's
recommendation
is
a
risk
available
on
weekend
in
Jenkins,
we
have
plugin
for
some
biscuits
and
find
the
communication
also
like
in
ferrets.
In
pages,
they
basically
direct.
B
And
here
you
can
see
basically
the
same
age,
because
this
bug
inside
to
retrieve
information
from
media,
and
it
was
a
default
behavior
for
years
and
unfortunately,
from
Winnipeg
in
sister
doesn't
work
as
they
expect,
because
firstly,
Mickey
was
just
like
that
plug-in,
provide
said
to
and
stores
in
the
accommodation
here,
change
look
here,
so
it
found
it
yeah.
This
is
one
piece
key,
so
that
also
use
kisses
for
its
output
conditioners.
B
B
As
far
as
I
know
now
the
cup
cheese
removed,
but
still
contributing
here,
it's
quite
complicated,
but
is
basically
no
way
to
protect
these
pages
from
that
was
basically
no
way
to
have
code
review
for
changes
proposed
by
others,
and
that
is
not
recognition
and
whatever
and
yeah
they're
all
one
of
others.
Access
to
that
is
communications
code
and
solutions.
B
Okay,
so
here
you
can
see
some
documentation
on
github.
So
what
is
a
once?
She
let
anybody
can
general
just
in
they
should
by
clicking
this
button
Eddington.
Can
you
think
of
criminal
pages
and
then
sending
public
requests
so
that
one
of
the
linking
of
smooth
them
unit
integrated
and
after
that
recommendation
lines
causing
the
Theriot
contribution.
We
use
that
reference
them,
the
change
logs
and
the
piece
of
major
changes.
So
really
it
helps
so
I'm
sure
she's
not
know.
B
So
but
the
customization
is,
for
example,
here
you
can
see
that
documentation
of
leads.
So,
for
example,
we
have
a
station
release
the
present
be
released
yet,
but
he
considers
changes
in
the
commutation.
You
can
scroll
down
and
you
can
see
that,
but
it
changes
in
the
commutation
which
basically
become
a
part
of
our
product,
basic
orientation
reservation.
So
for
every
release
you
can
access
documentation
for
this
particular
session.
Actually
it
was
also
not
the
case
for
weekend,
so
users
of
onions
of
obsolete
versions
can
use
the
communication.
So
basically
the
communication
is
code.
B
That's
why
it's
important
to
have
based
the
communication
and
many
plugins
default,
moved
to
that
one
point:
no,
the
problem
was
his
outline
in
a
website
because
he
it
looks
like
that,
but
yeah
thanks
to
speak
and
explore
the
contributors.
We
had
problem
that
there
is
America's
changing
about
edit
integration
inside
github.
It's
not
only
about
publishing.
B
Recommendation
but
other
stories,
for
example,
publish
the
change
logs
so
yeah
you
have
seen
this
change
log
service
drafter.
It's
also
a
big
hopper
integration,
plus
other
stories
like
taken
topics,
as
forgive
labels
from
github,
begin
documentation,
engaging
some
statistics
like
stars,
and
she
meters
number
from
github,
so
basically
making
this
portal
more
accessible
and
providing
some
additional
information
to
the
users
and
the
condition
is
the
first
step.
This
first
step
has
been
middle-earth,
that
is,
announcement
in
and
development
east,
and
here
you
can
see
that
there
are
just
few
examples
provided.
B
Basically,
when
this
change
was
implemented,
we
had
around
20
plugins,
which
she
just
eats
up,
which
really
a
difference
in
github
as
a
the
communication
side.
Just
because
plug-in
developers
didn't
reference
wiki
as
they
were
supposed
to
know.
This
approach
didn't
work
so,
but
right
now,
if
you
specify
github
URL.
So,
for
example,
here,
if
you
go
relational
support.
B
Here
and
if
you
just
use
expressional
a
bit
so
good
point
to
github,
then
once
you
plug
in
is
released,
Jenkins
update,
Center
will
process
today
to
inject
correct
links
and
then
inside
will
be
able
to
display
that
so
how
it
looks
like
so,
for
example,
here's
a
computation
as
code.
This
is
invaded
mutation
which
is
being
published,
and
it
goes
straight
from
one
our
github,
so
visible
images
is
all
hyperlinks,
so
related,
hints,
etc.
Are
all
of
it
works,
and
you
just
specify
your
own
and
periodically.
B
We
will
get
the
communication
published
automatically
if
you
want
to
see
how,
between
this
page,
to
look
like
it's,
five
discipline
offers
etc,
but
yet
we
kill
you
for
this.
Spinning
looked
like
that
yeah,
so,
basically
like
that
and
obsolete
change
lock.
So
anyone
who
was
visiting
this
page
they
just
so
this
obstacle
information-
is
that
a
film
the
connotation
so
yeah.
They
change
a
bit
more
than
one
week
ago
and
over
last
week
had
more
than
30.
Plugins
may
be
related.
B
Also
my
lyrical
strategy
and
many
other
top
dragon,
so
they
moved
the
communication.
So
now
these
applications
benefit
from
github
and
here,
basically
being
like
all
contributors,
all
containers
to
start
using
this
flow,
because
it's
much
more
convenient
and
you
really
need
one
line
changing
if
you
miss
megan
flow
or
grade
or
floor,
everything
is
will
be
published
and
that
this
electronic
you're
struggling
cause
the
application
and
chilly
not.
C
B
Okay,
so
basically
that
was
my
indeed,
there
is
still
a
lot
of
plans
to
do
so.
For
example,
yuning's
I
would
have
changed
openings
here,
maybe
on
the
publishing
of
the
documentation,
because
we
can
render
change,
looks
right
in
the
plugin
website
and
same
for
issues
etc.
So
there
will
be
a
lot
of
changes
and
the
results.
Other
changes
in
review
right
now.
B
B
A
A
B
There
is
pejorative
polling,
so
basically
the
discretion
is
the
spirit
of
exploration.
It's
about
six
hours,
if
I
recall
correctly,
I
didn't
I
need
to
change
it
and
check
the
code,
but
they
yep,
so
the
documentation
will
be
always
updated
when
you're
cutting
your
release
because
of
the
less
fashionable
additional
logic
and
you'll
be
also
periodically.
Even
if
you
do
not
do
the
leases
so
right
now,
this
plug-in
updates
a
shows
master
branch.
A
Well,
so
so
one
thing
that
I
had
had
suggested
on
the
list
was
it:
would
it
be?
Okay
if
I
started
submitting,
for
instance,
tickets
to
various
what
I'd
call
interesting,
plugins,
proposing
newbie
friendly
tickets
to
make
this
transition
for
plugins?
It
seems
like
a
task
that
would
fit
with
someone
who
has
not
terribly
experienced
but
could
submit
to
individual
plugins
a
pull
request
to
make
the
transition
to
them.
Yeah
Oktoberfest
was
the
place.
I
was
thinking
of
it.
Yeah.
B
Right
so
my
plan
was
to
have
a
ticket
template
for
that,
because
I
really
wanted
to
create
a
bunch
of
tickets
for
plugins
people
like
to
emigrate.
One
thing
that
right
now
an
integration
requires
minor
changes,
so
there
is
no
plug-in
installed
on
confluence
which
allows
to
extract
ASCII,
dog
or
markdown
from
this
page.
B
There
are
such
plugins,
so
I
wanted
to
chat
with
Jenkins
in
track
team
and
before
really
creating
these
tickets,
because
if
we
offer
a
way
to
export
the
skeleton
of
the
page,
it
would
help
a
lot
contributors,
because
otherwise,
in
some
sense
that
will
be
needed
a
friendly
ticket,
but
it
might
be
also
monkeyball
yeah,
usually
when
I
retrieve
the
documentation.
I
do
a
lot
of
copy
edits,
because
this
documentation
is
mostly
obsolete
in
many
cases,
but
it
still
better
would
be
with
him.
B
A
Thank
you
very
much.
Yeah
I
love
the
results.
We've
got
so
far.
I
had
a
question.
Should
we,
how
did
you?
How
do
you
get
the
count
of
number
of
plugins
that
have
adopted
the
technique
and
should
we
track
it
as
part
of
the
regular
doc
sig
to
say
hey?
How
are
we
doing
put
up
the
graph
in
part
of
our
metrics
or
not
relevant?
Yet,
oh
well,.
B
B
Structure,
so
it's
all
a
bit
centered,
which
basically
generates
information
once
we
use
updates.
This
is
the
surface
of
a
beans,
but
the
rules
additional
metadata,
which
is
exposed
specifically
for
playing
inside
example,
that
is
playing
in
the
communication
URLs.
So
this
is
a
JSON
file
which
basically
includes
documentation
in
URLs
for
every
plugin
later
there
will
be
a
change,
lock,
URL
and
other
fields.
So
this
is
how
I
plan
to
add
support
of
more
fields
and
hold
it.
B
Yeah,
no,
but
okay.
So
this
approach
has
some
disadvantages,
but
yeah
you
can
easily
see
that
there
are
52
plugins
which
define
github
as
a
source
of
the
communication,
so
this
52
released
plugins.
So
it
means
that
since
I
started
the
project,
they
were
28
plugins,
which
both
released
miss
it
haptic
mutation.
But
here
you
can
check
the
list
not
of
these
plugins
actually
being
published
as
mutation,
because
in
some
cases
you
can
see
that
the
documentation
points
to
is
that
I
did
help
organizations
such
case.
We
do
not
publish
this
documentation
right
now.
B
B
So,
for
example,
we
also
not
quality,
gives
it
points
to
read
me
Indy
yeah,
even
if
its
master,
it
won't
be
published
right
now,
so
I
created
upon
request
to
fix
that
and
basically
is
being
X,
will
also
fix
that
once
it's
finished
yeah
and
there
are
pieces
for
just
random
stuff-
is
being
referenced
from
github
but
yeah
in
for
the
most
of
the
plug-in,
see
it
small
as
a
safe.
For
so
most
of
the
plugins.
You
can
find
its
least
they're
actually
get
published.
B
They
think
that
not
all
plugins
which
related
to
the
communication
have
been
released
yet
so,
for
example,
I
mean
wait.
All
my
plugins,
but
I
haven't
released
all
my
plugins
yet
because
I
want
to
release
it
to
be
some
meaningful
fishes
to
consumers,
because
yeah,
if
I
release
a
plug-in
this
one,
how
certain
destinations
and
basically
everybody
rest
of
their
the
plug-in
just
to
pick
up
new
documentation.
It
doesn't
feel
right
to
me,
but
yet
so
yeah,
that's
the
current
state.
Any
questions.
B
A
B
And
I
would
just
say
that
it's
a
friendly
because
well
I'm,
not
a
Java
developer
at
all,
but
I
was
able
to
get
it
running
in
just
a
few
minutes,
because,
basically
us
young
there
is
documentation
for
that.
How
to
get
it
running.
How
to
verify
that
so
and
yeah
I
was
able
to
get
run
almost
immediately
in
development
flow
is
real-time
changes
to
for
visualization
and
the
course
itself
is
also
pretty
fine,
especially
for
once
who
is
familiar
with
JavaScript
and
react.
B
B
A
You
all
right
so
next
topic
was
community
bridge
sub
projects
for
docks
and
I.
Don't
have
a
dramatic
anything
dramatic
to
offer
there
other
than
that.
The
crucial
the
key
part
of
that
is
the
list
of
project
ideas,
and
that
is
being
assembled
now.
I
assume
that
two
weeks
from
now
when
we
meet
next
I'll,
have
much
further
to
discuss
and
we'll
begin
developing
it
from
there
Oh.
Like
any
insight,
you
need
to
want
to
offer
there.
A
B
It's
self
is
podracing.
Basically,
it's
also
related
to
what
the
permutation
seek,
because
the
objective
of
the
project
is
to
generate
instance,
pacific
specifications
of
jin
kazama
files.
So
basically
it
will
allow
to
embed
the
communication,
for
example
in
IDs,
because
the
additional
schema
can
be
used
as
a
source
of
documentation.
B
There
is
a
good
purpose,
so
there
you
know
the
likely
ship
just
competes
in
the
next
three
days,
the
result
of
things
to
be
done,
but
the
progress
is
being
made
regarding
community
Krish
itself
and
I'd
rather
put
onboarding
projects
on
hold.
So,
yes,
we
failed
advocacy
and
outreach
is
in
discussion.
So
there
are
some
many
issues
in
our
community
bridge
right
now,
for
example,
it's
not
clear
how
we
do
payments
just
because
later
granted
close
doesn't
seem
to
work
and
also
there
are
just
other
minor
issues.
B
A
B
B
B
So
yeah
there
is
another
announcement,
I'm
the
developer,
mailing
list
about
Oktoberfest.
So
basically
we
are
prepping
to
the
Oktoberfest.
It
got
a
bit
delayed
because
yeah
they
do
many
other
things
to
handle,
but
yeah
Oktoberfest
starts
on
October
1st,
so
we
still
have
some
time
and
we
will
definitely
announce
something
we
have
some
meetups
in
progress,
but
what
we
really
need
to
prepare
right
now
is
a
list
of
projects.
So,
for
example,
here
you
can
see
this
from
2018.
So
there
is
a
number
of
projects.
Felicia.
B
Can
we
be
friendly
tickets,
be
a
quick
start
guide
lines
and
defect?
Meteors
will
be
available
to
the
new
changes,
so
I
want
to
have
something
like
that
this
year,
so
we
have,
for
example,
Jenkins
core
website.
They
didn't
stay
there.
It
will
be
definitely
even
blink
filters
which
have
been
created
already.
Drinking
sex
will
stay
there
just
by
making
committer
like
various
color,
so
yeah
there
will
be
also
some
bus
and
Jenkins
eggs
and
they
gave
you
don't
build
trust
posting.
Each
other
configurations
code
will
be
there.
B
Then
Jenkins
I
will
be
an
enjoyable,
definitely
won't
be
there,
but
maybe
we
could
have
some
additional
projects
so
yeah,
for
example,
artwork
mutation
really
and
just
documentation.
So
if
there
are
any
I
knees
would
be
put
improve
so
Mickey
to
eat.
Relations
will
be
there,
but
we
could
suggest
other
meats.
Example.
We
can
Mickey
to
join
castle.
You
is
to
have
a
lot
of
developer
documentation
which
is
on
the
weekend
and
which
could
be
moved
so
yeah.
You
could
use
a
nice
opportunity
to
do
that.
A
B
B
A
I,
like
that
very
much
I've
had
the
notion,
I
think
I'm,
going
to
try
something
even
a
little
for
me,
a
little
more
radical
I'm
going
to
contact
some
local
universities
here
that
have
technical
writing
programs
and
asked
if
I
could
go
talk
to
their
technical
writing
class
locally
there
and
invite
technical
writers,
who
are
students
at
universities
here
nearby
to
to
join
in
during
Oktoberfest
I.
Think
it's
a
great
opportunity
for
them
to
do
something
that
they've
never
done
before,
but
they
will
professionally
when
they
graduate
with
their
degree
in
technical
writing.
Oh
yeah.
A
A
A
A
C
Yeah
totally
so
we
had
the
governance
board
meeting
and
we
made
there
was
a
lot
of
proposals
voted
on.
One
of
those
proposals
was
to
add
a
new
officer,
and
that
officer
was
for
the
documentation,
which
essentially
is
like
the
website
officer
and
should
be
defined
as
the
documentation,
so
that
was
voted
on.
It
was
approved
unanimously.
So
that's
awesome
and
I
believe
the
nominations
start
in
two
days,
I
believe
it's
the
15th
I
check.
B
A
This
graph
was
captured
this
just
today
for
the
last
year
of
time
to
merge
so
the
the
time
between
opening
of
a
pull
request
and
it's
merge
and,
on
the
left
hand,
side
you'll,
see
that
the
the
scale
is
exponential,
it's
yeah
nonlinear
and
that
first
line
one
hour,
the
second
10
hours
and
for
the
last
four
or
five
weeks,
we've
kept
our
median
time
to
merge
in
the
under
10
hour
range,
so
we're
being
responsive,
I.
Think
I,
think
that
was
a
good
sign
that
that's,
okay,
we're
we're
handling
things.
B
B
Yeah,
one
of
the
ways
is
to
just
agree
that,
for
example,
every
month
we
do
demo
and
for
example,
we
could
run
this
online
meetup
or
something
like
that.
Maybe
there'll
be
two
months.
For
example,
yeah.
We
have
some
studies
if
we'd
figured
out
what
to
do
with
swagger
hub
and
if
we
figure
out
them
under
the
communication
side,
maybe
something
else
from
our
previous
achievements
and
they
eat
good.
C
A
C
A
Good
okay
I,
like
those
so
in
terms
of
hosting
an
online
Meetup
Oleg.
Would
that
be
something
like
this?
Where
we
just
do
it
on
with
a
with
with
a
session
through
zoom,
or
are
you
envisioning
that
we
do
something
through
Google
dot
through
Google
online
meets
what?
How
is
that
working
for
you?
Well.
A
And
but
this
and
this
would
I
assume,
be
something
that
would
happen
outside
of
the
meeting
it's
intended
to
promote
people
persuade
them
hey.
You
should
come
here,
cool
things
that
are
happening
in
Docs
if
we,
if
we
called
it
something
like
Doc's
this
month
and
regularly
had
the
meeting
just
to
show
here's
the
last
month's
worth
of
cool
things
that
have
happened
is
that
sort
of
what
you're
envisioning.
B
B
A
B
I
might
be
not
committing
to
every
month
right
now,
or
maybe
we
could
just
try
one
event,
I
plan
to
do
what
I
seen
for
jinx
and
developer
tools.
All
this
stinks
developer
huddle
was
thinking
about.
Well,
basically,
the
communication
can
be
a
part
of
this
effort
or
it
could
be
a
separating
but
yeah,
maybe
maybe
if
you
could
run
one
event
and
see
how
it
goes.