►
From YouTube: 2022 03 04 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
to
documentation
office
hours,
it's
the
third
of
march
2022
topics
that
I've
got
on
the
agenda
news.
A
Let's
see,
we
had
interactive
tests
as
our
sorry,
it's
the
fourth
of
march,
because
in
india
it
is
in
fact
already
the
fourth
interactive
tests.
I
brought
it
forward
from
last
time
in
case
we
need
more
discussion
of
it.
Linux
installer
switch
this
one.
I
definitely
want
to
spend
some
more
time
on
and
then
google
summer
of
code.
If
there's
any
topics,
we
need
there.
A
B
B
That
I'd
like
to
discuss,
because
we
it
looks
like
this-
does
have
we
knew
it
was
coming
that
you
can,
that
the
ability
to
turn
off
the
agent
to
control
or
filter
on
the
ui
is
gone.
B
Is
correct
but
in
daniel's
notes
there
was
another
piece
of
it
that
I
didn't
know
was
going
away
and
I
want
to
make
sure
that
that
pr
in
case
it
ever
gets
merged
is
still
accurate.
So,
oh.
D
A
Okay,
so
on
the
way
of
news
jenkins,
2.337
released
and
thanks
very
much
to
those
who
reviewed
the
changelog
fixes
for
several
image
and
icon
issues,
still
one
or
two
left,
so
that's
in
progress
other
fixes
coming
in
happening
in
core,
in
particular,
so
there's
some
interesting
fixes
around
remoting
and
establishing
restart
behaviors
that
that
it's
good
to
see
jesse
glick
and
basel
crowe
and
jeff
thompson
working
together
on
some
things
that
we
didn't
quite
understand
what
was
happening
and
I
think
they've
got
a
better
idea
now
on
what's
happening
with
certain
restart
cases,
then
the
release
candidate
is
out
and
testing
is
happening.
A
It
will
highlight
some
of
these
things.
We've
still
got
an
open
question
whether
or
not
we'll
include
the
linux
installer,
I'm
more
and
more
persuaded.
We
should,
but
I've
got
to
re,
reopen
the
conversation
on
jenkins.io
or
on
on
the
jenkins
developer
list.
A
B
In
the
into
the
file,
it
is
line
67.99.
B
Right,
yes
and
the
admin
customizable
allow
list
for
calibers
and
file,
callables
and
file
paths
have
been
removed.
B
A
B
That's
what
I
was
reading
the
pros
on.
I
just
wanted
to
see
if
it
was
there,
so
I'll
go
back
and
check,
because
I
think
somewhere
in
the
docs
there's
it's
not
in
the
section
that
I
was
mucking
with,
but
there
is
a
link
to
the
docs
about
how
to
change
that.
A
A
A
B
Okay,
let
me
go
and
because
I'm
I'm
not
an
expert,
it's
one
of
those
things
I
knew
it
was
over
there
and
I
just
referenced
it.
Never
let
me
go
look
at
it
and
I'll
send
a
link
back
to
to
make
sure
that
this-
and
I
suppose
actually
people
don't
upgrade
that
fast-
that
we
probably
should
not
delete
that
doc
immediately.
But
we
should
put
a
big
warning
at
the
top
that,
as
of
release
such
and
such
this
no
longer
works.
B
A
B
A
B
A
Good,
all
right,
okay,
so
anything
else
on
that
changelog
encourage
everyone.
I
did
sorting
and
sort
of
grouping
of
things
from
based
on
my
own
taste.
You
are
welcome
to
dispute
that
you
are
welcome
to
disagree
with
it.
Please
don't
be
shy
if
you
find
something
you
think
would
be
better
done
better,
a
different
way.
A
B
D
A
Actually,
quite
the
opposite,
I'm
I'm
I'm
relying
heavily
on
your
reviews
and
making
a
much
much
lighter
review
myself
because
of
it.
So
so
I'm
delighted
with
your
reviews,
yeah,
I'm
I'm
absolutely
thrilled
with
the
reviews
from
others,
because
it
lets
me
put
much
less
much
less
worry
on
to
that
that
thing
before
we
publish
it.
A
A
And
basel,
for
instance,
has
basil
basel
wrote
a
request,
template
change
that
notes
that
the
phrasing
is
imperative
and
it's
like?
Oh
well,
thank
you
basel.
Yes,
that's
in
the
style
guide
and
he
put
it
into
the
pull
request
thing
so
that
hey
yes,
please
state
it
in
the
imperative
voice.
So
nice.
B
A
F
D
B
Instead
of
saying,
you
should
always
name
this
with
prefix,
it's
a
breed
of
dog,
just
say
name
this
file
with
a
prefix
this.
So
it's
all
it's
getting
rid
of
a
lot
of
the
soft
all
the
you
really
ought
to
do
this.
You
should
just
say:
do
it
rather
than
saying
you
should
walk
to
the
store?
Stay
walked
to
the
store,
that's
imperative.
A
A
D
F
A
D
I,
what
he's
trying
to
say
here
that
it
should
be
like
do
this
return,
that
no
no
does
this
returns.
That
so
can
we
look
at
an
example
and
translate
it
into
imperative
mood
just
for
my
help,
if
that's
not.
A
D
So,
okay
scroll
down,
so
this
one
there
is,
this
add
brazilian
portuguese
translation
property
files.
So
this
is
a
this
is
an
imperative
mood,
but
it
would
have
been
like
non-imperative
mode
if
it
read
something
like
ads.
Brazilian
portuguese
translation
right.
A
Right,
at
least,
I
think
that's
what
it
means.
It's
also
that
we
we
write
it
in
present
tense,
not
past
tense.
So,
instead
of
add
present
instead
of
saying
added
happened
in
the
past,
we
say
add
that's
what
this
release
is
doing.
Is
it
add
it?
It
will
add
brazilian
portuguese
translation,
property
files.
B
Yeah,
who,
in
general
you
know
life
is
sweeter
if
you
say,
keep
us
isolated,
but
it's,
but
it's
good
pros.
It's
well
the
contrast.
There
is
so
much
stuff
that
says,
because
we
used
to
do
such
and
such
and
it
caused
this.
And
this
problem
I
mean,
and
you
get
in
the
regular
doc.
You
have
to
read
three
or
four
lines
before
you
find
what
they're
talking
about.
B
It's
like
get
to
the
point
so
and
if,
if
calling
it
imperative
is
making
it
happy
for
everybody
else,
I'm
good
because
I
don't
know
what
else
to
call
it.
Succinct
with
me.
E
Yes,
yes,
it
helps.
Yes,.
D
C
A
Then,
and-
and
we
can
keep
an
eye
for-
we
can
continue
to
watch
for
samples
like
that
and
then
discuss
them
here.
I
think
that's
a
good
thing
to
do
all
right.
So
next
topic
was
interactive
tests.
I
think
we
had.
We
had
brought
this
one
to
a
conclusion
last
week.
Is
there
more
that
you
wanted
to
discuss
there
diraj.
B
Yes,
except
wait
a
second:
what
what
was
the
end
result
of
that
discussion,
that
it
would
be
nice
to
have
these
things?
Do
we
have
issues
filed
for
them.
A
Ever
doing
them-
or
I
I
have-
I
have
hopes
of
asking
some
particular
people
to
help
be
more
involved
in
interactive
testing
of
the
most
recent
ui
changes.
So
I'm
I'm
running
an
initiative
myself
amongst
some
fellow
developers
to
say
hey.
This
is
a
precious
time
for
us
to
be
doing
more
testing
to
explore
these
ui
changes
and
I
think
I'm
I'm
getting
it
across,
because
I've
got
other
people
who
are
interested.
So
I
think.
A
A
To
do
that,
we
need
more
testing
and
that
testing
right
now
is
best
done
by
human
beings
looking
for
surprises
and
oopses,
and
then
we
may
eventually
get
to
the
point
where
automation
would
help
us,
but
for
right
now
I
think
it's
human
beings
looking
for
to
be
sure
things
are
behaving
and
are
structured.
The
way
we
want
them.
C
A
The
linux
installers
now
use
system
d
as
their
way
to
control
the
process,
rather
than
using
the
system,
five
style
in
it.
That
has
the
significant
benefit
that
now
we
have
one
way
of
describing
how
to
configure
services
on
any
machine
that
used
a
linux
installer,
whether
it
was
debian
or
ubuntu,
or
red
hat
or
centos,
or
open,
susie
or
suzy,
any
one
of
those
six
or
amazon
linux
for
that
matter
or
alibaba
linux.
A
I
don't
have
data
yet
I
was
thinking
that
okay,
I
could
go
try
to
find
some
data
to
see
how
many
installations
we
get
of
a
weekly
and-
and
that
would
give
us
some
approximation.
Okay,
if
there
are
10
000
installations
of
a
weekly
within
the
first
week
of
its
install.
That's
that's
an
interesting
piece
of
data
compared
to
if
there
are
100.
A
B
A
How
much
I
don't
I
don't
know,
I
know
that
we
don't
have
documentation
on
our
official
documentation,
page
for
open
susie
or
for
susie
right.
So
I'm
not
terribly
worried
about
that.
One.
I'm
glad
we've
got
the
installer,
but
it
has
some
oddities
that
that
I
I'm
not
ready
to
worry
about
at
the
moment,
or
at
least
it
did
before,
and
and
so
it
was,
it
was
a
different
thing
for
me.
Susie
was
sort
of
a
I'm
less
worried
about
it
than
I
am
about.
Debian
and
red
hat
right.
A
A
A
The
challenges,
the
challenges
that
we've
got
lots
of
writing
to
do,
and
not
a
lot
of
time
to
do
it
so
right.
A
B
A
B
A
C
B
B
B
A
Actually
did
that
with
people
who
had
expressed
interest
in
system
d
and
they
they
did
test
it.
We
were
really
grateful
for
them
during
the
development
phase
before
it
was
ever
released
in
weekly,
we
had
reports
from
several
users
of
positive
testing.
So
so
we
were
very,
very
grateful
for
that.
Yeah.
B
A
B
A
Next
topic
I
had
on
the
list,
was
google
summer
of
code,
any
questions
or
or
concerns
there.
The
the
office
hours
start
in
30
minutes
there.
So
we
will
have
time
for
an
office
hours
discussion
if
there's
something
office,
hours
related.
A
A
F
Yeah
and
the
channels
seem
very
active
too
so,
like
people
are
asking
questions
on
like
twitter
and
I'm
mostly
focused
on
the
getter
stuff.
I
haven't
really
checked
the
community
channel,
but
I
know
that
getter
is
like
fairly
active.
So
that's
a
big
positive
too
right,
because
it
means
that
people
are
asking
questions
and
trying
things
out,
which
is
always
a
good
thing
and
then
hopefully
picking
up
some
of
the.
A
A
And
I
I
know
that
I'm
seeing
seeing
friendly
issues
are
being
addressed
because
I've
seen
or
being
attempted,
maybe
is
the
better
way
to
say
it
and
and
I've
seen
it
with
two
two.
Two
different
people
attempting
a
friendly
issue
on
the
gate,
client
plug-in
so
that
that's
great.
B
Maybe
one
of
them
would
like
to
work
on
the
system
d,
documentation.
A
A
Yes,
yeah,
okay,
and
what
I,
what
I
did
was
offered
two
people
on
this
one
proposed.
We
would
accept
two
to
mentor
two
on
this
one
and
two
on
this
one,
the
idea
being
that
we
can
probably
find
mentors
to
support
one
mentor
could
support
two
people
and
we
won't
be
overwhelming
anybody
or
if
we
get
two
mentors
for
two
people,
even
better
sure.
D
Section:
oh:
go
ahead!
Sorry!
So
the
third
point:
the
screenshot
updates
for
jenkins
dot
io,
that's
the
manual
one
right.
A
D
E
Chris
bald
so
very,
very
helpful,
interesting,
very
okay,
very
good.
A
My
understanding
is
it's
april
to
mid-may,
with
two
weeks
of
of
community
bonding
four
weeks
of
development.
A
A
B
B
A
So
what
what
are
the
comments,
so
checks
of
pass
ed
editorial
changes
made
in
january.
A
Yeah
yeah
this
was,
I
think
this
was
was
this
came
from.
Yeah
was
a
contributor
contributed
to
some
things
to
you
two
years
ago
and
we
can
either
we
could
either
continue
it
or
close
it
and
reopen
with
somebody
else.
Either
is
fine.
Now
I
don't
see,
I
didn't.
Oleg
is
the
one
who
requested
changes.
What
changes
did
he
request.
A
C
A
A
A
A
B
B
E
B
A
A
A
C
B
A
A
A
B
C
F
E
E
A
Yeah
this-
and
this
is
the
one
we
use
on
on
red
hat
demon
or
no
epel.
Actually,
that
provides
it.
C
A
F
B
B
B
A
A
A
Just
I
don't,
I
don't
think
that
we're
going
to
get
any
difference
truthfully.
His
question
is
still:
where
does
it
belong?
And
the
answer
for
me
is
we
want
the
content.
The
location
in
the
managing
chapter
is
not
bad
because
it's
it's
at
least
general
purpose.
It's
not
limited
to
pipeline
right.
A
A
B
A
A
A
Of
conflicts
from
the
github
ui,
so
this
one
just.
B
A
A
A
A
A
A
F
A
C
A
B
A
A
A
B
B
Could
we
run
to
make
make
and
take
a
look
at
the
formatted
is
going
through
quickly?
I
had
something
look
like
part
of
what
I'd
written
got
separated
from
the
first
part.
A
Okay,
so-
and
this
was
documentation
managing
and
it
is.