►
Description
Explore how Jenkins contributors use Crowdin Enterprise as localization tool in Jenkins. They use it to localize the messages and online help in Jenkins plugins. It simplifies the localization process for translators. They propose translations from a web browser, then a proofreader reviews, adapts, and approves the translation, and a GitHub pull request is submitted with the translation.
The tool feels like it fit very well into Jenkins development. They would like to show the tool so that others can help with translations.
A
Welcome
everyone,
it's
may
the
12th
2022,
and
this
is
a
jenkins
online
meetup
localizing
jenkins,
with
crowden
enterprise.
We're
grateful
to
alexander
brandes
and
to
bruno
verochton
for
joining
us
alexander
is
a
native
german
speaker.
Bruno
is
a
native
french
speaker
in
case
you
can't
tell
I'm
a
native
english
speaker.
That's
about
all
next
slide.
Alex
would
remind
you
that
jenkins
online
meetups
are
community
organized
events.
A
So
in
this
session,
if
you've
got
questions
and
answers
feel
free
to
use
the
question
and
answer
facility
that
zoom
provides
we'll
also
tend
to
answer
things.
If
you
ask
in
chat
but
question
and
answer
is
a
little
easier
for
us
to
manage
so
as
a
kindness
to
us.
If
you
do
it
in
question
and
answer
that's
better,
it's
not
that
we'll
ignore
you
in
chat!
It's
rather
that
it's
just
easier
for
us.
If
you
do
it
in
question
and
answer
and
after
the
meetup.
A
This
hyperlink
here
is
to
our
discourse
site
community.jenkins.io,
where
you'll
find
a
copy
of
the
recording
of
the
meeting,
and
we
can
have
conversations
about
the
topic
right
inside
that
discourse
size
site,
we're
very
grateful
to
discourse
for
hosting
the
site.
For
us
love
what's
happening
there
next
slide
so
alex.
This
is
yours
now.
B
Thanks
mark
yeah,
let
me
introduce
myself
first,
I'm
alexander
brandes
and
I'm
a
native
speaker
from
germany
and
one
of
the
main
presenters
today
during
this
online
meetup,
a
viewers
to
myself
on
github.
I
go
with
the
name,
not
my
fault.
You
may
have
already
seen
me
contributing
to
a
variety
of
repositories
in
the
jenkins
organization
and
outside
of
jenkins,
I'm
currently
a
business
science
student
from
germany
yeah.
Here
we
have
the
agenda
we
are
talking
about.
Today.
B
We
will
start
with
what
called
the
current
enterprise
is
and
what
we
are
planning
it
on
using
in
the
jenkins
cr
organization,
how
we
translate
something
with
crowden
that
something
bruno
will
show
us
how
it
translates
something
how
he
translates
one
of
mark's
plugins
into
french.
Then
I
will
take
over
again
and
show
us
how
we
review
something
on
crowded,
followed
by
that
we
will
see
the
approved
strings,
how
they
land
on
github.
B
First
of
all,
I
would
like
to
thank
crowling
for
sponsoring
us
and
hosting
our
instance
available
on
crowdend.jenkins.io,
because
without
without
crowding,
we
wouldn't
be
here
at
all.
So
thank
you,
yeah.
Actually,
translations
and
localization
is
an
important
aspect
in
terms
of
user
experience
like
you
may
know,
or
have
already
seen
in
core.
If
you
change
your
browser
language
to
something
else,
for
example,
in
my
case
that
would
be
french
or
italian,
you
can
see
that
jenkins
core
itself
provides
various
views,
localized
in
different
languages,
and
the
same
process
applies
to
plugins
too.
B
You
can
localize
plugins
in
the
same
way
like
you
can
localize
jenkins
core,
however,
localizing
plugins
isn't
easy,
especially
for
people
who
are
not
necessarily
familiar
with
jenkins
or
jenkins
fuse
at
all,
and
that
is
basically
the
reason
why
we
have
spent
the
past
bunch
of
weeks
investigating
into
a
different
alternative
and
crowded
enterprise
is
the
solution
we
picked
for
us,
a
quick
recap
on
how
localizing
works
in
the
current
ecosystem
of
jenkins
plugins
to
localize
a
plugin.
You
actually
need
to
have
quite
a
bunch
of
different
prerequisites.
B
For
example,
you
need
to
know
how
to
work
with
git,
at
least
at
a
level,
to
work
with
different
branches
and
make
it
recognize
the
changes
and
push
them
back
to
the
gita
repository
of
the
plugin.
Then
you
need
to
know
how
to
work
with
github
in
order
to
submit
these
changes
as
pull
request,
but
on
the
other
hand,
it's
not
just
all
about
software.
B
You
also
need
to
know
how
fews
and
jenkins
work
they
are
often
written
in
jelly.
That
is
by
far
not
a
language
that
is
come
to
know
these
days.
Unless
we're
used.
We
have
jenkins
views
written
in
java
or
groovy,
so
we
have
many
languages.
You
basically
need
to
be
aware
of
and
aware
of
the
oddities,
for
example,
using
non-net
non-latin
one
characters
in
javascript
properties
file
and
having
proper
utf-8
encoding,
just
in
order
to
submit
a
few
translations
or
exchange
a
few
words
in
a
plugin.
B
That
is
a
that
is
basically
quite
a
lot
just
in
order
to
submit
such
a
simple
change
and
that's
basically,
the
step
where
crowling
comes
in
crowden
provides
us
a
much
more
streamlined
solution
that
is
able
to
use.
Be
used
by
everyone
with
no
prerequisites
at
all
crowding
just
gets
rid
of
all
prerequisites.
I
just
mentioned.
B
If
you
are
using
crowden,
you
have
a
nice
and
handy
web
interface.
You
can
use
to
provide
these
translations,
you
don't
need
to
use
git
at
all
or
work
with
branches
or
submit
something
on
github
or
need
to
know
anything
about
java
view,
screw
reviews
or
gelly
or
anything
else
that
is
used
in
jenkins
to
make
fuse
in
the
way
how
they
are
used.
B
At
the
moment,
you
just
go
to
the
web
interface
type,
something
in
save
it
and
that's
basically
it
that
is
the
whole
process,
broken
down
and
outsourced
to
crowden
because
they
provide
such
an
intuitive
web
ui.
That
is
basically
be
able
to
be
used
by
everyone,
and
I
would
like
to
go
ahead
and
just
go.
Stop
screen
sharing
here
and
let
bruno
take
over
that.
He
shows
us
how
we
translate
a
few
strings
into
french.
C
Okay,
bad
keyboard
shortcut
anyway,
thank
you
alex.
So
here
we
are.
I
just
typed
crowdin.jenkins.io
on
my
browser
and
there
I
am.
Of
course
I
had
to
create
beforehand
an
account
in
order
to
be
able
to
participate
in
this
project.
Now
I've
got
two
plugins
that
I
I'm
not
assigned
to
this
plugin,
but
they
were
there
in
the
cloud
industry
in
io.
So
I
worked
on
the
first
one
and,
as
you
can
see,
it's
named
design,
library
plug-in
and
I've
got
chinese,
french,
german,
italian,
portuguese,
brazilian
or
spanish.
C
Unfortunately,
I
know
only
french,
I'm
a
native
french
speaker,
so
I
went
ahead
and
clicked
on
french
and
then
I
had
the
list
of
all
the
files
I
could
translate.
If
I
wanted
to
okay,
I
did
them
all.
So
that's
not
maybe
the
best
way
to
show
you,
but
there
are
some
property
files.
There
are
some
jellyfish,
maybe
not
in
this
project
anyway,
but
there
are
also
html5.
C
C
C
Cool,
so
this
one
seems
to
be
an
html5,
so
I've
got
a
render
on
the
left
of
the
screen.
That
shows
me
how
this
should
appear
in
the
html
file
at
the
end,
so
at
the
top
here
in
the
middle,
I've
got
the
name
of
the
ethics.
So
that's
the
phrase
I'm
supposed
to
translate
and,
as
you
can
see,
there
are
already
lots
of
proposals,
not
the
lags,
not
the
likes.
C
If
I
think
something
is
not
looking
good,
I
modify
it
and
I
made
a
mistake.
Unfortunately,
french
is
pretty
nitpicky
about
commas,
spaces
punctuation
in
general,
so
I
made
a
mistake.
I
added
a
space
and
I
shouldn't
have
done
so
and
crowding
tells
me.
I
made
an
error,
so
there
is
a
one
circled
in
red
which
will
tell
me
hey.
You
should
place
a
space
before
the
point
and
it's
written
in
french.
It
will
be
written
in
spanish
if
you're,
spanish,
for
example,
that's
super
cool.
C
I
learned
some
things
by
the
way,
because
I'm
not
sure
about
the
place
of
the
comma,
the
number
of
species
I'm
supposed
to
put
before
or
after
red
zone
and
then
crowding
did
everything
for
me.
So
once
I'm
happy
with
what
I
see
le
non
delights
in
french,
I
can
click
on
save
and
that's.
Okay.
I
have
finished
with
that
file.
I
could
have
lots
of
different
messages
to
translate
into
a
file,
but
for
this
one
there
was
just
one
message
to
translate.
C
So
it's
oh,
I
haven't
clicked
fast
enough,
but
he
has
proposed
me
to
open
another
file,
the
next
file,
which
hasn't
been
translated
yet
so,
as
I
haven't
clicked,
I
will
just
go
to
the
next
one
yeah
open
next
and
then
it
will
ask
me
for
the
translation
for
elastic
access.
I
don't
really
have
the
context,
so
maybe
it's
just
the
name
of
the
plugin,
so
I
should
not
touch
it.
C
That's
what
I
think
you
could
maybe
look
afterwards
if
that's,
okay
or
not,
but
I
think
I
will
stay
prudent
and
just
keep
it
this
way.
Of
course
elastic
is
not
a
french
word,
so
trolling
is
telling
me.
Maybe
that's
not
such
a
good
idea
to
leave
it
like
that,
but
yeah
I'm
gonna
leave
it
like
that.
I
won't
add
it
to
the
dictionary.
It's
perfect.
It's
just
a
name,
so
I
will
keep
it
that
way.
C
C
A
B
B
A
A
B
A
B
B
Thanks
mark
for
that
information,
yeah
bruno
just
translated
the
help
dashname.html
and
the
messages.properties
file
and
the
entire
process
bruno
has
shown
us
is
basically
the
entire
process.
Any
translator
has
to
do
in
order
to
submit
translation
proposal.
They
basically
had
to
encourage.jenkins.io
and
select
a
project
from
the
project
grid.
At
the
moment
we
have
only
elastic
access
and
the
design
library
plugin
integrated.
B
B
So
everything
is
already
green
and
the
middle
part
here
is
actually
where
you
put
in
the
translation
in
this
case,
elastic
access
stays
at
the
source
string,
elastic
x.
It's
because
it's
the
name
of
the
plugin.
But
if
you
pick
a
different
label,
we
can
see
the
french
proposal
by
bruno,
which
he
translated
a
day
ago.
B
Yeah-
and
this
is
basically
the
entire
way
a
translator
would
go
to
select
a
string.
You
want
to
translate,
put
in
the
translation
or
work
with
ground
machine
translations
if
they're,
accurate
and
actually
they're,
very,
very
accurate
in
very,
very
matched
cases,
click
the
save
button
and
you're
done.
You
don't
need
to
use
git
or
github
or
anything
else
here
at
all.
B
The
plugin
maintainer
can
provide
additional
information,
like
we
just
named
to
screenshots,
for
example,
to
show
where
something
is
used
in
jenkins,
because
not
not
everything
is
always
visible,
or
sometimes
you
have
to
click
through
different
menus
on
the
jenkins
web
interface
itself
to
find
where
something
is
used.
For
example,
if
it's
used
in
help
strings
or
something
which
may
be
a
bit
difficult,
so
yeah.
That
is
one
way
to
streamline
it
a
bit.
B
B
B
As
a
plugin
maintainer,
I
would
now
go
ahead
and
review
them
and
I
can
either
approve
them
by
clicking
the
tick,
and
this
is
an
approved
string
or
I
could
say,
hey
this.
Is
this?
Isn't
just
this
isn't
accurate
or
something
or
this
doesn't
actually
fit?
All
this
context
is
actually
wrong
and
go
ahead
and
say
no,
but
I
keep
this
up
and
leave
a
comment
on
it
so
possible.
Future
translators
are
able
to
pick
it
up
again,
so
alex.
A
Could
could
you
go
back
to
the
approve
when
that
you
did
that
one,
the
very
first
one
you
approved?
Could
you
can
you
still
change
it
to
be
a
french
language,
one,
because
I
think
in
this
case
it
could
be
french
language?
Is
it?
Is
it
possible
for
you
to
even
propose
that
as
a
proofreader?
No,
I
think
it
should
be
this.
B
B
Yeah-
and
this
is
basically
the
step
of
proofreading-
I
would
like
to
go
back
and
pick
a
specific
file
yeah.
Now
we
have
approved
and
translated
everything
of
the
messages,
the
properties
file.
This
is
basically
the
step
where
the
github
integration
takes
over
and
proposes
messages
underscore
fr.properties
as
new
file
to
the
plugin
repository
on
the
jenkins
ci
organization.
B
B
B
Yeah
there
we
have
our
elec
access
display,
name,
the
one
we
just
approved
proposed
by
bruno
and
approved
by
me
does
now
land
as
proposal
for
a
new
pr
on
the
gita
repository
of
the
plugin
maintainer
in
this
case
mark
would
go
ahead
and
review.
This
pr
emerged
right
away
because
we
have
already
proof,
rather
than
crowding
and
once
merged
and
once
merged
it
would
basically
be
available
in
the
plugin
repository
and
released
within
the
next
regular
release
of
the
plugin.
A
So
I
approved
it
and
I
confirmed
auto
merge
so
when
it
passes
its
ci
checks,
it
will
be
merged
and
now
it
may
even
be
merged
and
automatically
released.
I
don't
remember
the
automatic
release
settings
for
elastic
access.
This
particular
plug-in
may
not
auto-release
on
changes
to
localization.
I
don't
remember.
B
B
Yeah,
this
is
basically
the
workflows
shown
once
from
a
translator
aspect
and
once
shown
from
a
proofreader
or
plugin
maintainer
aspect.
Now
I
would
like
to
go
ahead
and
show
how
to
actually
get
crowden
to
recognize
this.
This
changes
these
files.
However,
this
is
more
something
for
plug-in
maintainers
and
that's
not
something
a
translator
has
to
do
or
has
to
know
so
yeah.
Let
me
go
ahead
and
pick
this
one.
B
This,
for
the
time
we
have
the
actual
actual
action
file
and
we
have
a
kronen.yml
configuration
file.
The
action
file
is
obtainable.
If
you
head
to
the
actions
tab
of
the
repository
click,
the
new
workflow
button-
and
it
will
be
available
here
very
soon,
once
a
pr
on
the
correct
template
suppository
has
been
merged.
You
can
basically
go
ahead
here.
Click
configure
and
basically
commit
your
change
right
away.
You
don't
need
to
copy
paste
anything
else.
You
can
work
with
our
proposed
sample
here.
B
B
B
In
order
to
obtain
a
new
project
on
calendar
drink
instead
io
we
have
made
up
a
new
workflow.
If
you
are
heading
to
the
infrastructure
repository,
you
can
select
a
new
help
desk
ticket
category
called.
I
think
we
named
it
crowded
in
projects
which
you
can
use
to
request
the
creation
of
a
new
project.
B
It's
basically,
it
basically
has
just
a
couple
of
files
where
you
enter
the
repository
on
github.
You
want
to
integrate
and
list
the
users
you
want
to
have
management
permission
and
the
infrastructure
team
are
basically
the
current
administrators
will
take
care
of
it,
create
this
project
and
report
the
project
number
back
to
you.
B
You
can
also
obtain
the
project
number
from
the
url
of
the
project,
so
yeah
once
you
have
changed
this
you're
basically
done
with
this
file.
Of
course
you
can
change
it
change
the
commit
message
or
change
the
pull
request
message.
If
you
want
to
let
it
say
something
else,
this
is
just
our
default
we
are
using
here,
but
below.
You
also
need
to
add
a
crawling.yml
to
the
root
project
of
your
repository.
B
That
is
where
you
tell
crowden,
where
the
translations
of
your
file
should
go
to,
where
the
source
strings
are
and
which
files
it
may
be.
It
may
should
ignore
right
below.
We
have.
We
are
using
this
setup,
the
source
string
tells
crowd
and
where
the
source
files
of
the
repository
are.
In
this
case,
we
are
right.
We
are
localizing
everything
by
default
in
english,
so
our
source
files
are
available
in
this
directory
under
the
proper
ending
with
our
properties
in
jenkins,
the
localized
files
are
going
in
the
same
directory
as
the
root
file.
B
B
The
filename
placeholder
equals
the
original
filename
and
the
two
letters
code
equals
the
proposed
language
in
this
case
underscore.
The
e
would
be
this
one,
and
the
translation
is
the
format
how
we
want
to
form
these
messages.
Here
we
are
using
the
same
placeholders
again:
file
name
underscore
to
letters
code.
B
B
The
bottom
bar
here
we
have
the
project
idf
and
api
talk
and
if
we
leave
them
untouched,
they
are
just
variables
for
the
column
for
the
crowdin
workflow
integration
once
that
is
once
that
is
done,
and
we
have
committed
these
changes.
We
are
already
all
set
here.
We
don't
need
to
add
further
files,
but
in
the
next
the
next
step
is
to
head
to
crowding.jenkins.io.
B
B
You
would
go
ahead
to
your
profile,
so
your
account
settings
access
tokens
create
a
token
give
it
in
your
name,
scope
it
to
projects
and
bind
it
to
the
project
you
want
to
use.
If
you
click
the
create
button,
the
next
window
shows
you
the
personal
access
token.
Once
this
output
you
put
back
to
the
github
repository
because
it
is
used
for
the
github
action
to
authenticate
with
the
project.
B
B
With
this
token,
with
this
one,
with
crowd
and
person
access
token
to
not
obviously
reveal
it
and
yeah,
and
then
we
are
basically
outside.
That
is
the
whole
integration
within,
in
this
case,
the
next
12
hours.
The
project
swings
with
crowden
and
pushes
source
strings
to
cloud
and
post
translations
from
crowded,
but
you
can
also
go
ahead
to
the
actions
tab
and
trigger
it
by
hand.
B
B
A
B
A
B
These
are
just
a
couple
of
default
languages
I
left
enabled.
But
obviously-
and
of
course
these
are
not
all
languages
crowd
and
offers
current
offer
several
hundred
of
different
languages,
but
I
don't
think
we
have
that
many
translators
in
the
current
ecosystem
to
take
care
of
it.
So
I
just
left
these
languages
enabled
by
default.
B
B
A
Yeah
I
had
to
okay
and
and
bruno's
highlighting
concurrent
work
now
can
happen
right
all
of
a
sudden
translations.
I
I
received
a
translation
just
this
morning
from
chris
stern
in
hong
kong,
providing
a
traditional
chinese
translation
for
the
elastic
access
plug-in
and-
and
I
did
nothing
he
pro-
he
contributed
it
or
chris
contributed
and
with
chris's
contribution.
A
B
Oh,
I
think
everyone
can
submit
their
plugin
through
the
infrastruct
infrastructure
help
desk
now,
because
why
not?
We
have
the
templates
here.
Everyone
is
welcome
to
join
us
and
up
their
plugin
in.
I
think
jenkins
core
needs
some
special
treatment,
especially
because
I
think
I
counted
it
through
intelligent.
A
couple
of
days
ago
we
have
several
hundreds
of
actual
source
files
there
in
many
many
different
locations
and
partly
translated
stuff,
half
translator,
stuff
super
outdated
stuff
stuff
that
is
actually
unused.
B
A
A
B
It
definitely
makes
sense
to
clean
up
core
first
and
sort
of
everything
that
is
basically
unneeded
in
case.
It
goes
ahead
and
wants
to
translate
something
and
their
translation
basically
lands
in
the
trash.
Can
then,
because
it's
unused
and
provides
nothing
useful
for
us
so
yeah,
but
we
definitely
could
and
should
have
core
itself
available
here
and
probably
guide
new
translators
and
contributors
to
use
this
and
over
github.
A
Thanks
very
much
alex.
Thank
you.
Thank
you
this.
This
looks
like
a
much
better
experience
for
people
who
are
willing
to
contribute
translations
to
jenkins
no
more
property
file,
editing,
no
more
utf-8
unicode
escaping
of
things,
no
more,
no
more
complications,
hiding
things
into
properties
and
figuring
out
which
file
to
translate
where
to
create
it.
This
simplifies
things
dramatically.
A
Well
and
now,
maybe
maybe
that'd
be
a
worthwhile
thing
to
discuss.
Would
you
be
willing
to
share
a
little
bit
on
the
history
of
utf-8
in
jenkins
property
files
that
that,
for
me,
is
a
is
a
a
surprising
thing
to
realize?
Oh
oops,
there's
a
complication
here
and
how
crowding
has
been
so
kind
to
help
us
work
around
the
complication
and
make
things
much
easier
for
users.
B
Let
me
grab
the
appropriate
p
r
to
show
it
of
better
yeah
got
it
right
here.
This
is
basically
the
current
translation
provided
by
it.
As
we
can
see
here,
that's
the
title
in
the
description
in
simplified
chinese,
and
this
doesn't
work
out
well
in
jenkins,
at
least
not
yet
because
we
do
not
require
java
11,
yet
not
allowing
us
to
use
the
newly
added
api
in
java
9.
B
So
we
basically
had
to
work
around
this
issue
for
the
time
being
gordon
implemented
a
custom
solution
for
us
to
export
stuff
properly
escaped
in
utf-8.
Looking
like
looking
like
this
one,
this
is
the
utf-8
exported
string
of
a
warning,
as
we
can
see
or
not.
Yet,
as
we
can
see,
everything
is
prefixed
with
an
inverted
slash:
u
and
the
appropriate
code
that
is
used
to
represent
the
chinese
character
and
his
renders
basically
like
this
one
shown
in
the
jenkins
ui.
As
we
can
see,
this
is
properly
proper
chinese
simplified.
A
A
special
thanks
to
krautin
for
doing
that.
That,
for
me,
was
absolutely
heroic.
The
the
the
java
way
of
handling
in
java
8,
these
unicode-based
multi-byte
characters
is
a
little
dismaying
right.
The
fact
that
we
had
to
put
them
in
with
backslash-
u
and
the
actual
unicode
character
sequence
makes
it
very
hard
to
read,
but
they
did
that
translation
so
that
the
translator
does
not
have
the
person
doing.
The
translation
does
not
have
to
do
that.
Work.
It's
done
by
the
the
crowd
in
software
at
the
back
end.
Did
I
understand
right,
alexander.
B
Yeah,
the
translator
doesn't
need
to
do
anything
at
all
here
if
they
are
using.
The
crowded
ui
bruno
has
shown
a
bit
before
here
they
will
just
type
in
their
language.
In
this
case
chinese
and
once
the
action
exports,
these
approved
strings,
they
turn
into
utf-8
and
are
properly
encoded,
so
they
are
shown
as
simplified
chinese
again
on
the
jenkins
interface.
A
B
Yeah,
for
the
time
being,
I've
just
opened
it
here
we
are
using
the
jenkins
infrastructure,
help
desk
to
manage
the
creation
of
a
new
project,
so
plugin
maintainer
would
head
to
the
jenkins
infra
organization
and
select
the
helpdesk
repository,
creating
a
new
issue
and
select
current
localization
project.
This
issue
template
is
pretty
simple
and
pretty
basic
and
helps
us
taking
care
of
our
repository.
Someone
wants
to
integrate
and
promoting
people
with
appropriate
permissions
to
to
be
able
to
manage
these
projects.
A
A
Should
I
do
it,
I
mean
so
add
schedule
build
plug-in
because
it's
been
in
this
and
I
inadvertently
deleted
it.
So
if
you
could,
if
you'd
be
willing
to
put
submit
the
request
here
that
way,
people
can
watch
what
it's
like
to
submit
a
request
here
to
please
create
a
localization
project
for
plugins.
Yes,
I
promise.
A
A
C
B
A
B
C
B
Yeah,
actually
translations
are
a
major
part
of
the
user
experience.
For
example,
if
you
are
not
a
native
english
speaker
or
don't
use
jenkins
score
at
all
in
english
and
have
it
available
in
french
or
italian
or
something
you
often
stumble
apart
plugin
pages
or
fusion
jenkins
itself,
which
aren't
translated
at
all.
B
So
if
you're
using
jenkins
core,
let's
say
in
italian,
you
basically
have
many
plugins,
which
are
which
either
do
not
support
italian
translations
at
all,
yet
or
basically
are
not
up
for
localization
at
all,
which
looks
out
of
place
and
is
definitely
much
harder
to
use.
If
you
have
different
locates
in
one
ecosystem
and
crowding
provides
the
streamline
solution
here,
to
be
able
to
add
your
project
with
ease
by
being
able
to
receive
translation
suggestions
by
everyone
who
wants
to
help
out.
A
So
so,
to
give
a
past
commercial
experience,
I
worked
for
an
organization
that
was
selling
very
heavily
in
japan.
We
were
selling
a
mechanical
computer-aided
design
system
and
the
users
there
flatly
refused
to
use
something
if
it
was
not
fully
translated
into
japanese,
they
expected
everything
to
be
translated.
A
Now,
an
open
source
project
doesn't
have
the
benefit
of
commercial
commercial
cash
driven
development.
We
rely
on
our
community
to
do
those
kind
of
translations
so
having
a
facility
like
crowd
in
makes
it
much
more
likely
that
we'll
be
able
to
get
those
translations
from
our
users
compared
to
my
commercial
world
experience.
We,
we
spent
enormous
amounts
of
money
being
sure
that
we
were
translated
into
japanese,
because
our
customers
in
japan,
if
they
saw
an
english
word,
would
send
it
back
to
us
as
a
bug
report
right.
A
So
so
it's
it's
intensely
valuable
and
and
especially
so
in
languages
that
don't
use
what
you
might
call
western
european
alphabets
right,
because
then
it's
disconcerting
you're
you're,
seeing
your
cyrillic
alphabet
or
your
or
your
katakana,
or
your
kanji,
or
your
your
korean
character,
your
hangul
character,
set
and
then
all
of
a
sudden.
It
switches
character,
set
and
now
you're,
seeing
english
it's
it's
just
not
nearly
as
comfortable
as
having
a
localized
product.
C
Yes,
to
tell
the
truth,
I
have
tried
other
ways
of
translating
messages
within
jenkins
in
the
previous
weeks
before
crowding,
and
it
was
not
a
really
pleasant
experience
to
say
the
least.
So
yes,
crowling
is
much
easier,
I'm
not
that
good
at
jenkins.
Yet
so
I
don't
have
to
know
jenkins
to
be
able
to
translate
anything
and
that's
super
cool
and
as
a
translator,
I'm
not
alone.
C
I
don't
know
if
you
see
that
easily
in
your
interface
alexander,
but
there
was
one
of
the
translation
for
your
recently
added
plugin
that
I
was
not
able
to
translate
because
I
don't
know
what
this
acronym
is,
and
I
ask
you
a
question
and
as
a
translator
I
think
I'm
not
alone.
You
will
see
it.
You
will
be
able
to
answer
my
question.
So
it's
not
just
a
process
of
me
myself
and
I
just
stuck
in
a
room
translating.
C
I
can
also
interact
with
the
plugin
maintainer,
who
could
help
me
finding
what
the
issues
are
and
trying
to
solve
them?
That's
pretty
cool,
and
there
is
no
another
thing
I
wanted
to
address,
which
is
not
that
cool
is
that
there
is
no
glory.
It's
like
because
the
pool
crest
that
will
happen
will
not
be
in
your
name
so
so
long
for
the
glory
of
having
contributed
directly
within
the
github
repository
belonging
to
jenkins.
But
anyway,
I'm
super
happy
to
be
able
to
translate
things
for
jenkins
plugin
so
easily.
A
A
So
I
didn't
I
didn't
internationalize
at
all,
and
so
I've
got
some
work
to
do
on
polygons
that
I
maintain
just
to
make
them
internationalize
that
they
internationalize,
so
that
their
messages
and
their
help
can
be
done
in
translation
and
and
and
that
that
part
now
there's
there
are
instructions
online
on
how
to
do
it.
But
it's
work
that
I
have
to
do.
B
B
Yeah,
these
are
a
bunch
of
guides.
We
have
just
published
to
be
able
to
read
everything
a
text
term
again
how
to
translate
something,
how
you
proofread
something
or
how
you
set
up
a
crowding
project,
how
you
create
a
personal
access
token,
how
you
authenticate
the
action,
how
you
work
with
the
cloudant
file
and
yeah
or,
for
example,
how
you
translated
a
plug-in
through
krollin,
have
a
breakdown
on
the
web
interface
again.
B
B
Yeah,
for
the
time
being,
we
are
still
using
the
help
desk
repository
for
that,
but
I
don't
know
how
I
pronounce
your
name
but
had
the
idea
that
we
integrate
this
with
the
repository
permission,
updater
and
utilize,
the
cloudant
api,
to
create
these
new
projects
automatically
bruno.
Would
you
help
us
with
the
product.
B
Thanks
yeah,
he
basically
proposed
an
alternative
approach
of
project
creation,
which
I
have
drafted
on
the
repository
permission,
updater
short
rpu,
which
we
are
using
in
jenkins
to
update
permissions
on
the
artifactory
or
gita,
for
example,
and
integrate
a
new
sequence
here.
Plugin
maintainers
can
add
them
could
add
themselves
to
and
let
the
repository
permission
updater
create
a
new
project
on
cloud
and
jenkins
and
io
to
propose
a
more
automatic
solution.
Instead
of
doing
that
by
hand
through
the
infrastructure
help
desk.
A
Yeah,
which
I
think
is,
is
brilliant.
This
would
be
a
really
great
addition
sometime
in
the
future
that,
instead
of
or
when
I,
when
a
new
plug-in,
is
created
or
when
a
plug-in
maintainer
wishes
to
add
crowd
in
support,
all
they
would
do
is
submit
a
pull
request
to
repository
permissions,
updater,
adding
crowd
in
managers
and
their
username
or
the
username
of
the
other
administrators.
B
Yeah
this
is
the
proposed
workflow
of
what
mark
and
I
are
doing
at
the
end
at
the
moment,
you're,
basically
creating
a
project
and
creating
a
team,
one
crowd
indulgence
of
io,
adding
these
people.
They
are
creating
the
project,
adding
the
team
to
the
project.
That's
already
it.
The
process
isn't
super
difficult
and
doesn't
actually
take
a
lot
of
time.
A
And
I
am
pleased
to
announce
a
new
release
of
the
elastic
access
plug-in
has
been
delivered.
That
includes
the
change
that
plug-in
happens
to
use
a
continuous
delivery
mechanism.
That's
a
little
different
than
other
mechanisms,
but
if
you,
if
you
go
to
elastic
access,
plug-in
you'll,
see
that
a
new
release
has
been
delivered.
A
C
A
B
I
think
we
went
over
everything
we
have
the
documentation
of
this
and
the
text
form
available
on
jenkins.io
how
to
create
a
project
and
how
to
manage
it,
and
I
would
say
if
there
are
still
more
questions
or
someone
actually
needs
help
or
is
lost
at
some
step.
You
can
always
hit
up
on
community.jenkins.io
or
use
the
mailing
list
or
use
the
guitar
chats.