►
From YouTube: 2022 11 10 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
the
European
Jenkins
docs
office
hours.
This
is
the
November
10th
2022
Edition.
Today
we
have
Mark
Waite
myself,
Bruno,
Brockton
and
Alex
Brandis.
Here
for
the
agenda.
A
We
have
a
few
action
items
to
check
on
the
Jenkins
elections:
lots
of
updates
there,
the
Ops
World
2022
was
yesterday:
we've
had
our
weekly
2.377
release
and
our
most
recent
LTS
release
still
out
and
successfully,
and
we
have
our
next
LTS
coming
up
at
the
end
of
November,
which
will
be
the
December
LTS
technically,
even
though
it's
on
the
30th
this
month.
A
Okay,
all
right
so
Mark
archiving
the
docs
mailing
list.
I
know
that
that's
still
something
that
TBD.
A
No
worries,
thank
you
very
much.
We
did
publish
the
October
newsletter,
October
Jenkins
monthly
newsletter,
so
this
has
the
updates.
A
A
And
going
forward
we're
going
to
be
having
that
available
for
the
community
as
well
to
offer
notes,
suggestions
and
any
kind
of
feedback
on
it.
So
that
will
be
a
part
of
the
newsletter
process
going
forward
and
then,
lastly,
since
Oktoberfest
has
ended,
we
are
going
to
have
a
recap:
blog
post
for
hacktoberfest.
It's
going
to
share
user
insights
and
Pub
contributor
insights
and
stories.
Some
stats
overall
from
hacktoberfest
and
advice,
quotes
and
General
ideas
about
the
Oktoberfest
contributing
and
project
and
just
how
everyone
kind
of
did
this
year.
A
So
it's
going
to
be
great
and
we'll
have
a
lot
of
great
information
for
from
the
contributors.
A
A
48
members
in
the
Jenkins
election
voter
group,
there
are
plenty
of
more
contributors
to
Jenkins,
so
we
really
want
to
make
sure
that
everyone
is
aware
and
can
join
the
group
to
join
the
group.
All
you
need
is
an
account
on
community.jenkins.io.
A
You
can
use
your
GitHub
account
or,
if
you
don't
have
a
GitHub
account
or
want
to
use
a
separate
account
for
this.
You
can
sign
up
and
just
dedicate
it
to
the
elect
Jenkins
election
voting,
but
being
a
member
on
the
site
and
having
an
account
is
required
and
any
prior
participation
is
appreciated,
but
I
would
still
be.
The
person
would
still
need
to
register
for
the
2022
Edition.
This
is
unique.
A
This
is
a
different
group,
and
this
is
the
list
of
folks
who
we
will
then
send
out
to
the
Condors
internet
voting
service
so
that
we
can
proceed
from
there.
Voter
registration
is
open
until
November
17th,
so
by
all
means
there
is
still
time
please.
A
B
A
Thank
you,
Xena
internet
nominations
are
also
open
right
now
they
go
until
November
5th
so
today,
so
there
will
be
an
announcement
with
all
the
candidates
and
their
statements
regarding
why
you
should
vote
for
them
once
the
voter
registration
is
completed.
So
November
17th
is
the
tentative
date
that
all
candidates
will
be
announced.
The
voter
registration
is
closed
and
then
voter
voting
itself
will
actually
open
at
that
time
as
well.
A
There's
also
a
community
discourse
thread
for
this.
For
this,
so
there's
multiple
points
of
contact,
multiple
points
of
information,
there's
the
blog
post
and
the
Jenkins
Community
blog,
the
community
discourse
thread
and,
of
course,
we're
talking
about
this
as
much
as
possible
in
all
of
the
different
office
hours
of
meetings
and
just
across
the
board.
A
Yeah
participation
is
a
big
part
of
it,
so
yeah
all
right,
so
devops
roll
2022
was
yesterday.
It
was
held
online
since
everything
got
kind
of
remixed
and
rescheduled
registration
was
available
to
all.
It
is
open,
since
it's
online
now
and
it
has
been
recorded,
the
recordings
will
be
available
for
anyone
that
had
registered,
signed
up
and
I
think
you
still
might
be
able
to
sign
up
and
sign
in
for
that
purpose,
but
the
record
the
recordings
are
going
to
be
available
indefinitely.
A
So
even
if
you
weren't
able
to
make
the
sessions
that
they
had
yesterday
they're
still
available,
and
they
you
can
still
see
all
the
talks
and
sessions
that
did
get
presented
there.
The
there
were
a
lot
of
talks
that
were
not
able
to
be
presented
in
the
online
format.
So
what
we're
hoping
to
do
and
looking
to
do,
is
eventually
reschedule
those
and
have
them
presented
as
something
like
a
Jenkins
online.
D
A
Or
any
other
sort
of
community
event
that
we
can
host
that
way.
We
can
present
some
of
these
other
topics
that
we
did
not
get
to
share
at
devops
world,
so
the
plug
and
health
scoring
is
one
thing
that
we've
been
working
on
a
lot
recently
with
the
Google
summer
of
code.
Participants
helped
out
a
lot
with
and
that's
something
that
we
definitely
want
to
share
and
elaborate
on,
but
I
want
to
make
sure
that
we
have
the
right
space
and
the
right
means
to
do
so.
First.
B
B
So
Kevin
was
just
mentioning
devops
World
2022
and
that
many
of
the
talks
were
not
selected
to
be
presented
during
the
online
format.
Yeah.
C
B
C
B
Another
one
on
this
same
topic
fits
with
Bruno
and
me
is
this:
we've
got
upcoming
Google
summer
of
code,
2023,
we'll
start
very,
very
intense
promotion
of
it
in
the
January
February
time,
but
we
could
already
start
even
sooner
than
that.
If
we
wanted
to
do
a
copy
of
the
workshop
that
Bruno
and
John
Mark
and
I
had
prepared,
but
to
focus
it
online
and
say
we'll
take
up
to
six
or
up
to
four
Google
summer
of
code
interested
people
and
take
them
through
the
workshop
record.
B
We
would
really
do
it
in
in
Zoom
meeting
in
a
zoom
meeting,
not
in
a
webinar,
and
we
would
require
pre-registration
and
have
very
limited
attendance,
but
I
think
it's
a
possible
if,
if
we,
if
Bruno
and
others
get
hints
that
there
are
people
who
are
interested
in
it,
we
could
do
that
pretty
easily
spend
two
hours
with
a
group
of
four
to
six
interested
people
and
take
them
through
a
whole
series
of
exercises
on.
How
do
you
contribute
to
open
source.
A
And
that'll
be
separate
that
would
be
separate
from
the
contributor
Summit
Workshop
plug-in
tutorial,
all
that
sort
of
stuff.
That
would
be
separate.
It.
B
It
would
be
it's.
This
is
a
very
different
thing.
It's
focused
on
taking
for
or
at
most
six
people
who
who
have
never
contributed
to
Jenkins
before
and
bringing
them
to
the
point
where,
in
a
two-hour
period,
they
successfully
submit
their
first
pull
request,
request,
yeah
and
that
pull
request
is
valid
and
useful
and
helpful
to
the
project
cool.
So.
A
B
C
A
Hope,
I
hope
everyone
can
join
up
or
at
least
share
their
interest
levels
on
that,
because
that
sounds
like
a
great
time
sounds
like
a
crash
course
like
I
got
recently
so
yep
cool
all
right.
Anything
else
on
devops
world
2022.
To
mention.
A
All
right,
so
we
had
our
week
our
weekly
release
2.377
go
out
successfully
and
last
week
we
had
our
LTS
2.361.3,
that
which
will
be
the
last
release
for
the
2.361
LTS
series.
A
Last
week
there
Darren,
Pope
and
Mark
were
able
to
do
the
live
stream
going
over
what's
new
with
the
LTS,
so
that's
available
in
on
YouTube,
and
we
just
had
a
small,
a
small
section
to
go
over
the
weekly
change
log
process
as
now
I'm
helping
a
lot
more
with
getting
those
changed.
Log
entries,
updated
and
adjusted
to
be
better
presented
so
just
to
go
over
the
process,
and
then
Alex
did
want
to
share
some
insight.
He
had
into
I
think
it
was
this.
A
The
second
piece
here
so
Alex
by
all
by
all
means
just
let
me
know
or
I'll
stop
when
we
get
to
that
point
and
I'm
more
than
happy
to
have
you
share
what
you
want
to
share.
A
So
the
first
thing
that
happens
for
the
weekly
change
log
review
process
is
I
will
just
go
through
and
review
the
weekly
change
log
and
verify
that
there
are
entries
to
change
and
what
they
need
to
be
changed
to
and
then
I'll
create
a
draft
pull
request,
that's
available
for
review
and
feedback.
That
just
suggests
the
changes,
I
plan
on
that
I'm
seeing
and
want
to
make
and
then
once
that's
created,
Mark
may
or
may
not
apply
the
changes
prior
to
it
being
published.
A
D
Yeah
yeah
thanks
Kevin,
that
sounds
like
a
good
workflow
yeah
that
is
placed
properly
there.
My
initial
question
was:
the
automatic
PRS
generated
are
basically
based
on
the
proposed
change.
Lock,
entry
of
pull
requests
submitted
to
Jenkins,
like
Jenkins
Jenkins
as
the
core
itself.
D
B
Sure
I
I,
so
Kevin
I'm
in
a
I'm
going
to
jump
in
here.
If
that's,
okay,
so
Alex,
there
are
some
things
that
we
can
do
that
I
think
confidently
would
actually
improve
it
and
others
where
people
continue
to
ignore.
What's
written
in
the
file
and
they'll
continue
to
ignore
it,
so
so
the
first
what
we
can
improve
right
now
in
the
pull
request
template
the
the
bullet
item
for
the
change.
Like
entry
starts
with
a
dash.
D
B
B
If
I
remember
right,
but
really
people
don't
read
it
or
or
they
they
write,
something
that
is
completely
different
or
off
and
I
think
the
answer
there
is
saying
use
the
imperative
form
is
the
best
we're
going
to
get
and
Kevin
or
other
writers
will
have
to
correct
it
as
necessary.
There's
not
much.
We
can
do
to
change
that.
One.
D
Yeah
as
someone
who
submits
a
few
pull
requests
which
are
not
labeled
as
skip
change,
lock,
I
can
only
speak
for
myself,
but
I
always
find
hard
to
come
up
with
a
change
like
entry.
That
is
not
super
in
detail,
because,
if
I'm,
if
I
mention
some
files
like
Angeli
or
something
that
I
did
change,
that
is
not
really
helpful
for
the
end
user
change
lock,
maybe
for
the
GitHub
change
lock,
but
not
for
something
we
publish
on
jenkins.io,
so
I
always
try
to
break
things
down
to
make
them
easy
to
understand.
B
And
and
and
that's
exactly
I
think
the
value
that
Kevin
and
other
changelog
reviewers
bring.
Is
it's
okay,
that
the
author
of
a
pull
request
expresses
the
chainsaw
as
best
they
can
Kevin
now
comes
in
thinking
like
an
end
user
and
his
extra
set
of
eyes
may
help
us
get
a
better
one,
so
I
think
what
you're
describing
is
an
ideal
process.
It's
just
fine!
It's
why
we
like
that.
There's
a
team
of
reviewers
that
look
at
the
changelog
after
the
after
the
submitter
does
their
best
job.
They
can.
D
Yeah
I
think
that's
needed,
because
if
you
compare
the
change
lock
off
from
the
GitHub
releases
tab
with
what
we
have
on
jenkins.io,
there's,
always
a
big
difference
into
how
things
are
actually
described.
The
GitHub
change
log
is
much
more
in
like
this
is
much
more
technical
phrasing
from
what
I
noticed
so
yeah.
B
Exactly
and
and
you're
you're,
absolutely
correct
and
I
think
I
think
that's!
Okay
right!
We
we've
we've
said
that
we
want
and
we
like
a
curated
changelog,
and
we
know
that
for
LTS
releases
we
really
have
to
have
someone
who
who
decides
what
should
be
in
or
out
and
and
so
since
we're
going
to
be
curating
we're
going
to
be
reviewing
we'll
just
take
advantage
of
that
and
keep
doing
it.
A
And
one
of
the
other
things
too
Alex
that
I've
found
I'm
doing
most
than
anything
else
is
reordering
the
entries
themselves,
because
a
lot
of
them
will
come
in
with
the
developer
ones
at
the
top
of
the
list,
which
ultimately
should
be
at
the
bottom
of
the
list.
So
it's
a
lot
of
rearranging
and
reformatting
Those
ads
I
come
across
them.
So
it's
not
it's
a
lot
just
like
of
streamlining
it
and
reformatting
things
more
than
changing
anything.
A
There
are
some
messages
that
I
might
update
to
reflect
a
little
bit
better
like
what
happened
or
if
there
is
a
bunch
of
small
minor
things
that
don't
need
to
be
described
like
a
Spring
Security
fix.
We
might
summarize
that
part
of
it
but
yeah
like
honestly
I'm
taking
a
lot
of
what's
already
there
and
just
putting
it
into
a
different
place.
B
You
do
make
a
good
point.
Kevin
on
the
the
developer,
changelog
entries,
the
the
guidelines
say,
move
the
goes
to
the
end
and
the
tool
doesn't
move
them
to
the
end
and
if
a
developer,
someone
who's
comfortable
with
that
tool,
could
extend
the
tool
to
put
developer
items
at
the
end.
That
would
reduce
one
of
the
things.
That's
a
fair
one.
D
I
mean
on
the
different
note,
I
think
the
chainsaw
generator
picks
up
the
developer
label.
We
put
on
PRS,
but
this
is
at
least
to
my
understanding,
only
useful
for
the
GitHub
change
lock,
because
the
Jenkins
IO
change
lock
has
only
two
kinds
of
items
like
we
have
bug
fixes
and
we
have
enhancements.
We
can't
really
highlight
something
as
developer
or
like
as
dependency
updates
there
only
if
we
are
prefixing
them,
but
prefix
them
them
with
developer
and
then
the
entry.
B
Actually,
the
the
change
log
has
the
concept
of
developer
and
if
you
look
at
the
fields
that
the
generator
writes,
one
of
them,
I
believe
is
called
category
and
developer
is
a
valid
value
for
that,
so
it
it
actually
does
know
about
it,
but
it
doesn't
present
them
to
the
user
in
a
visibly
different
way.
We
just
have
a
working
rule
that
if
it's
a
developer
topic,
we
put
it
at
the
end,
but
the
the
generator
doesn't
do
that
ordering
for
us
and
it
it
is
willing
to
do
other
ordering.
It
just
doesn't
do
that.
B
D
Yeah
I
was
I
meant
it
in
terms
of
colors
like
for
bug,
fixes.
We
have
the
red
one
for
enhancers.
We
have
the
purple
one
and
for
security,
fixes
the
yellow
one
like
there's,
no
real
color
to
distinguish
between
what
is
actually
for
developers
or
what
is
like,
I,
don't
know,
an
enhancement
in
terms
of
UI.
A
Alex
I
really
appreciate
that
again,
like
that's
awesome,
to
be
considering
and
thinking
of,
and
definitely
helps
with
kind
of
just
what
I'm
looking
at
on
a
regular
basis
as
well
for
sure,
because
I
want
to
make
sure
that
this
is
what's
being
shared
with
me
in
the
first
place
and
what's
what
everyone's
working
on
I
definitely
don't
want
to
make
any
changes
that
change
the
message
or
take
away
from
what
was
actually
done
as
far
as
work
goes,
so
anything
that
any
kind
of
feedback
or
anything
that
you
think
of
that
can
assist
with
that
or
make
life
easier
for
everyone.
A
Cool
all
right,
so
yeah
and
yeah
and
we'll
have
the
next
LTS
is
going
to
be
on
the
November
30th
release.
So
this
will
be
2.375.1.
So
in
the
next
version,
we're
going
to
be
coming
out
with
is
using
Baseline
2.375.
A
So
this
will
be
the
start
of
the
next
LTS
line.
The
change
log
and
upgrade
guide
are
needed
still
so
we're
going
to
have
the
changes
since
2.361
and
backboards
of
anything
since
2.375
was
actually
released.
Alex
is
the
release
lead
so
again,
Alex.
A
Thank
you
very,
very
much
for
volunteering
and
taking
over
as
we
go
to
the
last
last
new
LTS
of
the
year
really
or
the
theft
yeah
kind
of
not
really
but
yeah,
really
exciting,
really
really
really
great
stuff
and
there's
a
there's
been
a
ton
of
stuff
changed
and
fixed
and
added.
So
there's
going
to
be
a
it's
a
large
change
log,
this
time
around,
which
will
be
fun
great.
So
we
got
through
everything
on
the
list
here
on
the
agenda.
D
Yeah
just
really
quick
timing
in
on
yesterday
and
not
yesterday,
last
week's
Asia
doc's
office
hours
I
think
what
was
it
Chris
or
someone
else
brought
up.
The
LTS
checklist
is
pretty
not
much
of
use.
A
Yeah
Chris
yeah,
it
looks
like
there
was
a
mention
of
like
Chris
being
able
to
share
kind
of
his
release,
lead
experience.
D
B
D
Yeah
I
know
that
the
checklist
might
be
a
bit
confusing
I
mean
I
got
used
to
it
over
the
past
few
releases,
but
maybe
I
could
write
something
down
like
an
actual
text
form
rather
than
something
in
bullet
lists,
to
outline
what
actually
needs
to
be
done
and
how
things
need
to
be
done
rather
than
having
a
bullet
list.
Saying
hey.
You
need
to
do
this
and
this
here,
but
doesn't
explain
why
things
need
to
be
done.
Yeah
would
be
helpful
for
young
blood.
B
So
the
the
case
I'm
used
to
the
checklist
story
is
piloted
an
aircraft
who
spent
hundreds
of
hours
flying
airplanes,
but
a
checklist
assures
they
don't
make
make
foolish
mistakes,
but
it's
it's
not
a
training
document.
So
what
you're
proposing
I
love
it?
It's
the
idea
of
something
that
would
be
a
tutorial,
an
introduction
or
a
training
document,
not
just
the
checklist
I
like
that.
If
you're
willing
to
do
that
Alex,
that
would
be
great
yeah.
D
B
That
was,
that
would
be
me
and
Tim
General.
You
nailed
it
and
and
then
refined
by
you
and
refined
by
Chris
and
refined
by
yeah,
IL
defonso
and
Kathy
Chan
exactly
yep.
It's
yeah.
D
D
Yeah,
we
have
had
quite
a
few
PRS
to
the
checklist
over
the
past
few
months,
updating
a
bit
of
documentation
here
and
there
making
things
a
bit
more
clear
and
thanks
to
people
like
Joseph
Patterson,
who
Outsource
a
lot
of
work
to
updately
used
in
the
Beloved
materials
or
jcast,
to
reduce
the
need
to
submit
PRS
by
hand.
But
yeah
there's
still
a
lot
of
stuff.
You
need
to
do
by
hand,
and
that
is
barely
to
not
outlined
within
the
checklist.
D
B
D
B
A
Great
all
right,
thank
you
very
much.
Alex
appreciate
that
and
the
insight's
really
great
to
hear
and
clearly
can
lead
to
some
improvements
down
the
line.
A
So
that
covers
everything
that
we
had
on
the
agenda
for
today.
Is
there
anything
else
that
anyone
would
like
to
share
or
bring
up
I
know,
I
already
asked,
but
figured
once
again
in
case,
like
Alex
bird,
anything
going
once
all
right,
cool,
so
I
think
we
can
stop
the
recording,
then
Mark,
and
it
will
be.