►
Description
GitLab team members are located in 68 countries! Let's learn some fun words in other languages and then contribute to GitLab localization!
We will start by sharing which country each person is from and what languages they speak and each person will teach the group some words (like hello, how are you? good morning, good evening).
After this introduction round, the presenter will show how to contribute to GitLab's localization. We will all pull out our laptops and contribute to additional language support for GitLab.
Link to presentation: https://docs.google.com/presentation/d/1WWOCPYmWut8wXJowBgQg2mTI6XdLFk3m7fAHO8X8AvU/edit#slide=id.g55e9452978_0_75
A
B
A
A
A
That
involves
everything
from
translation
to
instrumenting
these
translations,
getting
them
from
from
the
translating
tool
into
gitlab
and
vice
versa,
pushing
any
new
strings
that
we
created
in
github
out
to
to
the
tool.
Something
where
we
haven't
really
spent
enough
time
is
really
kind
of
the
remainder
of
the
localization.
So
the
ability
for
us
to
not
just
speak
the
language,
but
also
respect
the
date
number
and
other
settings
that.
A
A
There
are
two
groups
of
or
two
levels
of
translators.
One
is
the
translators
which
are
you
know,
which
do
translations
and
they
also
vote
on
other
people's
translations.
So
that
helps
us.
You
know,
discuss
and
figure
out
which
translations
are
better
and
then
we
have
proofreaders,
which
there
is
at
least
one
per
language,
actually
there's
some
languages
which
have
none,
but
there
should
be
at
least
one
per
language,
and
these
are
the
final
approvers
of
a
particular
translation.
A
A
So
you
can
see
that,
for
example,
in
chinese
we're
pretty
much
keeping
up
and
we
do
get
most
of
the
strings,
translated
and
approved
sort
of,
as
we
add
them
to
gitlab
some
of
the
other
languages.
For
example,
french.
We
have
everything
translated,
100
translated,
but
only
11
of
those
strings
are
actually
going
to
show
up
in
gitlab,
because
we
don't
have
enough
proofreaders
and
approvers
who
can
actually
work
on
that.
So
that's
one
of
the
challenges
I'll
be
talking
about
at
the
bottom.
You
can
see
some
statistics.
How
many
words?
A
A
B
A
That's
a
really
great
question,
so
the
approvers
have
to
have
experience
being
translators
for
a
while.
Maybe
they've
done
that
with
gitlab
for
some
time
they
need
to
be
familiar
with
the
gitlab
vocabulary,
which
is
important
because
we,
you
know,
we
talk
about
certain
things
in
certain
ways.
You
can't
just
literally
translate
things
these.
These
will
also
be
translators
who
have
experience
in
other
projects
that
they've
been
doing.
A
Other
technical
translations
doesn't
have
to
be
that
they
have
a
lot
of
fit
lab
experience,
but
typically
what
happens
is
we
will
have
some
of
the
seniors,
senior
translators
or
proofreaders?
Take
a
look
at
the
work
that
they've
done
and
sort
of
promote
them
to
a
proofreader.
So
the
process
is
not
very
formal,
but
we
do
kind
of
try
to
promote
translators
with
experience
into
proofreaders.
B
A
B
B
A
Yes,
it
could
be
anyone
with
a
passion
for
translating
and
we
have
probably
more
translators
from
the
community
than
we
do
from
within
git
lab,
probably
more
proofreaders
from
gitlab
than
we
have
from
within
community.
But
it
is
not
a
rule
of
any
sorts
and
it's
just
kind
of
how
things
work
out.
But
yeah.
We
do
have
a
lot
of
participation
from
inside
and
outside
of
the
club,
both
proofreading
and
translating.
A
A
A
A
A
A
We
are
also
doing
once
a
month
the
update
of
the
level
of
translation.
So
you
can
get
an
idea
for
when
you're
selecting
a
language
like
how
much
should
you
expect
there
to
be
translated.
So
if
I'm
selecting
italian
and
we
have
a
two
percent
translated-
I
don't
expect
really
much
to
be
there.
But
you
know
if
I
take
something
that
is
like
a
portuguese
brazilian
portuguese
and
half
of
it's
been
translated.
I
would
expect
a
lot
of
it
to
be
translated.
A
So
some
of
the
challenges
that
we
face,
the
whole
manual
merge
of
translations
is
a
challenge.
I
do
this
once
a
month,
and
this
is
kind
of
as
often
as
I
can
do
it,
because
time
prohibits
me
from
doing
that
more
often,
but
that
still
means
that
it
takes
a
month
or
two
after
you
translate
something
before
you
can
actually
see
it
in
in
the
gitlab
ui.
A
A
A
We
also
have
a
lot
of
strings.
Many
more
strings
that
were
translated,
then
approved
so
really
getting
the
proofreaders
to
just
go
through
the
strings
that
have
been
translated
and
approved
them
would
significantly
increase
the
translation
levels
that
we
currently
have.
We
also
are
speeding
up
our
development.
You
know
with
each.
A
You
know
each
milestone,
there's
more
and
more
strings
being
added.
So
even
if
everything
stayed
the
same,
we
would
need
to
get
more
people
to
translate
each
month
because
we
have
new
strings
arriving
with
that.
We
also
have
the
translation
loss
so
a
lot
of
times
when
translation,
when
new
translations
are
added,
some
translations
are
taken
away.
A
Translations
are
changed,
so
if
we
just
decide
to
change
a
wording,
even
if
it's
just
like
an
adding
a
comma
to
fix
a
typo
in
a
large
chunk
of
text,
we
will
lose
that
chunk
of
text
for
all
the
languages.
It's
been
translated
on
because
it
is
now
a
new
string
and
that's
been
something
that
that
has
happened
a
lot.
So
if
you
take
a
look
at
the
bottom
chart
here,
you
will
see
you
know
how
many
words
were
added,
how
many
words
were
deleted
and
we
don't
have
updates.
A
A
A
B
A
A
So
the
very
first
thing
that
I
would
like
for
you
to
do
is
go
look
at
the
language
that
you're
interested
in,
and
you
will
see
two
files.
In
theory,
one
is
called
the
gitlab
as
in
translation
and
the
other
one
is
the
glossary
if
you're,
just
starting
or
if
this
language
hasn't
gotten
a
lot
of
translations,
it's
always
good
to
start
with
the
glossary,
which
means
we're
really
not
translating
strings
that
are
going
to
be.
A
You
know
used
in
in
gitlab
directly,
but
we
are
translating
the
glossary,
all
the
words
we're
deciding
what
we're
going
to
call
the
you
know
all
of
these
words,
so
words
such
as
issue
have,
you
know,
have
to
be
agreed
upon
and
figured
out
how
we're
going
to
talk
about
issues.
Direct
translation
to
some
languages,
don't
work,
so
some
of
the
languages
use
the
word
ticket
or
problem
in
order
to
to
speak
about
issues.
A
Similarly,
you
know
in
in
here
you
will
also
find
you
know,
typically
the
discussion
that
that
that's
really
important
is
the
one
about
the
word
you
and
how
we
talk
to
people.
So
how
is
you
translated?
A
lot
of
languages
have
formal
use,
informal
use
and
each
each
translation
community
each
language
makes
its
own
decision
as
far
as
what
is
the
appropriate
level
of
formality
for,
for
that
particular
translating
language.
So
those
are
discussions
to
be
had
in
the
glossary,
so
the
glossary
is
where
we
decide.
A
Then
we
know
that
this
is
the
word
that
we're
all
using
for
that
particular
translation.
So
you
know
for
me
to
translate
this.
I
would
have
to
use
the
variable
that's
given
to
us,
so
you
have
to
use
the
variable,
and
this
is
how
a
one
package
would
be
translated
to
bosnian.
It
would
be
percent
d
which
stands
for
one
in
this
case,
one
packet,
if
you
have
a
few
packets,
so
something
unlike
english,
where
you
have
just
a
singular
and
plural.
A
A
B
A
A
B
A
Creating
track
great
point,
I
will
so
I
am
showing
the
I'm
showing
kind
of
this
year's
translations
course,
but
I
will
definitely
be
looking
at
the
translations
that
happen
today
versus
translations
that
happen
tomorrow
during
the
other
session
and
I'll.
Let
you
all
know
which
day
one
in
the
meantime,
these
are
some
of
the.
B
A
Okay,
so
I'll,
let
you
complete
a
few
translations
that
you're
working
on.
I
do
want
to
talk
about.
You
know,
so
this
is
translating
you
can
also
be
voting
and
approving
is
you
won't
be
able
to
approve
things
yet
because
you're
not
a
proofreader,
but
let
me
see
if
I
have
an
example
of
where
we
might
be
able
to
vote
on
something.
B
A
Great
question
so
certain
brand
names
or
certain
trademarks
or
things
that
you
know
that
are
just
proper
names
should
not
be
translated.
So
you
know
we
wouldn't
translate
gitlab,
we
wouldn't
translate
git,
we
probably
wouldn't
translate
fork
or
some
of
the
technical
lingo.
It
really
depends.
So
this
is
kind
of
where
the
technical
knowledge
comes
in.
It
depends
on
how
these
developers,
let's
say,
talk
amongst
each
other
when
they're
in
their
country
speaking
their
language.
A
So
if
we
have
a
bunch
of
ukrainian
developers
talking
to
each
other
in
ukraine
about
git,
if
they
use
the
word
git,
then
that's
the
word
we
should
use
if
they
use
the
word
fork,
then
that's
the
word
we
should
use.
If
they
translate
the
fork
and
use
a
native
word
for
that
process,
then
we
should
translate
it
as
well.
But
typically,
if
these
are
commands,
like
git
commands
or
proper
names,
is
you
know
those?
We
should
not
be
translated
because
we
do
want.
A
We
don't
want
to
confuse
people
as
far
as
what
we
mean
by
certain
things.
So
definitely
there
are
words
that
should
not
be
translated
and
the
extent
of
how
far
we
go
with
some
of
these
things
really
depends
on
the
language.
I
know
one
of
the
very
tough
words
that
we've
had
to
think
about
over
the
last
couple
years
is
the
word
epic,
like
in
english.
A
The
agile
has
really
introduced
to
us
the
word,
epic
as
a
large
story
and
we're
all
familiar
with
it,
and
when
somebody
says
epic
nowadays,
I
don't
really
think
about
like
an
you
know,
odyssey
or
any
any
kind
of
like
old
stories
that
are
very
big.
I
really
think
about
you
know
a
portfolio
item,
so
so
in
english.
It
is
kind
of
easy
to
think
about
in
certain
in
that
way,
in
some
other
languages.
That
word
has
a
very.
It
has
a
slightly
different
meaning.
It
does
not.
A
A
It
is
just
not
something
that
has
ever
been
translated
into
that
language,
because
it's
very
technical
and
it's
a
fairly
new
use
for
the
word
so
really
depends
on
the
language,
and
I
think
this
is
kind
of
where
you
need
to
go
back
and
maybe
discuss
with
some
of
the
developers
from
your
country.
What
word
they
might
be
using
for
a
particular
concept.
B
A
Ignoring
it
will
do
the
same
thing
as
translating
it,
but
I
think
translating
is
the
right
thing
to
do,
because
that
means
that
we
have
agreed
not
to
translate
it.
So
if
the
word
git
lab
were
to
show
up
here
in
in
in-
and
you
were
asked
to
translate
it,
you
would
just
copy
down
verbatim,
and
you
will
accept
that
translation
so
that
we
agree
that
in
this
particular
language,
this
word
will
not
get
translated.
A
And
here's
also
a
way
to
vote
for
certain
translations.
So
here
are
several
translations
that
we
have
in
french
for
one
closed
issue
and
they've
been
submitted
by
different
people,
and-
and
you
know
this
particular
translation
has
16
votes
and
I
can
also
upvote
it.
I
am
proofreader
as
well,
so
I
could
potentially
even
accept
this,
but
this
is
sort
of
where
we
upload
translations
so
that
the
proofreaders
can
come
in
and
see
that
oh
yeah.
This
is
the
one
that
has
been
accepted
by
everybody
else.
A
So
the
way
to
discuss
some
of
these
is
in
the
app
as
well
as
if
you
notice
there
are
comments
to
the
right
of
each
one
of
these
source
strings,
and
these
comments
are
combining
the
discussions
from
different
languages,
because
there
may
be
some
typically
the
questions
that
we
get
around.
These
is
just
context
like
one
closed
issue,
that's
probably
more
clear,
but
something
like
none
well,
you
know.
What's
the
context
where
does
it
show
up?
A
You
know
is
the
noun
that
the
noun
is
related
to
you
know
a
feminine
or
a
masculine
noun
right,
because
it
matters
to
some
languages.
So
this
is
the
you
know.
This
is
kind
of
where
we
discuss
and
talk
and
answer
questions
about
each
one
of
these
and
you
know,
come
to
a
conclusion
on
what
is
the
right
approach
for
translating
that
particular
word
so
do
use
the
chat
as
well
to
chat
with
other
translators
or
just
read
through
the
chat.
A
It's
been
namespaces
have
been
tough,
they
were
introduced
because
a
lot
of
times
you
have
a
particular
view
that
has
a
lot
of
context,
for
example,
admin
settings
so
within
admin
settings
there
could
be
things
that
are
just
as
simple
like
back.
No,
yes,
cancel
and
without
any
context
we
would
have.
A
Probably
you
know
dozens
of
words
that
say
yes
or
no,
that
have
been
translated
from
different
views
if
we
translate
all
of
them
the
same
that
may
not
work
in
all
of
the
languages
because
the
context
matters,
for
example,
you
know
again
whether
the
concept
is
a
muscular
feminine.
You
may
have
a
we
use
a
different
word
to
translate
some
of
these
words.
A
So
we
have
introduced
the
concept
of
namespaces,
so
we
will
tell
the
translators
that
this
is
admin
settings
and
then
separated
by
pipeline
and
then
really
the
word
that
needs
to
be
translated
or
the
text
that
needs
to
be
translated
is
the
one
after
the
pipeline.
So
the
translation,
as
you
can
tell
here
for
french,
does
not
copy
down
the
admin
settings
part
or
the
pipeline.
A
You
really
only
translate
the
the
text
after
the
pipeline
and
that's
kind
of
how
it's
used,
and
that
has
also
been
confusing
to
people.
So
there
have
been
a
lot
of
translations
where
people
would
just
copy
down
the
namespace
or
translate
the
namespace
and
there's
really
no
no
great
way
to
do
this,
so
we
just
have
to
keep
keep
talking
about
and
keep
teaching
people.
So
thank
you
for
asking
this.
A
This
is
really
important
to
get
when
you
do
translations
is
that
namespaces
are
there
just
for
your
context
to
help
you
understand
where
you
are.
You
can
also
just
look
at
look
for
strings
in
one
name,
space
to
just
translate
all
of
them
together,
which
is
helpful
because
that
that
means
that
one
particular
view
or
one
particular
concept
will
get
all
of
those
translations
done
at
the
same
time.
A
So
yeah
namespaces,
you
omit
those
and
you
only
translate
whatever
is
after
the
pipeline
and
as
you
can
tell
here,
the
underlying
some
of
these
words
are
underlined,
which
means
they
have
glossary
items
and,
if
you're
not
sure
like
how
that
particular
concept
is
being
translated
into
the
language.
For
example,
how
do
we
translate
runners
into
french?
It's
probably
a
couple
different
ways.
Some
of
them
mean
people
running,
and
you
know
you
can
tell
here
that
you
know
the
french
community
has
decided
to
translate
it
into
executors
right.
B
A
So
jessica's
asking
about
the
formula
versus
informal,
french
and
german
are
the
ones
that
I've
seen
discussions
on,
but
I
think
some
of
the
other
ones
the
discussion
has
pretty
much
been
had
in
the
glossary.
So
if
you
take
a
look
at
the
glossary,
there's
probably
going
to
be
a
translation
for
you
and
probably
on.
That
word
is
where
the
discussion
was
had
in
the
chat.
A
A
So
that's
that's
one
way
to
think
about
it.
We
try
not
to
be
too
formal,
but
we
also
don't
want
to
address
people
as
if
they
were
children,
because
again,
there's
like
many
different
levels
of
formality
for
a
lot
of
languages,
so
you
kind
of
have
to
find
that
golden
middle
ground.
I
have
actually
found
that
microsoft
has
great
guidance,
so
they
have
published
their
guidance
for
translations
that
they
normally
use.
A
They've
published
those
externally
and
I've
like
read
through
some
of
that,
because
it's
it's
great
food
for
thought
for
a
particular
language
about
how
that
language
is
being
used
and
like
in
what
cases
you
will
use
a
formal
versus
informal.
So
I've
used
that
to
inform
myself,
but
generally
we
try
not
to
be
formal
and
speaking
at
people
from
above.
A
A
A
B
I
I
also
think
that
we
got
a
great
takeaway
here
for
community
relations
and
maybe
having
this
activity
as
part
of
hackathons,
which
is
also
excluding
no
code.
I
guess
I
would
call
it
omar
had
a
question
on
the
chat.
Is
there
a
way
to
know
whether
a
string
you
translate
finally
made
it
to
the
product
or
got
approved
for
inclusion?
It
would
be
cool,
it'll,
be
a
cool
feeling
and
the
motivator
to
know
that
my
translations
are
going
somewhere.
A
A
The
next
first
of
the
month
is
when
it
will
be
included.
So
I
do
these
merges
once
a
month
around
the
first
or
the
second
of
the
month,
whatever
day
I
get
to
it,
and
so,
if
you've
translated
something
that
was
eventually
proofread
and
approved
in
october,
it
will
be
in
the
november
release.
So
it's
always
kind
of
next
month
release
from
the
month
where
it
got
approved
until
we
get
some
time
to
automate
some
of
the
merging
activity
that
we
have.
A
No
and
and
that's
been
a
conscious
decision
that
we
would
not
want
to
translate
the
development
documentation
a
we
would
never
be
able
to
keep
up
and
it's
hard
for
our
developers
to
you
know
so.
Our
development
documentation
changes
often,
and
so
this
this
includes
not
just
development
documentation,
but
generally
the
help
docs
as
well.