►
From YouTube: 2022 11 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).
B
A
All
right,
so,
let's,
let's
take
those
then
so
first
action
items
I,
unfortunately
have
nothing
to
report
other
than
I've
made
no
progress.
There
is,
however,
a
monthly
Jenkins
newsletter
and
encourage
everybody
to
read
it.
It
comes
out
naturally,
once
a
month
as
a
blog
post.
It
comes
with
feedback
and
comments
from
the
special
interest
groups
from
various
other
places,
highlighting
the
results
from
that
month.
A
Yeah,
so
Alyssa
is
doing
it
with
help
from
Bruno,
ver,
Ashton
and
so
Bruno.
Does
the
technical
work
to
create
the
pull
request
and
Alyssa
gathers
the
content
if
you'd
like
to
submit
content.
You're
welcome
to
do
so.
She's
preparing
the
October
Edition
now
and
we'll
she's
going
to
switch
her
preparation
technique
in
the
future
to
use
community.jenkins.io
instead
of
using
a
simple
Google
doc.
So
look
forward
to
that
any
questions
on
the
action
items.
B
A
C
A
B
A
Got
some
Canada
a
candidate
for
the
board,
Basel
Crow,
but
he's
a
cloud
bees,
employee
and
so
we're
having
discussions
right
now
about?
Are
we
allowed
to
have
three
people
affiliated
with
cloudbees
on
the
board,
because
kosuke
is
still
officially
on
the
board,
even
though
he's
not
doing
anything
on
the
board
and
I'm
on
the
board
and
the
the
past
rules
were
always
that
kosuke
is
being
an
advisor
to
Cloud.
Bees
meant
he
was
affiliated
with
Cloud
bees,
so
discussions
are
ongoing
right.
A
A
C
A
A
No,
no
it's
yeah.
A
single
single
nomination
is
enough
to
bring
the
person
up
for
consideration
to
the
board,
but
if,
if,
for
instance,
any
of
you
say,
hey
I'd
like
to
be
the
docs
officer,
you
could
certainly
nominate
yourself
and
say
I'm
I'm
interested
in
that
and
then
then
the
election
will
work
it
out.
B
A
A
B
A
A
So
November
9th
next
Wednesday
whoops
November
9th
next
Wednesday
devops
world
will
be
presented
in
an
online
format,
but
it
will
instead
of
a
three-day
event.
It
will
be
a
four
hour
event.
A
It'll
be
done
at
two
different
times,
one
for
Asia,
one
for
Europe
I,
believe
it's
the
same
content
both
times
and
there's
no
charge
to
attend
so
you'll
you're
welcome
to
attend
there
because
they've
had
to
collapse
three
days
into
four
hours.
Many
of
the
talks
that
were
accepted
for
Orlando
could
not
be
in
the
online
event.
That
unfortunately
includes
the
contributing
to
open
source
talk
or
it's
contributing
open
source.
Workshop.
D
A
Yeah
and
I
I
haven't
looked
at
the
agenda
so
I.
It's
a
good
question
so
we'll
have
to
I'll
have
to
do
some
further
asking
around
to
see
who
what
the
the
agenda
topics
are.
Etc.
A
B
A
The
the
question
then,
for
us
as
a
group,
is
other
ways
we
might
present
those
talks
so
Jenkins
online
meetups
for
the
talks
was
one
idea
that,
for
instance,
plug-in
Health
scoring
would
be
a
good
thing
to
do
in
an
online
Meetup
have
Jake
and
rancha,
and
then
we
could
even
have
Adrian
and
diraj.
Potentially
even
you
join
for
a
conversation
about
what
that
would
mean.
A
The
workshops
could
be
done
in
a
slightly
different
format.
Workshop
could
be,
could
be
a.
What
would
you
call
it?
A
must
register
registrations
accepted
for
a
small
group
of
people
right
right
because
really
doing
it
online
it's
complicated.
If
we
do
try
to
do
large
groups,
but
a
small
group
of
people,
we
might
have
a
potentially
very
successful
experience
there.
I've
just
got
a
talk
with
my
colleagues
to
see
if
they're,
if
they
can
see
a
way
to
break
loose
the
time
to
do
it.
B
A
Although
there
I
suspect
the
recordings
of
those
kind
of
things,
the
ones
that
Darren
and
I
did
are
probably
far
superior
because
it's
just
the
two
of
us
and
working
through
exactly
things
so.
C
A
A
Exactly
that,
that's
the
idea.
There
is
the
workshop
experience
that
we
had
intended
was
live.
Coding,
live
debugging,
Etc
and
the
challenge,
then,
is
we
don't
want?
We
don't
want
the
risk
of
some
random
person
coming
in
and
disrupting
by
malicious
Zoom
bombing,
so
we
would
have
to
use
a
registration
system,
probably
password,
protect
Etc,
and
then
we
just
go
ahead.
D
Yep
and
we
don't
have
a
date
for
Jenkins
online
Meetup,
yet
right,
no.
D
B
A
A
Right
yeah,
so
online
meetups
can
be
as
short
or
long
as
we
want.
Certainly
I
would
never
want
an
online
Meetup
to
go
over
two
hours
and
most
typically
one
hour
or
less.
A
A
D
A
A
A
Exactly
the
the
common,
the
common
problems,
there
are
things
like:
oh
somebody
failed
to
put
a
hard
stop
at
the
end
of
the
line.
Oh
somebody
put
fail
to
classify
the
the
the
the
the
pull
request
at
all,
and
so
it
doesn't
have
a
classification
assigned,
or
they
gave
a
really
poorly
phrased
description
or
a
poorly
phrased
summary,
and
so
that
has
to
be
corrected
and
he
proposes
all
those
as
part
of
that
corrective
pull
request.
This
corrective
pull
request
is
actually
never
applied.
A
Well,
and-
and
certainly
we
welcome
anybody
who's
available
to
help
with
it
is
welcome
to,
as
it
turns
out
part
of
my
desire
to
prepare
Kevin
to
be
a
candidate
for
documentation
officer
was
I,
wanted
to
be
sure.
He
knew
how
to
do
weekly
change
logs
without
me,
and
so,
while
I
was
on
vacation.
Those
two
plus
weeks
Kevin
was
doing
weekly
change
logs
and
he
did
quite
well.
D
A
Okay,
next
and
this
one
may
be
of
interest
to
Chris
the
next
LTS
Baseline
has
been
selected
as
2.375..
It
will
release
November,
30th,
Kevin
and
I
will
work
on
creating
the
LTS
changelog
he's
he's
going
to
create
it
himself
as
the
first
draft,
and
then
he
and
I
will
review
it.
We
may
ask
the
others
here
in
the
doc's
office
hours
to
review
it
as
well,
but
it's
a
good
practice.
He
and
I
have
been
through
LTS
changelog
prep
at
least
three
times
previously,
so
it
feels
like
he's.
A
So
any
questions,
oh
the
reason.
I
said
this
might
be
interesting.
Chris
you've
been
a
release
lead
for
previous
long-term
support
releases.
If
you're
interested
in
being
released
lead
again
and
the
timing
works,
I
suspect
that
Tim
Jacob
will
put
out
the
request,
saying:
hey,
who
would
like
to
be
a
release?
Lead.
C
A
D
I
have
a
question
for
Chris,
so
how
is
your
experience
doing
the
releases
for
these
change
logs.
C
It
depends
because,
because
the
first
time
was
easy,
but
the
second
time
it
was
kind
of
more
challenging
for
me,
but
sometimes
it's
just
Communications
to
you
because,
like
back
and
forth,
like
I
need
some
notifications
right
well,
the
thing
is:
I
may
get
some
instructions
to
change
or
crack
some.
Some
like
commits
I've
made,
but
sometimes
like
the
communications,
may
not
be
100,
queer
and
so
yeah
that
that
could
be
easier.
C
A
C
A
And
and
the
trick
there
is
when
those
cases
when
we
detect
them,
we
submit
a
pull
request
to
fix
it
right,
but
that
meant
poor
Chris
on
occasion
was
left
with
I
wonder
what
they
meant
when
they
wrote
that,
because
it
was
written
almost
halfway
in
in
secret
code,
sometimes
so,.
B
A
Exactly
yep
and
that's
and
that's
that's
the
challenge
of
a
checklist
right,
checklists
from
from
Dr
gowanda's
checklist,
Manifesto
checklists
are
oftentimes
focused
on
Experts
practitioners.
You
know
when
a
pilot
goes
through
a
checklist.
They
use
all
sorts
of
shortcut
words
to
describe
things
because
rapid
pass
through
the
checklist
is
the
thing,
but
in
this
case
it's
also
a
teaching
tool
for
new
new
people
who
are
working
and
therefore
we
need
to
get
it
improve.
It's
keep
it
proving
it's
phrasing
right.
A
B
A
A
So
cool
yeah
and
and
now
as
a
fun
comparison,
there
were
almost
1
200
non-automated
PRS
submitted
during
October
10
to
15
percent
increase
compared
to
previous
preceding
months.
So
there's
been
a
real
real
positive
here
and
the
the
anecdotal
evidence
indicates
that
the
the
spam
rate
was
quite
low
even
better
this
year
than
last
year.
A
What
what
happens
is
sometimes
people
decide
that
they'll
submit
a
junk
pull
request
to
a
project
in
hopes
of
it
being
easy
and
getting
accepted
and
what
happened
in
years
past
was
open.
Source
can
open
source.
Maintainers
were
quite
frustrated
by
that,
because
now
they
were
wasting
time,
processing,
people's
silly
or
useless
pull
requests,
and
in
this
case
it
didn't
happen.
A
Because
we,
we
had
a
very
serious
threat
if,
if
you
have
two
spam,
pull
requests,
if,
if
digitalocean
detects
that
you
had
done
two
spam
pull
requests
you
rejected
from
the
program,
you
cannot
complete
it
successfully
if
you,
if,
if
two
of
your
pull
requests
are
flagged
as
spam.
C
A
That's
that's
I,
think,
that's
really!
Well!
The
there
is
I
guess,
there's
another
happy
story
here
and
we'll
get
into
highlights
in
just
a
moment.
But
the
one
of
the
happy
stories
for
me
is
that
that
contributing
to
open
source
tutorial
that
became
improve
a
plug-in
the
one
that
we
spent
a
year
creating
right.
It
started
in
hacktoberfest,
2021
and
then,
as
docs
office
hours.
We
worked
on
it
repeatedly
diraj
you
and
you
and
I
started
the
thing
and
we
worked
it
together
and
then
Meg
encouraged
it
and
Kristen
encouraged
it.
A
That
thing
finally
turned
out
to
be
very,
very
successful
for
hacktoberfest
we
had
at
least
four
or
five
people
who
said
hey.
Thank
you
for
that
contributing
guide,
it
was
great.
I
was
able
to
contribute
useful
I,
understood
it.
I've
learned
more
things
and
and
I
think
we
had
a
real
positive
from
that,
and
we've
got
now
a
good
idea
for
Google
summer
of
code
next
year,
based
on
the
concepts
in
that
tutorial
cool.
A
D
That's
a
very
nice
thing
to
mention,
because
the
biggest
point,
or
something
that
shines
in
this
story
is
the
YouTube
video,
the
live
stream
that
you
did
with
Darren.
That
was
very,
very
helpful
for
the
people
who
were
following
this
tutorial,
so
big
shout
out
for
that
live
stream
and
those
videos,
and
then
thank
you
for
those
that
document
contributing
to
open
source
by
mentioning
everything
in
such
a
detailed
way
for
any
newcomer
to
learn.
A
And
I
think
that's
that
was
really
really
positive.
I
I
liked
I
liked
the
results
we
got
from
hacktoberfest
20
to
22..
We
really
one
was.
We
avoided
the
mistake
that
we've
made
in
the
past
of
offering
challenging
repositories
as
part
of
the
part
of
the
hacktoberfest.
So,
for
example,
I
did
not
even
offer
the
get
Plug-In
or
the
get
client
plugin,
because
because
they're
just
too
challenging,
there
are
just
too
many
things
that
can
go
wrong
with
people
trying
to
do
pull
requests
there.
A
A
Yeah
interesting
idea,
thanks.
Let
me
let
me
make
a
note.
That's
consider
a
blog
post
on
hints
for
success
with
new
contributors
and
and
they're.
Not
none
of
them
are
bulletproof.
None
of
them
are
flawless,
but
things
like
mentors
available
right
right
tasks
that
are
valuable
but
simple,
right
and.
B
A
A
A
So
for
those
who
written
steps,
video
steps
Etc
right
because
there
are
some
people
for
whom
the
written
steps
may
not
be
as
as
readily
approachable
as
watching
us
on
screen.
Where
you
see
someone
making
specific
changes
in
an
IDE,
a
good
yeah.
B
A
A
Well,
and-
and
that's
that
maybe
that's
the
most
important
one
of
all-
is
keep
making
mistakes
and
keep
learning
from
those
mistakes
right
right
because
she
does
she
go
to
Africa.
Work
was
sort
of
sort
of
really
bad
on
the
first
iterations
it's,
but
we
learned
from
them
Stakes
right.
C
A
B
B
D
I
noticed
during
this
October
month
that
there
were
few
people
who
messaged
me
personally,
trying
to
ask
me
hey
what
should
I
do?
How
should
I
do
things
and
contribute
to
Jenkins
so
I
so
assistant
them
the
same
tutorial
or
and
some
general
things
as
well,
and
they
can
pick
anything
that
works
for
them.
So
then
they
picked
out
this
tutorial.
D
A
Yeah
very
well
and
that
that
is
a
that
is
a
I,
would
assume
in
the
captain.
Project
Meg
sees
the
same
kinds
of
things
where
there
is
an
awful
lot
of
specialized
knowledge
required
to
in
order
in
order
to
successfully
write
a
test.
But
how
does
one
acquire
that
knowledge
is
an
excellent
thing
for
a
tutorial
to
say,
look
we're
going
to
learn
together
in
this
tutorial.
Here's
how
you
use
your
debugger,
here's
how
you
watch
what's
happening
in
this
thing
with
your
debugger,
because
writing
a
test,
at
least
for
me.
A
B
Well
again,
I
mean
and
Mark
hammered
years
with.
Mark
testing
is
the
great
Achilles
heel
right
now
of
of
software
everywhere,
but
I
think,
especially
in
open
source,
because
it's
a
lot
more
fun
to
code
than
to
write
a
test.
Suite.
A
Well,
and
and
actually
a
lot
of
tests,
many
of
them
become
liabilities
over
the
long
life
of
a
project,
because
now
I
have
to
maintain
the
test,
in
addition
to
the
code
and
I've,
it
requires
thinking
about
both
of
them.
I
like
that
thinking,
but
but
really
it
there
isn't
it's
not
free
to
have
tests,
it's
also
expensive
to
not
have
them
so.
B
D
C
B
Industry
needs
this
stuff
and
there
isn't
easy
stuff
out.
There
is
an
accessible
stuff
out
right
that
right,
Mark
there's
like
big
classes
you
can
take,
but
but
if
you
like
it
and
they're
interesting,
you
should
think
about
that.
You
should
be
in
10
years.
You
should
be
somebody
that
everybody
goes.
Oh
dear
Ash,
you
knew
him
when
he
was
just
starting
out
wow.
A
Yeah,
what
at
least
I
think
what
Meg's
pointing
you
to
is.
The
testing
is
at
least
as
technically
complicated
a
field
as
software
creation,
because,
while
software
creation
has
to
worry
about
all
the
things
you
want,
the
software
to
do,
software
testing
also
has
to
worry
about.
How
do
we
check
that?
It's
not
doing
the
things
that
shouldn't
there
there's
a
software
testing
is
a
fascinating
domain.
B
B
B
D
A
So,
for
instance,
there
are
some
easy
ones
upgrade
the
the
parent
Palm.
There
are
some
more
challenging
ones,
replace
jota
time
with
Java
classes,
replace
HTTP
client
with
in
Java
11
with
the
native
Java,
those
kinds
of
things
and
and
there's
this
tool
called
open
rewrite
that
looks
like
quite
promising
as
a
way
to
write
these.
A
A
What
they
did
was
they
had
a
specific
problem.
They
were
trying
to
solve,
for
instance,
in
this
case,
I
think
it
was.
There
were
specific
types
of
security
issues
where
you
shouldn't
perform.
The
following
calls
it's
unhealthy
and
what
what
the
submitter
did
was
had
an
open
rewrite
rule
that
would
read
the
source
code
and
when
it
detected
that
flawed
Behavior,
it
would
rewrite
it
and
prepare
and
ship
a
pull
request.
A
B
C
A
D
C
A
A
So
first
things:
first,
we
had
in
doc's
office
hours,
I,
think
six
or
eight
weeks
ago
identified
a
non-trivial
challenge
that
the
developer
documentation
had
no
left-hand
navigation.
That
was
anywhere
near
acceptable.
What
it
had
was
a
long
list,
and
that
was
it,
whereas
the
left
hand
bar
on
the
user
documentation
had
very
nice
expanding
and
Contracting
things.
A
Now,
if
I
go
back
here
to
create
a
plugin,
Okay
navigation
there,
the
how-to
guides
reference
architecture,
reference
topics,
all
of
it
living
in
this
same
kind
of
layout,
as
we
have
with
the
user
documentation.
So
watch
this
as
I
go
to
the
user
guide.
Here's
the
same
experience
with
the
user
guide,
so
Chris.
Thank
you
very,
very
much.
Marvelous
I
sincerely
doubted
anybody
would
be
able
to
do
this
within
the
context
of
hacktoberfest
and.
B
A
A
B
D
C
D
So
for
this,
given
page,
if
you
want
to
you
know
if
you
hover
over
the
references
heading,
so
this.
A
D
A
A
A
D
D
A
A
Notice
that,
let's
look
at
it
now-
and
this
is
this-
is
the
the
current
look-
it
stays
nice.
We
don't
have
a
scroll
bar
at
all,
because
it's
it's
small
enough
that
it
doesn't
need
the
scroll
bar.
What
we
had
previously
was
as
though
this
release
reverse
proxy
configuration
was
always
expanded
and
users
will
have
at
most
one
of
these
reverse
proxies,
and
many
of
them
will
have
none
of
them.
So
for
them
it
wasn't
valuable
for
us
to
show
reverse
proxy
squid
or
IIs.
They
may
not
be
running
on
windows
at
all.
A
Iis
is
nonsense
for
them,
so
what
Chris
has
done?
Is
he
found
a
way
to
and
and
again
this
was
we
did
this
eight
or
ten
weeks
ago
identified
an
issue
listed.
The
issue
in
jenkins.io
marked
it
for
hacktoberfest
and
did
not
Market
good
first
tissue,
because
it
definitely
was
not
a
good
first
issue,
but
Chris
has
figured
out
a
way
to
make
it
work
and,
and
the
navigation
is
just
as
sweet
as
can
be.
Oh.
C
A
A
So
it's
two
years
out
of
date
and
in
the
world
of
kubernetes
two
years
is
almost
a
lifetime
so
great
that
that
change
thanks
very
much.
Then
we
got
some
cool
artwork
from
from
a
person
in
Turkey.
Yes,
here
is
Jenkins
in
Turkey.
Here's
Jenkins
for
Georgia
the
the
Georgia
Republic,
oh
wow,
and
here
is
nerd
Jenkins.
D
B
A
D
A
Do
not
that's
one
where
I've
it's
that's
a
dark
corner
of
the
world,
because
I.
B
B
B
A
B
The
list,
where
is
where's
the
the
the
woman
I,
didn't
see
the
woman
on
that
level.