Hi,

Andre Schnabel wrote:
Hi Martin, *

Martin Hollmichel schrieb:

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,


so a possible workflow might be:
- create / assign a non-english issue within the native lang project
- have a dedicated native lang qa member, that cares about such issues an gathers all informations that are necessary to confirm the issue - if the issue could be confirmed, a *new* issue would be filed by the qa member in english language, the non-english issue should be closed (e.g. as duplicate to the english one). - translating qa member and initial poster need to be cc'ed to the english issue, to provide further feedback

Anyway .. people within the native lang community should be aware, that this is a lot of work to do .. and that's the main reason, why we haven't established this workflow as a general rule yet.

Regarding the comment by hi ("Issues which is not written in english, will be closed as invalid!"): this is no general rule as well. But this could be dervied from the rule, that issues, that are not reproducable and user do not give more information on request, would be closed as invalid after a given time.

In a case like this it is also possible to reassign the issue to a person from that native lang project with the question: Please close this issue OR if it needs attention from development please file a new issue in English.

--
Regards,
Arthur

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to