holman/feedback — Issue #61: How do you destroy ideas?
Author: surfacedamage
Created: 2011-10-18 15:24:29+00:00
State: open

I've been very impressed with the feature set that github continually rolls out. You are like some omnipotent being watching over the development process, sees some pain, and then provides the perfect antidote.

But even as a mere mortal, I know better: not all ideas pan out. Not all ideas are great or well accepted by the community.

If you come up with what you think is a good feature, how do you test the water? Do you test out the concept internally first or do you have a way of rolling it out to a beta community for feedback?

Have you deployed a new feature, but then needed to kill it for some reason?

I'm very curious how your idea vetting process works. (Or perhaps -- unsurprisingly -- you are just always right.)