#72 Legal implications of out-of-sync Wiki
Opened 3 months ago by crameleon. Modified 3 months ago

TRANSFERRED from https://progress.opensuse.org/issues/127064, reported by @crameleon:

As we know, the non-English Wiki's are severely outdated and not in sync.
Besides this impacting the user experience of users preferring to read help articles in different languages, we should consider the legal aspect of the Impress and Terms of Service pages serving conflicting information (for example, some Wiki's still reference the Novell privacy policy).

Comment https://progress.opensuse.org/issues/127064#note-1 by @crameleon:

Just an idea - if we do not want to ditch the language-specific Wiki's anytime soon, maybe we should at least redirect legally relevant pages to a central place?

Comment https://progress.opensuse.org/issues/127064#note-2 by @pjessen:

If a wiki in is not being updated, maybe we ought to add some "disclaimer" of "apparently not being actively maintained". For important pages with legal information, I expect there will be a note indicating that it is a "translation only, please refer to the original in English". 

Comment https://progress.opensuse.org/issues/127064#note-3 by @simotek:

crameleon wrote:

> Just an idea - if we do not want to ditch the language-specific Wiki's anytime soon, maybe we should at least redirect legally relevant pages to a central place?

This is probably safest, with respect to every Legal / Translation issue i've ever seen the policy has been don't translate unless its going to be approved by a Lawyer who speaks the native language. So just forcing them all to use a central English page for licensing probably makes sense, if people really care they can put it in google translate to get an approximate translation in there language

Comment https://progress.opensuse.org/issues/127064#note-4 by @avicenzi:

simotek wrote:

    crameleon wrote:

>        Just an idea - if we do not want to ditch the language-specific Wiki's anytime soon, maybe we should at least redirect legally relevant pages to a central place?

>>    This is probably safest, with respect to every Legal / Translation issue i've ever seen the policy has been don't translate unless its going to be approved by a Lawyer who speaks the native language. So just forcing them all to use a central English page for licensing probably makes sense, if people really care they can put it in google translate to get an approximate translation in there language

This is the best for any legal-related topic. Translations can be misleading and need legal review, and what may be allowed by law in US/EU, might not be allowed in South America. Brazil, for example, has its own GDPR laws called LGPD (https://www.gov.br/cidadania/pt-br/acesso-a-informacao/lgpd). If you offer services or collect data from users in Brazil, you MUST follow LGDP, even if you are not based in Brazil.

Comment https://progress.opensuse.org/issues/127064#note-5 by @pjessen:

simotek wrote:

>    This is probably safest, with respect to every Legal / Translation issue i've ever seen the policy has been don't translate unless its going to be approved by a Lawyer who speaks the native language.

Hmm, I usually see a disclaimer that a text was translated from the original in whatever-language, which will take precedence in case of discrepancies. Maybe it is worth conferring with legal. I don't like the idea of a redirect.

Login to comment on this ticket.

Metadata