►
From YouTube: 2022 02 17 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
google
or
jenkins
stocks
office
hours,
I'm
so
used
to
running
other
things.
Welcome
to
jenkins
documentation,
office
hours,
it's
february,
17
2022,
reminder
that
we
abide
by
the
jenkins
go
to
conduct
topics
for
today.
Jenkins
is
the
way
and
some
questions
that
gavin
mogan
had
she
code
africa,
contributon
news
good.
First
issues
where
we'll
do
a
live
bug
fix
it's
my
proposal
anyway
and
then
a
topic
on
adding
a
troubleshooting
page
and
topic
on
linux
installers
and
their
change
from
init
to
systemd
any
other
topics
that
need
to
be
added
to
the
list.
A
Good
to
me.
Okay,
all
right
so,
first
topic,
then
gavin
mogan
joined
the
docs
office
hours
last
week
during
the
asia
time
zone,
and
we
did
a
detailed
review
of
the
content
for
jenkins
is
the
way
and
it's
looking
really
good
translation
so
that
their
conversion,
I
guess,
is
the
best
way
to
say
it.
So
what
he's
done
is
he's
converted
it
from
the
from
the
wordpress
site
now
converted
to,
I
believe,
asciidoc,
that
we
can
maintain
his
code,
nice
and
what
he
noted
is
hey.
A
A
B
Okay,
yeah,
I
think
the
the
the
timeline
for
renew
renewing
the
the
current
site
is
around
april.
C
A
B
A
year
it's
an
annual
subscription,
so
the
subscription
is
up
in
april.
A
In
in
the
jenkins
infra,
and
that
would
mean
a
github
repository
a
site
and
it
could
be
on
netlify
elsewhere,
you
know
it
doesn't
have
to
be
anything
that
we
do
an
awful
lot
for
and
then
we'll
coordinate
it
with
with
gavin
mogan.
Thank
you.
That's.
Thank
you.
That's
the
the
piece
that
I
wanted
to
check
on.
A
A
B
A
A
B
A
So
we're
just
working
the
details
yet
good,
okay.
Okay
still
so
that's
that's
the
thing
that
I
needed
since
still
need
mentors
and
open
to
more
project
ideas,
so
I'll
continue
mark
to
continue
recruiting.
A
B
So
mark
you
have
a
couple
of
names
by
by
theirs
are
they
are
those
confirmed
mentors.
A
A
A
Yeah
they're
we're
still,
it
feels
like
we're
still
short-handed.
In
particular.
Last
year
we
had
some
surprises
where
we
had
changes
proposed,
but
no
one
to
review
the
changes
who
had
permission
to
merge
them,
and
so
it's
it's
a
danger
here
that
having
mentors
in
this
case
is
necessary,
but
not
sufficient.
A
We
also
have
to
have
the
right
maintainers
agree
that
they're
willing
to
review
the
pull
requests
that
come
in
to
make
the
fixes
okay,
and
then
we
had
an
additional
project
id.
I
should
note
that,
from
from
from
gavin
mogan
saying,
hey
browser
web
browser,
automation
is
a
very
interesting
field
and
doing
screenshot
updates
with
web
browser.
Automation
might
be
something
that
could
be
done
so
automate
the
taking
of
screenshots.
A
A
A
A
A
A
A
A
A
Okay,
all
right
next
topic
was,
as
this
is
more
of
a
a.
How
do
we
want
to
do
it
question
and
so
zenob
for
you
and
alyssa?
This
is
a
really
good
one
for
a
check
for
the
two
of
you.
Gavin
mogan
asked
the
question
hey.
He
would
like
a
set
of
standard
responses
you're
having
trouble
running
something
inside
jenkins,
but
it
works
locally.
And
how
do
you
solve
that?
A
And
it's
a
it's
a
very
good
question.
We
actually
had
a
wiki
page
that
specifically
addressed
that
the
the
way
it
said
it
was
hey.
My
software
builds
on
my
computer,
but
not
on
jenkins.
Why
not-
and
this
then
lists
a
checklist
of
ideas
of
things
that
you
should
be
checked
to
understand
why
inside
jenkins
it
might
fail,
but
outside
jenkins
it
would
work
and
gavin
has
noted
some
additional
spots
now.
The
question
is:
where
should
be?
A
Where
should
it
be
placed
so
the
idea
I
suggested
to
us:
hey
here's
this
page
system
administration
and
it's
got
a
bunch
of
subtopics
backup,
restore
monitoring,
chef,
puppet
logging,
scripted,
diagnosing
errors
and
getting
a
thread
dump
those
kinds
of
things.
My
thought
was,
we
should
put
another
entry
here
at
the
same
level
as
diagnosing
errors
and
call
it
troubleshooting
and
then
have
a
page
that
has
those
frequently
asked
questions
or
common
common
concerns.
Hey
it
doesn't
do
what
I
expected.
Why
not?
A
C
So
my
thoughts
are
instead
of
putting
it
on
the
system
administration.
Why
not?
It
be
a
whole
different
section
on
its
own,
so
I
don't
have
to
because
I
think
troubleshooting
is
something
that
a
lot
of
people
have
issues
with,
and
it's
going
to
have
like
a
range
of
different
topics
when
it
comes
to
troubleshooting
and
as
time
goes
on,
if
it's
something
that
keeps
getting
updated,
it
will
get
potentially
very
large
with
very
different
topics
on
how
to
troubleshoot
jenkins.
C
So
I
don't
think
it
should
be
a
bad
idea
if
it's
like
a
different
section
on
its
own,
not
on
that,
like
a
different
section
for
troubleshooting
and
jenkins,
and
on
that
section
you
have
these
various
different
topics
that
you
have
to
troubleshoot.
C
That's
my
own
suggestion.
A
B
B
A
A
A
A
C
A
C
So
this
redirect
doesn't
mean
that
we
are
still
going
to
have
those
topics
under.
A
Yeah
so
good
good
question,
so
so
because
this
is
a
full
full
level
page.
So
diagnose
errors
is
a
top-level
page.
It
would
disappear
from
this
table
of
contents
entry
here,
so
it
wouldn't
be
visible
here.
But
if
someone
nav
opened
this
url,
it
would
immediately
redirect
them
to
troubleshooting
slash,
diagnosing
dash
errors
so
like
that
it
would
be
as
though
they
had
typed
the
correct
url
and
and
that
redirect
then,
is
a
permanent
thing
and
it's
the
jenkins
dot
io
site
is
designed
to
do
those
redirects
very
easily.
A
C
Okay,
because
I
was
considering
opening
the
pr
with
the
new
section
working.
B
A
A
Okay,
so
here's
I'm
gonna
go.
I'm
gonna
bring
up
my
thing
to
find
a
redirect.
A
A
A
A
B
A
A
A
A
C
C
C
Yes,
it
does,
but
if
I
have
any
further
questions
I'll
just
send
you
a
message.