Hi Alexandro,
as long as the component of an issue corresponds to the native-lang
project and the issue is assigned to a member of the project able to
speak this language, such issue are fine with me,
but as soon as such issues get reassigned to somebody else this doesn't
make sense anymore, since the new owner is not able to read all the
content of that issue. As soon as an issue gets reassigned to an
international member a new issue has to be filed with all relevant
information translated to English. And I don't like to see issue with
mixed languages in it. It does not make sense to expect that a developer
or qa person will work on issue which content is not understandable by him,
Martin
Alexandro Colorado wrote:
Hi, today I discover a mayor barrier for the native-lang projects,
since we are triying to be compliant by not attaching files to the
mails we need to use other methods to solve user issues. Like
issuezilla however I discover this post:
"" ------- Additional comments from hi Wed Sep 7 00:48:47 -0700 2005
-------
Issues which is not written in english, will be closed as invalid! ""
This is a major step backward in the globalization of the page. I was
kind of socked and I want to report a better explanation/re-negotiation
of this policy.
As commented on the NLC meeting, language is a mayor barrier to report
bugs, and the interface should be localized. However not even being
able to comment on issues on non-english language make this almost a
deliverable action to block native-lang triying to solve actual
problems from their user base.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
