So that I don’t forget, here’s a quick list of my current pain points with i18nInternationalization Internationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks. in general. Please add anything you feel to be relevant to these points, keeping in mind that it’s still rather high-level at this point.

I propose we schedule a series of chats (not just one), to approach each section of the final list (i.e. this one, amended). Sorry to pile on @nacin, but he will probably be needed, which means that his constraints for scheduling take priority.

Have at it.

LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in Forums


  • It’s impossible to create new forums right now.
  • The ones that do exist are running a very old version of stand-alone bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites., which is buggy and unstable.
  • There is no connection between RosettaRosetta The code name of the theme for the local WordPress sites (eg. is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. users and forum moderators and admins, permissions have to be given in two different places


  • Install the new bbPress pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party on all Rosetta sites and import content from existing forums
  • Keep the Pending/Resolved add-on, Akismet spam checking and whatever else is relevant
  • Implement sensible new user roles (see below)


(obviously just the tip of the iceberg, there’s a lot more that can be added to this)


  • No clear overview of who is reponsible for what
  • Codex page is completely out of date, and history has shown us that it’ll go on staying that way
  • No record of activity on a user’s profile (contributions to translation, locale forums, rosetta posts)


  • Kill the locale teams and forming teams pages on the Codex, they’re useless
  • The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. with (for now) simple information on language, latest release, team members and roles, contact page. This could probably be read automatically, from each Rosetta site
  • Direct download links, both for releases & language file bundles.


(note: some points below are very likely GlotPressGlotPress GlotPress is the translation management software that powers More information is available at tickets waiting to happen)


  • Neither Translate nor the import script (.POT-to-GP, a.k.a “import originals”) are aware of new branches, which makes it mandatory to add them by hand
  • There is no mechanism to download all language files as a bundle. This is not only important for existing stable installations, but also for those who want to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. test and most importantly for those who want to change to a language that wasn’t supported before
  • Not sure how this applies to others, but in languages with a lot of movement, too much time is wasted by validators on numerous suggestions of stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that should be in a “locked” state.


  • A way to automatically populate projects and the import secript by new branch
  • Don’t rely on developers to keep .POT files updated (i.e. run makepot from a Translate script, same as WordPress does now)
  • Implement export bundles (mostly for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.)
  • Implementa a new flag to allow for locking translations against new suggestions/imports

Need to elaborate/discuss

DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. system

  • Automate rosetta, forums, browsehappy deploys (i.e. add to queue, process once a day?)
  • Notify polyglots’ leads and lang admin of errors only
  • How do we get completely rid of svn?