Hi Sophie,
may be I can add here some information on the localization day...
The agenda for Friday, February 2nd was on the following topics:
+ Globalization - presentation - Rafaella (30 minutes)
+ QA matrix - live demo - Monica (30 minutes)
+ Documentation - open discussion - Uwe Fischer (1 hour)
+ StarOffice localization process - release engineering
- Joerg Jahnke, Ivo Hinkelmann (1 hour)
+ Open Translation Website - Brigitte Le Grand (30 minutes)
+ Help review project - Plus and Deltas - Next steps -
Berit, Sven, Rafaella (1 hour)
It has been a long day but it has definitively be very positive for all
of us :-) .
Regarding the German Help review project in particular the Community
has followed the instructions as posted some time ago on the [EMAIL PROTECTED]
list (see posting on L10n Help Testing / Linguistic Review). This gives
you the possibility of checking all Help files following the hierarchic
structure.
Let me know if you have more questions.
Rafaella
Sophie Gautier wrote On 02/13/06 14:55,:
Hi André, all,
Andre Schnabel wrote:
Hi all,
last week I was able to spend two days in Hamburg, to meet some
people of the Sun (qa and localisation) team and discuss several
topics. As Jacqueline Rahemipour (Co-Lead at the germanophone
project, coordinatin a review of the german help files within the
recent months) has also been there, we had two days full of
discussions with focus on qa and the localization quality and
process. ( But localization process for German is a real special one).
Oh, great !!
First of all, I like to thank Joost Andrae for inviting me and
organizing the meetings. And of course thanks to all the people who
had time for the meetings. The atmosphere was positive and
constructive.
I can imagine :)
The first day was focused on QA. We had a long meeting with Thorsten
Ziehm (Manager of StarOffice QA) and after that a short "get to know
each other" with some members of the Sun QA team.
My impression after all is, that we (community and Sun QA) have
different focuses and slightly different processes and styles of
working. But this is not that bad and can be used to get the overall
work done. But we nee to know better how we work :-)
You're right and I'm sure that this meeting will improve our work flow.
Some numbers presented by Thorsten have been interesting for that.
So, during 1.x codeline most of the issues (87%) have been reported
by Sun. For 2.0 codeline mayority of the issues (75%) has been
reported by the community. At the moment, the rate of CWS approvals
by the community is low, but we hopefully can improove that as well.
I don't understand what do you mean by approvals, you mean QA
responsible for cws ?
The work of the comunity with "filtering" and confirming issues is
welcomed and of increasing quality.
Bravo for the qa team !
Ok .. here are some of the ToDo's we've discussed (some of them are
long-term, for the short term topic's I'll come up with separate
mails at [EMAIL PROTECTED]):
- Community should be more deeply involved in feature testing. We
thought of providing dedicated builds for testing after feature
freeze, and test cases for features (some of theses test cases
already exist but need to be reviewed before beeing published)
/me think I have to finish to fill the Base test case
BTW, is the test case template you've made, approved ? Can I use it
for the Base test ?
- more CWS testing by community. We need to "promote" and document
this better. So more CWS could be proved by community
Yes, please, documentation because I quiet don't see what it is about.
Or does it mean integrating cws in testers distro ?
- make more information available for community (e.g. Sun has some
tools that collect and integrate informations form several places.
Thoses tools cannot be opened completely, but we hope some of the
most relevant information can be pushed to IssueZilla)
That would be great, it really takes a lot of efforts to collect infos
from specs, cws, features list, IZ, etc.
- See, how community can be more active in feature planning (not only
a QA issue and often discussed .. I hope, we can improve this .. help
and knowledge from francophoe community is welcome ;-) )
We are there :) Well, currently, Graph module is our first try ;) Once
finished (I'll try to publish a new version of the document this week
with more informations integrated by Tony), if we agree on it, the
process could be analyzed, documented and replicated for other features.
- collect wishes for TCM and see how they could be implemented (I've
opened a wiki page for that:
http://wiki.services.openoffice.org/wiki/TCM_wishes)
Imho, this is an urgent task because for the moment, we need to use 2
different ways to qa'ed our versions (it's confusing for our testers)
and it duplicates part of the work.
- activate community to review / verify and close fixed bugs
You mean this is not done currently for closed/fixed bugs ?
I cut your interesting part about OLH to jump at the end,
[...]
During the review, english help and UI have also been checked (but
not that detailed). Most of the issues only affected german
localization but not the English base.
Could you or Jacqueline describe us how did you do to review the pages
? I'm interested by the process you used.
Thanks a lot for your feedback and your work.
Kind regards
Sophie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
