launchpad development|
Size: 1776
Comment:
|
Size: 4298
Comment: Added link to upstreams
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| '''On Launchpad:''' ''hyperlink to a blueprint, normally'' | '''On Launchpad:''' [[https://blueprints.edge.launchpad.net/rosetta/+spec/import-upstream-translations-into-ubuntu|import-upstream-translations-into-ubuntu]] |
| Line 9: | Line 9: |
| As an Ubuntu developer/translator,<<BR>> | ''As an Ubuntu developer/translator,<<BR>> |
| Line 11: | Line 11: |
| so that it's easy to make use of them through global suggestions when translating Ubuntu.<<BR>> | so that it's easy to make use of them through global suggestions when translating Ubuntu.''<<BR>> |
| Line 13: | Line 13: |
| ''Consider clarifying the feature by describing what it is not?'' | Since we want to have all upstream projects' translations imported into Launchpad anyway, we are focusing on only how we share translations between upstreams in Launchpad (both hosted and imported) and Ubuntu. |
| Line 17: | Line 17: |
| This is a critical step towards bridging the gap between upstream and Ubuntu translations: once upstream translations are in Launchpad, we need to get them into Ubuntu as well. | |
| Line 18: | Line 19: |
| ''Why are we doing this now?'' | What do we get with this? |
| Line 20: | Line 21: |
| ''What value does this give our users? Which users?'' | * Better Ubuntu translations: they get imported from upstream very soon after they are done (<3 days) * Less work for Ubuntu translators: they can focus on Ubuntu-specific strings * Happier upstream translators: their translations get to Ubuntu users (at all, and faster) * Less duplicate work: because of a smaller time difference since last import from upstream (currently it's based on packaged translations in upstream tarballs), it's less likely to get duplicate same translations happening both upstream and in Ubuntu What is this basis for? * Sending changes from Ubuntu upstream in a form useable by upstreams. * Knowing what are Ubuntu specific strings so we can speed up translation of Ubuntu-specifics and report status on it. |
| Line 24: | Line 33: |
| ''Who really cares about this feature? When did you last talk to them?'' | === Ubuntu Translators Community === === Canonical OEM === === Ubuntu upstreams === GNOME, KDE, Debian, Open``Office.org, Firefox, Free``Desktop, GNU (Translation Project). More info on [[https://wiki.ubuntu.com/Translations/Upstream|Ubuntu's upstreams]]. |
| Line 28: | Line 43: |
| ''What MUST the new behaviour provide?'' | This feature must implement ''no-action-required'' import of translations from an upstream LP project into Ubuntu sourcepackage when there is a link between the two: automatic sharing of translations. |
| Line 30: | Line 45: |
| ''What MUST it not do?'' | It should not implement import from sources other than Launchpad upstream projects. It should provide no other features such as detection of template differences between upstream and Ubuntu templates. |
| Line 34: | Line 49: |
| ''Other LaunchpadEnhancementProposal``s that form a part of this one.'' | Will depend on the actual implementation plan chosen. |
| Line 38: | Line 53: |
| ''What are the workflows for this feature?'' ''Provide mockups for each workflow.'' '''''You do not have to get the mockups and workflows right at this point. In fact, it is better to have several alternatives, delaying deciding on the final set of workflows until the last responsible moment.''''' |
This should neatly integrate into existing workflows. There should be no change in user behaviour except that they won't have to do some things (like manually translate in two places, or download upstream PO files and upload them to Launchpad). |
| Line 45: | Line 57: |
| ''How will we know when we are done?'' | We know we are done, when upstream translations from a project in Launchpad are imported into Ubuntu sourcepackage translations at most 1 day later. Pre-requisite for this is that we have at least 90% of all Ubuntu upstreams imported into Launchpad translations. |
| Line 47: | Line 59: |
| ''How will we measure how well we have done?'' | Things we need to keep track of to know that this feature is working: * Number of new 'changed in LP' translations should approach zero * We'll either see better statistics for Ubuntu translations, or less karma awarded for them (i.e. people doing less work to achieve the same result) |
| Line 51: | Line 65: |
| ''This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the first part of our release change log. It is mandatory.'' | Ubuntu now gets direct translation imports from upstreams: there is no user action required. This eliminates duplicate work between Ubuntu and upstream translations, and should improve Ubuntu translations, along with getting upstream translations to users faster. |
| Line 55: | Line 69: |
| ''Put everything else here. Better out than in.'' | We are currently discussing following approaches to solving the problem: * [[/FallbackPOTMsgSet|FallbackPOTMsgSet]] * [[/FixingIsImported|Fixing is_imported and using existing message sharing]] * [[/ImportingDirectly|Importing directly into Ubuntu]] * [[/MessageSharingWithNewFlag|Message sharing with a new way of indicating upstream or Ubuntu current translations]] * [[/HandlingAtUpdateTranslation|Handling at updateTranslation level]] |
The purpose of this template is to help us get ReadyToCode on features or tricky bugs as quickly as possible. See also LaunchpadEnhancementProposalProcess.
Automatic upstream translations import into Ubuntu
Translations in Launchpad upstream projects should be automatically used in Ubuntu whenever possible.
On Launchpad: import-upstream-translations-into-ubuntu
As an Ubuntu developer/translator,
I want to see up-to-date upstream translations in Launchpad,
so that it's easy to make use of them through global suggestions when translating Ubuntu.
Since we want to have all upstream projects' translations imported into Launchpad anyway, we are focusing on only how we share translations between upstreams in Launchpad (both hosted and imported) and Ubuntu.
Rationale
This is a critical step towards bridging the gap between upstream and Ubuntu translations: once upstream translations are in Launchpad, we need to get them into Ubuntu as well.
What do we get with this?
Better Ubuntu translations: they get imported from upstream very soon after they are done (<3 days)
- Less work for Ubuntu translators: they can focus on Ubuntu-specific strings
- Happier upstream translators: their translations get to Ubuntu users (at all, and faster)
- Less duplicate work: because of a smaller time difference since last import from upstream (currently it's based on packaged translations in upstream tarballs), it's less likely to get duplicate same translations happening both upstream and in Ubuntu
What is this basis for?
- Sending changes from Ubuntu upstream in a form useable by upstreams.
- Knowing what are Ubuntu specific strings so we can speed up translation of Ubuntu-specifics and report status on it.
Stakeholders
Ubuntu Translators Community
Canonical OEM
Ubuntu upstreams
GNOME, KDE, Debian, OpenOffice.org, Firefox, FreeDesktop, GNU (Translation Project). More info on Ubuntu's upstreams.
Constraints
This feature must implement no-action-required import of translations from an upstream LP project into Ubuntu sourcepackage when there is a link between the two: automatic sharing of translations.
It should not implement import from sources other than Launchpad upstream projects. It should provide no other features such as detection of template differences between upstream and Ubuntu templates.
Subfeatures
Will depend on the actual implementation plan chosen.
Workflows
This should neatly integrate into existing workflows. There should be no change in user behaviour except that they won't have to do some things (like manually translate in two places, or download upstream PO files and upload them to Launchpad).
Success
We know we are done, when upstream translations from a project in Launchpad are imported into Ubuntu sourcepackage translations at most 1 day later. Pre-requisite for this is that we have at least 90% of all Ubuntu upstreams imported into Launchpad translations.
Things we need to keep track of to know that this feature is working:
- Number of new 'changed in LP' translations should approach zero
- We'll either see better statistics for Ubuntu translations, or less karma awarded for them (i.e. people doing less work to achieve the same result)
Release Note
Ubuntu now gets direct translation imports from upstreams: there is no user action required. This eliminates duplicate work between Ubuntu and upstream translations, and should improve Ubuntu translations, along with getting upstream translations to users faster.
Thoughts?
We are currently discussing following approaches to solving the problem:
