vB3 Hacks

[filburt1]

This is just a reminder: while vB.org has now upgraded to vB3, you still may not discuss or post vB3 hacks publicly here. Such discussion will be allowed starting with the vB3 RC (release candidate).

[TheEDIGuy]

Originally Posted by filburt1

This is just a reminder: while vB.org has now upgraded to vB3, you still may not discuss or post vB3 hacks publicly here. Such discussion will be allowed starting with the vB3 RC (release candidate).

It bothers me a little that vb.org is able to design (or adapt) a front page portal for the vB3 site, but is unable to either release it or help other vBulletin owners do the same.

Maybe it's just me.

[Erwin]

Originally Posted by TheEDIGuy

It bothers me a little that vb.org is able to design (or adapt) a front page portal for the vB3 site, but is unable to either release it or help other vBulletin owners do the same.

Maybe it's just me.

Why should that bother you? We also had the licensing system, the hack database, the hack installation system, and lots of other code that has not been released since they are proprietary code, and not for public release. Many hacks have been released, and some have not.

[Logikos]

i not mad at all, i would be if vb3 was out of beta, but not now. And i dont seem to see the hacks database yet. Im sure your still in the middle of coding it

[TheEDIGuy]

Originally Posted by Erwin

Why should that bother you? We also had the licensing system, the hack database, the hack installation system, and lots of other code that has not been released since they are proprietary code, and not for public release. Many hacks have been released, and some have not.

I guess it shouldn't. But seeing that vBulletin 3.0 is apparently stable enough for both vBulletin's own support forum and vBulletin.org's forum to be run on it, and their active discouragement of anything requiring code change to even be discussed anywhere, much less released, has me a littel depressed.

Combine that with the fact that vb.org hackers are apparently confident enough in the stability of the vb3.0 code to create a front page portal system for vb.org itself, but still won't allow anyone to publish similar code modifications, and you may begin to see where I'm coming from.

If it's stable enough for you guys to hack, it should be stable enough for the rest of the hackers to start publishing code. That's all I'm saying.

But, I'll climb back in my shell until RC is out. After all, it was my decision alone to upgrade early, although I wanted to be part of the debugging process.

[filburt1]

Originally Posted by TheEDIGuy

I guess it shouldn't. But seeing that vBulletin 3.0 is apparently stable enough for both vBulletin's own support forum and vBulletin.org's forum to be run on it, and their active discouragement of anything requiring code change to even be discussed anywhere, much less released, has me a littel depressed.

Combine that with the fact that vb.org hackers are apparently confident enough in the stability of the vb3.0 code to create a front page portal system for vb.org itself, but still won't allow anyone to publish similar code modifications, and you may begin to see where I'm coming from.

If it's stable enough for you guys to hack, it should be stable enough for the rest of the hackers to start publishing code. That's all I'm saying.

But, I'll climb back in my shell until RC is out. After all, it was my decision alone to upgrade early, although I wanted to be part of the debugging process.

The whole point of a beta is to find bugs. You'll notice that practically nothing has been hacked here except for the license system; likewise at vB.com. Hacking now completely destroys the effectiveness of the beta program because foreign code completely changes the product.

[FWF]

im happy to see vb.org running smooth on 3.0.0 Beta i cant wait for the R C its going to be nice.

[Link14716]

That's hypocritical at best. No one may post or discuss vB3 hacks, which means that naturally you do not encourage hacking the beta. Yet vB.org is running vB3 Beta 6, and using hacks to power it. Yes, the license system is needed, as is the installed/uninstalled hacks, and obviously the portal is great as well. But that is still no excuse to be hypocritical.

Oh well.... *cough**cough*vbulletin.nl*cough*

Just my $.02.

[filburt1]

Originally Posted by Link14716

That's hypocritical at best. No one may post or discuss vB3 hacks, which means that naturally you do not encourage hacking the beta. Yet vB.org is running vB3 Beta 6, and using hacks to power it. Yes, the license system is needed, as is the installed/uninstalled hacks, and obviously the portal is great as well. But that is still no excuse to be hypocritical.

Oh well.... *cough**cough*vbulletin.nl*cough*

Just my $.02.

It wasn't my decision. I was offered to post the announcement and I did. You'll have to take your complaints to a manager of Jelsoft because we're merely their pawns.

[Xenon]

As filburt said already, it wasn't our descision.
vb dev's have asked us and as we want to support them, we don't allow vb3 hacking until RC.

Of course hacking itself is allowed, but not releasing it on vb.org now.

Regarding vb.org: we've just hacked in what's absolutely needed on vb.org, nothing more.
All "special" hacks will appear with RC, as it's also easier for us, regarding upgrades et al.

but as already said, we just try to help vb3 devs, so talk to them if you're not content with the actual situation