You are free:
- to Share — to copy, distribute and transmit the work
- to Remix — to adapt the work
Under the following conditions:
- Attribution ...
- Share Alike ...
The Chinese cite shows that it is CC-SA (right bottom corner). Furthermore it freely acknowledges that it is based on stackoverflow. You can look at the blog [here](http://translate.google.com/translate?prev=_t&hl=en&...)
Here is an [answer](http://126.96.36.199/translate_c?hl=en&ie=UTF-8&sl=...) to what the relationship is between cnprog.com and stackoverflow:
The creation of CNProg are stackoverflow inspiration comes from (see "Why CNProg.COM create?")
SO once made to us, but because of Jeff and his team are currently no plans for localization, so we have created to serve the Chinese programmers CNProg. And our platform is already open source code, welcome like-minded friends to join us, millions of programmers to provide a domestic major technical Q & A community.
I can not see that anything morally wrong was done by creating this site - and it serves a useful purpose (by helping those people who speak Chinese).
> The language argument is a red herring that appeals to an outdated, pre-communications revolution worldview
This is the typical view of an English centric person. There are billions of people for who English is not a first language and whose second language English is not up to the standard that they can communicate with.
But who cares? I am sure that there are enough Chinese -speaking people to make this site a success.
I'm not addressing the license aspect of this particular case, I'm addressing the attempt to use language support as a justification for this practice.
Furthermore it freely acknowledges that it is based on stackoverflow... The creation of CNProg are stackoverflow inspiration
There is a huge difference between inspiration and outright cloning, and many additional consequences that result from the latter.
This is the typical view of an English centric person
Just the opposite. This is the view of someone currently in France, whose first company in my 20s was based in both Hong Kong and the US, makes web apps with labels in multiple languages and therefore recognizes the utter ignorance of claiming that language is sufficient justification for outright cloning a product or service.
Jeff Atwood and co. could never "copy" the StackOverflow community into China. And that's what they would have to do..."copy it to China". I highly doubt they could have done it and maybe this new set of programmers can. What harm is there in providing a community for Chinese programmers to thrive?
Look at all Google's efforts...and they aren't the dominant search engine in China. There is too much belief that if a Western company creates a product that they have implicit rights to world domination with it. I think a fragmented world is interesting and more competitive. If it takes copying to bootstrap that fragmentation, so be it.
Which is basically all the clone is at this point.
I still think your focusing too much on "language" rather than "community".
I'm focused on language because that's the justification being given for cloning web apps. No matter what language you want to deal with, claiming that you can't build a community without entirely cloning another team's web app is asinine.
At this point its more than a clone. He published the source with a permissible license (Apache) on a well adopted platform (django).
StackOverflow gave something to the world with its licensing. The creator of this new product followed the rules and even added the bonus of immediately giving something back to the world.
Your argument was that someone can't take a web app and "copy it to China," yet this is exactly what it is at this point from the perspective of someone using the application. So, according to you now, apparently it can be done as long as the person who "cop[ies] it to China" happens to be on Chinese soil at the time and, unbeknownst to a regular user, builds it using a different web framework and open sources it.
No, in fact your origin implication was the right one: the hard part is building a community and delivering a service customized for market beyond simply changing the language, something that so far has not been done here with this application yet.
I'm not sure what your point is, actually. Cloning successful products is hardly new or even frowned upon. Indeed, the computer you are using is most likely a descendant of a cloned IBM PC. Why argue?