On 05/24/2010 08:49 AM, Nathan wrote:
Edit check, review gap, review delay, check delay, wait approval, content pause, review pause, second check, second approval, etc. There are lots of possible names for this feature. Sometimes I worry that the Foundation staff work for a company built upon the value of community generated content and community sourced ideas, but don't truly *believe* that this value exists or can be relied upon. The best example is the fund-raising drive, when much of the best and most useful content came from the community after the original (and expensive) content was widely panned. Why not involve the community at the beginning? A request for endorsement of your favored options is not the same thing, and fails to harness real community enthusiasm.
A legitimate worry, but in this case I don't think that's what happened.
A few months back we discussed changing the name, but nothing exciting resulted from it. We couldn't come up with anything that seemed significantly better. Recently, two things happened. One, we were working on all the little bits of text, trying to choose good labels for things. We'd left that for relatively late in the process because it's easier to do that in a single sweep. Two, as part of pre-rollout activities, a broader set of people got involved.
Both of those activities caused people to look at the name anew, and a number of people got together to take another swing at it. They ended up with two candidates that they liked better. At that point, we involved the community to get a broader opinion. But we're all committed to shipping this as soon as possible, and that a new name, while nice, wasn't important enough to delay release. Thus, an attempt at keeping things quick. That again is based in my interpretation of what the community wants.
William