My Suggestions for vBulletin.org (when it upgrades to v4)

[cheat-master30]

1. Impex + vBulletin.org database
2. Drop all modifications made to vBulletin.org. Tough luck. Start from fresh vBulletin 4
3. Drop and completely revamp the style and layout.
4. Upgrade to vBulletin 4, using the new features like built in tags and what not.
5. Hire more paid staff from Jelsoft/vBulletin Solutions/Internet Brands to manage it backend wise.
6. Use the CMS for the articles, modifications, styles, graphics, etc.
7. Use blogs for the developers who make various modifications, as well as the staff team. Basically, it would act like an insight into how the community codes their top notch mods/hacks.
8. Use project tools for the modification bugs and what not, as well as problems with the site. This would unclutter the modification topics, and maybe make it so things like suggestions and bugs get seperate sections.
9. Have forum to post paid mods, as in details, link to where to get them, etc.
10. Profit!

Already posted this on AdminAddict, but I'll say it here as well. My suggestion in future is just to rebuild the site from the ground up on vBulletin 4, who cares less about any current minor modifications or styles made. Shouldn't mess with the license tie in thing, vBulletin.com works fine with it on version 4.