You misunderstand the vote, the vote is open to the public, only its results are closed until the vote is done.

I dont agree with the"Elite Pack" term. But thanks for the props, and this is meant to be a happy medium, between CKs "best of the best blog pack" and Black Claws "Everyone is equal" evebloggers.com - I think that it has real potential, and yes sounds really badass :P

I have your email, Ill send you a message and maybe we can begin putting our heads together.

Any special talents(coding, design, spelling?:P) you have would be a great use. The whole point of this project is that it flows with the community, it can expand and (hopefully not) shrink to fit the needs of the community. It would indeed be a lot of work, but the rewards would be well worth it.

Thanks, I agree that this could be of benefit to Capsuleers user base. I will send an email here shortly.

Help with the website would be great. While I am fairly confident with my web design skills, my web programming skills are lacking. I dont know if you are any better, but if this project is going anywhere, im going to learn, or have to find someone who knows some web programming o help out.

I was thinking more along the lines of the actual Sov mechanics code, but errors in the database are more than possible also.

Where is it documented that CCP knew about these issues before hand? I admit I haven't read all the info on this, so maybe I missed this. I havnt seen anything from CCP or otherwise that says that CCP knew about these issues before hand.

I dont ever remember hearing about CCP encountering these issues on the test server either(prior to launch). The truth is, its frustrating, but just because this bug is as big and bad as it is does not mean that they knew about it and ignored it. Its no secret that the test server cannot accurately simulate how things will work on the production server.

Wensly,

Lonetrek Hosting would love to donate to this cause. Please email me at admin@lonetrekhosting.com so we can work out some details.

No kidding. Maybe the structure is as simple as the code is not uploading to some of the system nodes as well as it should so parts of it are corrupted. I know that seems simple, but it would explain why some systems are fine an others arent.