Skip to content

Become a maintainer

Jean-Denis Vauguet edited this page Dec 1, 2013 · 16 revisions

Reminder: the English version of ruby-lang serves as the master one. I18n is thus based on the English content.

Why becoming a I18n maintainer?

Well, I18n maintainers are responsible for:

  • coordinating the continuous update process of a specific, localized version of the website
  • translating news items (from en/) as quickly as possible
  • reviewing relevant pull requests
  • being nice and helpful to contributors

Reactivity is a key factor here:

  • contributors may submit pull requests from time to time…
  • whereas maintainers are willing to provide continuous service.

I18n maintainers gain push rights to the repository, so they may skip using pull requests (for instance, when translating a news item). Using pull requests is still considered a good practice in most cases, though. I18n maintainers are not able to deploy in production.

Each language must be supervised by a team of at least 2 maintainers. No language without such a team of dedicated editors is to be featured on the production server.

This a long-run, volunteer position with a few requirements. Would you be:

  • reactive (see above)
  • proficient in both your native language and English
  • detail-oriented
  • willing to review localized pull-requests (good communication)
  • git qualified

then you may be a good fit :) Please consider applying with your rational by creating a new issue, here, on this project.

When considering bootstrapping a new language, please keep in mind you must be at least 2 editors, willing to back the section in the long-term. Otherwise, consider contributing every once in a while: this is fine too!

Clone this wiki locally