HandlingBugs

Revision 12 as of 2009-12-07 08:44:51

Clear message

THIS IS CURRENTLY A DRAFT

Triaging

Priority assignment

Tagging

When we have defined the required tags we should move them to https://wiki.ubuntu.com/Bugs/Tags

task

This tag can be use for any bug that requires a discussion or decisional action.

It can also be used as todo items for UTC members and to keep track of the current action inside the team.

import

This can can be used for any bug that is triggered or affects the Ubuntu Translation import queue.

This is valid for both PO and POT files and in general for any problem regarding the import of translation into Launchpad Translations for Ubuntu

This can be used for reviewing the import problems and as feedback for Rosetta devs

input-method

Any problem regarding the way character are entered.

Another terminology relevant is IME, which refers to Input Method Editor.

Examples: ibus, scim, deadkeys, keyboard layouts.

fonts

Maybe we can find a better name.

The idea is to tag all bugs affecting the way characters are displayed.

Examples: ttf-wqy-zenhei, ttf-dejavu, xfonts-base, xfonts-wqy

needs-pot-on-build

Tag for packages in main but don't generate a pot file during build.

More information can be found at Internationalization Guide for Developers.

needs-desktop-entry-i18n

Used for .desktop entries which require internationalisation

needs-lp-integration

For all packages that need to implement Launchpad integration in their help menu.

kubuntu

For all Kubuntu-related translation bugs.

ubuntu-unr

For all UNR (Ubuntu Netbook Remix) related bugs

  • Note at the Lucid UDS a change of name was discussed. The product will now be called UNE (Ubuntu Netbook Edition), so we should updated this tag accordingly -- dpm 2009-11-24 14:22:36

i18n

For all internationalisation-related bugs.

  • Since most of the bugs seem to fall undeer this category anyway, it might be worth dropping this tag. If we want to separate the technical translation bugs from the purely translation-related ones, we can still do this using the l10n tag. -- dpm 2009-11-24 14:22:36

l10n

For all localisation-related bugs. Usually these are spelling mistakes or bad translations.

needs-locale

This tag is used to track locales that needed to be created when a person is willing to help to have it set up.

For detailed work needed when adding a new language, refer to Adding New Language.

  • After talking to Aron, we agreed that needs-locale is a better chice than locales - the current tags should be updated accordingly -- dpm 2009-11-24 14:29:35

Other bug contacts

If an issue is CJK-related, please also subscribe the Ubuntu CJK Testers if they aren't shown at the "Also notified" list. This team was set up for solving CJK related issues with many relevant developers in it.

The major fields of CJK related issues are fonts and input-method.

Arabic

Persian

...

Boilerplate e-mails

<package> needs to generate a POT translation template on build

<package> needs to create a translation template during the build process, so it can be uploaded to Launchpad Translations and translators can do their work.

For more information, see:

 * https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation#Translation%20templates
 * https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation#Verifying%20translation%20uploads
 * https://wiki.ubuntu.com/Translations/TranslationLifecycle

Brainstorming

  • I am wondering if we need a tag for kubuntu, since they are to launch Project Timelord but still don't have a clear clue on what they are going to do with i18n/l10n issues. -- happyaron

    • Until they have made a decision whether to use Launchpad or not for bug reporting, I'd keep the kubuntu tag. -- dpm 2009-11-24 14:01:36

  • Comments from Qense, from the BugSquad:

I suggest to make the process of reporting more clear by implementing the following changes:

  1. The starting point of all translation bugs -- unless you know better already -- can still be the source package of the affected application.
  2. No extra tasks for bugs in upstream translations, this only adds extra clutter to the overview, generates extra mail noise and generates more work and confusion.
  3. Bugs in translations done at Launchpad should be reported against ubuntu-translations and keep the source package task, because: 4. The source package task is for maintaining the status of the bug concerning the system -- i.e. if the bug has been Triaged(=reported properly upstream or at ubuntu-translations) or if the Fix is Released -- the ubuntu-translations task should be for the status of the fix in Rosetta or the team only 1b. This means that translation bugs always need to be 'forwarded upstream', be it to real upstreams or to ubuntu-translations. This is what the triagers should focus on when triaging these bugs.
  4. Responsible for setting the status in ubuntu-translations are their (appointed?) members, responsible for the source package task is Bug Control (and the Bugsquad). Some members of ubuntu-translations that are very active on Launchpad/Malone could be granted membership of Ubuntu Bugcontrol -- if they don't already are a member -- to make it easier for them to manage the source package tasks.
  5. Use the Triaged status for the source package when the Bugsquad doesn't need to do any work on it anymore!

These points don't add a lot of new stuff, but things would be a bit clearer if both teams would agree on them and integrate them into the documentation.