This is really not a viable discussion anymore. Mr. vBulletin has declared that they have no intention of doing anything differently, so that pretty much sums it up.

I was not suggesting that someone review every single line of code. That would be ridiculous. However..... why Mr. vBulletin rejected the suggestion of publishing a set of guidelines, escapes me at the moment. I did not mean guidelines to be a set of strict rules or else policy. I see nothing wrong with having a standard checklist describing what an addon does.

Foor instance:

Files uploaded: yes/no .... list of files
Files Modified: yes/no ..... list of files
Templates added: yes/no ..... list of templates
Templates Modified: yes/no ..... list
Database changes: yes/no ..... list of changes
Admin CP changes: yes/no ... list

Uninstall directions included: yes/no


etc, etc.....

You most likely have noticed that all the really good mod coders already do this. I just wish all of them would.

As a community we've tried to do similar things in the past and had long threads about it in the past.

Basically no one wants to manage the problem and a lot of coders don't want to adhere to the "standards" that would have been put in place for personal reasons.

In other words I doubt it'll ever happen. Your best bet it to use a test forum and only download/use modifications from respected hack authors.

A phrase about herding cats comes to mind.

If there is a serious flaw in a modification (such as an SQL injection vulnerability), please report that modification. Staff will look at that modification and quarantine it if necessary.

Probably because it's the sort of thing a 5 year old would say.

Hostility begets hostility. If you post in a demanding and hostile manner people will respond in kind.

And to the OP; Since I'd rather not incurr your terrible wrath and more name calling, I'll simply suggest you read everyone elses reply again, and maybe adjust your bad attitude and sense of entitlement :rolleyes:

I hope I don't get called a poopoo head or something now :|

Coders on vBulletin.org are not paid for their work, it is all done voluntarily. There are already not many people who submit work (I mean, there are quite a bit, but we could always have more). Setting up a list of guidelines that they must follow, will probably just make vB.org have less people releasing modifications.

If applied from the start, the rules would've been accepted and followed. Changing this just because of a couple of coders who can not code logically is just bad... like Mike said!