►
From YouTube: 2023 05 25 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
this
is
documentation
office
hours,
it's
the
25th
of
May
2023.
topics.
For
today,
the
international
and
internationalization
and
localization
poll
request
from
je
Chan
the
upgrade
guide.
That's
for
the
release
coming
next
week,
Kevin
Martin's
unavailable
and
oh,
we
need
to
change
this.
One
instead
of
April
newsletter
is
published.
May
newsletter
need.
A
Right
and
then
other
topics,
stocks,
transition,
gsoc
I-
think
we
may
have
nothing
to
discuss
there,
but
we'll
test
it.
Let's,
but
I
think
gsoc
is
a
good
topic
and
then
the
pipeline
steps
reference
just
remains
as
a
reminder.
End
of
life
and
end
of
life
are
just
reminders.
Anything
else,
Bruno
that
you
want
to
add
yeah,
maybe.
B
B
Yes,
indeed,
because,
yes,
we'll
see
when
we'll
address
the
point.
A
Good
all
right!
Well,
so,
let's
put
it
I
want
to
put
it
high
on
the
list,
because
I
think
it's
an
interesting
topic,
good,
all
right
anything
else.
You
want
to
add
to
the
agenda.
No
thank
you!
Mark,
okay,
so
first
topic,
then
internationalization
and
localization
pull
request
from
je
Chen.
So
this
pull
request
has
a
long
history.
A
What
what
this
submitter
has
done
as
picked
up
a
pull
request
that
we
had
had
initially
started
some
from
by
somebody
else,
but
it
stalled
out
because
it
just
didn't,
get
didn't
get
attention
from
the
submitter
and
didn't
get
attention
from
us
and
they
went
away.
But
this
person
has
retrieved
it
again
and
said:
hey,
let's
try
it
so
so
what
this
does
is
it
provides
us
an
update.
I
wanted
to
show
this
preview
site
of
the
pull
request.
Okay.
A
So
what
this
is
the
internationalization
and
localization
top
level
section
in
the
developer,
documentation
notice,
it
says
it's
a
work
in
progress,
yeah.
What
it
did
was
added
a
new
section
in
there
called
internationalization
and
localization
with
details
of
what
are
the
tasks
that
developers
perform
and
what
are
the
tasks
that
translators
perform.
A
However,
this
the
sections
that
it's
adding
like
generation
of
message
classes
and
making
marking
messages
and
jelly
files
are
already
covered
in
other
places
like
internationalizationizing
messages
in
Java
source
code
and
in
jelly
views
and
in
groovy
views,
even
so
so
I
think
we've
already
got
the
content
and
this
content,
because
it
was
copied
from
the
old
Jenkins
Wiki,
is
actually
worse
than
the
than
the
new
content.
That's
on
the
site,
so
it
it
is
in
this
current
right.
A
It
I
think
the
the
thing
that's
been
retrieved
is
a
good
step,
but
it's
not
as
current
as
this
description
is
so
so
that
was
one
of
my
all
right,
but
there
are
things
in
this
page
that
are
absolutely
not
mentioned
anywhere
in
the
current
documentation.
For
example,
I
learned
something
new
by
reading
this
I've
been
doing
plug-in
development
for
a
little
while,
and
yet
this
page,
this
section
was
entirely
new
to
me.
I
had
no
idea
that
this
command
existed
and
that
what
it
did
and
how
it's
helpful.
B
Yes-
and
it
always
it's
with
the
same
title,
to
Target
internally
right.
A
Right,
which,
which
makes
it
sort
of
makes
it
a
little
unclear
now,
there's
another
complication
here
that
we've
also
got
a
tool
that
supports
translation
and
oh,
it
works
well
when,
when
it's
enabled
crowd
in
supports
translation
very
nicely
right
and
Bruno
I
believe
you've
had
experience
using
Cloud
crowd
in
to
submit
translations
for
Strings.
Yes,.
B
I'm
still
using
it
for
whatever
locable
resource.
A
Plugin
yeah
right
right
exactly,
and
so,
when
it's
enabled
for
relatively
few
plugins
they're,
only
12
or
so,
but
when
it's
enabled
it's
much
easier
on
a
translator
than
the
process
that
we
describe
of
edit
a
file
create
the
file.
If
you
need
to
submit
a
pull
request
Etc
this
is
this
batches
them
together
does
a
much
better
job.
So
what
I
thought
was
what,
if
we?
B
A
Because
the
developer
tasks
were
already
described
but
I
wanted
them
enumerated.
I
thought,
let's
put
the
the
numbered
list
of
this,
is
what
plug-in
developers
have
to
do
and
this
one
links
to
the
Java
source
code,
one
this
one
links
to
the
Jelly
views
when
I
did
not
link
to
the
groovy
views,
one
because
this
one
The
Groovy
user
and
says
we
do
not
encourage
you
to
use
this.
B
B
Yes,
sorry,
if
I
did
not
make
myself
clear,
I
didn't
want
to
put
crowding
for
the
Jenkins
score,
just
to
write
it
somewhere
in
the
documentation
that
you
can
use
crowd
info
plugins,
but
do
not
try
to
do
something
with
and.
A
And
there
it's
it's
actually
stated
here:
oh
cool,
so
so
I
agree
with
you
that
message,
I
think
I,
think
you're
exactly
correct.
So
what
I
said
was
translators
can
contribute
to
plug-in
localizations
through
crowd
in
after
they've
enabled
it
translators
can
contribute
to
Jenkins
core
and
plugins
not
registered
with
crowd
in
by
filing
pull
requests.
Crystal
Clear
yeah.
Well,
thank
you.
The
thought
was:
okay.
A
B
A
Okay
and
now
the
next
thing
that
I
did
in
this
in
this
draft
idea
was
the
crowding.
Oh,
oh
I
should
show
another
thing
right,
so
internationalization
and
localization
previously
was
listed
as
a
work
in
progress
yeah.
It
has
disappeared
and-
and
that's
gone
now,
because
I
feel
like
this
is
well
enough
described
to
say
that
it's
no
longer
a
work
in
progress.
Yeah.
A
It
is
good
point
so
so
we
could
my
reason
for
leaving
it
as
a
top
level.
Entry
like
that
was
that
I
didn't
want
to
have
to
resolve
broken
hyperlinks
that
might
point
to
it.
It
I
think
you're
right.
Ultimately,
it
really
is,
but
I
guess.
For
me
it
was
a
marketing
choice
to
say,
hey,
let's
leave
it
top
level,
at
least
for
now
in
in
order
to
encourage
more
people
to
use
it.
Yeah.
A
A
That,
but
here
there
are
three
segments
missing
content:
okay
and
I
need
I.
Think
I
can
grab
those
some
of
those
I
can
grab
this
content
from
what
je
Chan
wrote
this
one
I'm
just
going
to
have
to
describe
how
they
do
it,
and-
and
it's
not
that
hard
to
do
it's
just
okay-
have
to
describe
it
and
be
sure
it
works.
The
way
I
describe
it.
I
think
it's
as
simple
as
doing
LC
underscore
all
equals
something
fr.
A
B
B
I
have
no
idea,
okay
and
for
the
last
one
I
think
there
is
somewhere
something
that
we
could
could
be
base
modifying
exactly.
A
B
A
A
A
B
A
B
Okay,
so
you're,
okay,
with
that,
of
course,
it's
much
better
and
thanks
to
Jeffrey
chain
to
restart
this
cell
cure.
A
B
I've
sent
you
a
link
into
the
chat
if
you
want
to
visit
it.
Oh
good,
okay
and
I'm
afraid
it's
your
work.
Okay,
nothing
wrong
with
that.
I
was
just
feeling
bad,
you
know,
but
because
that
kind
of
PR
doesn't
look
like
film
at
all
and
I'm,
just
a
beginner
user
of
update
CLI.
So
I
don't
know
much
about
that
anymore.
B
First
time
being
sorry,
but
when
I
saw
this
PR
that
Damien
sent
me
Damian
de
portal
said
wow.
We
may
do
something
about
that,
because
it's
not
funny
at
all
to
do
that
kind
of
PR.
It's
boring,
as
can
be
I,
don't
know,
I've,
never
done
that,
but
I.
B
Imagine
you
don't
have
to
say,
but
anyhow
so
I
made
a
few
tests
and
unfortunately,
first
time
being
it
doesn't
work
because
Mark
these
files
have
changed
in
this
PR
and
now,
for
example,
we
are
using
blue
ocean
without
any
version
darker
Rock
flow
without
any
version,
so
no
need
to
keep
them
up
to
date
with
update
CLI,
but
I
found
a
few
of
the
files
where
we
are
referring
to
node.js
or
pine
Docker
image,
for
example,
and
so
on.
So
there
are
places
where
we
could
benefit
from
a
dead
CLI.
B
So
it's
just
an
idea:
I,
don't
have
a
proof
concept
to
submit
for
timing.
I,
don't
have
the
pr
ready
but
I'll
have
it
ready
by
next
week.
I
hope-
and
maybe
we
should
discuss
it
with
the
community
or
not
because
I
made
a
quick
search
and
didn't
find
as
many
buys
as
I
had
imagined
beforehand.
So
I
don't
know
you're
the
one.
Who
does
that
kind
of
thing?
Could
you
tell
me
anything
about
that?
A
I
I
think
it's
it's
very
valuable,
because
there
are
plenty
of
Dem
of
samples
that
use
an
explicit
version
number
and
that
version
number
is
inevitably
out
of
date.
Okay,
this
one
has
avoided
using
a
version
number,
but
what
that
really
means
is
it's
now
doing
an
a
non-vex
best
practice
right.
That's
what
was
my
points.
B
A
Right,
it
would
be
much
better
if
this
called
out
an
explicit
version
number
for
the
the
node
LTS,
but
that
it
stayed
on
the
LTS
version
of
node
and
updated
periodically
that
that
would
really
be
I
think
a
useful
thing
for
readers.
They
see.
Oh,
the
Jenkins
project
knows
how
to
do
versions,
and
they
don't
just
use
the
easy
out
of
use
the
an
unversioned
number.
Let's,
let's
make
it.
A
A
A
A
Good
all
right
anything
else
on
the
topic.
No
thank
you.
Mark.
Okay,
next
topic,
then,
is
I'm
behind
schedule
on
doing
the
change
log
and
upgrade
guide
and
Mark
complete
it.
It's
not
a
hard
task,
it's
just
got
to
be
done
and
it
takes
an
hour
or
two
to
do.
The
extraction
and
review
Etc
Bruno
I'll.
Ask
for
your
help.
Of
course,
would
you
be
willing
to
review
it.
A
All
right
anything
else
on
on
the
change:
login
upgrade
guide;
no
thank
you.
Okay,
Kevin
Martin's
unavailable
until
June
12
he'd
shared
with
the
the
Jenkins
governance
board
that
he's
out
we're
gonna
delay
the
Java
11
to
Java
17
documentation
transition,
while
he's
out
that's
not
that
harmful,
because
Debian
12
release
is
in
June
sometime,
yeah
and
I.
Think
it's
likely
late,
June.
A
Read
yeah
so
so,
therefore,
we're
not
we're
not
at
big
risk
right
now,
when
Debian
12
releases,
there
will
be
some
people
who
will
use
it
and
they'll
be
frustrated
that
the
Jenkins
instructions
don't
tell
them
to
use
Java
17,
but
small
group
compared
to
the
total
set
of
Jenkins
users.
Of
course,
all
right,
then,
let's
see
what
else.
Oh
next
topic
main
newsletter.
A
That's
just
a
reminder
as
a
board
member
I
need
to
do
some
Bruno
you're
still
going
to
create
the
pull
request
right
so
yeah
great
all
right,
let's
see,
and
this
one.
A
B
Yeah
and
we're
still
in
the
bonding
period
for
first
time
being
because
people
contributors
are
working
on
the
bio,
the
first
blog
post,
the
project
description,
page
and
so
on.
So
we
are
progressing
slowly.
We
had
gsock
office
hours
earlier
today
and
that
went
fine,
no
blogger
whatever.
So
everything
is
progressing.
Some
groups
I've
already
started
coding.
I
know
it's
very
frustrating
doing
only
ASCII
dog
and
you
want
to
put
some
code,
so
some
of
them
have
started
and
it's
doing
is
going
well,
so
nothing
bad
to
share
great.
A
A
A
A
A
B
A
A
Right
exactly
okay,
so
on
this
one,
this
is
now
merged,
so
users
who
are
running
Centos,
7
or
red
hat
Enterprise,
Linux
7
on
the
weekly,
we'll
get
a
notice
beginning
next
Tuesday
on
if
they
upgrade
to
the
new
version.
The
next
next
LTS
Baseline
will
include
the
change,
so
that
would
be
roughly
August
and
it's
2.400.