launchpad-dev team mailing list archive

[Danilo Šegan <danilo@xxxxxxxxxxxxx>]

У пет, 16. 07 2010. у 10:33 +0200, Robert Collins пише:
> Hi,
>     search in launchpad is showing up as a common issue affecting
> responsiveness of pages and causing timeouts.
> 
> We currently have two separate search engines, and having discussed
> our search implementation with a couple of arbitrary folks, it seems
> to be the case that we don't have a consistent, cohesive set of
> stories for search.
> 
> I've created https://dev.launchpad.net/LEP/Search as a place to gather
> our users stories for search in a single consolidated place. We need
> this to be able to evaluate how well our search works for us, which is
> a fairly important component in evaluating the result of any work done
> on this performance issue: it would be all too easy to either preserve
> a non-beneficial aspect and hinder our optimisation work, or fail to
> keep an important thing.
> 
> So - please hop into the Search LEP and record your user stories!

I've recorder another 4 for translators (in addition to Jono's one) so
we are now at:

1. As a translator
I want to find other translations to my language of the template
so that I can reuse them.

2. As a translator
I want to find an untranslated (English) text I've seen in the UI
so that I can translate it.

3. As a translator
I want to find a badly translated text (a translation) I've seen in the
UI
so that I can fix the translation.

4. As a translator
I want to find a translation page for one particular program I use
so that I can improve/provide the translation.

5. As a translator
I want to find translations for similar English texts to the translation
I am providing
so that I can better reuse existing work.

At the moment, we provide partial solutions to 1, 2 and 3 (2 and 3
limited to a single POFile, so you've got to know where to search for
the translation first).  We lack the global search of both English and
translated texts in translations, just like we lack 4.

We implement 1 on the +translate page as something we call "external
suggestions" (i.e. it's wider than that: we show all translations for
this identical string across entire LP database). 5 is similar to 1 in
mostly being a helper tool for translators (to reduce duplicate work),
and the most important concept there is "similarity" of the two strings.
FTS-based comparison might be a first approach there, but we'd
ultimately want something much nicer.

In my opinion, 1 and 5 don't really belong among the "search" user
stories, simply because they would be extensions of the translation tool
itself.  Similar considerations apply to them as with 2, 3 and 4, so I
still left them on the page.  All this scrabbling simply because of my
uncertainty about it :)

Cheers,
Danilo