[UbuntuWomen] Ubuntu-Women team on Launchpad

[vid]

Hi All,

On 3/30/06, Matthew Paul Thomas <mpt at canonical.com> wrote:
>
> Hi everyone, I'm Matthew, and I'll be your friendly local Launchpad
> developer. :-)

:-) <waves a hello>


> First, in Launchpad, a "project" doesn't mean what you think it means.
> Launchpad uses the term "project" to refer to a group of products, so

thanks, figured that eventually..... but I was unsure if I was
thinking right, as I see many teams being created but cant find a
co-relation between both. Its even more confusing when all the
upstream Debian work get's accounted for in LP but there is no way of
knowing ...who, what, where, when, how ...if you know what I mean.



> they can share the same bug tracker and translation group (a
> "translation group" being a set of translation teams). Mozilla, Gnome,
> KDE, and Apache are projects, because they produce many related
> software products. But Ubuntu Women? Not really. :-)

Ok, so LP is basically used to track upstream work easily in
Ubuntu.... Fine so far, but .... Unlike Debian, Rosetta does not say
which package/product should be translated first. It just lists them
in alphabetical order and that is confusing. In the NLP of Debian they
have an order of translation for packages. Where can I find this
information in LP/Rosetta ? Personally speaking a lot of time is
wasted in  learning and figuring out different methods/systems
followed by different distros and common processes would help us
greatly.  On a side note there is a  Debian-i18n meeting[0] in Spain
and it would really help and make things easier if Rosetta developers
could be there to find common ground between Ubuntu and Debian.
Christian Perrier is the Debian contact for those wishing to attend.

Can Malone have an automated feature programmed to compare each bug
(after it has been filed) for similar keywords/strings. Sometimes
people filing the bug provide this info, while some dont. Matching bug
numbers could be displayed on LP to allow a volunteer-bug-squasher to
compare if it is indeed a duplicate bug and decide further action on
case-to-case basis. This feature will help compare duplicate bugs
filed by oversight and filter them making it easier to track duplicate
bugs filed.
Disclaimer : Its a suggestion only, as I am not a developer so dont
flame me for not coding it myself.


[0] http://wiki.debian.org/WorkSessionExtremadura2006i18n


> Second, if you're organizing people to translate Ubuntu wiki pages, I
> don't think Launchpad can help you, really. The Ubuntu wiki is a wiki,

Hmm... we are in the process of moving/building UW from a wiki-page to
something more concrete but the ubuntu-wiki will be retained so people
can easily contribute and collaborate as before.


> That's because you haven't registered any products to translate. If
> you're going to make books or leaflets or something that can be
> converted into .po files for translation, you can register those as
> products in Launchpad, and translate them from there (the Ubuntu
> Documentation Team is going to be doing this, for example). But if
> you're just going to translate wiki pages, you don't need Rosetta for
> that.

... so translating via UW does nothing for your karma[1] so to speak
... too bad :-(  Clytie, if I understand correctly, it means
translating Ubuntu-wiki pages cannot be accounted in the LP system
unless it is registered as a product for which it has to be available
as a complete package and not single wiki pages (as it currently is). 
I do hope I am making some sense :-) with all this.

[1] https://wiki.launchpad.canonical.com/KarmaCalculation


> Personally, I regard every entry in the Launchpad FAQ as a bug waiting
> to be fixed. It should be obvious in Launchpad itself how to do things,
> without going to a FAQ! Here the main problems were that (1) Rosetta
> doesn't explain well enough what sort of things you can translate with
> it, and (2) Launchpad doesn't explain projects well enough. I've just
> fixed part of the first problem (the fix should appear on launchpad.net
> sometime in the next week), and I'll get to work fixing the rest now.

Hmm.... how about a different terminology to help reduce our
confusion. Maybe we define the word "project", "product" differently
as opposed to what it actually means in LP. Its just that people think
differently all the time so some FAQ's just defining these will be
nicer :-)

Thanks again,

Vid