*This is another article in a series of posts where I will be outlining some of the goals for my team for the Ubuntu 10.10 cycle which I am in the process of planning for*.
Ubuntu has always had a strong commitment to ensuring that it is available in everyone’s local language. We have seen incredible growth in this area, and Ubuntu is available in many languages, and this hugely helps people use the system and helps adoption.
With this goal in mind we have invested heavily in providing some rocking tools to make translations as easy as possible; this includes tools such as [Rosetta](https://translations.launchpad.net/) in Launchpad, and the facilities that make the workflow simple for every day translators.
The translations process has two fairly key users:
* **Translators** – people who translate strings. Many of these folks are often non-developers, and in many cases power-users who speak a given language who want to help translate Ubuntu. Many of folks want to dip in and out of translations: they want a list of things that need translating and will contribute when they have time.
* **Developers** – these are people who want to ensure that their application has rocking multi-language support. These kinds of folks have a more systematic requirement: translations become a feature that they want to support in their apps.
I am keen for us to focus on these two specific demographics in the 10.10 cycle, and I have asked **David Planella** on my team to work on this.
I have asked David to focus on some key areas:
* Simplifying translation workflow: ensuring it is dead simple to get involved as either a *translator* or *developer*.
* Raise the awareness and importance of translations in the Ubuntu community.
* Identify tools and infrastructure needs to improve how our translations community works.
* Identify what needs we have to ensure we are working as effectively with upstreams as possible.
So, as with [my previous 10.10 planning article](https://archivedblog.jonobacon.com/2010/03/23/planning-for-10-10-improving-how-we-review-patches/), what feedback do you folks have that David can focus in on?
