Hi Pavel,
Your proposal appears to be a response to two problems:
1. ft leaving OOo
2. the increase in translation related issues as a result of more
thorough translation efforts
It seems appropriate to me. We (he project) do have one request. The BIDI
category allows us to differentiate issues that specifically affect us
from more general UI issues. Therefore we would ask that when you merge
the BIDI category into the UI category you add BIDI as a keyword to each
of these issues so that we can still query them separately.
- yba
On Fri, 3 Mar 2006, Pavel Janík wrote:
Hi,
during my visit in Hamburg at the beginning of this week and even before,
we (Eike and me) discussed the current status of l10n issues handling in
IssueZilla. Current status in IssueZilla is as follows.
We have five subcomponents:
BIDI Bi-directional writing. Covers other areas like RTL, printing of
mixed language text, too.
Default owner: ft
Issue count: 243
code Use this component if you are able to reference a piece of source
code, in which the issue occurs. Patches are highly
appreciated. This component is mainly meant for issue reporters
with developer skills.
Default owner: ft
Issue count: 864
helpcontent Online Help issues
Default owner: iano
Issue count: 419
ui Use this component if you are not able to reference a piece of source
code, in which the issue occurs.
Default owner: sba
Issue count: 985
www Web publishing module
Default owner: ft
Issue count: 81
So this is the current status. ft is the default owner for three
subcomponents but he is no longer available for OOo work. This means we
have to re-work the subcomponents.
The incoming flood of issues contains several common types of issues:
1. help content translation related issues
The current owner of such issues is iano. Such issues should contain
"[XY]" at the beginning of summary, where XY is the ISO code of the
language. Good example is #i58507# ([DE]: Errors in "Symbole bearbeiten"
in German Math help).
If the language is not so-called Sun language, iano will reassign to the
person responsible for that language (see
http://l10n.openoffice.org/languages.html for more information).
iano: is this OK for you?
2. translation related issues (with the exception of help)
The same as above, but UI only related translations. We plan to *add*
this component.
iano: is this OK for you?
3. new localedata subcomponent
Locale data are worth its own component. The default owner will be Eike
Rathke (er).
4. unify BIDI and UI to UI
UI related issues not related to translation. The current owner of UI
issues is sba, BIDI issues are owned by ft. As all of these issues are
almost always bugs in VCL and friend modules, we would like to ask for
the current owner for the future UI component.
5. code and www components will stay
I'll take www component and we are looking for someone who will take
care about code component. Any volunteers?
What do you think about the proposal in general?
--
EE 77 7F 30 4A 64 2E C5 83 5F E7 49 A6 82 29 BA ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [EMAIL PROTECTED] - tel: +972.2.679.5364, http://www.tkos.co.il -
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
