Quoted By:
Once I get out of the shower and figure out what I'm doing today, I'm going to post the results from the demo feedback survey.
I discussed this a bit with a few people on skype yesterday, and I feel we should be making a list of every piece of feedback, and then going through each one and deciding if it is worth acting on to improve, and crossing out the ones we aren't, so then we are left with a "demo improvement to do list".
In fact, I'd be more than happy to go ahead and start doing so on a public google docs document, if you all don't mind me starting on compiling a list. I wouldn't be picking and choosing, everything that was said that has a specific piece of tangible feedback I would be listing, as well as the number of times it comes up. I can also split the results at the reddit incident, which actually shot up the number of responses by 33%, but I don't think that we should entirely discount their opinions: They have a more unbiased view of the project since they are an outside player.
last time I checked, we had about 350 responses. about 130 of them are from redditors (Well, this was the number of people who voted in the 3 days after the reddit incident). This is a pretty good sample size, so I would say that the survey was a massive success.
I had hoped we all could decide on a more concrete plan to approach this than this (actually figuring out how we would collectively decide which pieces of feedback to act on once the list is made), but when I brought it up to a few people via skype, they said no, so, this will have to make due.
Also holy shit can you people stop shitposting.
