UDS

Differences between revisions 8 and 9
Revision 8 as of 2010-04-27 14:09:42
Size: 6221
Editor: 168
Comment: Added new roundtable
Revision 9 as of 2010-04-27 14:14:22
Size: 6441
Editor: 168
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
   * Could langpack-o-matic build the translated XML files for documentation to be shipped in language packs? Even if we cannot get it to build for all packages, even if only for ubuntu-docs would be a big improvement.

Introduction

The purpose of this page is to list all suggestions for the UDS Maverick translation sessions to be used as a basis for the final schedule.

Session proposals

  • Translations community roundtable (DavidPlanella)

    • Unstructured session to discuss and gather feedback on all around the Ubuntu translations community
      • Proposed topic: QA of language packs (GaborKelemen) - asking translators to test each updated package before release may be too much. With on-demand updates, it may be unnecessary to withhold untested updates.

  • Launchpad Translations roundtable (DavidPlanella)

    • Unstructured session to discuss and gather feedback on all around Launchpad Translations as a tool
  • Desktop and Translations roundtable (DavidPlanella)

    • Roundtable with members of the desktop team to discuss everything related to translations. Proposed topics:
      • Implementing gettext support to PolicyKit

      • Firefox and OpenOffice.org translations

      • Common approach for building POT template on non-desktop packages using plain gettext instead of intltool, e.g. mountall, in the same way as CDBS GNOME packages use langpack.mk

      • Could langpack-o-matic build the translated XML files for documentation to be shipped in language packs? Even if we cannot get it to build for all packages, even if only for ubuntu-docs would be a big improvement.
  • Translations Community Advocacy (DavidPlanella)

    • Session to discuss how to rise awareness on the global Ubuntu Translations community, both within and outside the Ubuntu community.
  • Translations Community Learning Content (DavidPlanella)

    • Session to discuss ways of providing content to ease start contributing to translations.
  • Translations Community Events (DavidPlanella)

    • Discuss a series of events throughout the cycle to help promoting the Ubuntu Translations project and increase participation in translating Ubuntu.
  • Extend the translations reporting site (DavidPlanella)

    • Continuation of the Lucid blueprint on how to improve how we report translation status for Ubuntu
  • Translation teams outreach (DavidPlanella)

    • A session on an effor to get in touch with all of the translations teams for a health check. Make sure to understand their needs and if they need help in any area. Raise awareness on the new team policies, especially on having information on the team's communication channel on their Launchpad page, along with info on how to join the team.
  • Launchpad Translations Reporting API (DavidPlanella)

    • Discuss the current status and implementation of the Launchpad Translations reporting API, as per the specification Adi is working on.

  • Developer education on localization (DavidPlanella)

  • Universe is translatable in Launchpad (DavidPlanella)

    • Session to assess if it's desirable to make all localized applications from universe also translatable in Launchpad, not only those from the main repository.
    • Previous spec

  • Improve Translations Packaging for Help in Ubuntu Applications (DavidPlanella)

  • Development of a strategy to provide translatable documentation for Ubuntu applications.
  • This will also allow OEM projects to use documentation and its translations from Ubuntu, installed independently from the monolithic ubuntu-docs package.
  • Ideally the translated documentation should be shipped in language packs.
  • Proactive bug detection (GaborKelemen)

    • Discuss the possibilities of proactive bug detection: this would need more and earlier testing of packages for translation problems (lack of i18n infrastructure, untranslatable files/strings, needs-pot-on-build, needs-desktop-entry-i18n...)
    • We also need to devote more manpower to fix bugs in time, and reducing the average lifespan of bugs. Goal: 0 translation bugs at release time Smile :)

  • Fixed schedule for translation updates (GaborKelemen)

    • Predicatable translation updates could help scheduling work
    • Not only language packs, but DDTP, (k)ubuntu-docs, and whatnot too
    • Perhaps we could introduce on-demand updates, so that a language can get an update when it needs it the most
    • "Supported release" should mean not only security fixes, but translation updates too!
  • Creating a localized help.ubuntu.com (GaborKelemen)

    • help.ubuntu.com should detect my browsers locale settings and show the content on my language
    • Asking teams to create localized versions of that site makes no sense: we duplicate the infrastructure and the work to maintain it for nothing.

  • Improving communication with translators

    • (From the Ubuntu Manual Team)

Final list

Deferred

These topics will not been included in the final list of sessions, but can nonetheless be discussed (e.g. in roundtables)


CategoryTranslations

Translations/UDS (last edited 2010-04-30 17:42:14 by 168)