The CPM are our "elected" officials, they represent the voice of the community. They need to have just as much say in the development of this game as anyone on the dev team.
The dev teams needs to eat their own dogfood / live their own code. They don't but the CPM does, thats why they need a say.

You weren't elected, and therefore aren't representative of the players. You're illegitimate, and should have no more rights than any other player - aside from laying the groundwork for a legitimate, representative body.

A decent sentiment, but, honestly, CPM0 should have only one responsibility - preparing the infrastructure for CPM1.

You weren't elected, and therefore aren't representative of the players. You're illegitimate, and should have no more rights than any other player - aside from laying the groundwork for a legitimate, representative body.

You guys shouldn't even have the CPM tag on the forums.

A fair enough point.

This is part of the reason we call ourselves CPM0, and not CPM1. But, ask yourself this ; Isn't the core part of the infrastructure, the process by which the CPM interacts with CCP? Establishing a voting process right now would be entirely meaningless, because CPM1 would just have to trudge through all same the roadblocks we're trying to clear for them. There has been progress, albeit slow in regards to setting up procedures that allow us to communicate, but many of these processes are not being used by CCP as well as they could be, which is yet another roadblock.

That being said... any player could say exactly what we have collectively drafted as a group and posted in the OP. Most of it is observations that any outside observer could make. It's simply a statement of how things are, since the information chain & feedback process is the integral function of the CPM institution, and people need to know where it stands.

A decent sentiment, but, honestly, CPM0 should have only one responsibility - preparing the infrastructure for CPM1.

You weren't elected, and therefore aren't representative of the players. You're illegitimate, and should have no more rights than any other player - aside from laying the groundwork for a legitimate, representative body.

You guys shouldn't even have the CPM tag on the forums.

There is a pretty apparent culture difference.

However, I don't think this is the real source of the problem, and the absolute worst thing CCP could do is turn this into a witchhunt. It's not just one person or group of people causing this, the communication gap is a roadblock that exists in the process itself, that needs to be removed at all costs. This is not about placing blame or trying to find fault in any person or team. That doesn't matter. The last thing we want CCP to take from something like this is that there is anyone in the company causing this, who would just become a scapegoat, get fired, and have CCP think they 'solved' the problem.

Now more than ever, CCP needs all of their employees to be at their best. They need to work together with each other and with the community, and any assumption that anyone needs to be blamed or is at fault for this will just take away from any cohesion they might otherwise form as a result of this effort.

TL:DR - This is not a people problem. This is a "Operating Procedure" problem.

Giev CCP Unifex on dust that dude rocks

I always assumed that 95% of CCP Shanghai did not speak english.

Language Barrier

Just to clear this up, none of the CCP staff we've ever engaged with have had any problems with English. The management of the Shanghai studio is almost completely made up of expats, and English is the required operational language spoken inside the company.

Good guess Regnummyummytummy - but unfortunately this goes deeper than anything hiring some translators could fix.

Whatever.

If this thread doesn't get a blue tag soon, I'll lose all faith in humanity.

Oh... the CPM got something better

Oh... the CPM got something better

So, some good(ish) news to report, following up to this.

Prior to even posting this, we poked CCP PR. We wanted them to know we were going to post something that was going to end up being pretty grim, and why we were posting it. Following this courtesy call, emails were sent out and we were contacted by several of the higher-ups, asking what was up to hear it for themselves. We were told this stuff was being added to the agenda of meetings with the higher-ups this week, and that they'd get back to us in a meeting shortly after.

This was pretty much expected, but we're not so much posting this to turn heads at CCP or to make it seem like we're trying to bully them into a response, so much as to acknowledge to the public "This is how things are right now". Our hope is that in the following week(s), we can hopefully have something much more positive to report. We want to keep the players in the loop as much as possible with what we're doing and how it's going.

Now, on to the positive stuff!

After posting this, I had a nice, lengthy talk with CCP Cmdr Wang. We talked about this statement, why we were making it, what our goals were with it, and the conversation progressed into something massively productive, beyond anything I could have hoped. He explained clearly and concisely CCP's internal design process and terminology and planning structures. We talked about the devblog process and how they determine what information is getting out and what precisely the 'hoops' are in order for a blog to land in the communities' lap. We talked about dev & blue posts, and any rules regarding those that apply to information getting out.

We also discussed the hotfix process & how the weekly reports from the community team play into those, and how those fixes are prioritized. We expanded our conversation into marketing, and while I can't get too much into what we talked about here, it was good info and super helpful.

In summary :

CCP Cmdr Wang gave us a MASSIVE amount of insight into many of CCP's processes that we have grievances with, and explained the proper terms to use to best ensure we 'click' with the devs and can communicate with them as efficiently as possible using language and methods that would best allow us to make the impact we're attempting to do. Now, in the meeting later this week with the higher-ups, we'll be completely armed to take best advantage of this opportunity and do the most good.

Couldn't CCP go an extra step (in the future) and sync new DUST content to SiSi? That way community members who have access to the Singularity server can help test new DUST content before it's released to Tranquility.

Couldn't CCP go an extra step (in the future) and sync new DUST content to SiSi? That way community members who have access to the Singularity server can help test new DUST content before it's released to Tranquility.

That's probably one of the better ways to conduct testing rather than throwing it to the wolves and hoping for the best.

Until you guys actually share what the exact details are the community is in the same boat while the CPM takes a step forward. Unless this info is being publicized - nothing is changing.

There is a pretty apparent culture difference.

However, I don't think this is the real source of the problem, and the absolute worst thing CCP could do is turn this into a witchhunt. It's not just one person or group of people causing this, the communication gap is a roadblock that exists in the process itself, that needs to be removed at all costs. This is not about placing blame or trying to find fault in any person or team. That doesn't matter. The last thing we want CCP to take from something like this is that there is anyone in the company causing this, who would just become a scapegoat, get fired, and have CCP think they 'solved' the problem.

Now more than ever, CCP needs all of their employees to be at their best. They need to work together with each other and with the community, and any assumption that anyone needs to be blamed or is at fault for this will just take away from any cohesion they might otherwise form as a result of this effort.

TL:DR - This is not a people problem. This is a "Operating Procedure" problem.