Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Rimas,
On 17/02/2011 16:17, Rimas Kudelis wrote:

2011.02.17 14:47, Sophie Gautier rašė:
So as indicated on the steering discuss list, we have settled a
staging Litmus site at This site will
handle all our QA tests and may be even VCLTesttool results in the
future. We should be able to use it to handle beta, RC, l10nQA and
nightly builds testing.

That would be nice. One thing to note though: Mozilla's guys told me
Litmus is no longer being developed (except bugfixes). They're
developing a replacement for it at the moment, so Litmus is apparently
pretty much in a dead-end. We'd have to maintain it ourselves.

Ok, so may be it would be good to follow what they are doing. Are you in contact with them? I can also follow up if you prefer.

We need to adapt the tool to our needs, even if I see that some work
has already been done (Rimas, is it you? :-) and define together what
still needs to be done and if it's possible (like opening the creation
of TCS to more members for example). We need also to document the tool
ant the process on the wiki, add the native-language QA members in the
loop, etc...

Well, if you mean the minimalistic style adaptation (s/mozilla/libo/g
:)), then yes, that's me. ;)

thanks :)

The test cases aren't mine.
First of all, what still needs to be done is undef errors fixed. :) I
have a few more ideas for afterwards though:
1) the build id field and checks should be adapted for our use. It looks
like Jean-Baptiste has already come up with a workaround for this, but
it should be fixed instead of worked around.
2) testcase localization implemented correctly. I absolutely dislike the
way it's done now. To the extent that I want to revoke admin rights from
everyone but me. :)
3) platform/language autodetection (it looks like the criteria fields
are there, but they aren't being used)

However, I'm a total newbie in Perl programming, and I'm not very good
with my schedule, so any help is more than appreciated. :)

yes, this is why I posted here, to get more people working on adaptation. And Nino in CC proposed himself also.

Who would like to work on this? May be this should be also the good
moment to open the native-language mailing list and move on it with
the QA teams of the native-lang communities?

I think what we're discussing here is an infrastructure thing first of
all. Yes, the NL teams will be the primary users of this particular
tool, but I tend to think that its *usage* can be discussed on the L10n
list, while the process of setting it up and implementing features that
we need is only relevant to the NL as much as to any other team.

I don't know if LibO has a services/infrastructure team, but I think
that its list would be the correct place to discuss this (or just a
bunch of CC'ed people). Meanwhile, all that we probably need from the
website team for this particular project is to create templates/css
styles. Or am I wrong?

No, but more people from the NL teams should be able and wanting to help here, my issue is that currently, apart from mailing their representatives directly and keep the discussion off list, it's not really easy. I face the same issue with the PR distribution, I can mail people directly, but I would really prefer to do it on a list.
Kind regards
Founding member of The Document Foundation

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.