Hi Joost,
Thank you for your comments.
I do not stick on using the issue tracker, but opening the door
of the issue tracker to the local contributors definitely attract
them to participate in the world wide project, OpenOffice.org.
Current, biggest problem with ja native language project is that
they have been suffering from low quality and low usability from
local users' perspective of view.
Tremendous amount of requests and lots of suspicious phenomena
have been posted and discussed in the local mailing lists and/or
local BBS, but they are not under managed, most of them have not
been reported to the developers, and just left as a fragment of
information here and there.
What do you think of the fact? That can be considered a loss of
wealth. I guess many local projects spread in the world have
similar concerns. Why don't we have a common tool that can be
shared and cooperated with the world wide native language projects
to give a light on such efforts. One of practical systems could
be the issue tracker.
Again, i would not stick on the issue tracker if the projects
had an effective system to manage fragments of information and
to accelerate improvement in quality of OOo from local users'
point of view.
Having two issues for one problem raises a problem which I don't like to
have within IssueTracker:
-> statistical work isn't possible anymore
Definitely, you are right!
How about using a type 'Task' instead of 'Defect' ?
Does the statistics include 'Task' that concurrently exists
in the issue tracker?
-> who cares about closing the issues in native language if the other
issue has been fixed ?
The submitter, who knows what is happening with the problematic
software and how the software should work, will confirm the fix
with a subsequent official/developer build released by RE from
Hamburg and will close the article that he/she submitted.
All local members can be automatically notified via e-mail that
the fix has been made because the first article is connected to
the real issue with a field either 'Depends on' or 'Blocks.'
-> a target milestone can only be set for one of the issues (because the
developer does only understand the issue in 'common' language.
That would not be a matter if local contributers chose a type 'Task'
assigned to them.
Kind Regards, Tora
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
