►
From YouTube: Docs SIG 2020 01 17
Description
Jenkins documentation special interest group meeting Jan 17, 2020. Topics include the new plugins.jenkins.io site, progress on docs migration from Wiki pages to GitHub repositories, Jenkins core changelog management, Jenkins developer meetups, and the latest reports of contributors and contributions to Jenkins documentation
A
A
So
on
today's
agenda,
we've
got
report
of
previous
action
items
and
I've
put
in
a
documentation,
progress
status
report,
including
a
couple
of
demos
and
some
discussion,
then
developer
meetups
are
a
topic
for
this
time
and
then
we'll
look
at
some
statistics
on
contributors
and
contributions
to
close
out
the
session.
If
we
have
time
I
capture
those
the
statistics
on
contributors
and
contributions,
just
in
case
we
need
them
and
that's
it
Oleg.
Anything
else,
you'd
like
to
be
sure
we
include
on
the
agenda
no.
B
A
Well,
but
that's
a
that's,
a
very
good
win.
Let
me
put
that
I'm
gonna
put
that
down
to
the
end
right
before
the
Data
Report,
because,
as
we
consider
participation
in
Google
season
of
dogs,
it
needs
a
lot
more
preparation,
good,
okay,
mm-hmm
all
right.
Thank
you.
Okay,
so
report
on
sections
I
had
created
the
pull
request,
but
it
was
empty
for
docs
project
ideas.
I've
closed
that,
rather
than
waste
time
in
the
pull
request
queue
with
it.
A
The
idea
that
I've
got
is
I'm
going
to
map
the
pages
and
concepts
from
the
wiki
to
Jenkins
at
I/o
then
create
tickets
for
those
concepts
so
that
we
can
then
have
anybody
pick
up
a
ticket
as
a
newbie
friendly
ticket
and
use
use
that
as
a
way
to
make
progress
on
this.
My
apologies
that
I
haven't
done
this.
Yet
it's
coming.
B
Yeah,
but
one
thing:
I
don't
understand
case
so
for
me:
newbie
friendly
documentation,
tickets
and
okay
Doc's
project
IDs.
We
were
quite
afterburn
all
because
a
newbie
friendly
tickets
are
small
tasks
for
those
who
want
to
just
start
and
the
communities
we
project
ideas.
We
are
rather
for
google
season
of
adorbs.
Another
bigger
problem
comes
like
community
bridge,
so
they
would
have
been
rather
about
major
projects,
so
both
both
activities
makes
sense,
but
yeah
I,
don't
think
that
maybe
friendly
ticket.
Yes,
so
what.
A
The
thinking
I
had
on
that
was
that
newbie
friendly
made
sense
for
some
of
the
tasks
because
they
may
be
purely
a
transposition
of
content
from
one
place
to
another,
and
small
tasks
like
that
could
easily
be
newbie
friendly.
I
could
do
it
as
a
separate
as
a
separate
topic
it
just
for
me.
It
fit
with
if
there's
something
on
the
wiki,
but
is
in
fact
easy
to
transform
that
justifies
being
newbie
friendly.
There
are
other
things
which
are
new
on
TV
and
really
are
a
major
idea
that
won't
be
newbie
friendly,
yeah.
B
A
B
Well,
it
still
makes
sense
a
it's,
probably
just
another
action
item,
because
you
need
any
be
friendly
tickets,
that's
for
sure,
well,
yeah!
So,
but
if
we
have
a
documentation
project
for
example,
and
coming
into
bridge
and
well,
we
could
take
100
plugins
and
say
we
are
going
to
migrate.
Them
is
a
documentation
project.
But
yet
to
be
honest,
I
don't
expect
it
to
be
exciting
for
whomever
works
on
that.
So
I
would
rather
not
on
such
project.
A
Right
right,
agreed,
I,
think
I,
think
the
concept
I
had
for
newbie
friendly
is
fair
for
you
to
your
observation
is
accurate
that
hate
that
may
not
belong
in
a
project
idea.
We
just
put
up
as
part
of
our
newcomer
package
if
they
would
like
to
contribute
the
documentation
they
click
through
to
the
newbie
friendly
and
they
can
get
them.
That's
good,
yeah
I,
like
that
mm-hmm.
A
Great
okay,
thank
you
mm-hmm!
So
then,
as
a
regular
action
item,
an
ongoing
action
and
I
have
a
I
need.
I,
send
out
a
summary
of
the
doc
sig
to
highlight
that
for
the
governance
and
I
assume
that's
still:
okay,
Oleg
that
I
don't
need
to
report
those
the
we
had
agreement
is
okay
or
the.
The
governance
board
is
okay,
just
receiving
a
summary
by
email.
B
So
I
think
that
it
would
be
nice
to
have,
for
example,
a
summary
as
a
dev
least,
that's
for
sure
I
mean,
for
example,
quarterly,
summary
or
months
this
summer.
It
doesn't
matter.
But
if
you
talk
about
bigger
scope
example,
if
you
want
to
highlight
all
the
work
which
happened
the
beginning
of
the
seek,
it
might
make
sense
to
have
a
blog
post
example
in
my
New
Year
blog
post
I,
just
added
some
stats.
B
A
B
A
All
right,
then,
on
to
the
documentation,
progress
report,
so
I
wanted
to
show
a
demonstration
of
the
plugins
do
static
site.
I
am
thoroughly
impressed
with
how
how
much
good
and
solid
work
Gavin
Mogan
has
done,
and
what
a
wonderful
piece
of
work
this
is
to
show
to
people.
So,
instead
of
a
dynamically
generated
site,
it's
now
static.
So
if
I
click
here,
here's
the
plugins
index-
and
it
was
the
page-
opens
quickly
now,
if
I
choose
some
plug
in,
let's
say:
mailer
there,
it
found
it
and
bang
it's
up
and
running
no
generation
process.
A
This
came
from
github,
it's
been
extracted
from
the
readme
as
code.
Likewise,
we
get
the
same
thing
with
their
plugins.
Now
that
are
allowed
to
have
a
table
of
contents
like
the
git
plug-in.
Now.
Has
this
automatically
maintained
table
of
contents
here,
thanks
to
it
being
an
ASCII
dot?
So
with
config
with
documentation
is
code,
we've
got
a
much
better
set
of
documentation
for
plugins
and
that
the
plug-in
pages
load
much
faster
as
far
as
I
can
tell
our
search
rankings
seem
to
be
improving.
A
A
A
Progress
report
that
Gavin
provided
for
us
as
well,
and
that
is
now
hosted
on
Jenkins
style
and
delighted
to
see
that
we
have
over
200
plugins
that
have
completed
their
migration
to
documentation
as
code
and
several
even
in
this
top
list
have
pull
requests
pending
that
are
ready
to
ready
to
go
for
the
next
release
of
that
version
of
that
particular
plugin.
You.
B
A
A
B
A
A
B
Oh,
by
the
way
you
wanna
think
mark
forgot
to
talk
about
to
say
about
plug
inside
that
the
plugin
set
is
also
now
mobile-friendly,
because
before
that,
in
the
previous
implementation,
we've
had
some
issues
with
Styles
etc.
But
now
it
pours
updated
and
it
looks
much
better
on
mobile
screens,
which
is
important,
because
now
we
can
just
reference
links
in
social
media
and
they
don't
look
like
crap.
A
B
Okay,
now
let's
go
to
the
immigration
status.
So
yes,
I,
said
you
know
what
we've
had
from
the
the
reason
for
that,
yet
that
my
still
mine,
you
are
yeah,
no
because
he
in
my
kiss
network,
just
by
X
everywhere.
Ok,
so
our
problem
is
week
exported
that
it
pulls
information
from
just
from
hospitalist
of
opinion,
all
requests
and
force.
It's
a
moving
target,
so
I
spend
some
time
this
week,
just
a
query
carpenter
to
find
all
up
pending
and
pull
requests.
A
B
Cannot
automatically
automate
that,
because
automation
well
I
will
need
to
update
it
a
bit.
The
default
automation
on
github
for
Kanban
horse
is
too
dumb.
So
when
you
merge
it,
it
goes
to
done.
Oh
it
does.
Okay
yeah,
so
I
will
need
to
update
it,
but
right
now
automation
is
disabled
for
this
book.
So
you
have
to
look
at
this.
Both
in
Manila
requests
which
emerged
so
I
can.
A
Okay
and
I
I
admit
that
the
the
crucial
thing
here
is
when
a
change
for
wiki
docket
to
convert
github
documentation
from
to
dog
github
documentation
from
wiki
happens,
the
merge
is
necessary,
but
it's
not
sufficient,
because
we
need
to
release
other
plugin
and
that's
not
a
column.
That's
represented
here.
How.
B
Well,
other
is
done,
which
basically
means
through
these
force-
it's
not
a
problem
for
moving
from
your
to
done,
because
we
be
cakes
Porter.
If
you
go
here,
it's
a
for
the
list
against
it
posts
information
from
the
update
center.
So
when
you
take
a
look
at
this
status
oak,
basically,
this
information
comes
from
the
update
center.
So
it
has
some
log,
but
once
you
release
a
plugin
in
a
few
hours,
it
will
be
moved
to
Green
status
here.
So
you
do
not
rely
on
these
BOTS,
but
it's
a
rather
for
information.
B
A
B
Because
I
captured
some
a
political
West's,
maybe
not
all
of
them-
yeah,
for
example,
here
change
your
rows,
fish
plugin
to
find
a
github.
So
it's
a
for
pipeline
model.
If
you
should
declare
care
for
other
pipeline,
plugins
I
might
have
missed
the
pool
request.
To
be
honest,
so
I
mean
to
double
check
because
again
there
is
no
automatic
creation
of
this
column,
because
yeah
plug-in
meaning
is
just
ate
whatever
they
want,
and
we
need
to
capture
that.
A
B
A
B
Okay,
so
let's
go
back
okay
yeah,
so
this
board
well,
basically,
is
better
than
the
implementation
we
had
before.
But
it's
still
far
from
me
video
here
you
can
just
wear
the
things,
for
example.
So
how
I
do
that,
for
example,
github
yeah,
I,
kill
bet
you
can
find
some
poor
requests.
For
example,
here
there
is
a
Google
Earth
plug-in
which
is
not
listed,
so
we
can
just
drag
and
drop
it
to
this
column
yep.
B
B
Yeah
moaning
dogs
from
Wikia,
that's
security,
so
here,
for
example,
we
can
see
that
the
best
status
is
merged,
so
AJ
has
to
go
to
the
pool
request.
I
can
see
that
yeah,
it's
moved,
they
can
check
the
committee,
and
here
you
can
see
that
this
request
has
been
actually
released.
So
jess
has
already
did
release
yesterday.
I
just
put
it
to
done
so.
I
don't
need
to
worry
and
yeah.
You
can
see
that
example,
that
is
pipeline
supporting
him.
B
B
A
A
B
A
B
A
B
We
still
have
a
lot
of
father
dogs
on
weekend:
I
moved
a
team
ji
come
from
almost
a
bunch
of
governance,
dogs
and
moving
the
Romanian
dogs
gradually.
Sometimes
we
had
to
use
advanced
integration,
for
example,
for
governance
board
meetings,
because
it
was
just
not
sustainable
to
keep
the
agenda
on
the
plug-in
side,
etc.
So
we
improve
and
clear
tuning
there.
B
Okay,
I
can
just
show
it
to
you
so
here's,
for
example,
governance
meeting.
So
now
we
use
combination
of
static
website
and
Google
dog,
but
Google
doesn't
buy
it.
So
even
if
you
don't
have
permissions
to
this
Google
Doc,
you
can
just
go
and
suggest
changes
directly
from
the
changes
on
your
page.
So
you
don't
really
need
to
worry
where
this
Google
Doc
is
located.
You
can
find
it
here
so
they're
more
such
things,
but
he
requires
additional
steps
for
the
migration.
A
B
B
A
B
Let's
just
spend
some
time
on
that:
okay,
I
can
just
do
the
demo
from
my
laptop
okay
mm-hmm,
so
for
those
ones
who
is
watching
this
meeting.
That
is
a
change
log
for
Gingka,
say
on
it's
hosted
here,
but
this
change
location
has
a
machine-readable
format.
So
it's
a
change.
Log
Tiamo,
which
is
hosted
on
jenkins,
hang
on.
B
So
yeah
that
is
wiki
mo
file,
this
Yama
file,
it
has
fixed
structure.
So
this
structure
includes
references
to
issues
or
requires
messages
to
be
displayed,
referenced,
sister
fees,
and
actually
there
is
additional.
There
are
additional
features.
For
example,
we
can
put
multiple
references
so
that
users
can
see
I,
just
phone
I,
referenced
and
yeah
an
example
here
put
some
pretty
remote
in
changelogs
using
this
mechanism,
and
we
are
also
working
on
referencing
contributors.
B
B
Sometimes
I
was
doing
it
in
emergency
cases
because
nobody
likes
my
change
looks
but
the
problem
that
somebody
has
to
do
that
every
release,
and
we
you
also
want
it
to
some
kind
of
automation
for
that,
because
it's
a
convenience
time
which
would
be
spent
on
better
things
like
integrating
continuing
the
quest.
So
in
order
to
do
that-
and
there
was
a
tool
which
was
originally
created
by
Ben
Daniel
back,
which
is
holding
his
courses-
doctoral
generator
change,
local
generator.
Basically,
it's
a
tool
which
was
able
to
draft
these
animals
for
political
motivations
and
littles.
B
B
To
politician,
information
and
I
was
bored,
so
ya
know
them
are
for
stable
change
ones,
but
I
will
show
weekend
so
and
this
tool
was
created
by
Daniel
back,
but
historically,
it
was
quite
difficult
to
use
because
it
was
a
bunch
of
Ruby
scripts
which
wasn't
running,
for
example,
on
my
machine
I'm,
a
heavy
user
of
Windows,
and
they
were
not
also
Iranian
modern
machines
which
Bosh
has
a
default
interpreter,
etc.
These
clips
were
still
working,
but
they
also
had
issues
with
the
fourth
month
because
they
wanted
to
present
and
they
changed
up
format
strictly.
B
So
they
look
quite
a
lot
of
formal
elections
and
yeah
in
November
and
later
I
spent
some
time.
Another
talk
to
my
bed,
so
we
can
see
that
there
are
some
releases.
I
know
the
tool
operates
in
poker
and
it
also
generates
change
logs,
which
emerge
closer
to
the
final
format.
I,
don't
know
they
used
to
be
before,
but
it
still
a
lot
of
things
to
be
done,
but
at
least
everybody
can
take
this
change
law
and
just
educate
them.
B
So
let
me
show
it
to
you,
you
don't
I
am
using
official
contingent,
so
he
is
deliberately
configured
for
this
repository
and
if
you
need
to
cut
a
change,
look,
you
basically
run
it
up
credentials
in
order
to
access
the
rest
api
to
information
about
clippers
and
they
generate
stable
changelogs.
You
need
access
to
jitter,
because
button
metadata
is
actually
in
jitter,
not
in
github.
It's
something
we
could
improve,
but
yeah.
That's
the
current
state,
so
I
run
this
tool.
B
I
didn't
pass
version
parameter
and
it
will
be
just
changing
change
lock
for
the
incoming
quickly
release
so,
basically
based
on
all
pull
requests
which
we
have
integrated
and
yeah.
The
two
can
also
generate
leaves
between
versions
if
he
needed
or
generate
a
change,
look
for
particular
version,
and
here
you
can
get
Ad
Exchange,
lock
so
which
sir
generated
automatically
here
you
can
see
that.
Well,
basically,
ever
it's
a
pull
request,
it's
fixed
by
Jessie,
which
was
most
recently
it's
a
bug,
fix
preferences,
pull
request,
issues
and
idiom
Goods
a
draft
of
the
message.
B
So
currently
the
draft
includes
a
pull
request
title
so
similar
like
we
do
in
release.
Drafter
pipelines-
and
it
also
includes
proposed
change
logs,
because
change
request,
template
project
is
called
also
includes.
Proposed
change
looks
so
we
can
share
a
drinking,
so
we
can
just
take
a
little
bit
of
quest.
I
haven't
seen
what's
this
request,
but
it's
from
Daniel
and
they
can
follow
the
template.
So
here
you
can
see
that
that
is
proposed,
a
change
log,
which
is
the
text
which
will
be
added
in
addition
to
that.
B
So
then,
when
Marc
or
somebody
who
is
a
change
log
Corp
editor,
he
will
just
take
this
text
and
process
it
to
the
final
change
log.
We
can
improve
it
later,
but
at
least
generate
some
stops
and
it
can
also
break
down
which
change
lots
it
needed,
because
their
main
purpose
of
this
format
is
that
she
is
applying
multiple
traditional
countries
each
year
and
it's
a
problem
with
release
trousers
because
for
release
drafter,
you
have
to
go
to
the
pier
title,
modify
it
in
hood,
all
the
text
etc.
B
Okay,
we
resolve
it
in
a
different
way
or
it
could
be
support.
Beliefs,
drafter,
but
it's
just
not
supported
a
moment.
So
that's
how
it
works.
But
it's
wasn't
enough
for
us,
because
we
also
wanted
to
make
it
a
part
of
continuous
delivery
pipeline
so
that
there
is
no
automation,
no
even
need
to
for
running
bed,
and
it
will
build
see
easier
to
provide
users
for
change
log
of
income
and
changes
so
that
users
can
see
what's
going
to
end,
maybe
on
Genki,
say,
or
at
least
on
github
repository.
For
that
purpose.
B
We
don't
have
a
tool.
At
the
moment
we
didn't
have
a
tool,
and
now
we
have
hug
the
most
of
our
repositories.
He
used
a
release
driver
and
for
Jenkins
you
can
see
that
was
release
drafted,
which
was
again
generating
a
almost
up,
which
is
similar
to
what
a
course
in
job
automation
tool
does,
but
he
it
was
too
generated
by
the
least
draft
means
a
lot
of
hogs
that
sent
from
the
next
weekly
release.
It
will
be
reverted,
and
now
we
needed
the
user
readable
change
logs.
So
there
is
a
grecian.
B
Duplicated
I
still
need
to
figure
out
why
but
yeah
we'll
fix
that
well
slightly
because
of
an
from
the
master
file,
but
at
least
know
that
it
will
be
a
markdown
changelog
which
is
released
immediately
after
the
Big
D
release.
So
you
don't
need
for
public
questa
towards
the
master
cheese
dog
to
be
merged,
and
now
it's
also
possible
to
see
incoming
changes.
What
we
do
a
scan
some
time
to
make
this
doctor
continue
actually
a
compatible
with
github
actions.
B
B
Yeah
what
we
have-
and
we
have
a
simple
pipeline
here-
it's
called
workflow
and
it
actually
involves
multiple
steps.
So
we
it
invokes
a
step
for
hub
release,
draft
the
one
I
wish
you
seen.
It
also
invokes
our
changelog
generator
and
then
it
invokes,
publishing
and
publishing.
I
just
started
publishing
to
release
draft.
It
cost
some
issues.
So
it's
not
something
I'm
going
to
use
at
the
moment,
but
we
also
have
from
changelog
ammo,
so
here
I
just
inject
changelog
draft,
which
is
generated
by
this
tool
into
artifact
being
generated
by
aegisub
action.
B
So
what
it
means.
If
you
go
to
actions
you
couldn't
see
that
list
of
transcription
which
has
been
triggered
on
every
push
at
the
moment
later,
we'll
increment
support
for
tech
pushes
so
that
we
can
easily
access
change
for
particular
tech.
But
right
now
you
can
just
see
that
there's
a
bunch
of
requests,
and
here,
for
example,
we
have
a
pull
request
for
the
last
meteor
because
he
ate
it.
So
it's
a
change
triggers
by
Kiki.
So,
for
example,
we
can
just
go
here
and
see
a
change
load
drugs
generated
for
the
previous
treaties.
B
So
there
is
a
bunch
of
actions
and
there
is
generate
a
mole
change
law.
So
what
you
have
seen
in
my
console-
you
can
also
see
it
here,
but
for
real
changelog
and
he
is
a
drug
being
generated
on
the
github
actions
and
after
that
that
this
draft
has
been
uploaded.
So
I'm
not
sure
what
it's
available
for
the
it's
available
for
this
kid
or
like.
A
B
One
line
below
because
it
it
is
from
Kiki,
basically
cast
abilities
and
they
changed
before
incoming
creaminess
will
be
m'kay.
All
oh
I
see
so
you
had
to
do
children
I
see
I,
misunderstood
it
right.
So
that's
why
I
want
to
implement
support
of
text
so
that
it
will
become
more
Tribble,
but
yeah
I
haven't
gone
through
it
and
go
to
it,
and
here
there
is
a
change
log
here
mode.
So
again
it's
generated
by
two.
B
We
can
just
download
it,
unfortunately,
but
it
will
be
the
same,
but
just
in
archive,
so
you
can
upload
yeah
the
camel
take
it
in
submit
a
pull
request
to
Jenkins
on
your
website.
So
this
is
what
we
have
now
what
we
can
do
it.
We
can
automatic
creation
of
pool
requests.
We
can
improve
this
formatting
so
that
there
is
pipeline
which
basically
deliver
the
request
to
Jenkins
IO.
B
We
also
can
add
support
of
text
so
that
it
will
be
explicit
way
to
oh
yeah.
This
is
just
one
of
my
next
steps
for
this
generation.
In
addition
to
that,
what
we
want
to
what
we
need
to
do
for
the
next
releases
is
the
automatically
generated
update
guidelines.
We
started
doing
some
changes
on
that
front.
For
example,
now
there
is
new
request
template,
which
include
requires
people
to
specify
a
bigger,
intense
if
it's
applicable,
so,
for
example,
he
it's
not
applicable,
but
we
can
take
requests.
B
He
we
have
too
many
labels,
but
yeah
break
going
needed.
So
there
is
a
take
him
and
you
can
see
that
7qu
request
struck
and
the
last
one
is
for
from
Jeff
Thomson
for
removal
of
agent
protocols,
the
change
they
are
announced
for
the
previous
speaker,
and
here
you
can
see
that
we
have
a
text
of
these
proposed
change
loads.
A
B
Yeah,
so
what
I
was
saying
that
these
guidelines
structured?
So
if
you
open
this
change
lock,
you
can
see
that
there
are
multiple
entries
and
this
entries
again
the
using
machine,
readable
format.
So
these
guidelines
is
generated
and
it
means
that
we
can
also
generate
templates
for
that.
So,
let's
take
a
look
and
just
playing
to
show
one
example.
A
B
A
B
A
You
very
very
much
it's
exceptional,
I
I
know
how
much
I
enjoyed
how
much
attempt
it
has
improved
since
since
I
started,
doing
it
and
how
how
nice
this
tooling,
is
looking
forward
to
the
tooling
improvements
that
are
coming.
That's
even
even
better.
Thank
you
very,
very
much
Oh
like
what
a
great
experience
it
is.
B
A
Thanks
to
given
19
it
is
it's,
it's
been
very
active.
That's
really
great!
Thank
you.
So
next
topic
that
I
had
on
the
agenda
was
Jenkins
developer,
meetups
2020
and
one
of
the
ideas
that
came
to
mind
as
I
was
looking
at.
The
configuration
is
code
plug-in
I
submitted
a
pull
request
to
it
for
a
minor
change
and
saw
a
very
impressive
array
of
tooling
that
they
automatically
invoked
that
I
had
never
used
before
so
now.
A
I
know
how
to
use
the
pen,
debat
and
I
know
how
to
use
release
drafter,
but
I've
never
used
Kota,
see
I've
I
just
started
using
sonar
source,
but
they
also
have
an
LG
TM
comm.
That
appears
to
do
to
do
security,
checks
and
I
assume
they're.
Others
services
like
that
and
my
thought
was
it
might
be
good
for
a
developer
meetup
to
bring
the
configuration,
is
code,
team
or
others
together
to
say.
A
A
Good,
so
the
idea
is
so
a
good
point.
Can
I
assume
there's
a
way
for
me
to
query
and
see
what
the
applications
are
that
are
used
and
which
plugins
are
using
those
applications?
Then
I
could
potentially
reach
out
to
the
authors,
the
maintainer
czar,
those
plugins
and
say
hey.
Would
you
like
to
join
us
for
this
session
and
tell
us
how
you're
benefiting
from
this?
Well.
B
B
A
Will
do
and
so
that
that
feels
like
to
me
a
very
interesting
and
I'm,
not
sure
we
could
assemble
it
in
the
roughly
one
week
that
we
have
prior
to
me
going
offline
for
about
a
week
to
do
FOSDEM.
So
I
assume
this
will
be
a
February
or
later
developer
Meetup,
but
I
would
like
that
and
I'm
happy
to
convene
it.
I
would
I
would
love
to
moderate
it
and
gather
people
together.
Well,.
B
If
you
need
to
meet
up
in
one
week,
I
can
do
a
little
dependable,
because
I
have
everything
to
run
it
if
needed,
so
it
will
be
like
Cydia
shot
a
meet-up,
maybe
a
30,
to
40
minutes
with
all
the
value
of
discussion,
but
I
can
do
it
next
week,
yeah
and
for
the
rest
of
the
tools.
Here,
you
can
just
stab
link
it
in
the
background,
just
roughly
something
we
already
presented.
A
B
A
B
A
B
A
You
doing
all
right
so
Google
season
of
darks
we
are,
we
are.
We
are
actually
pastime
Oh,
like
I'm
prone
to
say,
that's
shift,
google
season
of
docks
till
next
week's
meeting.
We
can't
forget
about
it,
then
I
did
want
to
go
over
a
brief
look
at
the
the
data
from
the
contributors
and
contributions
really
elegant.
A
Thanks
for
your
work
on
the
time
from
poor
request
to
engagement,
we
are
averaging
under
eighty
five
percent
of
our
pull
requests,
get
some
acknowledgement
well
within
one
day,
and
we
just
went
on
the
latest
bump
to
slightly
over
one
day,
but
our
our
mean
time
for
the
fiftieth
percentile
is
very
nicely
in
the
one
hour
that
the
pull
request
backlog
on
Jenkins.
That
IO
is
looking
really
good
time.
Think
er
opened
emerge
likewise,
is
looking
good.
A
B
Nothing
from
my
side
so
yeah
one,
not
fine.
One
interesting
start,
which
I
posted
every
New,
Year
blog
posting-
that
we've
had
187
documentation
contributors
just
a
during
the
last
quarter,
so
it
includes
basically
everybody
or
modified
markdown
or
ski
doc,
files
within
Jenkins
elation
with
them
gingka
sion.
So
it's
not
an
accurate
number,
but
you
provide
some
approximation.
A
Just
for
your
stats
thanks
very
much!
Thank
you.
Thank
you
all
right,
I'm
gonna
go
ahead.
I,
think
we're
done.
I'm
gonna
go
ahead
and
call
this
as
a
done
session.
Thanks
very
very
much
for
your
time.
Oleg
and
notes
are
here.
The
recording
will
be
posted
to
the
YouTube
playlist
for
the
documentation
special
interest
group
thanks.
Everybody
thank.