Welcome to our platform where you can easily collaborate with others to help make Icinga accessible to all throughout the world!

Reporting Bugs

If you found a typo, bad wording or some other error in a source string or translation, you can report it here!

Just sign-in and »search for the offending string«. Once found, please add a comment in the respective scope.

A developer or translator will then either fix the issue or ask for further feedback. Please make sure to »enable notifications for mentions in comments« so that you don't miss any question.

How To Contribute

To contribute to any component on here, you'll also have to sign-in first.

You also need to sign our Contributor License Agreement (CLA): https://icinga.com/company/contributor-agreement/

Once you've done that, wait for your copy of the agreement that's sent to you by mail. By then, or shortly after, you should be able to start with the translation.

You are still unable to contribute or you already have signed the CLA in the past?

Then please »contact us« and we'll check your agreement. If everything is fine, we'll enable you to contribute and get back to you.

How It Works

Translations are split into two phases.

As a translator you'll propose new translations for yet untranslated messages. A reviewer then will take a look and accept or change them.

If you think there's something to improve on an already translated message, or you are simply not sure if your proposal is correct, add a new suggestion instead.

Suggestions for yet untranslated messages can also be accepted by other translators. Suggestions for already translated messages can only be accepted by reviewers.

Failing Checks

If a translation has errors, it won't be accepted. A reviewer may solve them, but translators are highly encouraged to only provide valid proposals.

Becoming a Reviewer

This depends on how many other reviewers there are and how active they are. In general, the more reviewers the less the chance to easily become one.

If for e.g. Arabic there is no reviewer yet, your chance to become one is certain if you feel you want that responsibility. We cannot review such languages ourselves and will accept any and all valid proposals otherwise near a release.

If there are already many active reviewers for a (to us) foreign language, we may delegate the decision to them.

But anyway, to ask for the reviewer status, »contact us« and tell us the languages you want to review.

Style and Wording

While this mostly depends on the language, there are some general rules we think everyone should follow.

Don't write novels

Most of the messages are shown in a UI with sometimes limited space. It may not always be avoidable that the translation is longer than the source string. But please keep your translations only as long as absolutely required.

Addressing the user

In some messages the user is addressed directly. While in English, this may not be a problem, but many languages use different polite forms depending on the situation. If this is the case, please use a rather neutral form. We don't provide the capability to have multiple translations for a single language, so all users have to stick with a single one. If there's no neutral form or you don't want to use one, you may also rephrase the message so that it doesn't address the user directly.

Placeholders

You may encounter placeholders like %s or %3$.2f. These are »conversion specifications« and must not be changed. But you can freely move them around. The context usually gives a hint about their purpose and meaning.

You may also encounter some placeholders of this form: {{#link}}some text{{/link}} or {{#emphasized}}a word{{/emphasized}}. These are templates that usually represent HTML tags. Also these must not be changed. But you can also move them around, while keeping the structure intact: {{#link}} must appear before {{/link}} and the text inside them should still be inside. Though the text they encapsulate, i.e. some text or a word, should be translated by you.