I've had a couple of wishes rejected, with no explanation given. From certain comments, I rather get the sense that I'm not alone in this. It's especially frustrating when a wish garners support from the community, and is then rejected silently.
When a member of the core development team decides that a particular suggestion is so unhelpful as to reject it out of hand, the rest of us would love to know why. Even a single line — e.g. "would require complete overhaul; too costly" or "duplicates other wish: [[[link]]]" — will help us avoid making reject-worthy suggestions in the future. True, we have bad ideas sometimes. But if so, we all want to learn why they're bad, so our ideas can get better.
That way, everyone benefits.
Agreed. It's nice to know why something is rejected, just for the sake of being able to repeat that reason when others ask for it on the community, or some other site.
Shane Smith
Web Developer and Wikidot Community Administrator
Links: Blog, Wikimated, Editor (STE), Documentation
I agree. It's a courtesy to the users (customers?) Even just a short explanation like Ben said. I had a wish rejected with no explanation and frankly I found the lack of even a "hello, you're wish sucks" to be a bit offputting.
To me, a little courtesy goes a long way and I do not see why wikidot should expect it's users to help make it better if the users cannot be given a simple explanation about why wishes are rejected.
On a positive note, I've noticed that Wikidot does not reject wishes quite so quickly any more.
The team now seems to be waiting a few days, to allow us to discuss a wish and come up with other, better solutions, before rejecting something outright.
Shane Smith
Web Developer and Wikidot Community Administrator
Links: Blog, Wikimated, Editor (STE), Documentation