I don't have a well defined opinion on adding new language. However, one thing that I'd like to bring up to the attention on that occasion is it is already quite cumbersome to update two versions of the docs. Especially when we add new sections or change smaller parts of an existing document. Right now if I add three sections in an English version I have three additional places in the Chinese documents where I need to paste that. With additional language it doubles, making it 6 places where I have to manually paste the added parts.
I'd be way more welcoming for adding a new language if we had a better tooling/process for synchronizing changes across different languages. Or if we agree the translations are best effort documents and we do not update them when changing the English documents. Best, Dawid On 08/06/2020 09:44, Robert Metzger wrote: > Hi all, > > we've received a pull request on flink-web.git for adding a Japanese > translation of the Flink website: > https://github.com/apache/flink-web/pull/346 > > Before we accept this PR, I believe we should have a discussion about it. > > *Relevance*: Looking at Google analytics, our users are coming from China > (1.), US (2.), India (3.), Germany (4.), Japan (5.). > I'd say that is high enough to consider a Japanese translation. > > *Reviewing*: I'm not aware of any committer who speaks Japanese. How would > we review this? > The contributor is offering to open follow-up pull requests, which I > believe is fine to bootstrap. Ideally we'll be able to attract more > contributors over time. > > In my opinion, if we find one or two reviewers, I would give this a try. > > What do you think? > > Best, > Robert >
signature.asc
Description: OpenPGP digital signature
