►
From YouTube: 2021 01 11 Docs Office Hours
Description
Jenkins documentation office hours Jan 11, 2021 with topics including summary of progress on documentation pull requests and a discussion and review of the end of year blog post. The end of year blog post discussion also highlighted areas where we should be encouraging new contributors to join us.
A
Got
topics
I
had
put
on.
I
would
love
to
review
with
the
three
of
us
doing:
a
combined
review
and
adding
additional
content
to
this
blog
post
draft
that
oleg
and
oleg
and
marky
jackson
have
been
assembling
it's
due
wednesday
to
the
continuous
delivery
foundation
and
they
would
love
to
have
our
feedback
on
it.
So
edit
live
during
the
meeting
is
my
proposal
we'll
have
some
fun
with
it?
Then
jenkins
in
google
summer
of
code
was
the
topic
security
release.
A
Fine,
okay,
all
right
so
the
and
I
think
the
most.
Maybe
what
we
do
here
is:
let's
put
this
one
down
a
few
just
to
get
through
a
couple
of
of
sort
of
trivial
news
things,
and
then
I
hope
we
can.
If
you
don't
mind,
we'll,
spend
the
bulk
of
the
meeting
talking
about
this
one
and
I
generating
ideas
back
and
forth
of
topics
that
we
can
include
in
it.
A
The
scaling
jenkins
on
kubernetes
pull
requests
still
needs
additional
work
because
I
haven't
worked
on
it
over
the
holidays
and
there
I
I
need
to
work
with
kristen
whetstone
to
have
her
guide
me
how
to
use
the
some
specific
things
that
I
couldn't
figure
out
how
to
make
them
work
with
this.
With
this
what's
described
here
so
whoops.
A
C
C
A
A
C
A
C
A
Well
as
a
and
if,
if
you
can't
do
the
added
as
a
linked
pull
request,
then
that
says
that
the
the
people
who
have
merged
permission
should
probably
see
this
comment,
that
you
gave
and
go
ahead
and
go
do
the
linking
because
it
it
makes
sense
to
me
that
4058
should
be
linked
here,
because
that
that
lets
docker
then
automatically
close.
The
pull
request.
A
A
So
that
covers
oh,
then.
Next
next
item
was
jonathan's
pull
request
and
we
did
in
the
last
within
the
last
12
days
or
so
three
days
ago
we
merged
this
one
and
so
the
j
meter.
There
is
a
page
now
that
describes
j
meter.
We
still
have
three
yet
to
do,
but
nine
of
his
pull
requests
have
been
merged,
so
nice,
nice
step
forward,
and
what
that
j
meter
page
migration.
A
C
You
just
just
small
comment
and
the
question
also
j
meter
is
performance,
testing
kind
of
tool,
open
source
which
had
been
for
a
hundred
years,
but
there
is
also
blaze
meter,
which
is
not
open
source
but
the
product.
So
my
understanding
as
the
rule
of
thumb,
we
should
reference
only
open
source
projects
in
this
integration
and
how
to
not
just
any
any
products
right.
I'm
just
raising
this
question
because
blaze
meter
is
kind
from
from
the
same
category,
but
it
does
better
report
it
and
so
on.
A
Right
right
well-
and
that's-
that's
actually
a
really
good
question,
so
I
think
blaze
meter
actually
be
maybe
mentioned
on
jenkins
dot.
Io,
let's
see
just
so
it's
listed
as
a
plugin
and
there
was
a
blog
post
and
we
we.
We
certainly
welcomed
the
blog
post.
So
this
is
a
blaze
meter
based
blog
post
and
and
no
issue
there
and
we've
as
an
example
of
other
things
that
we've
done
with
proprietary
solutions.
A
We've
certainly
got
the
tutorials
on
how
to
install
with
ibm
cloud
and
your
tutorial
on
google
cloud,
and
we've
got
one
pending
now
on
aws
cloud.
So
I
or
here
this
lab
view
app
labview
is
definitely
not
an
open
source
solution,
so
we're
we're
open
to
do
do
any
of
them.
I
like
I
rather
like
that.
We've
got
a
that
that
we
make
the
distinction
you
described,
that
we
prefer
open
source
when
it's
available.
B
A
A
All
right
so
then
the
reminder
reminder
was
google
summer
of
code
is
coming
and,
and
we
would
love
to
have
more
suggestions
for
project
ideas
and
for
mentors
now,
google
summer
of
code
is
all
about
code,
so
it's
less
about
documentation
other
than
to
encourage
them
to
document
what
they're
working
on
but
absolutely
would
love
to
have
more.
We
had
a
blog
post
from
cara
de
la
mark
inviting
a
calling
for
additional
mentors.
A
A
The
next
topic
was
security
release,
so
this
come
this
next
week
we
will
have
the
jenkins
2.263.2
and
jenkins
2.275
and
it'll
be
a
security
release.
It
was
announced.
It
was
announced
last
week
that
it'll
be
a
security
release
and
the
change
log
has
been
submitted
for
the
lts
and
final
revision.
Of
that
change.
Log
and
of
the
weekly
will
be
available
wednesday
when
it
ships.
A
D
A
A
A
C
C
A
C
A
A
A
A
So
what
this
graph
says
is
the
yellow
line
seems
to
be
companies
and
the
oh,
no
is
it
which
one
is
which
okay
is
that
one
number?
Okay,
so
the
the
green
line
is
companies
contributing
and
committing
and
the
company's
access
is
on
the
left
so
beginning
back
in
2018
we
had
80
distinct
companies
that
their
metrics
said
were
contributing.
A
If
we
go
all
the
way
back
to
2020
january,
we
had
92
companies
contributing
documentation,
we've
dropped
off
a
little
bit
until,
and
I
don't
know
why
we're
seeing
that.
Oh
this
is
that
one.
That
number
is
because
it's
for
this
month,
it
hasn't
come
in
the
data
isn't
available
for
january
right,
we're
only
11
days
in
so
I'm
not
worried
about
that
one.
A
C
A
C
A
A
A
A
C
A
A
C
A
So
this
one
doesn't
count
the
wiki,
but
but-
and
this
one
may
not
based
on
their
description
because
they
say
anyone
anything
changing,
md
files,
so,
for
instance,
jenkins.io
does
not
use
md
files,
we
use
adoc
files,
and
so
this
thing
may
actually
be
understating
the
amount
of
documentation,
but
it's
looking
across
all
repositories.
So
it's
looking
at
plug-in
repositories
and
jenkins
core
and
jenkins
infrastructure.
So
it's
looking
much
more
broadly
than,
and
even
so
we're
still
getting
increasing
contributions
by
number
of
people
and
well,
we
haven't.
C
E
A
A
C
A
But
even
even
that,
for
me
is
is
commendable
because
it
says
hey
from
from
2016
to
now.
So,
across
the
space
of
five
years
we
have
almost
doubled,
haven't
we
so
we
were
at
50?
No,
not
quite
so
we're
we're
a
good
30
or
40
percent
higher
in
terms
of
number
of
documentation.
No,
in
fact,
we
did
double
very
close
to
double
the
number
of
committers
from
our
our
start
in
early
2016.
Is
the
data
here
to
this
high
point
in
end
of
september.
A
C
A
A
Much
more,
that's
that's
actually
a
really
good
question
and
I
think
we
should
be
able
to
answer
the
question,
but
I
don't
know
the
answer:
let's
duplicate
that
tab
and
go
find
out.
Okay,
so,
let's
see
what
else
there
is.
So
your
question
was
about
com
companies
contributing
in
repository
groups
or
well.
Let's
try
that
one.
A
Yeah,
so
if
I
read
this
correctly,
companies
contributing
okay
number
of
users
number
of
individual
contributors,
so
we
are
1600
here
up
now
to
at
our
peak
2
000,
so
2082
there
1930
so
roughly
2
000.
If
we
take
the
average
across
all
three
of
those
quarters
so
we're
up
by
what
is
that
400
over
2000
is
20.
E
A
A
Developer,
I
don't
know
what
developer
activity
counts
would
mean
that
doesn't
help
me
this.
This
tells
me
who
are
our
top
contributors
notice,
oleg
jesse,
daniel
julie,
hoffner,
tim
jacom.
These
are
people.
I
know
that's
good
yeah.
You
are
number
seven
there
yeah!
That's
that's
a
weird
one
because
well,
that
is
odd.
So
why
is
that?
C
C
A
A
A
C
A
A
A
A
A
A
So
what
we
wanted
to
do
was
this
is
a
proposed
end-of-year,
summary
blog
post,
that
markie
jackson
started
and
that
oleg
nanchev
and
I
have
been
adding
comments
to
and
text
etc.
So
key
highlights
and
the
thought
that
vlad-
and
I
had
was
the
three
of
us
could
independently
during
this
meeting,
spend
time
in
this
document
and
make
our
own
proposals
to
it,
so
that
we
could
help
excellent.
A
So
here
is
the
url
to
it
and
I'll
put
that
into
the
meeting
notes
or
into
the
the
chat,
and
you
can
just
open
it
on
your
computer
and
take
a
look
at
it.
Your
comments
will
just
go
in
his
comments.
Okay
and
one
of
the
things
that
helps
with
the
blog
posts
is
images
like
this
nice
happy
new
year
and
I
suspect
we
ought
to
do
pictures
into
the
jenkins
user
interface
thing.
I
think
that's
a
good
one
to
embed
a
picture
and
I'm
going
to
go,
find
a
picture
of
the
plugin
manager.
A
E
A
A
C
B
A
E
E
A
D
E
A
A
E
E
Yeah
got
it
yeah,
okay,
looking
forward,
I
have
a,
I
mean
you,
you
guys
and
janice
and
are
the
greatest
ones,
but
we've
had
a
lot
of
talk
about
making
ways
to
get
more
people,
especially
underrepresented
groups,
feeling
comfortable
and
stuff,
and
it
seems
like
documentation,
is
a
good
place.
Why
don't?
We
have
more
people
showing
up
at
this
meeting
I
mean:
do
we
need
to
have
some
time
make
a
big
deal
and
announce
a
special
session?
That's
just
for
people.
E
Who've
never
contributed
before
to
come,
and
you
know-
or
you
know
something
like
that
to
to
drum
up
some
interest.
I
I
think
there's
a
lot
of
people
out
there
who
would
like
to
contribute,
who
are
a
little
bit
scared
if
they
just
hear
its
regular
office
hours,
they're,
probably
a
little
bit
scared
about
going
in
and
looking
like
an
idiot,
not
realizing
how
kind
and
gentle
everybody
would
be
and
that
they
would
be
welcome,
but
you
know
do
we
do
we
need
to
do
something
to
drum
up
some
more
interest
or.
A
A
Well,
and
and
interestingly
enough,
I
think
linkedin
is
a
good
as
a
good
suggestion
there,
because
we've
we've
recently
surpassed
the
number
of
twitter
surprises
subscribers
with
the
number
of
linkedin
subscribers.
We
have
more
linkedin
subscribers.
Where
we
can
do
full-size
posts,
we
can
embed
pictures,
we
can
do
all
sorts
of
things
than
we
do.
Twitter
followers
and
we
have
a
good
number
of
twitter
followers
already
so
linkedin
is,
is
an
even
more
interesting
thing
than
I
thought.
A
E
E
You
know
to
go
in
and
fix
code
and
then
you've
got
to
test
it
and
you've
got
to
deal
with
a
test
environment.
It
all
gets
complicated
if
you
want
to
go
in
and
clarify
a
sentence
in
the
documentation,
it's
much
straighter
for
more
straightforward
and
we
had
a
lot
of
stuff
at
devops
world
about
you
know,
diversity
and
underrepresented
groups
and
making
them
feel
welcome,
and
it
really
annoyed
me
that
in
all
that
it
was
more
a
thing
of
these
things.
E
These
bad
things
have
been
known
to
happen
and
we
feel
your
pain
rather
than
say.
You
know,
here's
some,
please
that
you
can
get
in
and
get
started
and
you
will
be
safe
and
maybe
alyssa
could
help.
You
know
just
you
know
and
which
I
mean
we
don't
want
to
be
stupid
and
sound
like
we're
being
tokenism
or
something,
but
maybe
we
can
particularly
target.
They
must
have
mailing
lists
that
came
out
of
who
attended
or
watched
those
videos.
E
A
Adding
links
to
office
hours
in
in
the
comments,
oh
in
the
descriptions
of
our
youtube
one
or
more
of
our
youtube
videos-
I
mean-
maybe
maybe
it's
already
that
we
could.
We
could
take
your
idea
there
and,
let's
not
just
say
this,
we
get
to
do
it.
We
will
also
add
links
to
office
hours
of
our
youtube
videos.
E
It
just
seems
to
me
that
there's
a
lot
of
work
that
is
sort
of
simple
work
that
people
could
get
started
with.
You
know,
and
it's
like
I
mean
I
know
for
me.
I
know
how
to
write
but
the
I
you
know
getting
comfortable
with
the
project
and
then
once
I
was
that
I
could
say
you
know
gee.
I
could
do
a
better
job
at
describing
this
subject
than
what's
here.
A
E
A
A
E
E
A
A
A
C
A
A
A
E
A
A
Well,
we
would
we
would
certainly
I
would
love
to
have
more
contributors,
but
in
this
case
I
think
it's
a
good
story
to
tell
look
the
documentation.
Contributions
are
stronger
than
the
the
the
documentation
contributor
count
is
actually
stronger
than
the
code
contributor
count,
because
if
we
look
at
the
code
contributor
count,
we
had
that
earlier
right,
contributing
companies
contributing
in
repository
groups.
This
one
shows,
if
we
s,
if
we
do
quarters
and
last
five
years,
we
see
relatively
flat
in
terms
of
number
of
contributors
to
code,
so
2
000.
A
A
E
B
C
A
That
that
I
do
not
know,
I
don't
know,
certainly
the
the
data
behind
this
is
is
only
as
good
or
the
the
graph
is
only
as
good
as
the
actual
data
behind
it
and
they
give
us
a
link
to
their
table.
So
we
could,
we
could
go,
read
it
to
see
if
it's,
if
it's
an
error
and
probably
they
would
even
accept
I'll
bet
you
they
would
even
accept
poll
requests,
let's
see
if
they
do
yes,
they
would
probably
accept
a
pull
request,
correcting
their
data.
A
A
A
E
A
Yeah,
so
let
let's
put
let's
see
if
we
here
we
go
plug-in
docu,
so
there's
an
entry
here
on
plug-in
documentation,
migration
and
I
can
provide
some
text
for
that
to
describe
how
the
progress
we've
made
and
it's
it's
actually
quite
astonishing.
How
well
we've
done
so
if
we
look
at
documentation
here
and
we
look
at
the
here's-
a
good
one,
this
one
is
shows
from
the
github
projects
view.
This
is
an
incomplete
view,
but
still
interesting.
A
We
have
had
had
126
projects
that
have
tracked
themselves
as
releasing
their
documentation
now
from
github
and
59,
have
merged
and
are
waiting
for
a
plug-in
release
with
35
in
progress.
Now
that
that
ratio
is
is
very
attractive,
it's
great
to
have
126.
there's
an
even
better
piece
of
data,
which
is
this.
A
Let's
see
if
I
can
find
it
the
wiki
exporter
and
this
one
takes
a
while
to
load,
because
what
it's
doing
is
it
will
compute
based
on
the
plug-in
site
which
how
many
of
the
plugins
have
made
the
transition
to
the
to
online
documentation
in
their
own
repository.
Instead
of
relying
on
the
jenkins
wiki
and
last
I
checked,
it
was
almost
600
of
the
roughly
1
800
plugins.
Here
we
go
so
595
have
made
the
transition.
E
A
A
A
Never
make
the
transition
right
exactly,
but
the
if
you
look
at
the
just
visual
effect.
If
we
look
at
the
how
this
feels
in
terms
of
color,
you
see,
the
blue
is
pr,
but
not
yet
released
and
we're
still,
we
haven't
hit
an
empty
row,
there's
our
first
empty
row.
What
number
is
that
row?
I
don't
know
if
I
can
see
a
number,
but
I
can
tell
you
how
many
installations
of
that
plug-in
there
are.
A
A
A
A
A
E
C
E
A
A
E
I
have
a
dumb
plugins
question.
You
see
I'm
here
just
to
ask
them
questions,
there's
that
that
steps
that
reference
page,
that
you
said
is
auto
generated,
which,
by
the
way,
I
think
I
saw
the
fee
pr
go
through
to
fix
it
so
it's
best,
but
that
lists
all
the
plugins
that
can
add
steps
to
your
pipeline
and
those
for
me
all
of
those
steps
that
you
can
click
from
there
and
you
get
some
documentation
about
the
steps
themselves
now.
Is
that
documentation
a
is
it
auto
generated
out
of
code
and
b?
A
Okay,
so
it's
definitely
not
plug-in
documentation
because,
for
instance,
if
we
look
let's,
let's
pick
one,
let's
pick,
let's
pick
the
get
plug-ins
one
that
I
know
okay,
so
here
we
go,
here's
the
get
plug-in.
So
I
found
this
and
I
click
that
so
this
documentation
is
extracted
from
the
plug-in
source
code
okay
and
placed
into
this
webpage
for
for
use.
E
A
Right,
it's
extracted
directly,
so
here's
another
example
get
the
get
bisect
plug-in
this
is
extracted
from
and
you
see
it's
relatively
minimal
right.
There's
not
an
awful
lot
of
content
here.
The
author
of
that
particular
plugin
hasn't
hasn't
taken
the
steps
to
document
all
the
details,
like
the
git
plug-in,
has.
E
A
A
See
if
we
can
find
the
checkout
scm
page
there
we
go
this
one
now
we're
going
to
have
to
wait.
That
was
faster
than
I
expected.
So
this
is
the
checkout
scm
step
which
has
which
has,
if
you
look
here
like
30
or
40,
implementations
of
the
step
right
and
one
of
those
is
used
by
250
000
users,
250
000
installations.
This
thing.
E
B
A
A
E
A
Way
beyond
initiated
right,
you
have
to
know
oh
well,
I
need
git
scm.
Okay,
I
might
have
looked
for
the
word
get,
but
if
I
looked
for
the
word
git,
how
many
times
does
it
occur
here?
Only
three!
That's
not
that
bad
okay,
so
they
might
get
lucky
there.
But,
but
really
this
page
is
an
indicator
that
there's
a
lot
to
be
done.
There.
E
Right
but
well,
there's
a
place
for
a
guide
too.
That
goes
through.
We
started
a
little
bit
in
our
training
materials.
I
don't
know
if
that's
the
right
place,
but
it
was
the
one
we
had
open,
but
you
know
there's
some
cool
things
you
can
do
with
the
get
plug-in
you
know
and
to
just
references
and
say
you
know,
if
you
want
to
know
every
bloody
thing,
this
thing
does
that
they're
all
listed
there,
but
these
are
the
common
ones
right,
and
maybe
we
need
a
layer
like
that.
I
don't
know,
but
I
just.
C
E
E
A
E
E
A
E
A
Do,
and
so
this
could
give
some
hint
of
what
fraction
has
been
done
as
we
go
through
to
the
top.
You
know
if
we
said
what,
if
we
said,
the
top
300
plug-in
yeah
this
this
needs
some
excel
slicing
and
dicing,
and
excel
is
really
good
at
that
kind
of
slicing
and
dicing.
So
so
this
may
be
a
fun
project
for
me
just
to
see
a
documentation,
migration
project
products.
E
A
B
A
A
Oh
no
news,
I'm
using
I'm
intentionally
using
excel
on
my
desktop
on
my
windows,
computer
yeah,
because
I
in
this
case
there
are
things
that
excel
locally,
can
do
that.
I
don't
quite
know
how
to
do
them
with
with
google
doc
with
google
sheets,
but
I'll.
Send
you
a
copy
of
this
that
way.
You've
got
it
and
you
could
try
some
some
different
different
slicing
and
dicing.