Help the Blender 3D project to set it up for Launchpad

As a member of ~bf-committers, you are a maintainer and have all the power to do this your selves.

A. I don't see anything wrong with the external bug tracker. It is fine to not use Lp Bugs to track bugs.

B. You can register the imports of branches and own them yourselves so that you can mange them without requesting support.
Do you want us to delete https://code.launchpad.net/~vcs-imports/blender/translations ?

C. Project maintainers setup translations because they are organising a community that we are not familiar with.

So,

It seems, that the template file is somehow broken.

Why do we need a template file, and do we need one?

Can't we just use .po files from http://projects.blender.org/scm/viewvc.php/branches/?root=bf-translations ?

POs are translated messages, POTs are the messages that need translation. gettext-based internationalisation uses the POT to lookup a message from the PO file that matches the user's language. So POT are what users translate. POTs are often generated for intl-tools or some other gettext-compatible script by scanning the source code for messages. Maybe someone edited the template file(s) instead of generating them.

Curtis Hovey: It seems the bug tracker does not work correctly.

Why are the translations here somehow outdated?

In the new 2.6x series for translation, I have configured "branches" branch, for the very fresh actual translations, there are about 16,000 strings, we just see the old 6000 ones, from 2.4 series.

Pleas help:https://translations.launchpad.net/blender https://translations.launchpad.net/blender/translations

I see that the project is set to use the external bug tracker you want. The page is correctly telling people to report bug elsewhere. If there is a problem with the upstream bug tracker, you need to contain its administrators.

https://translations.launchpad.net/blender only lists "Blender translations series" (https://translations.launchpad.net/blender/translations/+translations) for translations. It is the only series setup to import/sync translations with a branch: If you want to translate the 2.6x branch, then visit
    https://translations.launchpad.net/blender/2.6x
and choose "Set up branch synchronization"

I thought, you are able to use other bug trackers, with launchpad?

That is incorrect. Only Launchpad' own bug tracker allows you to report bugs and show listings. External bug trackers have two uses: first to tell users where to report bugs to the developer community, secondly, the track might support bug watches.

A bug watch is a link between a bug that affect a project that uses Lp's bug tracker and a remote bug in another tracker that is blocking the fix. Lp will poll the remote bug and update the Lp bug with the status. Ubuntu uses Lp's bug tracker, so it uses bug watches to link bugs in Ubuntu package to bugs in blender's bug tracker. No has created bug watches to track upstream blender bugs yet.

Can you help us, to somehow import the bugs from the blender bug tracker, into the launchpad project, and setup watches properly?

https://help.launchpad.net/FeatureHighlights/BugWatches

seems to tell me that there is such an option, for big projects, or I am wrong?

Why don't we get all 16,000 strings from the SVN repo, that got imported into the vcs bzr branch, in the translations category, here?

How to set this up properly?

It shows, that the last changes are only a few days old, but we had 6000 translations with an other, older series, not the 2.6x series.

Why does it not show the all new strings, 16,000 ? https://translations.launchpad.net/blender/translations

We are willing to import bug for the developers of blender if they want to switch to Launchpad to track bugs. No one should setup an Lp as an alternate bug tracker from the one used by the actual development community. No one benefits from building a separate database of bugs that the principal developers are not looking at.

Bug watches are used by project that are hosted by Lp to follow upstream changes in projects that do not use Lp. Since your project does not produce code, it does not use Lp, it cannot use bug watches. A bug watch is created *after* a bug is reported on a project that uses Lp, Using the "Affects project" link, the user selects "blender" project, then Lp asks for the URL to the bug in blends's bug tracker. All the bugs listed on https://bugs.launchpad.net/ubuntu/+source/blender need review and if the bug is not code, not packaging, they need someone to find the bug in http://projects.blender.org/tracker and enter it in Lp using the "Affects project" link.

Again, if the blender development community is not using Lp for code hosting or merge proposals, there is no benefit to using Lp for code hosting. There are only two uses for branches in this case: 1 to allow distribution packagers to create recipes that build from blender's trunk for distro users, and 2 to allow communities to translate messages.

I think point 2 is what you want to achieve. Since blender is hosted by sourceforge, you can export POs from you work and submit them as a branch to the developers using their rules. When Ubuntu gets the same version of of branch that you translated, it will see the your translations because of the message-sharing feature. Ubuntu us using 2.6.3a and has those messages.

You have not visited "Set up branch synchronization" shown on https://translations.launchpad.net/blender/2.6x . I think you want to choose "Import template files" so that Lp knows you want to translate all POTs in the branch.

Thanks for claryfying many things.

On the posted linked page, I see:

Translations are imported with every update from branch lp:blender.

That is not we want, like I said, we have a seperate branch for that, and we have a seperate series for that.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.