►
From YouTube: 2022 05 05 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
jenkins
documentation,
office
hours,
it's
the
5th
of
may
2022.
Thank
you
for
being
here
topics.
I've
got
on
the
agenda
news
joe
june
lts,
baseline
selection,
crowdin
enterprise
and
on
crowdin
enterprise
alex.
I
wanted
to
ask
you
about
utf-8
encoding
and
what
you've
learned,
if
you're
willing
to
alternatives,
etc,
options,
etc.
A
B
A
Darren
pope
and
I
will
do
a
live
stream
today,
talking
about
what's
new
in
it
relatively
minor
things,
one
interesting
bug
fix
and
we're
prepping
for
the
june
lts
baseline.
It's
looking
much
better
thanks.
So
much
for
your
help
alex
and
the
there
is.
There
are
pending
changes
from
adrian
le
charpentier
for
a
for
a
what
was
it
a
feedback.
B
Yeah,
I
think,
a
couple
of
weeks
ago,
we
released
a
version
which
contained
quite
a
lot
of
regression,
fixes
yeah
and
introduced
and
worked
down
the
your
excavation
dashboard
even
further
within
the
past
weekly
releases
and
the
next
one
adrian
took
care
of,
I
think,
as
we
merged
a
couple
of
hours
ago
and
we'll
land
in
the
next
weekly
next
week.
A
A
For
the
screenshots,
on
the
assumption
that
those
are
the
those
are
much
more
much
closer
to
what
june
will
look
like
than
if
they
were
to
use
the
previous
lts,
so
it
looks
very
good.
Actually,
you
can
see
the
pull
requests
and
you
can
see
the
results
arriving
in
and
a
few
pages
on
jenkins.io.
A
B
Yeah
just
to
pick
up
the
topic
from
last
week,
I
think
a
couple
of
hours
later
when
we
submitted
the
pr.
We
had
the
issue
that
brackets
and
things
were
actually
escape
when
they
shouldn't
be
escaped.
A
Okay,
so
that
configured
to
not
do
that
and
we're
we're
good
to
go.
B
C
Cool,
I
don't
know
if
there
is
a
right
moment
to
discuss
that,
but
I
have
experienced
some
kind
of
bug
with
crowding.
C
C
Instead
of
column
jelly,
it's
column,
space
ali.
B
C
You're
right,
of
course,
I
have
to
translate
it
by
myself.
Afterwards,
most
of
the
time
there
is
a
translation
proposal
that
is
not
far
from
the
truth,
so
I
start
from
that.
But
for
whatever
reason,
the
proposed
translation
when
it's
there
is
a
column
jelly,
it's
transforming
to
column,
space
ellie,
but
yes,
you're
right.
It's
not
once
I've
done
it
by
myself.
If
I
were
to
write
it
by
myself,
the
error
wouldn't
be
there
because
I'll
be
right
by
that.
B
Yeah,
the
suggestions
are
actually
generate,
are
actually
computer
generated,
because
these
are
machine
translations.
We
don't
have
much
input
on
them.
They
are
generated
on
the
way
crowling
interprets
our
files.
At
the
moment,
we
have
only
design
library
and
one
of
max
plugins
available
to
feed
machine
translation
with,
and
it
isn't
much
smart
yet.
A
Okay,
that's
fine,
okay,
but
but
so
that
lobbies
that
one
of
the
benefits
then
or
one
of
the
needs
here
is:
we
need
to
add
more
plugins
to
the
pool
of
plugins.
I
wanted
that
for
the
the
webinar
anyway.
So
are
you
okay
alex
if
I
attempt
to
add
other
plugins
like
test
ng
or
elastic
axis,
or
a
few
others
and
I'll
try
to
do
it
on
my
own
and
then
see
if
see?
If
I
can
be
successful
without
having
you
to
guide
me,
if
I
fail
okay,
we
will
have
learned
something.
C
Okay,
by
the
way,
should
I
go
on
with
the
translation,
should
I
try
to
finish
the
first
plugin
translations
yeah,
because.
B
A
B
A
A
B
On
it,
the
current
state
is,
if
you
translate
at
least
someone
has
approved
a
couple
of
strings
in
the
chinese
translation
on
crowding,
which
let
the
action
to
generate
a
pr
as
intended
and
as
shown
on
github
chinese
simplified
was
actually
there
like.
You
could
read
it
if
you're
a
chinese
speaker,
but
if
I
mean
I
approved
the
pr
and
pulled
it
in
and
once
released.
B
I
checked
again
with
the
local
plugin
that
these
strings
are
not
properly
encoded
for
the
client
like
it
just
has
shown
some
gibberish
that
is
far
from
chinese
yeah,
and
then
tim
reminded
me
that
these
fights
actually
need
to
be
encoded
but
encoded
in
a
way
that
I
don't
have
the
actual
hdmi
at
the
moment.
But
at
least
in
a
way
that
to
make
sure
the
chinese
stays
chinese
and
what
gets
become
some
gibberish.
C
B
B
Issue
or
not
issue,
but
the
underlying
way.
How
it
is
done
is
that
stapler
first
loads
it
in
the
wrong
thing
and
then
stops
at
because
bazel
left
a
comment
that
java,
9
and
ongoing,
which
will
become
the
next
java
version
in
september
for
jenkins,
will
have
a
way
to
force
you
to
have
eight
first.
A
B
A
B
Yeah,
I've
taken
a
look
over
the
crowded
documentation,
but
I
at
least
couldn't
find
a
case
where
you
can
configure
it,
but
I've
contacted
crowden.
I
think
a
couple
of
days
ago
how
they
would
go
about
it
because,
for
the
time
being,
we
can't
properly
rely
on
the
exported
translations
from
clothing
because
they
are
not
accurate
because
of
that
a
way
to
go
around
would
be
to
transform
the
exported
strings
manually
into
utf-8,
but
that
would
require
to
edit
dpr
again.
C
That
was
kind
of
my
next
question
a
long
time
ago,
when
I
had
a
lot
of
trouble
with
non-ut
yeah,
not
into
f8
and
java
property
files.
I
had
to
encode
each
of
my
property
files,
which
were
used
for
translation
thanks
to
escape.
You
know
it
was
a
backslash
you
and
then
your
utf.
Whatever
code,
it
was
pretty
straightforward,
but
it
was
a
pain
in
the
neck
to
do
that.
Make
sense.
While
we
are
not
using
java,
9
or
not,
or
is
it
even
possible
to
add
a
step
to
the
workflow.
B
I
think
you
can,
I
mean
I
think
you
could
write
a
bash
script
and
let
github
actions
do
that
if
you're
added
or
at
least
have
a
basket
with
a
few
lines.
It
basically
transforms
these
files
for
the
time
being,
if
crowd,
but
I
think
robin
will
get
back
to
me
anytime
soon.
At
least
I
hope
okay.
So
we
can
work
out
a
solution.
A
Yeah,
so
so
for
me,
there's
a
there's
a
if,
if
cr
crowdin
has
a
specific
solution
for
us
great,
that's
that's
the
ideal.
If
they
don't
short
term
this
script,
to
do
a
transformation
or
a
github
action
to
do
the
transformation
doesn't
sound
too
bad
and
then
long
term.
Once
we
really
require
java
11,
then
we
we
can
update
stapler,
it's
really
it's
not
that
we
can
use
utf
properties
right.
We
can
update
stapler
to
use
the
new
new
property
facility
with
uta
ukfa
properties
right.
B
A
A
Oh
all,
right
right,
okay,
good
point,
all
right,
so
it
is
jelly
and
html
help
files
are
unaffected.
They
can
be
use
utf-8
right
now.
B
A
A
B
A
Excellent
so
alex
it
looks
like
we've
got
so
one
is
we
wait
and
hope
that
crowdin
will
tell
us
hey
here's
this
way
you
handle
it
and,
and
it
all
works
easily.
If
that
doesn't
work,
we
look
at
native
to
ascii,
not
record
recode
or
other
solutions
that
could
do
a
similar
transformation,
because
what
what
crowdin
is
providing
is
valid
utf-8.
C
B
A
B
Yeah,
I
think
a
great
way
would
be
to
actually
show
how
to
use
from
a
translator
aspect,
from
a
project,
maintainer
aspect
and
from
a
proofreader
aspect,
so
we
actually
cover
all
states
how
to
translate
something:
how
to
approve
something
and
how
to
review
something.
I
think
that
is
a
major
aspect
that
plugin
maintainers
will
going
to
use.
B
C
B
A
B
Go
ahead,
yeah
one
question
from
my
side:
how
do
we
want
to
let
people
access?
How
do
we
want
to
let
people
create
the
project
at
the
time
being
only
project
maintainers
can
create
these
projects
like
we
have
done
in
the
past
sessions.
If
you
remember
the
workspace
thing,
you
click
the
plus
button,
but
that
is
only
something
instance,
maintainers
or
administrators
can
do.
B
My
idea
was
like
to
possibly
go
through
the
infrastructure
help
desk.
So,
like
people
raise
an
issue
on
the
help
desk
labelled
as
crowded.jenkins.io
say,
hey.
This
is
my
plugin.
Please
create
me
a
project
on
calling
the
jenkins
at
io
and
possibly
me
or
someone
else
who
would
like
to
take
care
of
that,
would
do
that
and
say:
hey
here's
your
project
and
then
they
can
go
ahead
and
copy
and
paste
the
github
workflow
considering
this
is
a
pretty
simple
task
to
do.
B
B
A
B
B
A
B
B
A
B
B
A
Sense
so
triage
so
helpdesk
triage
assigns
the
ticket
to
to
one
of
the
crowd
in
maintainers
or
crowdin
admins,
and
that
could
be
today.
That's
three
of
us
and
if,
if
you're
comfortable,
we
could
add
others,
but
that's
the
three
of
us
for
now
yeah.
B
B
A
A
B
B
B
Yeah,
which
then,
but
then
someone
of
us
approves
yeah,
and
then
I
could
basically
run
the
action
on
github
and
considering
design
library,
for
example,
is
integrated
with
continuous
delivery.
I
could
basically
go
ahead
and
merge
this
pr
straight
away
to
have
it
available
release.
I
think
within
the
next
half
an
hour
or
something.
A
C
A
Good
good
question,
so
so
what
happens?
Is
we
do
it
as
a
zoom
webinar
and
as
a
zoom
webinar?
That
means
the
panelists
have
full
screen
sharing
and
speak
speaking
ability,
but
the
participants
can
only
ask
questions
through
the
q
a
facility
during
this
I'll
act
as
moderator
and
I'll
monitor
the
q
a
and
be
the
voice
to
raise
questions
saying,
oh
alex.
I
think
I
should
ask
you
this
question
here
or
oh.
I
should
ask
you
this
question
at
that
point.
That
was
my
question.
I
wanted
to
know
who
will
be
the
moderator
yeah?
A
A
Answer
from
the
audience
questions
questions
from
the
audience
now,
and
I
I'm
also
assuming
if
we
need
to
talk
about
alternatives
for
utf-8
locales
for
utf-8
what
which
it's
tough
to
say
this
should
I
say,
multi-byte
strings.
No
utf-8
is
probably
for
full
utf,
full
utf-8
support,
yeah,
and
that
will
depend
on
whatever
you
learn
between
now
and
may.
12.
B
B
A
I
think
we've
got
tools
like
this
that
perform
at
least
perform
checks,
because
we've
got
a
spell
checker
that
runs
on
jenkins.io
as
a
github
action
and
and
what
it
does
is
uses
a
docker
image
that
a
docker
container
image
that
has
a
spell
checker
inside
of
it,
and
so
it
must
be
feasible.
I
guess
at
minimum
we
could
do
a
safety
check,
that
the
pull
request
doesn't
include
utf-8
encoding
inside
the
property
files
before
well
yeah.
Okay,
there
there
are
alternatives,
good
all,
right.
A
Okay,
well,
I
think
I
feel
like
we're
ready
for
an
online
meetup.
Okay,
ready.
We've
got
at
least
an
agenda
and
a
plan
for
may
12th
alex.
If
you
can
be
there
say,
15
minutes
early,
so
that
we
can
do
technical
checks
to
be
sure.
Yes,
your
web,
everything
is
working
right.
We
know
how
to
screen
share,
stop
screen
chair,
yada
yada,
the
usual
things
bruno,
likewise,
yep
yep
great,
all
right.
A
A
A
And
we've
seen
good
progress
there.
Pull
requests
are
arriving
had
another
session
with
pipeline
help
today
and
making
progress.
A
Wait
all
right.
Any
other
topics
for
today
then
on
how
about
the
project
management,
how
she
doing.
A
She's
been
she's
been
the
best
of
all
of
the
all
of
the
experiences.
Thank
you
very
much
for
doing
that.
She's
been
absolutely
wonderful.
Sends
the
reminders
helps
me
keep
on
track
worries
about.
Are
you
updating
your
document?
Are
you
keeping
these
things
current?
Oh,
we.
We
must
do
that
again
next
year,
nice
all
right.
Thank
you.
Sorry.
I
forget
to
mention
how
valuable
that
is,
because
it's
just
she's
doing
wonderfully.
Thank
you.
Thank
you.