We Made CloudSpokes Scoring More Transparent

We love transparency.

Our goal here at CloudSpokes is to make the judging process for challenges as open and transparent as possible. After a winner is announced for a challenge we think that the public should be able to see all of the individual scorecards for each particpant. Not only does this keep the process transparent but also provides valuable feedback for the participants from the judges and other participants.

We also think that participants should have access to all of the code that is submitted for a challenge. That way the challenge is not only about winning money and badges but becomes a learning process as well. The whole community becomes better from the shared submissions.

We ran our CloudSpokes Public Scorecard Service challenge to build the Apex REST service to return the scorecard results for a challenge. There is no front-end design work involved, just the Apex REST service that will call from the CloudSpokes rails site. It was interesting to see that the submissions were not from our usual (large) pool of normal Force.com developers. First and second place were won by members that came to CloudSpokes with other skills besides Apex and Visualforce and have gravitated to these challenges over time. We recently announced that the result from this challenge are already live on the site. 

	peakpado Place: 1 Money: $500
	romin Place: 2 Money: $150
	snehaheda Place: 3 Money: $100