►
From YouTube: Docs SIG 2020 06 26
Description
Jenkins documentation special interest group meeting from June 26, 2020. Includes a demonstration of the latest enhancements to the plugins site, a demonstration of removing offensive terminology from a plugin through the GitHub web pages, CommunityBridge mentorship program for documentation projects, Google Season of Docs latest status, and latest data on contributions to Jenkins documentation.
A
A
Talk
through
the
topics
and
then
we'll
be
sure
we
do.
The
topics
recording
will
be
posted
on
the
YouTube
channel.
Please
remember
that
we're
adhering
to
the
Jenkins
contributor
code
of
conduct
so
agenda
review
report
on
previous
action
items
I'd
like
to
do
a
demo
of
the
latest
plug
in
site,
enhancements
for
just
to
record
it
and
show
people
that
some
of
the
really
great
things
that
Gavin
and
Finnick
have
done.
We
had
a
Google
season
of
Docs
topic
2
to
cover
for
yesterday's
office
hours,
we're
happy
to
answer
questions.
A
If
someone
arrives
that
needs
them,
we
Oleg
will
help
give
us
an
overview
of
community
bridge
and
what
the
mentorship
might
mean
and
how
we
approach.
It
would
spend
a
little
time
reminding
on
Doc's
office
hours
and
we've
got
a
question
there
that
we'll
need
to
address
and
then,
as
a
concluding
item
review
latest
data
on
contributors
and
on
contributions,
anything
else
that
should
be
in
the
agenda.
Oleg.
A
A
It's
it's
interesting
to
see
the
the
falling
data
rate
of
requests
to
wiki
dot
Jenkins
at
I/o
as
we're
doing
page
replacement.
Oh
like
we
had
an
item
for
you
on
list
the
github,
apps
and
plugins.
They
use
them
anything.
You
want
to
report
there.
No
okay
and
I've
still
got
that.
I've
added
the
new
action
item
to
place
a
new
meeting
URL
into
the
calendar.
B
B
A
B
A
You
know,
for
instance,
this
time
is
not
good
for
for
a
number
of
candidates
that
might
be
potential
mentors
and
we
might
do
two
sessions.
Something
like
that.
So
let
me
take
the
action
item
to
look
for
additional
mentors
and
to
get
a
poll
when
they
could
join
us
mmm-hmm,
any
other
action
items
there.
B
A
So
next
item,
then,
was
a
demonstration
of
the
latest
plug
inside
enhancements.
Gavin,
Morgan
and
spinach
connection
II
have
done
an
amazing
job
of
of
creating
the
Jenkins
plug-in
site
and
continuing
to
enhance
it.
So
this
is
the
plug-in
site.
Let's
take
a
look
at
it
at
a
little
higher
resolution
and
I
look
for
a
plugin
and
notice
now
that
across
the
top
there
are
four
tabs
documentation,
releases
issues
and
dependencies,
and
so
in
the
documentation
tab,
that's
the
documentation.
We've
had
before
for
a
little
bit
now.
A
The
releases
tab
is
relatively
new
and
uses
content
from
the
from
the
github
hub
releases
pages.
To
present
what
is
a
really
nice
layout
of
features,
improvements,
context,
that's
generated
for
this
plug-in
in
this
particular
case,
using
release
drafter.
So
my
job
as
a
plug-in
maintainer
is
easier
because
release
drafter
helps
it
and
it's
presented
very
nicely
to
readers.
A
There's
also
the
dependencies
tab
and
the
dependent
these
tab
shows
me,
which
plugins
and
their
versions
are
required
for
mine,
and
then
the
issues
tab
now
when
I
click
this
issue,
this
particular
plug-in,
has
tragically
a
lot
of
issues
so
I'm
going
to
choose
a
plug-in
that
has
fewer
issues
open
against
it,
so
that
we
can
see
a
little
bit
faster
rendering
of
the
issues
list.
This
will
actually
generate
a
list
of
issues
that
are
in
the
JIRA
system,
makes
it
all
much
easier
for
the
for
the
user
thanks
to
their
marvelous
work.
A
B
B
This
option
it's
the
small
matter
of
programming,
because
we
basically
already
support
this
expert
example
for
the
communication
pages,
so
we
can
render
markdown
and
asciidoc
easily.
We
just
need
to
wait
an
engine
for
that
and
quite
differently
for
issues.
Now
we
support
from
imaging
jitta,
but
now
many
plugins
actually
is
it
happiest
to
track
the
issues
and
again
we
will
need
support
here
for
the
plugin
side.
B
Anyway,
it's
a
great
start
also.
Now
we
have
tabs,
so
we
can
keep
updating
the
content.
So,
for
example,
what
I
have
in
mind
statistics
on
the
right,
so
we
have
installation
graph,
but
actually
we
have
much
more
study,
statistics
on
stats,
gently
say:
oh
and
maybe
we
could
create
a
new
top
all
the
statistics
and
then
setup
that
use
the
right
top
for
additional
metadata
became
a
gauge
before
suggestions
etc.
On
the
main
screen.
B
B
We
have
to
visit
a
repair
mission
updater,
and
this
is
a
source
of
truth
for
the
list
of
maintenance.
So
we
will
easily
benefit
from
updating
this
list,
maybe
even
moving
released
somewhere
like,
for
example,
instead
of
graph
put
input
on
the
right,
page,
etc,
so
that
more
screen
size
is
used
for
documentation.
When
you
open
this
page
so
yeah,
there
are
such
minor
inconstancy
and
they
wish
we
could
can
do
I
really
like
the
progress
on
their
website.
I
will
go
to
a
post.
You
know.
A
So
well
and
I'm
I'm
fascinated
by
the
idea
of
stats.
I
was
just
using
statue
esterday
to
do
some
research
on
a
potential
update
of
a
dependency
and
was
really
impressed
with
the
amount
of
information
I
can
extract
it's
a
little
difficult
right.
It's
not
not
terribly
attractively
presented
sometimes,
but
I
got
lots
of
useful
information
of
stats.
That
Jenkins
thought
I
owe
in
helping
me
address
a
question
that
I
had
yeah
yep.
B
We
can
I
provide
a
lot
of
information
starts.
Maybe
but
release
histories
I
mean
distant
contributors
because
github
does
it.
Why
don't
we
do
it
on
outside?
We
definitely
could
do
that
so
I
things
like
that.
It
can
be
definitely
considered
next
as
improvements
and
what
I
hinted
yesterday
was
need
to
keep
categorizing
plugins
providing
information.
A
A
A
B
B
And
we
good
number
of
applications
so
big
spot
of
options,
how
to
bid
more
students,
potentially
region,
not
students
meant,
is
using
other
programs.
So
last
year
introduced
community
abhrush
mentorship
jenkins
to
be
trend.
One
project,
forging
speculations
good
developer
tools
with
sliding
it
worked
pretty
well
and.
B
Given
a
lot
of
interest
in
the
communication,
I
would
suggest
to
review
such
options
for
the
communication
projects
as
well,
so
that
one
problem
we
have
is
mentorship
capacity
and
another
problem
is
budgets
because
community
which
allows
doing
mentorship
program,
for
example,
even
unpaid
mentorship
and
basically
amount
of
money
for
this
depend,
is
arbitrary
and
decided
by
the
organization
but
yeah
for
wolves
and
dogs.
If
you
want
to
match
this
treatment,
I
mean
ferrets
know
what
one
participant
community
breached.
We
definitely
need
to
shake
some
trees
in
order
to
find
sponsorships
and
whatever.
B
A
Excellent
yeah,
the
the
the
experience
with
the
hackfest,
highlighted
our
need
for
more
mentors,
more
reviewers,
more
people
who
who
are
willing
to
assist
as
Jenkins
skilled
users
now
I
assume
that
in
this
case,
mentors
probably
don't
have
to
be
explicitly
Doc's
experts,
but
they
probably
do
need
to
be
Jenkins
exports.
Do
you
have
any
guidance
you
want
to
give
on
that
with
regard
to
who
would
be
a
good
candidate
for
mentoring
and
to
act
as
a
mentor.
B
Definitely
the
have
expertise
in
Jenkins,
because
all
the
communication
projects
are
the
way
to
talk
to
the
Jenkins
features
and
the
experience
wishing
as
a
user.
It
is
really
important.
Yeah
I
would
like
to
highlight
that
as
a
user,
that
is
a
developer,
not
a
contributor,
because
all
the
projects
we
have
on
the
list
they
focus
user
documentation
at
the
same
time
documentation.
So
some
expertise
is
documentation,
as
code
misses,
kiddo
is
not
down,
would
be,
definitely
welcome.
A
Excellent
yeah
and
I'd
like
to
note
that
experience
with
docks
and
a
ski
docks
is,
is
good,
but
I
would
argue,
is
almost
a
teachable
skill
even
for
the
mentors
that,
if
they
needed
to
learn
that
well,
while
acting
as
a
mentor,
that's
probably
okay,
the
crucial
thing
is:
they
do
need
to
be
experienced
in
the
use
of
Jenkins
I
didn't
if
they,
if
they
aren't
familiar
with
Jenkins,
that
makes
them
a
very
poor
mentor.
It's
really
hard
to
mentor
someone
on
documenting
Jenkins.
A
If
you're,
not
a
Jenkins
user,
you
now
now
I
assume
they
really
don't
particularly
need
to
be
on
specific
language
skills.
Right
I
mean
we
could.
This
does
not
require
that?
Oh,
you
must
somehow
be
native
speaker
or
something
like
that.
Rather
Jenkins
use
is
the
crucial
thing
and,
and
the
other
things
are
nice
to
have,
but
we
need
users.
A
B
Yes,
well,
somebody
would
have
to
do
that
and
yeah
one
thing
which
makes
sense
to
highlight.
So
if
we
talk
about
google,
seasonal
dogs,
google
season
of
dogs
solely
focused
on
a
recommendation
in
english,
if
we
talk
about
community
bridge
mentorship,
basically
its
self
funded
program,
but
at
the
same
time
we
define
other
rules.
For
example,
it
means
that
there
is
a
potential
technical
writer
and
would
be
interested
in
documentation,
for
example
in
chinese,
in
french
or
the
working
localization
etc.
A
That's
a--that's
a
good
idea
and
an
interesting
idea.
I
had
not
thought
of
that.
It
makes
sense.
We
could
choose
it's:
it's
community
bridge
community
bridges,
funding
from
the
Jenkins
project
typically,
and
therefore
the
Jenkins
project
could
choose
to
fund
someone
who
writes
Chinese
language
documentation
or
who
updates
a
localization,
interesting
yep.
B
B
A
Do
you
have
any
anything
you
want
to
describe
there
in
terms
of
what
sort
of
next
steps
should
people
take
if
they
would
like
to
be
considered
for
this?
Is
it
something
where
you're
looking
for
candidates
I
know
I'm
going
to
be
recruiting
for
Mentors
anything
you
want
to
recommend
there,
or
is
this
still?
This
is
what's
coming
and
we'll
do
a
webinar
or
a
blog
post
on
it
as
we
get
closer
so.
B
B
Then,
if
you
want
to
run
five
projects,
you
would
need
to
find
a
lot
of
mentors
I.
Think
a
number
of
our
participants
of
this
seek
meeting.
Well
it.
It
will
definitely
be
a
good
challenge
for
us.
Eight
yeah
I
would
be
interested
to
try
and
if
you
can
find
someone,
if
we
had
a
lot
of
contributors
to
the
documentation,
that's
yours
at
first,
maybe
somebody
would
be
willing
to
be
a
mentor.
B
A
Like
that,
that's
so
the
idea
there
is
that
if
they
wanted
to
do
something
shorter,
they
could,
if
they
said,
I'd
like
to
try
a
four
week
project
of
this
I
proposed
it
now.
Are
you
envisioning
that
a
community
beige
product,
a
project
proposal
for
community
bridge
would
follow
some
of
the
same
patterns
we've
used
for
google
season
of
Docs,
where
they
write
up
the
proposal?
It's
reviewed,
publicly,
etc
and.
B
So
basically
we
will
seasonal
dogs
follows
always
the
best
practices
of
google,
google
Summer
of
Code
and
google
Summer
of
Code
is
16
years
of
program
or
thousands
of
students
more
than
ten
thousands
of
students.
By
now
and
yeah,
it's
pretty
successful,
it
has
quite
established
practices
and
knowledge
was
collected.
Obviously
when
it
comes
to
documentation,
there
are
some
changes
in
practices,
but
in
principle,
yeah
I
think
that
the
same
framework.
A
Okay,
now
I
haven't
seen
if
not
no
XenApp
yet
so,
let's
skip
ahead
to
Doc's
office
hours.
As
a
reminder,
we
have
Doc's
office
hours
Monday
late
evening.
It's
I
believe
10:00
p.m.
UTC
and
Thursday
morning
or
sorry
morning
is
such
a
knob.
It's
Thursday
mid-afternoon
UTC.
If
I
remember,
right,
Oleg,
isn't
it
it's
so
it's
it's
like
2:00
or
3:00
p.m.
UTC
mm-hmm.
B
A
B
So
next
week
the
meeting
at
2:00
p.m.
UTC
you'll
happen.
Oh
okay,
yeah,
but
again
it
really
depends
on
the
participation
if
there
is
no
potential
90s
changing
this
time
slot.
Actually
this
time
slot
was
selected
based
on
the
feedback
in
doodle.
There
are
several
modes
of
participants
who
would
be
interested,
but
if
nobody
joins
again,
I
will
just
cancel
this
sessions,
because
here's
any
other
contributor
I
have
a
lot
of
other
things.
To
do.
Right
like
like
reviewing
the
applications.
A
B
That
big
time
slot
is
probably
not
ideal,
for
example
for
Europe,
because
it's
what
he
knows
and
not
everybody
can
speak
here
in
14
hours.
It's
not
Google
see.
This
is
another
quote.
When
we
talk
about
students,
most
technical
writers,
work
somewhere
so
and
the
same
time,
it's
probably
not
enough
early,
for
example,
for
East
Coast,
so
yeah
the
time
is
empty
eights
from
too
early
for
what
I
don't
know,
but
definitely
this
float
is
not
so
open
to
change.
The
time
comes.
Oh
okay.
A
Yeah
and
and
I
think
that's.
That
was
what
motivated
us
to
choose
that
Monday
evening
late,
it's
after
working
hours
for
in
most
in
many
portions
of
the
US
and
very
late
in
working
hours,
even
in
California.
So
but
but
again
they
I
think
you
hit
it.
You
described
it
exactly
correctly.
Those
hours
are
for
contributors
and
if
no
one's
there
to
to
attend
will
look
for
other
hours
or
cancel
them.
We've
got
other
things.
We
can
do
that.
Help
the
dogs,
great
okay,
all
right,
you
would
mention
terminology
clean
up.
B
But
progress
is
not
material
and
because
well-being,
we
would
benefit
from
all
contributors.
We
put
contributions
to
English
the
communication
clean
up,
especially
during
the
communication
additions
to
French
on
occasion.
But
if
you
go
to
the
github
query,
you
can
find
a
lot
of
angeas
if
you
want
I
can
just
finish
and
show
how
to
find
it
and
how
to
fix
it
at
actually
that.
A
B
Actually,
I
wanted
to
record
a
really
short
demo
or
something
like
five
minutes.
Someone
I
fix
something,
but
here
maybe
I
will
do
it
next
week
and
return
back.
So,
okay
I'll
share
my
screen.
Okay,
do
you
see
it?
I
do
okay,
so
we
have
rode
my
bike
and
my
agent
terminologically
know
it's
also
linked
from
cig
meetings.
It's
a
link
from
the
previous
blog
post.
B
B
So
basically,
if
for
my
system
in
which
it
will
have
a
consensus,
we
want
to
change
that.
We
don't
have
consensus.
What
would
be
the
new
name
and
our
decision
that
we
will
proceed
with
a
public
board,
so
we
will
select
ten
most
popular
options,
I'll
put
them
on
the
ballot
and
after
that
governance
meeting
will
be
signed.
What
would
be
the
final
choice
for
black
is
white
list?
Again
you
we
have
a
decision.
We
want
to
change
that.
B
A
So
that
one
for
me
was
a
very
enlightening
to
watch
some
of
the
transitions,
because
many
of
the
transitions
significantly
improved
their
phrasing
by
removing
the
use
of
blacklist
or
whitelist
completely
and
not
using
a
la
Lister
denialists.
They
just
described
what
they
were
doing
without
using
a
keyword
just
to
talk
about
it.
So
it
is
ver
that
one
is
very
much
context,
dependent
yeah.
B
A
B
Okay,
so
let's
go
back
to
Asians,
which
is
probably
the
most
critical
part,
so
for
agents
we
didn't
bring
in
decision
because
a
decision
was
made
in
2016.
We
decided
that
the
new
terminology
for
slaves,
agent
or
not,
depending
on
the
context
there
is
an
epoch
which
includes
a
lot
of
cleanup
items.
So
we
aim
a
little
disabling,
be
it.
We
put
it
on
our
roadmap,
and
here,
for
example,
you
can
see
that
there
is
a
number
of
things
from
Neutron
coming
from
the
dishes.
So
here
in
the
psychic,
you
have
some.
B
If
I
login,
you
can
find
maybe
2000.
So
whatever
issues
reported,
but
it's
just
a
tip
of
the
iceberg
and
if
you
want
to
see
a
real
extent,
you
just
make
use
github
purchase
here.
For
example,
you
can
find
a
few
examples
and
if
you
use
another
which-
and
you
can
again
just
running
a
bit
harsh
so,
for
example,
here
for
slave,
you
can
find
that
the
more
than
370
occurrences
some
of
them
are
in
the
code.
Some
of
them
are
in
HTML
and
mostly
the
communication
and
help
files.
B
Even
a
zip,
NC
and
here,
for
example,
would
mortals
markdown
it's
mostly
the
communication
in
with
me
pages,
and
so
some
uses
a
belated
3k.
We
also
have
a
plan
to
clean
that
up,
but
does
in
my
image
and
I
clean
up
EPS.
Is
it
a
bigger
problem?
For
example?
Here
you
can
find
examples
just
inside
the
documentation,
so
I
will
just
show
you
how
to
fix
something
or
pay.
For
example,
Jake
clouds
begin.
So
let's
take
a
look
at
this
page,
so
this
is
a
documentation,
oh
all
right.
So,
let's
see
so.
B
This
is
the
page
which
is
over
to
be
used
on
the
plugins.
That
I
believe
also
it's
already
used
as
documentation.
Even
so,
we
that's
what
I'm
going
to
check,
because
I'm,
not
100%
sure
will
I
didn't
use,
check,
outs,
plugging
these
things,
but
yeah
it
uses
it
happens
and
searches
of
the
communication
example
research
for
slave.
You
can
see
that
the
biggest
number
of
occurrences
they're-
actually
quite
a
number
them
okay
and
yeah.
Let's
just
show
how
to
fix
it
without
using
any
ad
etc.
A
B
Yeah,
so
if
you
go
to
the
Jake
calls
page
there
is
we
need,
so
you
can
click
on
this
file
here.
That
is
a
pencil
button,
so,
depending
on
whether
you
have
access
to
this
repository
or
not,
the
behavior
will
be
slightly
different.
But
generally
you
will
get
to
this
edit
page
and
here
example,
just
to
avoid
pushing
to
monster
I
will
just
say:
okay,
let's
just
do
a
full
cycle.
B
B
B
So,
let's
take
a
look
at
our
page
being
a
bit
hub.
You
can
search
so,
for
example,
I
just
search
for
sleep
so
and
that
that
search
thing
you
did
that
just
by
pressing
ctrl
F
that
was
yeah
yo
playing
press
ctrl
F.
If
you
want
you
can
not
have
regular
expressions.
So,
for
example,
he
make
sense
to
just
use.
A
B
Never
really
used
regular
expressions
in
this
way
right
now
it
works.
So
here
you
basically
see
the
list
of
items
we
want
to
clean
up
and
again
you
can
see
that
some
of
them
are
related
to
plug-in
a
DS.
So
it's
not
something
you
can
fix,
but
it's
just
what
we
can
and
again,
if
you
check
it
out,
you
can
just
replace
it.
B
A
B
B
A
B
A
B
What
I'm
going
to
do
I
will
go
to
file,
and
here
we
have
this
file.
Jake
loves
one.
Obviously,
so
again,
we
can't
really
do
anything
with
the
name
of
this
file,
because
it's
a
part
of
public
API
and
renaming
with
salsa
persist
on
the
disk,
etc.
In
principle
in
is
possible,
but
it
will
take
a
lot
of
more
time
than
we
have.
The
seating
also
clean
up
this
file,
because.
A
B
A
B
So,
let's
just
check
whether
we
have
other
users
of
slave
yeah.
You
can
see
that
that
is
a
lot
of
other
things
here
and
there
so
again,
I
will
probably
give
it
to
somebody
who
wants
to
fix
that
sometime,
because
there
is
a
lot
of
such
straightforward
things,
but
there
is
a
lot
of
usages
and
be
a
new
browser
problem
okie
deal
because
in
ID
you
can
just
do
message,
replace,
etc.
Right,
I'll
probably
live
with
the
way
I
started.
A
A
So
it
this
could
have,
for
instance,
touched
the
Javadoc
where
Javadoc
uses
of
the
word
slave.
It
would
be
fine
to
replace
them
and
the
online
help
other
other
things,
but
it's
okay
that
you're
doing
just
one
small
step
towards
this
improvement.
This
is
the
improvement
you
did
with
something
you
detected.
Therefore,
it
helps
you
readers
by
hey.
Let's
remove
fix
the
things
that
we
detect.
B
B
So,
oh,
it's
a
ouch
I'm,
not
sure
what
the
monkey
nurse
will
say
about
it
because,
for
example,
they
may
say
that
you
have
taught
the
entire
code
base
and
then
I
will
do
that
just
not
today,
but
still
it's
a
good
start
right,
so
yeah.
Maybe
next
week,
I
will
record
another
demo,
which
will
be
a
bit
more
straightforward,
but
general
needs
what
we
can
do
and
it's
releasing.
A
Thank
you,
yeah
I
thought
that
was
either
that's
brilliant.
That
was
absolutely
wonderful.
Thanks
very
much
Oh
like
we
had
one
more
item,
it
was
just
Google
season
of
docks.
We
don't
have
any
other
participants,
so
I'd
note,
July
9th,
is
the
deadline
for
project
proposals
to
Google.
Mentors
will
be
reviewing
and
commenting
on
proposals
over
the
course
of
the
next
week
week
or
so.
We
look
forward
to
further
conversations.
A
Questions
can
be
raised
in
Monday's
office
hours
or
in
next
Thursday's
office
hours
or
we're
happy
to
discuss
it
in
the
get
er
chat
channel
happy
to
discuss
it
in
the
Google
Docs
mailing
list
or
in
the
Jenkins
Docs
mailing
list.
All
those
are
great
places
for
discussion.
I
propose
that
we
not
worry
about
looking
at
the
data
on
contributors
and
contributions,
given
where
we're
at
in
time
Oleg
and
say,
let's
rip
people
can
refer
to
the
notes.
I'm
not
concerned
by
the
data.