►
From YouTube: 2022 08 25 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
It's
recording
now,
thank
you
so
welcome.
This
is
the
august
25th
edition
of
jenkins
doc's
office
hours
2022.
today
on
our
agenda.
We've
got
action
items
google
summer
of
code.
If
the
han
wants
to
share
any
updates
there.
A
The
september
lts
aka
jenkins
version
2.36,
1.1,
search
improvements
for
jenkins.io,
the
commercial
support,
page
proposal,
the
current
bluehead
blue
ocean
admonition
status
and
then,
if,
if
we
have
time
a
couple
of
other
items
here
about
chain
log
entries
and
the
hacktoberfest,
so
first
things
first
mark's
been
able
to
take
care
of
the
she
codeafrica
contributon
results,
blog
post.
A
Everything
else
is
still
mean
to
is
still
needed
to
be
taken
care
of,
but
he
is
out
of
office
this
week
or
today,
which
is
why
we're
joined
by
alyssa
who's,
helping
with
hosting
and
yeah
he'll
have
more
when
he
gets
back
on.
Do
you
want
to
share
any
google
summer
code
updates.
B
Hi,
yes,
sure
so
this
last
week
I've
been
working
on
completing
the
tests
for
these
processing
layer,
so
those
tests
are
complete
and
kristin
has
given
me
a
couple
more
tests
to
write,
so
those
will
be
completed
by
the
end
of
the
week
and
after
that
I
think,
we'll
be
almost
set
on
completing
the
google
summary
of
code,
the
entire
project
plan.
So
nothing
would
be
left
on
our
to-do
list
and
there
are
a
couple
of
things.
Small
things
that
we
have
to
look
after
one
is
the
cleanup
that
I
mentioned
last
week.
B
So
the
website
you
know
we
want
to
see
if
that
changes,
the
content
and
after
that,
we'd
also
like
to
get
some
examples
of
the
experimental
plug-in
releases
that
is
mentioned
in
the
issue
on
the
five-time
step
stock
repository.
B
So
we
want
to
get
some
examples
for
that,
so
that
we
can
go
ahead
and
rectify
that
issue
if
it's
still
person,
so
we
were
not
able
to
find
an
example
for
that.
So
we
are
not
sure
if
that
is
even
an
issue
as
of
now,
because
the
example
that
mark
mentioned
is
is
not
an
experimental
plugin
anymore,
so
it
has
been
converted
into
proper
plugin
and
so
yeah.
B
We
have
to
look
into
that
and
we
have
to
do
some
research
on
the
side
of
getting
the
plug-in
name
in
front
of
the
classes,
for
example,
for
classical
cm.
We
want
to
see
that
it
is
coming
from
get
plug-in
now
that
is
more
on
the
resource
side,
since
we
don't
have
proper
descriptors
for
those
parameters
but
yeah
just
something
that
is
ongoing,
but
it's
not
a
blocker
for
a
gsoc
project
as
that's
what
it
is
concerned,
and
I
have
not
changed
the
ui
of
the
links
as
much
the
after
clicking
on
the
expand
button.
B
Share
so
this
is
how
it
looks
now
so
earlier
the
links
were
getting
slightly
larger,
but
now
they
go
uniformly
with
the
code
font
style.
So
basically
we
can
just
see
that
happening
everywhere
and
as
a
part
of
the
project.
I
would
also
like
to
create
a
configuration
file
as
a
starting
point
so
that
we
have
some
result
of
this
processing
there.
B
So
easing
up
some
work
from
the
docs
maintainers
I'll,
try
to
add
around
nine
to
ten
parameters
in
the
config
file
itself,
so
that
we
see
some
results
in
the
reduction
of
the
size
of
the
page
loading
speed.
B
So
I
think
it
will
be
a
good
starting
point
for
the
process,
the
new
feature
that
is
added
and
yeah.
I
don't
think,
there's
anything
else.
Thanks
a
lot.
A
Thank
you
very
much
bihar.
This
is
there
anything
else
that
we
can
do
to
help
with
what
you're
looking
for
as
far
as
the
examples
go
or
any
of
the
other
items
here.
B
Yes,
so
we
were
actually
looking
for
help
in
identifying
any
experimental
plug-in
that
could
come
up
in
the
pipeline
steps
reference
so
any
if
anyone
is
able
to
find
an
example.
For
that,
please
let
us
know,
via
the
talks
or
twitter
channel
or
anywhere
possible
and
I'll.
A
B
Look
at
the
issue
that
that
was
that
I
was
talking
about
in
this
space.
So
after.
A
Some
time,
okay,
great
awesome,
thank
you
so
much
and
is
the
link
in
getter
already,
or
would
you
be
able
to
share
that.
B
I'll
I'll
share
it
in
the
chat
or
I'll.
Add
it
as
a
comment,
maybe
I'll
hyperlink,
the
exciting
writing.
B
A
So
there
are
the
changelog
and
the
upgrade
guide
are
essentially
complete.
I've
been
able
to
compile
everything,
get
all
the
back
ports
in
there.
We've
had
some
items
come
up
with
open,
jdk
11
that
we're
able
to
add
in
there
and
make
sure
people
are
aware,
as
it
does
affect
the
latest
the
release
coming
up.
There
are
already
resolutions
in
place.
We
just
didn't
get
a
chance
to
get
to
them
prior
to
the
release,
so
they'll
be
coming
down
the
pipeline
soon
enough.
A
On
top
of
that,
the
faith
is
looking
for
a
blog
post
for
the
cdf
blog.
This
would
be
a
little
different
from
the
required
java,
11
blog
post.
That
basil
had
contributed
recently,
but
we'll
probably
draw
a
lot
from
that.
It's
a
little
higher
level
and
more
about
the
innovations
and
major
changes.
Jenkins
has
had
over
the
years
that
gets
us
to
today
and
juggle
11.,
and
it
will
also
provide
java
17
support.
A
A
There
is
plans
to
improve
the
search
results
that
show
up
on
jenkins.io.
We
use
algolia,
but
right
now
the
jenkins
io
algolia
is
a
little
older
and
needs
to
be
upgraded
from
the
legacy.
Scraper
that'll
take
some
time,
and
it
looks
as
though
someone
with
specific
credentials
will
need
to
take
care
of
this
aka
either
mark
or
gavin
mogan
mark
has
created
a
github
issue
for
it,
but
there
has
not
been
any
movement
on
it
as
of
yet
so
there
there's
nothing
of
note
in
the
issue
itself.
A
A
We've
talked
a
few.
We've
talked
over
the
last
few
weeks
months
about
the
commercial
support
page
proposal
that
gavin
has
submitted
and
shared
still
looking
for
feedback
still
looking
for
any
kind
of
ideas.
Discussions
suggestions,
anything
at
all
for
that.
If
you
have
any
proposals
or
ideas
on
how
a
support
page
would
be
helpful
to
vendors,
commercial,
convent,
commercial
vendors
or
support
vendors
feel
free
to
share
it
there.
It's
it's
available
to
anyone.
So
lines
of
communication
are
open.
A
We
have
the
blue
ocean
admonition
so
right
now,
it's
actually
been
compiled
into
all
the
jenkins
pages.
We've
got
it
in
the
tutorials.
We've
got
it
in
the
blue
ocean
docs.
A
We
are
looking
to
put
it
into
the
plugin
documentation
which
basil
has
done
already,
and
then
we
still
need
to
try
and
figure
out
how
to
add
it
to
the
docker
hub
entry
for
the
blue
ocean
container.
This
is
something
a
little
outside
of
the
jenkins
project,
but
connects
directly
to
it.
So
it's
just
a
little
bit
more
involved
and
then
in
here
we,
the
idea
would
be
we
have
to.
We
have
a
link
to
the
official
docs
and
in
the
embedded
name,
admonition
as
well.
A
The
change
log
entries
and
multiple
repositories,
just
a
matter
of
fact,
if
we
get
multiple
change
log
entries
from
multiple
repositories,
anytime,
there's
a
you-
know,
wide
sweeping
release
mark's
going
to
check
in
with
the
developer
list
about
potential
solutions
from
that
or
best
ways
to
combine
all
those
into
less
entries,
and
then
last
in
the
list
here
is
just
oktoberfest.
Documentation
contribute
contributions.