Do you want your hack built into vBx?

[s.molinari]

Hello all,

I was just wondering. How about adding a field to the hacks database which lets the author give permission for his or her hack to be added into future versions of vB by the vB.com dev team?

What do ya think?

Scott

*edit* I reworded the above question. I see now how it could have been misinterpreted.

[Chris M]

Eh?

Satan

[Admin]

I also don't quite understand...

[Mark Hensler]

I would advise against that. If vB wants to incorporate a hack, they can contact the author.

I'm not even sure what the laws would be about people copyrighting hacks.

[s.molinari]

Mark your right about the contacting thing. But I still think it would be a good idea. I mean, I would let the vB crew use my hacks if they wanted. Firstly it saves them time, which means newer versions with more/better features can be developed and released more quickly and secondly, I have a personal stake in the product. (Which I have anyway)

Maybe it's my perspective that leads me to believe that it's a good idea. That's why I asked for your ideas. And I do appreciate the feedback even if it is just an "Eh?"

Scott

[Eniyi]

That would be nice and make things much easier. If the author of an hack is posting the hack here to be used free, Vb developer team can also use that hack and such a feature would prevent problems. It's a good idea.

[Admin]

I can count the number of hacks that were put into vBulletin on the palm of my hand, really. Usually if the developers see a good hack, they will rewrite it themselves, making it much better code-wise.

[Sparkz]

Hopefully you're right
But there are a few things that have been released as hacks here that I'd like to see in vB3.

Another thing about hacks and the resulting code would be that you try to make it as easy to install as possible, while still retaining as muc h of the originally planned functionality there.

Releasing something that would take a couple of hours to install due to all the code-edits would be worthless for most people.

Not having to worry about stuff like that, the dev-crew can, in most cases, do a much better job of it. Knowing the code like they do probably doesn't hurt either :P