There are so many proposals entitled: Stack Overflow (in language x).

My question is - are these proposals actually viable?

For example, if these sites reach beta, will the SE team implement a completely separate site for them?

e.g. http://stackoverflow.fr (for french), http://stackoverflow.de (for german).

Or will they have a similar take to this question. - For example, if you post a question with the german filter on (de.stackoverflow.com) - metadata is added to that question to say that it is in german, and then that question will only appear on de.stackoverflow.com - but all the sites use the same users and everything else as stackoverflow.com?

If these sites are going to be implemented, how will they be implemented?

link
2  
I also wonder the answer for your last question a lot. You didn't mention it in the question but I think you separate the other non-English sites from the scope of the question and consider only the code-related proposals. Because it is OK to have non-English sites as discussed in meta.stackoverflow.com/questions/52331/… and discuss.area51.stackexchange.com/questions/2571/… – petrichor Jan 7 at 13:42
1  
@İsmailArı so I should rename the quesiton "How will non-english sites be implemented"? – Alex Coplan Jan 7 at 13:52
1  
I think the name is nice. I just wanted to add the links to the related discussions. I don't know any non-English site launched by SX Inc and I really wonder what they think about the format and the process. – petrichor Jan 7 at 17:27
2  
@İsmailArı German Language and Usage is in public beta phase. – kiamlaluno Jan 10 at 2:39
@kiamlaluno Thanks, I didn't know that. It seems to be a good example for bilingual SX site. – petrichor Jan 10 at 10:05
It will be viable when: 1-) They make it possible to translate the user interface of the localized version of Stack Overflow and 2-) When they ease on the requirements for getting a proposal to beta stage. Currently it is nearly impossible to get a localized version of any StackExchange site because you can't gather enough people with the required reputation - They have no reputation (and most likely will never earn any) because they don't participate on SO and that is because THEY CAN'T UNDERSTAND ENGLISH, which is why all of these proposals were created in the first place. – Caio Proiete Jan 22 at 18:38
I'm sure there are foreign language programming languages, but I really hope anyone programming in any major language would be more than capable of navigating the basic nav structure of stack overflow. Programming is so English-centric (and I find it hard to call that a bad thing, since it fosters communication!) I doubt any non-English version would be particularly helpful, it would just segregate other language programmers away from the good answerers on SO. – Ben Brocka Feb 26 at 17:48
feedback

4 Answers

up vote 30 down vote accepted

First of all, English is not my native language and I'm not a big fan of using it. Even given that I'd say those proposals are doomed - they have no chance of creating a site as useful as original StackOverflow.

There're two reasons why I think so. The first reason is: if the site is not in English you lose most of the current top users. The second reason is those site will dilute effort. I speak English and Russian - I would now have to participate in two sites and answer the same questions twice.

And finally it is not really necessary, because currently you can't be a qualified developer unless you can write and read in English at at least some intermediate level - it is just impossible, because most of the blogs, documentation and new books are in English.

This is why I firmly believe that currently StackOverflow in any language except English is destined to languish in poverty - it will have little traffic and be mostly useless.

link
3  
Actually I agree with you in most points, but you probably not consider that some languages are spread far enough to build a solid base of documents(blogs,tutorials,..). For example there is a german version of the Microsoft Developer Network, so someone from a german speaking region can actually become a developer without knowing much more english than the coding languages english keywords. – SwissCoder Feb 11 at 15:50
3  
@SwissCoder: I can't evaluate the German version of MSDN, but I've seen the Russian one and it's horrible - the translations are done formally and are often just misleading so I'm much better off just reading the English version than try to deduce what the translator meant. – sharptooth Feb 17 at 7:48
No, at the german MSDN site, they don't do that. Sure some resources get translated automatically, which are not realy readable many times. The difference is, they do let people translate many pages. And they even have German people writing own articles about the technologies, so you get good resources there. – SwissCoder Feb 17 at 16:24
4  
Very true, if you don't know English, you can't be a software developer. Period. – markus Feb 26 at 23:49
feedback

They're as viable as any other proposal in Area 51, and just like any other Area 51 proposal, if the proposal has sufficient support from a community, it will get created.

It's a bit premature to discuss the specifics of a hypothetical site, but the thinking right now is that language-specific sites will NOT be created as a filtered version of — in this case — Stack Overflow. They will be created as independent communities with their own subdomain, their own users, their own tags, their own meta, their own moderators — in short, their own community with their own norms.

Beyond that, the actual implementation details will be for the dev team to decide as they work out the localization issues.

link
Did you intentionally use "subdomain" here? i.e, you're intending to create programmation.stackexchange.com rather than stackoverflow.fr as the OP specified? – Kevin Vermeer Jan 9 at 20:38
@Kevin Yes, "subdomain" is intentional. Currently sites are named as subject.stackexchange.com. Sites do not receive their own domain name but typically are a subdomain under "stackexchange.com." There are no immediate plans to follow a different naming convention for international sites. But that can all change, once a site is launched. It's still a bit too soon to speculate definitively. – Robert Cartaino Jan 9 at 23:52
1  
@RobertCartaino instead of allowing Secession to happen, what about user-improvable translations of SO? – Tobias Kienzler Jan 11 at 12:05
feedback

I believe that country and/or language specific sites are indeed viable, not as much because of contents (I agree English is the lingua franca of software development, and refusing to learn it is stupid) but mainly because of culture.

A community is defined not only be its objective properties (ex. what subjects are on/off topic) but by subjective ones as well (ex. how strictly you have to stay on topic, how much duplicate questions are tolatetad, how personal/impersonal the questions can be, etc). Two or more groups of people may have similar goals (ex. develop software) but wildly different means of collaborating with each other to seek those goals.

I believe this Wikipedia article about Low Context Culture vs High Context Culture might be relevant to illustrate my point. Certain behaviors that feel "natural" for a high context individual can be seen as "annoying" or "disruptive" by a low context one. Conversely, normal behaviors by the latter are seen as "cold" and "unhelpful" by the former. A site with similar objectives but different culture may cater more to large niches of people who otherwise would have trouble "fitting in" a different one.

At last, I'd like to point out that just because someone has knowledge of a foreign language it doesn't mean s/he has the fluency and vocabulary to be productive in that language: I often find myself wanting to know about a subject, and while I know precisely the concept I'm interested on I can't translate it to the right English words to google it. Trying to ask other people is equally clumsy, and when I'm finally able to explain myself the retort is usually like: "oh, so you mean X?" ...and I realize that searching for X would have given me what I wanted in the first hit. This situation is embarassing for me, wastes other people's time, and is much more prevalent than a native English speaker might think it'd be.

link
feedback

There are many questions that are country specific, like the calculations of taxes amount, and implementations of business rules modeled on the laws of a country. As computer programs often solve specific questions, it would be a good thing to have localized sites.

A good partition of questions could be:

  • Technical questions go to English Stack Overflow
  • Questions that are specific to a country go to the Stack Overflow of the language spoken in the country.

Of course, if a language is spoken in many countries, like French, this partition does not work very well.

link
2  
Tax questions aren't programming questions. I find it very hard to believe there are actual programming problems that people face in German but not ever in English. Domain-specific knowledge isn't on topic for SO, they would be on topic for that domain's site. The whole domain would have to be localized to that specific language (like our language and usage sites) to really be viable. – Ben Brocka Apr 28 at 15:26
feedback

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged