Any good reason polls aren't enabled?

Kal · September 8, 2009, 4:00pm

From one of the guys upstairs:

If the community desires certain features enabled then the day-to-day administrators are the ones to petition. I rarely make decisions about features or at least believe I’m not the decision maker. There may be a misunderstanding going on between the day-to-day admins and myself in that they are waiting for me to say they can turn on features and I’ve been assuming they can turn on any features they want. If a feature causes a performance problem (unlikely for most features) then I’ll tell them why we need to turn it back off.

That said in the past I’ve been a bit gruff in my response to them when I’ve had to turn a feature back off so we’ve probably arrived at an unspoken impasse where I think it’s fine for them to turn on whatever they want and they think they can’t turn anything on. In the first few weeks after the upgrade I also told the day-to-day admins to not mess around with features because I was also doing things and I didn’t want us to bump into each other. So I’ll take responsibility for not going back to them later and saying they could turn on features. I had just assumed that after the performance had stabilized last fall that they could do anything they wanted but it looks like I dropped the ball. Finally, I don’t know exactly why it’s become “common knowledge” that most features can’t be turned on due to performance reasons. From my perspective there are only a small number of features that could cause a performance issue and I think we can turn them on and see what happens anyway. If they don’t work we’ll turn them back off. That doesn’t mean we haven’t had problems with certain features in the past. We have but we’re now in some cases two, three, or even four pieces of hardware and one to two major version levels of vBulletin away from those previous times. Conditions have changed so we can change too.

ETA: Link.