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.

[ChopSuey]

They've been with 3.6.12 for a reason. Don't see why this shouldnt happen.

[Paul M]

My (personal) comments.

1. Why would we need Impex ?
2. What purpose would that serve ?
3. These styles wont work in vb4 anyway, so thats bound to happen.
4. You suggestions are for when we upgrade, so upgrading is a bit of a given.
5. Thats up to IB.
6. For Articles yes, makes sense. Why would the CMS be used for Mods & Styles ?
7. Not sure if blogs are useful or not, seems you are suggesting they be used as articles.
8. PT will not be an official product, but yes, we would like a bug & suggestions system for mods.
9. Thats never been vb.org policy, but we'll see if it changes.
10. vb.org isnt here to make a profit.

[ChopSuey]

Originally Posted by Paul M.

4. You suggestions are for when we upgrade, so upgrading is a bit of a given.

Missing an " R " there paul? (Couldnt resist)

[cheat-master30]

Originally Posted by Paul M

My (personal) comments.

1. Why would we need Impex ?
2. What purpose would that serve ?
3. These styles wont work in vb4 anyway, so thats bound to happen.
4. You suggestions are for when we upgrade, so upgrading is a bit of a given.
5. Thats up to IB.
6. For Articles yes, makes sense. Why would the CMS be used for Mods & Styles ?
7. Not sure if blogs are useful or not, seems you are suggesting they be used as articles.
8. PT will not be an official product, but yes, we would like a bug & suggestions system for mods.
9. Thats never been vb.org policy, but we'll see if it changes.
10. vb.org isnt here to make a profit.

1. Because otherwise you have a load of unused tables taking up space, especially for things that get replaced by better features.

2. Because pretty much everything can be done with default features... prefixes... tags... And because save your panicking about not upgrading, just drop the smaller modifications that I hear have been made all round this site..

3. True.

4. Darn it... redundancy.

5. It'd be nice though. And they promise they'll overhaul this, or at least did once in the past.

6. Because it looks more like the standard style and makes more sense than an edited postbit template.

7. Not sure. Maybe it'll help the staff, I don't know. Best to set an example, otherwise no one use the suite features on their own forums either.

8. Awesome.

9. Good idea though, it's been requested dozens of times now.

10. It's merely a saying. Basically... follow this and you get success.

Edit: For 10, read this page and you'll understand it:

http://tvtropes.org/pmwiki/pmwiki.ph...tepThreeProfit

[Gio~Logist]

I agree with everything Paul said except #10. Reason, being this site indeed is in order to make IB more money - if not one way than another. It clearly plays a great role in the community and customer base, no? I don't see why profiting would hurt, from softwares to platforms to phones, extending plugin development can only play to your advantage - especially if you're exposing it and charging devs even. But in the end, this clearly isn't a choice for any of us to make.

I can definitely see the need for better use of displaying content for articles and what not, as well as a new front page, but other than that I'm sure you guys will do just fine with the upgrade.

[fanyap]

vB.org could be a HUGE revenue source for IB if they take the right steps and implement the correct things this community really has needed for quite some time.

[Paul M]

Originally Posted by cheat-master30

1. Because otherwise you have a load of unused tables taking up space, especially for things that get replaced by better features.
2. Because pretty much everything can be done with default features... prefixes... tags... And because save your panicking about not upgrading, just drop the smaller modifications that I hear have been made all round this site..
3. True.
4. Darn it... redundancy.
5. It'd be nice though. And they promise they'll overhaul this, or at least did once in the past.
6. Because it looks more like the standard style and makes more sense than an edited postbit template.
7. Not sure. Maybe it'll help the staff, I don't know. Best to set an example, otherwise no one use the suite features on their own forums either.
8. Awesome.
9. Good idea though, it's been requested dozens of times now.
10. It's merely a saying. Basically... follow this and you get success.

1. We dont have loads of unused tables, nor would we. Im pretty sure space is not an issue with IB either
2. Prefixes yes, tagging .. maybe. Neither of those would replace some of the basic features like install tracking.
3. -
4. -
5. I cant comment on what plans IB have (cause they dont tell me ....).
6. The same layout for mods, articles etc does not make sense, each has their own requirement.
7. This seems to be a common misconception, vb.org is a place to get/discuss modifications, its purpose is not a vb showcase.
8. I guess it depends on what happens to PT, and peoples time.
9. See 5
10. Not a saying ive come across.

[haothiencz]

@Paul:

Personaly, we have a highly customizied board, w many modified templates, mods, like what you are having here at vbulletin.org.

Many times, members keep asking us, hey guys why dont you upgrade our site to latest version?

The answer used to be: we have a lot of customized mod rite here, upgrade will make many trouble and waste time for us to start everything from the beginning (ok, not everything but almost to make sure it's compatiable with the latest version).

We said it when vbulletin release the 3.7 , 3.8 and now the brand new coming 4.0.

I said to my member, even vb.org dont have the lastest version because of the same thing what we have here. So, why we have to pay for the renew and continues with new version?

Its just my opinion but I'm sure many people here have customized board like you guys here and doesnt want to do upgrade with the same reason like me. Then why dont you start the new guru?

As Gio said, I believe that you could done it well without any problem, just need time here.

[Princeton]

upgrading just for the sake of upgrading?!?

The top 2 reasons to upgrade are....
1__ security
2__ new features

security - we are always on top of security patches, etc

new features - up to this point there's nothing screaming at us; not saying that we don't want changes just saying that what is out there is not necessarily what is needed at this moment

Should we upgrade? NO, IT'S NOT NECESSARY
Can we do it? YES
Do we want to upgrade to vBulletin 4? MOST DEFINITELY

Please answer the following...

Do we have to upgrade our software for you to enjoy the addons, the articles, and/or the thousands of posts on vbulletin.org?

Are you having difficulties navigating the site?