I'm still confused with some features of Launchpad

Tue Mar 20 10:08:20 GMT 2007

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Séverin Lemaignan escribió:
> [all the links below relate to the Beta version of Launchpad. Please
> remove the "beta" for those who aren't in the beta team.]

Hi

> 
> I'm trying to figure out how to set up a new translation for Blender.
> 
> I go on the project page, here
> https://beta.launchpad.net/blender
> 
> If I click on Translations, I get what I expect, very fine.
> https://translations.beta.launchpad.net/blender/+translations
> I can translate.
> 
> But what am I translating, here ? which branch, which release ?

If you read the header of that table you can read:

'Template "blender" in Ubuntu Breezy package "blender"'

So it's a translation of Breezy's template.

That's something we are fixing right now, as Breezy is a bit old and
should appear there.

> 
> Now, if I go to the main branch, bf-blender, here
> https://beta.launchpad.net/blender/bf-blender
> 
> and I click again on "Translation", Rosetta says "no template available".

That's because no one followed the procedure to import Blender directly
from upstream.

> 
> I set up a new release, 2.43, in the branch.
> https://beta.launchpad.net/blender/bf-blender/2.43
> 
> One more time, I click on "Translation", and predictably no template is
> available.
> 
> I don't exactly get the purpose of the release page since I can't
> specify any specific CVS/SVN repos or specific translation template for
> this release.

Right, we don't yet support that kind of import, but you have there, on
the actions item an entry named: 'Upload translations' which will allow
to submit a tarball with .pot and .po files.

Anyway, you should read first
https://help.launchpad.net/RosettaImportPolicy before requesting any new
upload.

> 
> And it becomes trickier when we introduce the linkage with the actual
> Ubuntu package.
> 
> On this page,
> https://beta.launchpad.net/blender/bf-blender/+ubuntupkg
> I've an array of "Ubuntu release" -> "Blender package" (actually, always
> the same).
> If I go on the page of the "Blender package in Ubuntu Feisty" here
> https://beta.launchpad.net/ubuntu/feisty/+source/blender
> 
> I see that blender 2.43 is available in the distro. But I see no obvious
> way to link this page to the matching release page of Blender
> https://beta.launchpad.net/blender/bf-blender/2.43

That's because those are two different context. launchpad.net/blender is
for product specific translations used directly by its developers. The
Ubuntu ones are related but not really dependent of blender developers
handling its updates. Also, a product releases are not able to have
translations directly, you use product series for that task (it makes no
sense to have a template for each single release, but for the branch (or
product series) from where you do all those releases.

> 
> And if I click on "Translation" from the "Blender package in Ubuntu
> Feisty" page, I get no result.

That's due a limitation in Ubuntu side, we only import packages that are
in main. Blender was in main for Dapper and Breezy so we have it
imported there, but with Edgy, it was moved to Universe.

> 
> So, to summarize, I think:
> * the "Translation" link (as well as "Bug", "Code"...) should not appear
> when it's not appropriate (for instance on the "Blender package in
> Ubuntu Feisty" page), or possibly link to the right page to translate
> the package.

Well, in the Ubuntu pages, we inform that there is no way to translate
that package where you want to. Which IMHO is the right thing to do.
Sometimes, our automatic system fails and that gives some direction to
the users on the way to notify about that problem.

For the product pages, yes, we are going to improve the translations
pages to make it a bit more clear.

> * too much page for the same package: for instance, if I discover a bug
> in Blender 2.43 on Feisty, where should I report it ? At least, I miss
> some documentation.

Well, if you go here:

https://bugs.launchpad.net/blender/+filebug

you can see that Blender is not using launchpad to track their bugs, so
it's clear you cannot file bugs about 2.43 release.

Another thing is when you are using Ubuntu as your distribution, in
which case, you file a bug against Ubuntu. Just like other distributions
have their bug trackers to be a gateway between the users and the
developers of a concrete part of the distribution to filter too bugs
related to the way that software is integrated, in this case, with Ubuntu.

Anyway, we will be happy to know how would be your ideal way to improve
it. If it makes sense, I'm sure it will be implemented.

> * It should be more obvious that when you're on this page for instance
> (the bf-blender branch):
> https://beta.launchpad.net/blender/bf-blender/
> you're still in the Blender Project "sub-pages". Maybe a "tree-widget"
> to represent all the sub-pages of a project could be useful.

I will leave this one for Matthew, our UI guru.

> 
> 
> 2 last small things:
> * on the main page of the Blender project
> https://beta.launchpad.net/blender/
> the "status" box says "Doesn't use translation" which is false.

No, it's not false, Blender project is not using Rosetta at all, Ubuntu,
though, is.

I think you are mixing two different things. One thing is Blender as a
project and another thing is Ubuntu, which has a concrete version of
Blender.

> 
> * is it possible to change the icon at the left of the project name ?

Yes, the one who registered Blender, https://launchpad.net/~urreta
should do it.

> 
> 
> ...I hope my english was not too painful to read :)

No problem at all.

> 
> Thanks everybody for the nice work on the Launchpad beta,

Thank you.

Cheers.
> 
> "Bises" from France,
> Séverin

- --
Carlos Perelló Marín
Ubuntu => http://www.ubuntu.com
mailto:carlos.perello at canonical.com
http://carlos.pemas.net
Alicante - Spain
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF/7KTEuPMamD5V9cRAs04AJ4w37+S2u7oLtTDjwrENy+6MkYAIQCfeBF4
X71BeQV5oQmAOCyj/MT0C5A=
=lObo
-----END PGP SIGNATURE-----