►
From YouTube: 2023 05 19 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
everyone:
this
is
the
19th
of
May.
It's
documentation,
office
hours
topics,
I've,
got
Kevin's
unavailability
pipeline
steps,
ref
end
of
life
notifications,
early
end
of
life;
anything
else
that
needs
to
go
on
the
list.
Chris
did
you
want
some
something
for
Google
summer
of
code,
yeah,
probably.
B
A
Great
all
right,
so,
let's
go
first
topic,
then
Kevin
Martin's
unavailable
until
June
12th,
so
Kevin
has
shared
with
the
board
the
Jenkins
board
that
he'll
be
unavailable
until
the
12th
of
June.
So
we're
we're
trying
to
decode
what
can
we
do
to
handle
his
absence
as
documentation
officer?
So
one
of
the
things
we'll
do
is
accept
that
we're
going
to
delay
this
the
work
on
this
Java
11
to
Java
17
transition.
A
This
is
where
we
need
to
document
how
to
install
make
our
default
documentation
install
from
java
17
rather
than
from
java
11..
It's
a
it's,
not
time
critical,
but
we
wanted
to
get.
It
started
around
the
time
that
Debian
12
releases
right
now,
they've
announced
Debian
12
were
released
sometime
in
June,
so
I'm
not
overly
worried
by
it.
C
Do
we
have
do
any
I've
been
out
of
it,
but
a
couple
of
years
ago
we
had
some
guidance
for
performance
for
the
various
Java
things
to
do
and
it
was
sort
of
java
release
specific.
Are
there
any
changes
of
that
for
17?
Anything
like
that
or
not.
A
A
Lot
of
custom
tuning
Chris:
do
you
have
any
specific
experience
there.
B
I've
heard
about
it,
but
personally
I,
don't
I,
don't
know,
there's
that
much
of
a
difference,
maybe
a
little
bit.
C
A
C
A
A
All
right,
okay,
so
so
now
the
next
piece
is
there.
There
are
certainly
other
things
that
Kevin
does.
For
instance,
he
would
regularly
review
the
pull
requests
submitted
to
jenkins.io
and
what
we're
proposing
there
is
hey
until
mid-june.
When
he's
back.
Let's
invite
others
to
assist
so
Bruno
Marsden
has
agreed
to
assist.
A
A
D
A
D
C
A
A
C
D
A
C
A
C
That
you
could
go
through
faster,
so
great,
whatever
works
for
you,
I
always
enjoy
working
with
you.
I
always
learn.
Something,
though
thank.
A
You
thanks
very
much
so
I'll.
Do
the
weekly
change
logs?
That's
not
a
not
a
big
burden
because
most
of
it's
automated
and
for
the
upcoming
long-term
support
release,
2.401.1
I'll
handle
changelog
and
upgrade
guide
as
a
way
to
be
sure
that
I'm
still
able
to
do
that.
Confidently.
Kevin's
done
the
last
four
or
five,
maybe
six
or
seven,
and
so
I've
gotten
a
little
rusty.
A
We
hope
so,
yes,
the
release
lead
for
Alex
Alexander
Brandis
is
release,
lead
and
he's
been
patient
with
me
in
the
past,
the
set
of
changes
doesn't
look
huge.
B
So
I
the
thing
I
would
like
to
discuss
about
is
like
the
documentation.
Processes
of
different
projects
feels
like
right.
Now
we
don't
have
a
scientific
ways
to
do
things,
so
it
was
like
different
people
adopt
different
kind
of
like
Technologies,
for
keeping
track
of
documentation,
and
we
may
want
to
make
some
recommendations
about
2D
what
to
use.
What
what's
available,
that
sort
of
things.
A
B
A
So
one
is
Google
doc
to
to
maintain
notes,
maintain
meeting,
notes,
blog
posts
for
status
reports,
and
so
this
was
let's
call
this:
the
the
past
techniques
flawed
and
imperfect,
as
they
were
blog
posts
for
status
reports,
meetups
for
interactive
sessions
for
demos
and
interactive
question
and
answer
yep.
A
A
B
A
Now
is
it
to
all
participants
or
to
at
least
some,
so
it's
it's.
It's
immediately
available
without
upload
to
Youtube.
B
Yep
but
the
downside
is
you:
don't
have
a
copy
on
YouTube,
correct,
yeah.
A
A
Do
community
bonding
is
in
progress
all
right
and
each
group
is
meeting
with
each
set
of
mentors
our
meeting
with
the
contributor,
and
there
is
a
checklist
provided
by
the
org
admins
that
we're
using
to
be
sure
that
we
make
sure
we
do
the
do
the
community
bonding
well,
there's
also
a
checklist
on
the
project
overall
right
and
then
there's
an
overall
checklist
provided
by
the
org
admins
and
that
just
came
out
was
it
yesterday
Chris?
Maybe
today.
B
Don't
think
so
I
might
be
interested
in
is
to
use
something
like
I
mean
I'm
thinking.
It's
like
I
think
we've
used
it
in
the
past
for
some
projects
so
get
up.
Wakey,
that's
one
also
like
maybe
maybe
like.
B
We
can
try
like
try
alone
or
maybe
get
projects
depending
on
the
like
the
ability
of
the
resource.
So
it's
like
for
projects.
It
may
not
be
available
for
some
people
for
for
certain
projects
like
jenkins.io
rebuilding.
A
A
Okay,
and
so
so,
Trello
Trello
and
GitHub
projects
are
both
quite
good
at
task
tracking
right,
that's
yeah,
so
in
and
in
terms
of
that,
couldn't
we
also
consider
using
if
we're
talking
about
task
tracking,
we
could
also
consider
Jenkins
jira
right
I
mean
puzzle.
Crow
uses
Jenkins
jira
quite
effectively
with
epics
to
capture
the
big
picture.
D
D
A
B
C
And
just
with
GitHub
somebody
and
Captain
who's
very
good
is
actually
because
we
have.
We
are
not
using
jira
for
for
the
open
source
work
and
we
just
have
a
label
an
epic
label
right,
so
we
have
documentation
and
then
he
has
sort
of
a
forum
where
you
know
describe
the
problem
and
what's
the
solution
going
to
look
like
in
all
this
and
then
and
then
manually
as
you
create
the
individual
issues
at
the
bottom?
There's
a
list
of
issues
that
are
tied
to
that.
C
C
You
know
the
you
know
the
whole,
the
small
PR,
and
you
forget
that
bugged
me
at
first
too,
because
I
was
used
to
thinking
the
big
thing
you
know
and
I
realized.
It
would
have
been
much
easier
if
we'd
done
that
as
a
group
done.
Initial
training
on
this
is
how
you
do
stuff,
rather
than
where
you're
constantly
criticizing
them
and
then
they'd
feel
beleaguered
and
they'd
go
off
and
they'd
try
to
do
better,
and
it's
like
okay
I
only
put
eight
weeks
of
work
into
this.
Instead
of
the
whole
thing
all
right.
A
C
A
For
me,
I
think:
that's
that's
general
advice
right
right.
A
Yeah,
that's
a
question
that
harsh
the
gitlab
plug-in
modernization
contributor
asked:
hey:
do
you
prefer
small
pull
requests
or
large?
And
that
was
an
easy
one
small,
because
it
almost
always
benefits
everybody.
When
you
do
the
work,
it
is
real
work
to
break
a
large
idea
into
small
pull
requests,
but
that
work
is
very,
very
useful
to
all
of
us
right.
C
D
A
A
D
A
D
A
So
the
the
remaining
topics
actually
are
not
especially
crucial
that
we
discuss
them
here.
So
we
had
a
damaged
page
on
jenkins.io
that
is
fixed.
Did
some
reverse
some
some
bisecting
to
find
out
what
broke
it
and
then
wrote
a
test
to
assure
that
it
stays
fixed
and
don't
have
time
right
now
and
probably
won't
for
a
month
or
two
to
to
decode
why
this
thing
broke,
just
see
that
it
did
and-
and
there
is
therefore
a
blocked
change
request
that
is
failing
tests
and
that's
why
it's
blocked.
A
This
one
right
here
will
remain
blocked
because
the
test
will
keep
failing
until
we
figure
out
why
the
tests
what's
really
causing
the
thing
to
fail
to
do
its
job
at
low
risk.
There's
no
real
harm
it.
So
long
as
this
thing
never
passes
the
test
and
still
doesn't
deliver
its
content.
The
site
looks
just
fine.
A
It
will
find
this
pipeline
SCM
step.
I
click
that
link
and,
in
the
broken
case,
this
phrase.
Nested
choice
of
objects
would
be
immediately
followed
by
this
thing.
Having
lost
all
of
the
intervening
content
between
them
interesting
yeah,
it
changes
the
the
size
of
this
file
from
when
it's
correct
correctly
sized
it's
75
or
more
kilobytes,
that's
incorrectly
sized,
it's
less
than
five
kilobytes.
So
it's
easily
tested
yeah.