►
From YouTube: 2022 09 23 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
A
All
right
so
action
items
archive
the
docs
mating
list
is
going
to
have
to
wait
until
after
probably
wait
until
November
because
of
travel
schedules
and
whatnot
be
warned
that
I'm
out
of
the
office
next
week
and
October
10th
through
October
27th.
A
Right
well
so
action
items,
no
progress:
devops
world
I
did
embed
a
link
to
the
multiple
blog
posts
for
devops
worlds
that
have
come
in
over
the
last
roughly
month
or
so
really
great
work
from
various
people,
so
Bruno
Mars
and
Tim
Jacob,
John,
Mark,
Mason,
Alyssa,
Tong,
three
or
four
or
five
others.
So
some
of
the
best.
This
is
I,
think
the
single
best
collection
of
blog
posts
we've
had
in
a
very
long
time.
A
And
the
modernizing
a
plug-in
blog
post
has
been
has
oh
I
should
update
that
has
been
merged.
Yay.
Oh
wait,
a
second.
Why
isn't
that
listed
in
that
list?
Oh
there,
it
is
improve
a
plugin,
so
it's
there
and
it
includes
all
the
links
special
thanks
to
dhiraj
for
his
work
and
we're
we're
set
for
it.
We're
going
to
use
that
that
tutorial
will
be
the
basis
for
a
workshop
that
we
do
at
devops
world
all
right,
yep.
A
So
now
the
The
crucial
one
for
today,
hacktoberfest
so
Europe
office
hours,
did
some
more
work
on
hacktoberfest
and
let's
take
a
look
at
that,
so
we've
got
Kevin
submitted
a
proposal
to
take
out
one
item
from
this
list.
I
think
it
was
a
it's
already
been
merged,
so
there
are
some,
for
instance,
the
newcomer
friendly
issues.
That's
a
good
one!
For
people
there
are
others
that
I'm
not
sure
they
are
as
ready.
For
instance,
I'm,
not
sure
we've
got
enough
reviewers
on
Jenkins
file
Runner
to
keep
it
there.
A
It
was
being
actively
reviewed
while
what
was
in
Google
summer
of
code,
but
I'm,
not
sure
that
Chris
is
available
still
to
review
okay,
the
Prometheus
plug-in
likewise
so
I
think
and
techton
I'm,
not
sure
that
there
we
need
to
ask
their
contributors
now,
the
the
artwork
yes,
because
that's
the
docsig,
oh,
oh
speaking,
of
which
Meg
I
needed
to
ask
you
we've
been
a
long
time
without
with
you
acting
as
a
triage
person.
Would
you
like
to
become
a
copy
editor?
A
B
A
B
A
And-
and
that
may
be
the
the
model,
because
what
we're
seeing
right
now
is,
we
only
previously
had
two
copy
editors
me
and
Tim
Jacob
and
I'm
going
to
be
out
and
Tim's
going
to
be
out
next
week.
So
having
Kevin
with
permissions
means.
Okay,
we've
still
got
somebody
who
can
merge
things
to
jenkins.io,
but
having
you
as
an
additional
backup
might
be
a
good
thing,
knowing
full
well
that
hey
it's
not
going
to
be
a
heavy
activity
for
you,
it's
more,
oh
we're
in
a
need
for
you
right
now.
B
A
So
now
one
of
the
things
that
came
out
of
that
out
of
the
hacktoberfest
discussions
was
how
do
we.
This
is
something
that
Kevin
and
Bruno
observed
earlier
today.
How
do
people
know
which
plugins
they
should
approach,
and
one
of
the
things
was
that
oh
and
it
looks
like,
did
we
not
get
that
copy
into
the
oh
here?
It
is
good.
B
B
B
A
In
this
case,
the
problem
is
getting
people
to
review
the
pull
request.
Okay
and
so
the
the
thought
was
hey.
Okay,
maybe
what
we
do
is
we
reach
out
to
the
maintainers
of
these
plugins
and
ask
them?
Would
you
be
willing
to
consider
a
pull
request
to
to
merge
to
update
your
documentation
to
Move
It
from
Wiki
to
GitHub.
A
And-
and
that
could
also
be
but
I-
think
if
I
look
at
this
one,
for
instance,
that's
actually
not
a
bad
for
sure
look
is
hey,
that's
not
bad,
but
it's
up
for
adoption
and
because
it's
up
for
adoption,
that
really
means
it's
not
likely
a
great
fit.
Okay.
It
was
released
three
or
three
weeks
ago,
but
it
may
have
been
released
for
a
relatively
special
case.
Reason:
let's
see
what
the
well
yeah
I,
don't
know.
I
mean
the
the
maintainer
looks
like
it.
It
may
yeah.
A
B
A
Oh,
no,
it's
much
better
in
the
main
docs,
because,
no
matter
how
good
it
is
in
the
wiki,
the
wiki
is
not
changeable.
We
can't
we
can't
update
it
and
so
getting
it
into
the
main.
Docs
puts
it
close
to
the
developer
and
close
to
other
maintainers
who
can
who
can
update
it,
as
as
they
make
changes
to
the
plug-in
they're.
Maintaining.
B
A
Yeah,
that's
true!
Well,
the
other.
The
other
technique
is,
we
could
just
declare.
So,
for
example,
there
is
we
could
just
declare
we're
going
to
the
the
docs
office
hours
is
going
to
adopt
it
long
enough
to
do
the
merge.
It's
a
little
bit
odd,
but
hey
it
works.
We've.
We've
we've
done
adoptions
temporarily.
For
other
reasons.
A
A
So
so
obviously
it's
sat
here
for
for
a
long
time
without
making
progress
or
this
one
Ms
build,
the
pull
request
has
merged,
but
there's
not
been
a
release
of
the
plug-in
since
the
pull
request
merged.
Is
that
really
the
case
now
wait
a
sec
that
that's
hard
to
believe
because
no
release
since
2019,
okay
I've
got
to
take
a
tour?
Now,
no
look
at
it
there.
It
is
it
released
in
2020.,
so
it
has
released.
A
A
A
A
A
A
B
And
I'm
starting
to
feel
like
I,
just
we
did
it
right
for
some
of
them
and
when
we
can't
do
it
right,
let's
do
something
and
Market
in
some
ways.
So
people
know
that
you
know
the
content
or
we
could
file
an
issue
for
each
one,
that
we
merge,
that
we
could
not
be
sure
whether
the
content
is
still
accurate
or
we're
suspicious
of
it
and.
A
A
We've
we've
actually
got
that
right
this
this
report,
this
report
already
tells
us
exactly
that,
because
what
it
says
is
hey
look
here
are
the
things
that
are
okay,
if
I
sort
by
status,
I
can
look
at.
Oh,
let's
look
at
instead
of
okay,
let's
look
for
PR
merged
and
there
will
be
a
few
that
will
be
listed
as
that
the
pull
request
has
merged
but
not
been
released
and
a
bunch
of
them
have
been
deprecated.
So
there's
no
change
necessary
here
we
go
so
PR
is
open
or
merged.
A
B
I'm
thinking
about
not
visible
to
you
but
visible
to
the
Garden
variety
user,
who
comes
and
looks
at
the
plugin
and
the
plug-in
page
for
that
plugin
to
know
that
you
know
the
you
know,
there's
a
small
chance
that
the
material
here
may
be
dated
well.
A
A
I
think
well,
I
think
it's
an
interesting
idea,
because
what,
if
we
said,
hey,
we're
going
to
and
and
we've
there's
actually
a
convenient
way
to
do
it?
Let's
see
where
was
that
this
one?
Okay?
So
if
we
looked
at
this
one
and
said,
let's
take
the
top
10
of
these
or
top
20
and
open
check
each
of
them
to
see,
does
it
have
an
issue
report
that
so
I'm
going
to
do
exactly
that
close
everything
to
the
right
I'm
going
to
open
this
one?
A
A
Go
we
create,
we
create
ourselves,
a
template
of
the
actually
I.
Think
I've
got
a
template
of
the
wiki
migration
bug
report
and
we
put
it
in
there
and
call
it
a
good
first
issue
that
the
challenge
here
is
well
yeah.
That's
hoping
that
someone
be
would
be
willing
to
pick
it
up
and
that
the
maintainer
is
willing
to
review
it.
If
it's.
If
it's
picked
up
so.
A
Yeah
then
we
then
I
have
to
do
the
adoption
thing
so,
but
we
do.
All
we
have
to
do
is
click
this
report,
an
issue.
A
Let
me
see
if
I
can
find
a
boilerplate
of
that
Jenkins
jira
Wiki.
A
Mike
plug-in
Dot
migration
to
from
Wiki
to
GitHub.
Let's
try
that
maybe
there's
something
already
in
here-
migrate,
doc
from
Wiki
to
GitHub
for
this.
Yes,
so
we've
got
some
of
these
now
they're
there
from
two
years
ago,
but
we've
got
that.
A
B
Chh
I,
don't
know,
ask
him
and
a
couple
of
other
people
I
mean,
but
it's
always
I
mean
you've
had
to
tell
me
sometimes
it's
something.
This
is
better
than
what
we
had
we're
merging
it,
even
though
it's
not
you
know,
but
we
all
we're
kind
of
all
high
Achievers
who
are
used
to
getting
everything
right
before
me.
But
to
me
this
is
getting.
This
is
two
years
we've
been
trying
to
get
these
things
converted
because.
A
A
A
Okay,
I'm
not
seeing
any
hints
here
about
okay,
one
more
helper,
Jenkins
jira
convert
plug-in
documentation
to
GitHub.
A
A
A
With
links
to
the
documentation.
B
A
A
A
B
Am
I
have
one
I
have
a
two
second
one
for
you,
an
issue.
I
did
not
file
that
we
talked
about.
Can
you
go
to
the
Jenkins,
I
o
Docs
sure
and
system
administration,
and
it's
something
we
talked
about
re
all
those
we
talked
about
pulling
all
those
reverse
proxies
into
one
section.
We
just
mentioned
it,
but
that
would
be
something
to
do.
A
B
A
B
A
So
what
if,
what?
If
we
took
what,
if
we
took
as
a
counter
proposal,
this
subset
the
detailed
one
page
at
a
time,
subset,
uh-huh
and
put
right
now?
There
is
this
configuration
examples
here
at
the
bottom
of
this
page.
What
if
it
moved
up
to
the
top
here
above
General
guidelines-
and
we
took
these
out
so
that
we
would
get
have
a
better
chance
of
getting
rid
of
this
vertical
scroll
bar.
A
A
B
A
Yeah
I
mean
okay.
Maybe
how
about
are
you
given
the
idea?
How
about
let's
Let's
test,
drive
it
and
see
if
it's
worth
it
here,
we'll
give
ourselves
five
minutes
and
try
it
to
see
if
the
Prototype
looks
as
good
as
we
hope,
because
I
think
you
and
I
can
do
this
in
five
minutes:
live
yeah
yeah,
so
sis
admin-
you
reduce,
reverse
proxy
Toc
right.
So,
let's.
B
A
B
A
A
A
A
A
B
A
Okay,
so
here's
the
same
page
in
the
Prototype,
so
current
page
prototype,
so
it
takes
out
the
vertical
scroll
bar
uh-huh
and
now
what
did
you
want
to
see?
Oh.
B
Okay,
so
go
the
the
reverse
proxy,
the
general
one
see
there.
You
see
configuration
examples,
but
I,
don't
know
what
configuration
examples
are.
A
B
A
A
A
A
A
B
A
A
Now
that's
most
interesting:
is
it
broken
on
this
page
and
I
haven't
known
it?
No
that
works
just
fine.
A
Okay,
so
it
wasn't
as
fast
as
I'd
hoped
because
something's
wrong
with
this,
the
Prototype
and
it
oh,
oh,
wait
a
sec.
It
may
just
be
this.
B
A
A
A
A
A
B
A
A
A
A
A
A
I
can
do
the
nginx
thing
from
here,
but
when
I
try
h
a
proxy,
it
fails.
So
it's
that
there's
something
about
the
page
navigation,
that's
causing
it
to
want
that.
There
must
be
an
entry
on
the
left
for
a
page
on
the
right,
and
that
may
mean
that
we
have
to
move
the
page
down
one
level.
So
this
is
this
I
think
this
has
failed.
The
good
first
issue
test.