►
From YouTube: 2022 07 21 Docs Office Hours
Description
Documentation office hours 21 July 2022. Topics included:
* News
* Look and feel improvements for www.jenkins.io
* Blue ocean status message
* Search improvements for www.jenkins.io
* Commercial support page
* Changelog entries from multiple repositories
A
B
A
Site
commercial
support,
page
proposal
and
upcoming
change
log
and
look
and
feel
improvements
poll
requests
that
I
think
actually
I'd
like
to
adjust
this
one
to
be
higher
on
the
agenda
so
that
we
make
sure
we
get
to
it
because
it's,
I
think
it's
a
really
important
one
all
right
and
this
one
probably
should
go
up
actually
yeah.
What
that
really
means
is
this
one
can
go
down.
A
Like
that,
okay,
so
there's
a
draft
proposal
for
an
agenda.
Anything
bruno
you
need
to
add
no
thank
you
mom.
Okay,
then,
first
items
on
the
action
items,
I'm
sorry
to
report
that
I
still
have
not
made
progress
on
my
action
items
and
it's
going
to
be
several
weeks
before
I
can
they're.
Just
these
things
have
to
wait
on
news
jenkins,
2.360
released
and
it
has
a
new
configuration
page
for
I
think
it's
freestyle
projects.
A
Yeah,
it's
it!
It
moves
the
moves.
The
navigation
links,
the
in-page
navigation
links
from
the
top
bar
to
the
left.
I
guess
exactly
to
the
side
panel,
where
they're
much
easier
to
see
much
easier
to
detect
and
and
it
I
like
the
look
very
much
now.
For
instance,
the
folders
plug-in
does
not
yet
have
that
change.
A
A
Then
we
had
pipel
google
summer
of
code
presentations
today,
including
a
presentation
by
vihan
fora
on
pipeline
step
stock
generator
and
thanks
very
much
to
vihan
we're
already
seeing
improvements
on
the
the
pipeline
steps
pages
and
very
grateful
to
him.
For
that
now,
we've
got
a
a
new
topic
here
or
a
topic
we
had
before
the
look
and
feel
improvements.
Page
pull
request
has
been
through
some
iterations
and
I
think
it's,
I
really
do
think
it's
ready
to
merge.
A
Let's
do
a
look
at
it
just
to
see
here,
so
this
page
notice,
the
the
gradient
blues
and
the
consistent
color
for
the
download
button
here,
the
yes,
the
jumbotron
continues
to
navigate
and
we
retain
the
other
layouts.
Now
one
of
the
things
that
has
may
have
to
change
is
the
plug-in
site
may
need.
We
may
need
to
coordinate
with
it
as
to
how
we
whoops.
I
have
to
go
this
direction
there,
because
the
plug-in
site
borrows
or
or
grabs
content
from
jenkins.io
to
keep
its
look
and
feel
consistent.
A
B
Yes,
I
totally
agree
with
you.
You
should
do
that
if
you
have
time
to
yeah
community
jenkins.aop
is
a
place
to
be
when
talking
about
ui
changes
and
so
on.
I
think
a
lot
of
our
users
are
in
communities
and
things
that
I,
of
course,
are
also
in
guitar.
But,
yes,
we
have
a
discussion
with
think
that
state
that
we
can
have
a
look
at
when
we're
not
in
the
craze
of
discussing
yeah.
A
A
A
So
in
this
case,
if
we
look
at
the
documentation
on
blue
ocean,
it's
not
the
disclaimer
is
not
in
the
first
page,
and
so
this
is
one
where
I
would
want
it
in
this
page
and
kevin
didn't
put
it
there
yet.
So
I
think
it
should
be
here.
Okay
and
I'd.
I'd
almost
think
that
we
want
it
very
high
on
this
page,
possibly
even
before
the
what
is
blue
ocean
or
inside
the.
What
is
blue
ocean,
I'm
not
sure
which
of
those.
B
A
Right,
exactly
and
and
the
fact
that
it
is
still
very
much
usable
and
very
very
much
we
want
to
continue
describing
it.
We
don't
want
to
take
away
these
pages,
for
instance
on
the
creating
a
pipeline
page
here
I
think
he
chose
to.
Where
did
he
insert
it?
I
don't
see
it
on
this
page
actually
interesting.
A
So
I
know,
for
instance,
he
did
it
on
this
page
on
the
dashboard
page.
But
for
me
the
surprise
was
where
he
put,
it
was
below
the
first
screenshot,
so
it's
it
ends
up
below
the
fold.
For
you
know
it
requires
page
down
before
you
see
it,
and
I
think
we
probably
want
it
very
early
in
the
page.
The
trouble
is,
I'm
not
sure
if
we
want
it
as
the
first
text
that
they
see.
Maybe
it
is
the
first
text
they
see.
B
A
Good,
all
right,
so
your
tendency
is
put
it
put
it
very
early,
that's
mine
as
well.
I
think
it's
worth
asking
others.
Let's
see
pipeline
editors,
another
one
where
he
inserted
it
and
here
again
he
inserted
it
below
the
first
video
and
I'm
prone
to
want
it
above
maybe
it
should
be
not
the
first
paragraph
but
after
the
first
paragraph
yeah,
but
I
really
do
I
like
it
much
better
there
than
below
the
first
video
yeah,
because.
A
B
A
A
A
A
B
A
Exactly
so
so,
or
to
upgrading
java
from
java
8
to
java
11.
all
more
relevant
than
any
of
the
the
results
that
came
from
this
search
and
what
what
gavin
then
did
is
he
asked
our
search
provider
algolia
who's
donated
the
search
engine
for
us,
what
we
can
do
to
improve
it,
and
their
answer
was:
oh,
oh
you're
running
an
outdated,
outdated
configuration.
You
need
to
migrate
from
the
legacy
scraper
to
their
new
new
technique.
What
it
is
is
we
use
they've
donated
a
facility
called
doc
search.
A
This
is
a
facility
they
provide
to
open
source
projects
where
the
open
source
project
just
informs
algolia
we're
willing
to
have
you
scrape
our
site
and
algolia
will
maintain
all
the
indexes
and
everything
without
our
infrastructure
without
jenkins
infrastructure.
Okay,
so
so
they've
changed,
they've
they've
upgraded
migrated,
but
we
haven't
done
it
yet.
So
this
is
sort
of
a
development
task
that
involves
some
integration
and-
and
we
need
need
some
time
to
follow
their
directions.
A
B
A
A
For
this
upgrade,
I'm
a
little
worried
that
it
may
there
may
be
a
limit,
a
very
limited
set
of
people
who
actually
have
control
of
of
this
part
of
the
things,
and
so
it's
going
to
take
some
something
exploring
it.
Maybe
gavin
and
me
are
the
only
two
people
that
have
access
so
so
I
think,
let's
create
get
an
issue
created
and
then
we'll
track
it.
There.
B
A
A
A
Great
all
right,
okay,
next
topic
or
anything
else
on
other
topics,
no,
no
okay.
So
next
topic
for
me,
was
commercial
support
page.
This
is
a
proposal
from
gavin
mogan
that
what
he'd
like
to
do
is
create
a
a
vendor
commercial
vendors
who
are
providing
commercial
support
for
jenkins
implementations,
and
there
are
several
that
do
this,
for
instance,
cloudbees.
Does
it
red
hat?
A
A
Yeah,
I
think
I
think
that
gavin
started
that
process.
Okay,
may
we
may
also
want
to
ask
the
outreach
outreach
sig
to
contact
potentials
so,
for
instance,
one
member
of
our
board
of
the
jenkins
board
evalina
vilcos
previously
had
worked
for
a
company
that
provided
these
kind
of
things.
I
think
her
current
employer
does
not,
but
she
may
know
some
and
she's
a
strong
northern
europe
contact.
A
B
A
Right
well-
and
that's
that
I
think
is,
is
a
maybe
that's.
A
a
question
we
bring
to
gavin
is
what,
if
we
were
trying
to
describe
how
you
do,
because
these
are
certainly
commercial
vendors
right,
they
are
very
much
commercial
vendors
and-
and
they
are
very
much
doing
things
that
help
jenkins
and
help
users
of
jenkins
be
successful.
A
So
so
it
feels
like
hey.
That
would
be
a
good
thing
to
mention
them
now,
yeah,
so
maybe
okay,
good.
Let
I'm
gonna
put
this
in
the
notes
here
and
discuss
further,
adding
cloud
providers
to
the
commercial
vendors
list,
although
he
may
gavin
may
may
be
concerned
there,
because
I
think
his
intent
was
commercial
support.
Vendors.
B
A
A
So
what
we
get
is
the
jenkins
weekly
change
logs,
those
things
that
look
like
this
jenkins
docs
here
when
I
look
at
the
change
log
for
long
term
support
or
even
better.
When
I
look
at
the
weekly
change
log,
this
change
log,
its
content
is
collected
automatically
by
a
program
that
tim
jacom
wrote,
and
it's
done
for
every
pull
request
that
is
submitted
to
jenkins
core.
A
Something
else
it
is,
it
is
definitely
something
else
and
it's
something
else,
because
the
thing
it's
creating
is
actually
a
yaml
file.
That
is
a
data
representation
of
these
change.
Log
entries,
oh
okay,
and-
and
so
that's-
that's-
a
great
help,
that's
much
better
than
the
old
process
where
we
created
that
data
interactively.
A
A
That
probably
should
be
in
a
change
log,
because
it
was
very
much
an
added
capability
and
it
was
an
added
capability
that
became
visible
about
the
same
time
as
a
particular
jenkins
controller
release.
So
it
would.
It
wasn't
specifically
tied
to
a
controller
release,
but
it's
it
would
be
effective
to
put
it
in
there,
but
we
never
look
at
that
repository
for
changes
and
therefore
we
never
detect
to
add
it
to
the
change
log
I
see
and
and
there's
here's
a
more
a
very
specific
example.
This
java
17
one.
A
A
A
You
know,
I'm
I'm
open
to
any
one
of
those,
but
the
challenge
for
me
is
then,
if
we
did
that,
how
would
the
changelog
generator
know
what
to
include
yeah
you're
right,
because
we
don't
use
release
tags
on
the
packaging
repository
right
and
and
we
don't-
we
don't
use
them
there,
because
we
don't
really
have
any
use
for
a
release.
Tag
on
a
packaging
repository
release,
core
packaging
is
just
tools.
A
B
B
A
Yeah
well
and
and
it's
it's
guided
self-interest
right,
I'm
interested
in
it
because
then
it
reduces
the
number
of
times
that
we,
the
docs
sig,
misses
a
change
log
entry
because
we
didn't
insert
it
interactively
yeah
great
all
right.
I
will
bring
it
to
the
bring
it
to
the.
I
will
ask
in
the
jenkins
developer
mailing
list.
A
Last
last
topic,
then,
is
the
changelog
and
release
guide
for
2.346.3?
We've
got
a
request
already
sent
by
tim
jacom.
Looking
for
the
release
lead,
we
don't
have
a
volunteer
yet,
but
I
hope
early
next
week
to
find
a
volunteer
to
take
it
great,
and
that's
all
that
I
had
any
other
topics
from
you
bruno.