cn-members came on Mumble and we talked about all this. We agreed there needs to be a happy medium between massive censorship, and devs being careless with their words.
I proposed to him a very simple solution:
1. Statements, Proposals, blogs, and posts should be peer-reviewed by the dev team before publishing. Their collective social intelligence should be much greater than the sum of their parts, and sufficient for anything blatantly bad PR.
2. The finalized text should be given to a dedicated Chinese community member to translate, to post along-side the text simultaneously.
To this, cn-members told me that they asked for this exactly, many many times over the past year. He said that the problem has come down to habits, and that the dev team needs to be proactive in changing their habits.
Can a dev comment on the above proposal? Are you aware the Chinese has been asking for this? Is there any reason why this cannot be implemented into your communications?
I didn't know this was going on.. but when ths PR thread came out this was exactly what I suggested regarding training devs and changing the culture. It's not the easy way, but it's the better way... and everyone in the end is better for it.
I think this makes sense... I just don't think it is a priority vs. the demands being made on everything else. I can see how this proposal would be treated as a 'we will get to that later' type thing. Problem is the issue festers.
I see no reason why stuff can't be peer reviewed before release. It's just good sense.
Show Posts
... pretty much what I was thinking. 
