►
From YouTube: 2022 02 18 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
Welcome
everyone:
it's
the
17th
of
february
2022.
These
are
jenkins
documentation,
office
hours
in
in
asia.
It's
actually
the
18th
we'll
go
ahead
agenda
topics.
I've
got
news.
Jenkins
is
the
way
content,
merge,
weekly
change,
log
review
process,
discussion
just
to
be
sure,
we're
okay,
there
lts
changelog
for
upcoming
a
troubleshooting
section
proposal
that
came
from
gavin,
mogan
and
xena
in
today's
earlier
session,
had
a
refinement
for
it
good
first
issues.
If
we
have
time,
I
thought
we
could
go
through
and
do
a
live
bug
fix
so
that
others
could
see
hey.
A
Okay,
so
we
and
at
the
conclusion
of
this
session,
so
after
one
hour,
we
will
end
here
because
then
we
begin
a
30
minute
session
on
google
summer
of
code
for
those
who
may
be
interested
in
google
summer
of
code.
So
it
won't
be
on
this
call,
but
a
different
call
and
I'll
be
there
and
alyssa
tong
will
be
there
great.
Then.
So,
let's,
let's
talk
to
one
item
of
news,
2.335
has
been
released.
A
It
is.
It
now
includes
the
systemd
based
linux,
installer
and
a
migration
facility
that
migrates
from
the
old
installer
to
the
new
we've
had
two
different
users
who
mistakenly
thought
they
could
perform
upgrades
in
linux
by
just
changing
the
war
file
and
what
they
need
to
do
is
really
run
the
full
insta
run
the
installer
or
run
the
package
manager
upgrade
and,
and
so
we'll
we'll
probably
put
some
documentation
there
about
it.
A
The
ui
improvements
have
been
a
little
more
brittle
this
time.
If
we
look
at
the
jenkins
download
page
for
the
weekly,
what
you'll
see
is
quite
a
number
of
bugs
that
have
been
reported,
mostly
related
to
images
that
are
not
being
rendered
correctly.
A
A
Lts
is
coming
march
9th,
and
this
one
will
have
the
first
phase
of
ui
improvements
and
changelog,
and
upgrade
guide
will
be
needed.
I'd
propose
we
plan
to
do
a
draft
review
next
week
during
office
hours.
That
will
be
just
after
the
delivery
of
the
elk
of
the
release.
Candidates.
C
Yes,
no
question
is
just
looking
forward
to
review
the
draft
to
know
more
about
it.
The
process,
that's
all
yeah,.
A
Well,
and
this
one
this
one
because
of
the
ui,
the
ui
improvements
mean
that
more
effort
will
be
needed.
A
D
It'll
also
be
nice
because
going
forward
in
the
docs,
when
we
have
to
mention
that
this
change
is
it's
nice
to
have
a
blog
post.
We
can
link
to.
A
The
blog
post
would
be
likely
the
week
the
same
week
as
the
release.
A
A
A
Let's
gavin's,
the
initial
request
was,
let's
put
it
all
under
www.jenkins.io,
but
we've
realized
that
would
double
the
size
of
the
repository,
because
there's
an
awful
lot
of
content
here.
So
what
we've
counter
proposed
is
thanks
to
a
suggestion
from
oleg
nanashev
is
let's
use
a
different
location,
and
so
the
proposal
is
jenkins
is
the
way.jenkins.io
as
a
separate
site
under
the
jenkins.io
domain
name
and
we'll
put
the
stories
there.
It
will
have
this
look
and
feel
and
we
won't
have
to
pay
the
extra
cost
for
the
hosting.
D
D
A
What
we,
what
we
probably
will
not
have
is
we
had
a
separate
organization
who
was
doing
the
curation
and
the
coordination,
and
we
will
probably
switch
this
to
instead
use
pull
requests
to
coordinate
it
and
since
pull
requests
should
be
lingua
franca
for
all
of
us
or
everybody
who's
using
jenkins.
I
don't
feel
bad
about
that.
D
Yeah
not
at
all,
but
that
means
we
need
a
contributing,
a
doc
file
for
the
repo
right.
A
C
Yeah,
I
think,
on
github
there
was
a
conversation
between
tristan
and
gavin
where
kristen
said
that,
do
you
want
mark?
Do
you
want
to
add
it
as
a
agenda
to
the
meeting?
So
is
this
was
the
same
thing
or
not?
I'm
just
reminding.
A
A
Okay
next
topic,
then
weekly
change,
log
review
process.
So
thanks
to
thanks
in
particular
to
dhiraj
to
others.
If
you've
been
involved
in
weekly
change,
log
review
the
technique
we
switch
to
is
asynchronous,
and
that
makes
it
better
for
me
in
that
I
don't
have
to
have
two
two
office
hours
during
the
week
on
different
days,
both
late
nights.
A
C
I
think
it
works
great.
My
concern
was
just
that
I
I'll
not
be
able
to
look
at
the
pull
request
multiple
times
during
the
day
during
the
week,
so
during
monday.
I
would
just
remember
it
like
at
a
weird
time
that,
oh
today,
I
need
to
review
it
so
I'll
just
go
to
the
github
and
look
at
the
pr
and
would
just
spend
around
half
an
hour,
something
like
that
and
I'll
just
review
it
and
be
done
for
it.
So
it
is
easier
for
me
as
well.
Okay,
good
all
right.
A
A
A
A
A
Yeah
and-
and
thank
you
very
much
so
I
think
what
I'll
I
may
try
sending
reminder
emails
on
sunday
evening
or
early
monday
morning,
just
in
case
and
we'll
watch
it
and
see
if
it
helps
if
it
doesn't
help,
I
stopped
sending
them,
but
if
it,
if
it
helps
great,
we'll
watch.
A
I
I
was
just
going
to
send
them
to
you
to
the
all
the
to
those
who
are
in
attendance
at
this
meeting,
because
you've
been
the
reviewers
so
the
candidates
to
be.
Oh,
that's
a
good
point.
The
candidates
to
become
to
become
what
what's
the
title
again,
how
embarrassing
copy.
E
A
Copy
editors
right
receive
the
receive
the
reminder
yes,
and
we
still
don't
have
the
the
contributor
license
agreement
thing
so
I'm
holding
off
on
having
you
submit
a
contributor
license
and
therefore
holding
off
on
making
a
copy
editor
still.
D
D
It
for
dynatrace2.
A
A
So
so
it's
just
trying
to
trying
to
avoid
some
work.
Yes,
we
could
make
you
go
through
the
cla
process
that
I
submitted,
but
it
was,
it
required
gpg
signing
of
something
and
this
and
that-
and
it
was
really
complicated.
Then
oleg
had
me:
do
the
easy
cla
process
as
a
test,
and
it
took
about
three
minutes,
and
so
so
I
was
much
happier
with
the
easy
cla
process.
It's
a
lot,
a
lot
more,
a
lot
more
friendly
to
people
who
are
contributing.
C
That's
great
so,
okay,
last
question
from
my
side
is
you're
saying
to
we
need
to
complete
it
before
your
end
of
monday.
So
it's
like
the
the
previous
docs
office
hours
time.
Yes,.
A
A
A
D
A
A
A
A
There
nope,
okay,
lts
change
log.
So
this
one,
the
back
port
candidates,
are
in
process.
We'll
start
we
should
plan
to
review
it
for
next
week
and
so
review
at
next
office
hours
or
before
next
office
hours.
A
C
A
Great
yeah
and
and
deeply
valuable,
much
appreciated
that
you're
willing
to
review
it.
We
will
also
do
an
upgrade
guide
and
the
upgrade
guide
will
follow
the
usual
pattern
of
a
number
of
things
that
have
to
be
noted
in
it
because
they
are
actual
upgrade
upgrade
relevant
changes
and
there
are
some
things
that
may
require
migration
or
plug-in
compatibility
concerns
that
have
to
be
noted
in
the
upgrade
guide.
A
A
A
So
so
what
he
suggested
was,
could
we
have
a
troubleshooting
section
or
what
he
suggested
was
he
wants
a
page
to
put
these
kind
of
things
and
in
getter
I
had
suggested
well,
let's
put
a
troubleshooting
page
underneath
the
system
administration
page
and
in
reviewing
it
today
in
doc's
office
hours,
europe
time
zenob
suggested
hey.
Why
don't
we
just
create
an
entire
troubleshooting
section
like,
and
here
let's
take
a
look
at
it,
and
so
I
can
show
you
what
her
idea
was.
A
D
D
A
A
D
E
Right
right
exactly
so,
it's
like
I,
I
would
I'd
rather
have
it
like
a
top
level,
and
I
don't
know
if
we
need
to
further
break
things
down,
but
I
think
starting
off
with
immediately
like
just
maybe
almost
in
the
form
of
a
question
like
this
is
selenium
is
like
you're
saying,
selenium
is
broken
or
my
job
is
wrong,
or
you
know-
or
I
think
I
saw
one
even
in
the
chat
or
chat
today
about
the
the
jenkins
home
was
set
to
a
different
thing
and
right
they
might
not
have
really,
but
that's
an
example
like
system
admin
stuff,
but
maybe
I
think
you
know
it's
a
little
bit
different
than
being
able
to.
D
A
A
D
A
Okay,
so
the
thing
that
I
wanted
to
show
briefly
here
was
this
wiki
page.
That
already
has
some
of
these
kind
of
things.
Admittedly,
it's
not
a
pretty
page,
but
it
gives
us
several
failure
modes
with
error
messages,
and
so
so
it's
the
the
pattern
and
notice
the
date
stamp
on
it.
It
was
all
the
way
it
was
started
originally
10
years
ago.
A
E
That
works
for
me.
I
originally
started
looking
at
the
community
forum
because
I
didn't
know
if
we
were
because
I
didn't
know
if
there
would
be
a
good
place
to
put
it
there.
I
like
it
on
the
jenkins
io,
because
that
way,
it's
a
little
bit
more.
If
you
feels
a
little
bit
more
official
than
like
doraj
was
saying
about.
Like
someone
googling
like
a
stack
overflow
for
her
to
answer
that
could
be
out
of
date,
we
will
have
to
make
sure
that
we
keep
these.
We
add
these
to
reviewing.
D
Make
it
clear
because
they
that
there's
two
ways?
Obviously
we
would
love
to
have
prs
against
this
when
it
happened
right,
but
tell
them
if
they
have
an
issue,
and
they
don't
know
how
I
mean
they
may
see
the
problem
and
they
don't
know
the
answer
that
they
can
file
an
issue
right.
A
D
E
A
E
A
E
D
D
D
A
D
E
D
A
C
Yes,
so,
since
christine
also
said
that
this
troubleshooting
troubleshooting
section
will
help
us
to
put
our
position
in
like
the
near
stack
overflow
when
user
is
searching
for
the
error
message,
I
was
wondering
like:
is
this
the
only
place
for
troubleshooting?
We
have
in
jenkins
dot
io
or
there
are
other
sections
as
well,
where
there
are
error
messages
and
there
are
solutions
in
form
of
blog
posts
or
maybe
a
dedicated
section.
C
My
main
intention
is,
I
was
wondering
like
it's
it's
a
very
big
idea.
I
was
wondering
like.
Can
we
increase
the
visibility
of
jenkins,
oh,
like
whenever
a
user
is
searching
for
jenkins,
related
messages
so
like
before
staff
overflow?
They
would
be
thinking
like
hey.
I
should
first
of
all
look
at
this
search.
Result
on
jet
comes
dot
io,
because
that's
where
the
error
is
so.
I
know
it's
a
big
big
thing,
but
just
wanted
to
know
what
you
think.
A
Yeah
a
good,
I
think
it
would
be
a
great
goal
someday
rank
higher
than
stack
overflow.
A
D
A
D
A
D
A
E
A
E
A
A
A
D
A
A
Security
section
section:
yeah:
okay,
so
let's
open
up
that
one
and
let's
go
look
at
its
site
preview
and
see
if
it
has
the
same
problem,
because
if
this
fixes
it,
then
we
don't
have
to
whoops
wrong
steps,
hang
on
just
a
minute.
If
this
fixes
it,
then
we
don't
have
to
do
what
we
should
focus
on
is
getting
this
merged
and
let
that
fix
it
as
well.
D
A
A
A
D
Stuff,
yeah,
no,
go
you
want
it,
you
want
to
grab
it
and
do
whatever
you
want
me
to
do.
It.
A
Actually,
I
think
it
may
be
best
if
we
have
well,
we
can
have
you
do
it
or
I,
I
think
we
could
do
the
investigation
as
a
team
here
and
then
you'll
have
to
actually
be
the
one
who
submits
the
the
change.
So
we
could
have
you
submit
the
the
the
correction.
D
Okay,
well,
let's
look
at
it
quickly
and
then
maybe
I'll,
take
it
I'll
go
get
the
get
that
branch
and
get
it
up
now
to
confuse
you
all,
but
for
good
reasons
we
want
to
wait.
Okay,
I
did
not
touch
this
particular
section.
It's
the
link
to
it
and
security
that
I
was
in.
D
Right
or
or
this
could
be
separate,
then
maybe
I
was
seeing
it
as
something
else.
What
I
had
done
we
used
to
have.
We
did
at
one
point
along
the
way
we
had
a
separate
file
that
was
about
the
enabling
the
agent
controller
and
that
file
went
away
because
that
option
went
off
the
ui,
so
it
is
now
buried
in
the
in
the
section
about
distributed,
builds
at
the
end.
It
says
that
this
you
know
this
is
something
that
happens
and
and
then
it
points
to.
A
D
D
D
Get
in
since
I
haven't
I've
stopped
looking
at
this
all
the
time.
I've
just
lost
hope
that
it's
ever
gonna
move.
Could
we
look
at
the
preview
for
distributed,
builds.
A
Sure
so
you
want
to
look
at
just.
Let
me
get
back
there,
okay,
so
you
want
to
look
at
this
one
and
you
say:
distributed
builds
yes,
okay,.
D
It's
it's.
It's
it's,
oh
god
he's
got
it.
D
And,
let's
see
so,
this
should
have
a
link
to
the
because
and
just
but
if
you
can't
turn
the
filter
off
anymore
there
you
can
tweak
the
rules.
This
should
be
the
link,
then
you
could
tweak
the
rules
112
starting
line
112..
You
can
tweak
the
filters
rules
by
adding.
Allow
deny
rules
to
specify
the
commands
see
so
now
is
that
the
bad
link.
A
A
A
D
D
D
A
A
A
Oh,
and
by
the
way
others
have
shown
how
you
can
do
this
exact
kind
of
thing
using
git
pod,
so
you
don't
even
have
to
run
it
on
your
own
computer.
A
Yeah
john
mark
mason
showed
how
to
do
how
to
do
development
on
jenkins.io
using
gitpod
so
that
you
don't
have
to
have
a
local
workspace
at
all.
A
A
No,
he
just
says
fix
it,
so
the
picture
is
visible
and
what
daniel's
observation
is
that
there
may
be
other
pictures
that
have
a
similar
problem.
So
we
need
to
look
for
other
pictures
in
this
securing
jenkins
section
that
may
similarly
be
broken
because
they're
somehow
their
picture
has
been
okay,
that
one's
okay,
that's
good,.
A
But
there
may
be
maybe
other
things
that
have
been
damaged
in
the
same
way
and
we
need
to
just
cross
check
each
of
these
pages
to
be
sure,
yeah
right,
so
I'd
propose.
We
admit
that
that
didn't
work.
The
way
I'd
hoped
it
would
we'll
we'll
do
that
kind
of
thing
later
and
call
this
one
try
again
later
mark.
D
B
A
A
D
D
D
D
Quite
possibly
but
but
that's
what
I'm
saying
is
so
this
is
act.
You
know.
D
A
Okay
next
topic,
then
linux
installer
switch
from
system
five
to
six
in
it
to
system
d,
I'm
going
to
do
a
blog
post.
There
were
many
open
issues
that
were
resolved
in
the
linux
installers.
As
a
result
of
of
this,
this
improvement
special
thanks
to
basel
crow
for
for
a
complete
rewrite
of
the
linux
installers
to
use
modern
linux
initialization
system.