►
From YouTube: 2022 08 11 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Today
we
have
quite
a
bit
of
agenda
some
action
items
that
mark
can
provide
an
update
for
we
have
our
google
summer
of
code
participant
pahan
in
the
meeting,
so
hopefully
he'll
be
willing
to
share
some
updates
and
anything
new
that
he
might
have
for
us.
There.
A
We
have
the
september
lts
the
jenkins
2.36
1.1
release
coming
out,
and
we
have
the
changelog
upgrade
guide
and
a
blog
post
to
make
for
it.
There
are
a
lot
of
changes,
so
we
have
to
address
all
those
and
make
sure
it's
very
clear.
A
A
The
next
lts
baseline
again,
the
one
that's
going
to
be
coming
out
in
september,
will
require
java
11..
So
that's
another
big
piece
of
it
that
we'll
have
to
make
sure
our
users
are
aware
of
that's
going
to
come
along
with
a
blog
post,
the
upgrade
guide,
the
change
log
itself.
We're
also
going
to
this
is
java.
17
support
is
also
going
to
be
coming
as
a
an
option.
A
A
It's
got
some
feedback
and
we'd
like
to
get
some
further
discussion
going
on
ideas,
topics
or
maybe
additional
items
that
we
can
throw
in
there
to
help
make
it
a
better
page.
A
I
threw
a
quick
note
in
here
about
the
blue
ocean
status
statement
because
well
has
been
implemented
in
most
of
the
blue
ocean
docs
pages.
There
are
still
a
couple
places
that
it
needs
to
be
added.
I
found
that
one
of
the
tutorial
pages
needed
an
additional
statement
added
and
the
docker
hub
page
still
needs
to
get
updated
and,
finally,
just
an
idea
of
change.
Log
entries
coming
from
multiple
repositories,
which
mark
tell
us
a
little
bit
more
about
and
just
what
that
is
going
to
entail.
A
So
let's
go
ahead
and
get
started
these
action
items
mark.
Do
you
have
anything
that
you'd
like
to
share
on
the
blog
posts
and
mailing
lists.
A
Okay,
great,
thank
you
so
much
all
right.
Would
you
like
to
take
us
through
the
project
and
anything
that
you've
been
working
on
last
week.
C
Sure,
thanks
a
lot
so
since
last
week,
the
first
thing
I
did
was
move
the
tool
to
java
11
as
mark
machine
in
the
last
minute.
So
that
reminded
me-
and
I
moved
it
to
java
11.
So
that
is
done
and
the
issue
that
we
were
facing
in
the
steps.
So
we
were
losing
out
some
plugins.
C
So
I
I
found
out
the
issue,
and
that
was
basically
with
the
artifact
that
we
were
using
the
new
artifact
and
that
has
been
changed
and
released
and
the
new
documentation
is
up
to
the
mark
and
the
main
thing
that
has
been
done
this
week
was
the
good
progress
was
about
the
project's
main
aim.
That
was
separating
the
documentation
of
new
pages.
So
now
I'm
able
to
configure
the
paragraphs
that
I
want
into
a
config
file
and
it's
automatically
separating
those
particular
sections
out
from
the
documentation.
C
This
is
visible
all
right,
so
I'll
show
you
what
I've
done.
I
I
hope
my
vs4
is
also
visible,
yep
right,
no
problem
there,
okay,
so,
basically
now
what
we
can
do
is
we
can
the
user
can
enter
any
any
documentation?
Maintain
a
government
could
mention
these
params
in
the
config
file
and
the
process.
C
Those
particular
sections
will
be
removed
now,
and
there
will
be
a
hyperlink
to
these
new
pages
that
we
have
created.
So
let
me
show
you
what
I've
done
so
I
currently
put
these
three
parameters
inside
the
config
file,
so
that
is
first
class.
Get
scm
second
is
first
and
third,
is
the
class
multi-stm,
so
I'll
show
you
the
results
that
are
obtained
not
to
work
much
on
the
ui
of
the
links
and
all
but
yeah.
C
So
you
click
on
that
and
now
you
see
the
scm
documentation
is
lost
and
you
can
basically
click
on
it
and
it
will
lead
you
onto
a
new
page
and
which
will
now
contain
the
get
stm
documentation,
the
entire
documentation
that
was
coming
under
get
stm
and
the
beautiful
thing
about
this
is
it
has
this.
Is
this
will
happen
everywhere?
The
git
same
documentation
was
coming
out
to
be
repeated,
so
we
have
saved
a
whole
lot
of
space
that
was
that
was
being
occupied
by
this
and
I'll.
C
Show
you
the
example
for
this
as
well.
So
multi
scm
was
in
itself
another
class
which
had
these
parameters
inside
it
again,
so
it
also
had
to
get
scm
so
we
had
to.
We
had
to
basically
click
through
and
now,
but
now,
when
we
click
on
this,
it
will
lead
us.
C
Same
page,
so,
if
you,
if
you
can
see
both
these
urls
are
the
same,
so
it
is
referencing
to
the
same
page.
So
I
have
implemented
that
to
every
hierarchy
possible.
So
this
can
be
basically
understood
for
other
things,
also,
so
for
perforce.
Also,
I've
done
the
same
thing
and
everywhere
the
first
parameters
occurring.
You
can
see
that
the
new
page
is
coming
out
to
me,
the
one
that
I've
separated
out.
C
So
basically,
this
will
help
us
manually
configure
the
parts
that
we
want
to
separate
out,
because
it's
not
required
to
separate
our
smaller,
smaller
parameters
such
as
this
one.
So
there
is
no
actual
use
of
creating
a
new
page
for
this.
So
the
way
that
I
could
I
thought
was
to
go
for
the
manual
configuration
rather
than
the
automated
one.
I
also
tried
the
automated
one
and
I've
also
put
a
threshold
in
this.
C
So
now,
for
example,
if
someone
mentions
a
world
scm
by
mistake
in
the
conflict
file,
it
will
first
of
all
check
whether
the
vault
scm,
in
fact,
has
that
much
documentation
that
it
has
to
be
separated.
So
the
threshold
number
that
I've
said
is
500
lines
and
if
it
does
not
cross
that
it
will
not
separate
it
out
and
yeah.
C
So
basically,
there
are
some
things
that
the
person
will
have
to
keep
in
mind
while
entering
values
in
the
config
file,
and
I
am
going
to
document
that
once
the
pull
request
gets
merged
along
with
the
pull
request,
maybe
I'll
build
a
readme
that
goes
along
with
the
repository
so
that
the
things
are
consistent
and
yeah,
so
I'll,
basically,
work
on
refining
the
class,
bringing
some
more
modularity
and
improving
the
variable
names.
Putting
some
comments
so
till
next
week
I'll
try
to
get
this
for
request
merged.
B
A
B
B
C
B
B
C
Reason
why
I
shifted
to
the
click
mechanism
was.
It
was
looking
inconsistent,
so
basically
opening
up
a
page
like
this
and
seeing
that
separate
blue
things
sitting
right
there,
I'm
sure
which
one
looks
better
and
I
I
was
going
to
ask
that
in
the
next
box
office
hours
about
the
ui
part.
So
I
didn't
focus
much
on
that,
but
I.
B
C
That
it
was
looking
slightly
looking
off
if
we
have
a
blue
link
sitting
there
rather
than
having
so
user.
Whoever
wants
to
see
the
multi
symbol
or
obviously
press
on
this
and
they'll
see
oh
there's
a
link
over
here
and
then
they
can
basically
click
and
go
on
so
yeah.
B
B
Okay,
thank
you.
I
was
just
trying
to
understand
so
so
what
you've?
What
you've
done
it
looks
like
is
deduplicated
so
that
getscm,
instead
of
being
replicated
multiple
times
with
all
of
the
content
it's
got
is
now
in
a
single
location
and
yet
their
navigation.
Still,
they
click
that
plus
sign,
and
it
now
gives
them
one
one
more
click
and
they
have
the
page.
C
Right
so
this
is
basically
applicable
for
every
step,
so
I'll
show
you
one
more
example:
the
big
one
pipeline,
groovy
libraries,
so
it
basically,
this
itself
has
around
three
to
two
to
three
occurrences
of
gate
scm
and
once
we
configure
it
properly
a
lot
of
content
from
the
space.
So,
as
you
can
see,
the
loading
time
is
already
slightly
reduced
from
what
it
was
before
the
javascript
acting
time.
So
I'll
show
you
an
example
from
a
cm
and
again
if
we
go
ahead
and
click
yeah.
C
This
is
the
link
that
we
want
to
see
so
yeah
again
the
same
page.
So,
basically
the
way
I'm
doing
it
right
now
is
not
very
efficient.
I
would
say,
but
it's
not
taking
a
lot
of
time.
So
I
was
surprised
by
how
fast
this
is
happening.
What
I'm
doing
right
now
is
I'm
for
every
keyboard
that
we
have
entered
in
this
file.
C
I
am
hydrating
through
all
the
ascii
docs
and
looking
for
the
first
occurrence
of
that
particular
particular
parameter,
and
then,
and
once
we
are
creating
that
new
ascii
dock,
I
am
not
creating
it
again,
I'm
not
overwriting
it,
but
I
am
iterating
through
all
the
ascii
docs
and
creating
that
duplicates
minus
the
parameter
that
we
have
separated
out.
So
basically,
all
the
documents
that
we
see
here
are
the
duplicates
after
running
one
loop.
C
These
are
the
duplicates
of
their
previous
version,
but
for
the
ones
that
do
not
have
git
has
same,
for
example,
the
exact
same
thing
has
been
copied
on,
so
this
is
not
very
efficient
to
do,
but
this
was
not
taking
a
lot
of
time
actually
so
for
three
parameters,
the
running
the
entire
build
was
was
taking
around
nine
to
ten
seconds,
and
that
is
not
the
bottleneck
because
we
want
to
generate
the
documents
first
so
to
ascii.
C
B
That
that's
impressive,
so
you
have
just
proven
once
again
that
there
are
times
when
brute
force
search
is
the
best
way
to
do
it.
Excellent,
so
you
did
it
you're.
You
really
are
truly
iterating
more
more
times
than
absolutely
necessary
and
you've
shown.
Who
cares
that
you
iterate
more
times
than
necessary?
It's
still
faster
than
the
than
other
parts
of
the
conversion
process.
Well
done.
A
B
A
A
B
Look,
we
switched
from
div
based
layout
to
table
based
layout
18
months
ago,
and
then
we
switched
here
and
we
switched
here
and
we
or
we
we
did
java
java
seven
to
eight
this
many
years
ago.
Then
we
did
tables
to
divs.
Then
we
did
this
ui
set
of
enhancements
issue.
I
so
story
after
story
and
then
conclude
with
and
now
the
next
release
we'll
do.
B
B
A
Yeah
I
mean
if
anything
too,
we
could
maybe
post
it
to
two
separate
blog
posts
or
maybe
split
it
up
a
little
bit.
So
one
is
for
the
java,
11
changes
and
coming
and
then
jenkins
retrospective
kind
of
topic.
I
guess,
but
right
yeah
either
way.
I
think
that
would
be
yeah.
That's
totally
yeah.
I
like
that
idea.
A
lot.
C
A
A
Okay,
great
anything
else
on
that
one
mark.
A
Great,
so
the
next
item
on
the
list
is
the
search
improvements
for
jenkins.io,
and
I
know
we've
talked
about
it
mark
I
I
we've
said:
we've
discussed
how
the
search
results
may
not
bring
up
the
expected
results.
Searching
for
upgrade
doesn't
show
the
upgrade
guides,
and
this
is
due
to
algolia
needing
to
be
upgraded.
A
Currently
it's
on
the
legacy
scraper
and
it
needs
to
be
updated
to
the
newest
format
in
version
and
if
I
recall
it's
either
yourself
or
gavin,
that
would
need
to
do
this.
Is
that
still
the
case.
A
Got
it
and
is
there
any
you
have
the
github
issue
as
well
to
track
all
this
progress,
so
that's
already
made.
Is
there
anything
else
that
we
should
be
aware
of
for
this,
or
is
it
just
something
that's
going
to
be
coming
down
the
pipeline
at
some
point,
yeah.
B
C
A
The
next
lts
baseline,
we
discussed
that
it's
going
to
be
requiring
java
11..
The
weekly
release
at
the
end
of
june
already
requires
java
11
and
has
dropped
java
8
support.
So
now
this
will
be
mirroring
that
something
I'll
also
need
to
do
is
make
sure
to
update
the
existing
blue
jenkins
documentation
so
that
there
isn't
a
discrepancy
for
the
weekly
versus
the
lts.
A
So
that's
something
I'll
need
to
update,
but
that'll
be
a
simple
removal.
A
The
upgrade
guide
and
changelog
are
going
gonna
get
started
within
the
next
couple
hours
by
myself
and
mark
either
in
this
meeting
or
after
the
fact.
So
that
will
have
progress
made
and
we
will
be
able
to
continue
working
on
that
as
we
approach
the
release
date.
A
The
commercial
support,
page
proposal
that
was
submitted
by
gavin
logan
still
looking
for
ideas,
discussions
feedback
on
this.
If
you
feel
strongly
in
any
way,
you
should
perform
about
support,
making
a
support,
page
or
being
able
to
reach
support.
Any
ideas
are
welcome
here,
and
you
know
this
is
something
that
we
want
to
improve
and
make
it
a
lot
easier
for
folks
to
be
able
to
reach
support
vendors
that
we
work
with
whether
it's
support
like
vendor
support
or
commercial
vendors
regardless.
A
We
want
to
be
able
to
have
just
really
helpful
information
available
to
the
jenkins
community,
and
this
is
one
of
the
best
ways
that
we
can
go
about
doing
that
for
them
we
do
need
some
more
information
from
the
vendors
themselves
so
that
we
can
provide
a
better
visualization
for
that
what
kind
of
offerings
they
have
their
location.
Things
like
that,
so
that
we
can
make
sure
people
are
getting
the
most
out
of
this
site
and
mark
did
you
want.
B
A
Okay,
I
was
just
going
to
try
and
find
it
to
putting
it
up.
B
A
So
yeah,
so
it's
a
really
rough
idea
right
now,
but
something
like
this,
where
we
have
those
times
that
are
available
where
offerings
they
have
community
involvement,
which
is
great,
so
you
can
see
what
plugins
they
work
with,
and
the
community
members
that
are
part
of
that
group.
So
that's
actually
that's
even
more
than
the
brazil
last
time
I
saw
it.
So
that's
awesome.
B
Well,
then,
if
you'll
click,
the
back
link
up
at
the
top
left
top
left
of
the
page,
so
there
we
go
so
so
here
we've
got
a
concept
and
it
might
be
cloudbees
and
red
hat.
It
might
include
one
or
more
additional
vendors
that
are
doing
commercial
products
based
on
jenkins
or
doing
support
for
jenkins
at
this
level.
And
then
you
click
through
one
of
the
requests
that
I
had
was
hey.
B
B
A
Right
so
yeah
so
yeah,
based
on
all
that
again,
any
feedback
is
welcome.
Here.
The
link
is
in
the
agenda
for
this
idea
and
I
can
post
it
in
the
getter
channel.
If
anyone
else
would
love
to
check
in
on
it
or
just
read
through
it,
even
you
don't
have
to
make
suggestions.
You
can
just
find
out
what's
being
discussed.
A
Okay,
okay,
yeah,
the
so
blue
ocean
status
statement
is
something
that
came
up
earlier
this
weekend
of
last
week,
we've
added
it
to
more
pages
and
places
since
it
was
missing
from
locations
such
as
the
actual
blue
ocean
plug-in
page
itself.
A
The
docker
hub
page
needs
a
status
update
added
for
the
blue
ocean
container.
It's
a
different
process
of
updating,
though,
and
we
need
to
make
sure
we
have
the
right
permissions
and
ability
to
go
ahead
and
update
that
before
we
can
make
that
update
and
then
something
that
I
noticed
when
I
was
looking
through.
Is
that
a
couple
of
the
tutorial
pages
don't
have
the
status
statement
on
there
so
I'll
be
adding
that
later
this
week,
early
next
week
to
make
sure
that
everything
is
aligned
mark?
A
And
then
next
week
mark
is
going
to
be
on
vacation,
so
he
will
not
be
joining
us
for
the
meeting
also
be
here.
So
we
will
still
happen
to
you
and
we're
going
to
check
in
with
damian
to
see
if
he
can
host
it.
For
us.
B
Well,
we
need
to
well,
I
guess
what
I'm
raising
is.
We
need
somebody,
I'm
not
sure
that
we've
got
enough
time
to
get
you
permission
to
be
given
the
access
to
the
zoom
account,
and
so
we
need
somebody
who
already
has
it.
We
know
that
damien
has
it,
I'm
pretty
sure
that
alyssa
tong
has
it
as
another
possibility
yeah,
and
so
it's
if
you're,
okay
with
it
kevin,
can
you
negotiate
with
one
of
them
to
see
if
you
can
get
some
help
from
them
to
to
do
it?
A
A
Okay,
yeah,
so
then
I'll
check
with
you.
What's
up
about
that
and
yeah
that
way,
we
can
have
a
host
and
everything
and
I'll
still
be
here
available
for
the
meeting.
So
it
will
still
happen,
but
yeah
we'll
just
have
to
have
someone
helping
us
out
with
that.
So
all
right
great,
so
we've
gotten
through
the
agenda
and
action
items.
Is
there
anything
else
that
we'd
like
to
touch
base
on
answer
the
agenda?
Any
comments
about.
A
Okay
and
mark
and
I'll
start
talking
about
working
on
the
changelog
upgrade
guide
between
three
six
one,
one
on
our
own
separately
from
this.
So
next
time
we'll
be
able
to
share
some
further
information
about
that.
A
B
B
B
We
just
need
to
highlight:
we've
taught
people
in
past
years
how
to
do
that
yeah,
it's
an
an
easy
one
to
teach
again
hey.
This
is
how
you
make
that
conversion
yeah.
That's.
B
Others
there
is
the
well
there
are,
I'm
not
sure
we
are
we're
as
successful
in
the
past
with
wiki
page
conversions,
because
we've
still
got
a
number
of
them
that
are
sitting,
because
it
requires
a
level
of
expertise
that
most
of
these
new
contributors
don't
have.
So,
I
would
say,
intentionally
exclude
wiki
page
conversion
from
hacktoberfest,
because
it's
not
been
successful
in
the
past
too
much
knowledge
required.
B
What
what
when
I
say,
wiki
page
conversion,
what
I
mean
is
documentation,
wiki
pages,
so
these
were
pages
that
talked
about
core
jenkins
concepts
or
important
things
that
you
would
do
or
not
do,
and
many
of
them
are
by
now
five
or
six
years
old
and
so
out
of
date,
and
so
it
was
so
filled
with
errors
that
a
person
attempting
to
convert
them
will
bring
the
errors
forward
and
not
realize
it.
And
then
it's
up
to
the
reviewers.
All
of
a
sudden,
the
reviewers
are
now
doing
all
the
work
of
doing
the
port.
B
A
Yeah,
I
was
thinking
too
mark.
I
know
that
I
had
taken
over
for
the
sheet
code,
africa,
the
screenshot
updates
in
a
lot
of
areas.
Did
the
we'll
be
able
to
finish
like
the
inclusive
naming
updates
and
that
sort
of
stuff.
I
know
I've
still
found
a
couple
areas
where,
like
the
screenshots
for
those
could
be
updated,
but
I
was
talking
to
dan
about
some
other
items
recently
that
maybe
we
can
discuss
further
and
add
to
the
list
of
what
should
be
changed
so.
B
Yeah
the
the
problem
for
me
with
inclusive
naming
updates
is
it
needs.
It
needs
a
level
of
technical
discretion
that
many
of
these
hacktoberfest
contributors
don't
have
they're.
If
we
tell
them,
you
can
convert
everything
except
java
symbols,
they
will
still
inadvertently
convert
java
symbols.
We
had
that
with
the
contributon
people.
They
were
saying.
Oh
look,
there's
here's
this
java
source
code.
I
need
to
convert
the
word
master
to
controller
and
what
that
did
was
break
the
api
right,
and
so
they
they.
It
was
actually
a
net
negative
there.
So
I'd
much.
B
Rather,
we
focus
on
on
just
the
at
least
right
now.
My
mental
model
is
just
the
the
wiki
to
mark
down.
Conversion
for
plugins
is
already
there.
There
are
still
800
plugins
that
need
conversion,
so
there's
no
lack
of
work
to
be
done
there
and
and
some
of
those
plug-ins
that
need
conversion
have
as
many
as
10
or
20
000
installations.
B
A
I
can't
think
of
anything
right
now
mark,
but
I'm
sure
something
will
come
up
as
we
continue
working
on
this
stuff,
so
yeah
awesome.
Well,
I
think
that
covers
everything
for
today
we'll
go
ahead
and
stop
the
recording
and
it
will
be
available.