Setup of a new project

Revision as of 08:01, 29 September 2016 by Nemo bis (talk | contribs) (→‎Message group configuration: fix grammar)
Jump to navigation Jump to search

Verify the project

Requirements and process: Translating:New project for details. Best practices we usually enforce (main pain point): Translating:Localisation for developers.

  • License
  • Quality of strings
  • Message documentation
  • Activity and interest (releases, contact person)
  • File format
  • Push access: ensure push-access is given either to L10n-bot (wikimedia gerrit) or Niklas and Siebrand (GitHub or BitBucket).

Repository configuration

Edit repoconfig.json and repoconfig.commit.json, bin/EXTERNAL-PROJECTS bin/REPONG-PROJECTS in the translatewiki repository.

Also for myself, not currently in version control.

Read-only mirror link:

Some documentation exists at Repository management, but it is mostly outdated by the new repong framework, where most projects have already been converted to.

Message group configuration

Lots of examples under groups/ in translatewiki repo. Old but mostly still valid documentation:

Need some info such as logo and message group description done in the next section.

Choosing a group id:

  • Practice is to use lowercase letter with dashes as level separators in case of multiple groups
  • Prefix "out-" is deprecated and should not be used for new projects
  • In case of multiple groups, the aggregate group should get the top level name, i.e. "blockly", and contain all groups named "blockly-*". Suffixes like "-0-all" are deprecated.

Wiki configuration

TranslateSettings.php needs updated to register the yaml file, possibly new namespace as well if none of the existing ones fit.

Translating:projectname needs to be created (copy template from Translating:FreeCol) for example. Logo needs to be in Commons or uploaded to

Description needs to be added to and page marked for translation.

Other misc things:

  • Add babel templates (this is forgotten very often - the whole thing should be automatized)
  • Add support to Template:Support and relevant categories

See also