Translations Utopic Unicorn (14.10) Roadmap

Registered by amjjawad  on 2014-05-05

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This is Ubuntu GNOME Translations Roadmap for Utopic Unicorn (14.10)
- https://wiki.ubuntu.com/UbuntuGNOME/SubTeams#Translations -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Translations Utopic Unicorn (14.10) Roadmap
-----------------------------------------------------------------
1- As discussed during Trusty Tahr Cycle - https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/ubuntu-gnome-translation - we shall start hopefully with this cycle to do the Translations of Ubuntu GNOME to different languages. We need a Driver for this mission and interested volunteers.

2- No need to create new team on Launchpad. Team Leader and Members of Ubuntu GNOME Translations group could be part of Ubuntu GNOME Marketing and Communicaitons Team (https://launchpad.net/~ubuntugnome-comms) and Ubuntu Translations (https://wiki.ubuntu.com/Translations) - See: https://wiki.ubuntu.com/UbuntuGNOME/Translations

3- Other Plans to be discussed with the driver of this area and this blueprint will be updated accordingly.

Blueprint information

Status:
Complete
Approver:
amjjawad 
Priority:
Essential
Drafter:
amjjawad 
Direction:
Needs approval
Assignee:
Jānis Marks Gailis
Definition:
Pending Approval
Series goal:
Proposed for trunk
Implementation:
Implemented
Milestone target:
None
Started by
amjjawad  on 2014-06-15
Completed by
amjjawad  on 2014-11-13

Related branches

Sprints

Whiteboard

--[Jānis-Marks Gailis]: About the translations, we need to localize the documentation. The thing we need to know is how the docs are made (from a technical Point Of View), and how can we translate those.
On the other side, there is all the marketing stuff, that we absolutely need to localize in order to get more and more users. For this stuff, it's much more simple: if it's about a .svg infographic, the easiest way (to start, because if we have many translations it will become much more difficult) is to make a .po file, which would be given to the translators, that they send us back so I integrate the translations into .svg files. So the translators will need no skills about using inkscape. And we could do similar things with .xcf files (that are the GIMP projects).
There is also another one thing about the marketing: it's the communication. The best would be to get through the LoCoTeams, but they think (and I agree with them about that) that it would show the divised side of the FOSS community. So the only place we can make our marketing is the web. On social networks, like twitter or facebook. So I think we should coordinate the publications on, for example, twitter, by preparing a few day before, some tweets that we would publicate at a defined time. And we would have a separate Twitter account for every language, that would have at least one translator.

Today, I think we should start with the Twitter publications translation; because it's one of the rare ways for us to bring more and more users, and in the same time we should start to see how we would be able to provide a localized version of our docs to the end-user.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.