So, ultimately you do not envision independently developed commercial products being downloaded directly from this or an alternative Jelsoft supported site?

At this time I do not. There is no infrastructure to support such a thing. I do envision bringing awareness to commercial endeavors to our customers. If there was the infrastructure for a commercial marketplace, it might be a different story. Such a marketplace would require much more rigorous controls on commercial addons than can be implemented at this time.

What if someone went out on there own and created a vbulletin commercial product database? Would you guys point users thataway?

If you read the other thread, I bought the domain name vbulletincoders.com. Which would be a directory listing on third-party sites offering paid and/or commercial hacks to the members of vb.org. I emailed vbulletin if the use of vbulletin in the domain was allowed, and this was the response:

So, I really didn't get any of my questions directly answered. I also asked if I weren't allowed to run such a site with the mentioned domain name, why were others allowed? (ie. Floris and www.vbulletin-fans.com)

That wasn't answered either. So, I'm quite dissapointed in the response..

I was given EXACTLY the same response re: vbulletintoolbox.com and vbulletinhandyman.com.

Quite disheartening then to see all the other vbulletin*.com sites that are allowed to flourish (and get onto the BOTM).

See here for more on this.

I just found this on vbulletin.com

Found here

Now I am really confused....would Jelsoft lie to it's customers?

Maybe it's more a case of 'Although he posts as if he does, Floris doesn't actually know everything that is going on'?

That post annoyed me too, because it was Floris that gave me the impression that 'non-commericial' uses of the domain name (like he was doing) were acceptable...so I registered the domains, then was told that it was not.

I read it as the trademark process is ongoing for the name vBulletin. It does take a while for that to go through (upwards of over a year).

getting back the vb certified thing, maybe a small fee to become ceritifed would be a good idea which would help fund the program and the team that moderate it. it would probably also deter those who really would not be qualified and would waste the moderator/certifiers time. now this certification could apply to developers, vendors, hosts, and softwares. here are some ideas

everytime a software is upgraded it must be resubmitted for certification. a developer/vendor/host would have an annual or periodical certification to make sure they are up to date and following vbulletin's guidelines and standards. if they fail to pass the certification the person's/software's certification is removed. also if a provider is certified they could maybe have access to customer emails such as vb.org to verify purchases and prevent unlicensed people from downloading their software. this of course is up to jelsoft and their team.