Policy on unsupported hacks?

[nix]

Would this be enough?

https://vborg.vbsupport.ru/showpost....postcount=1697

[Paul M]

Nope, that's second hand - you could ask Redlabour where it was posted, as I cannot find it anywhere. Have you tried to contact Crist ? From reading a few pages in the thread I'm sure he would allow it, I found a couple of instances where he gave others permission for the 3.6 version (inc the eventualy releaser).

[nix]

Originally Posted by Paul M

Nope, that's second hand - you could ask Redlabour where it was posted, as I cannot find it anywhere. Have you tried to contact Crist ? From reading a few pages in the thread I'm sure he would allow it, I found a couple of instances where he gave others permission for the 3.6 version (inc the eventualy releaser).

Thats how I took it also. So it would be okay? I've tried contacting Crist but nothing has come up yet. I'll ask Redlabour if he can find it for me.

Thanks for you time.

Well I talked to the other Author and he has rights to the mod now from Crist. So he gave me the go ahead to release something. Is that enough?

[Dream]

Did the other author receive permission from Christ?

[Shazz]

Originally Posted by Dream

Did the other author receive permission from Christ?

Read post #9 from Paul

[nix]

Yes he did. They talked and Crist pretty much gave him control over the mod.

[Shazz]

So if Crist gave him permission to, Could he give you permission to instead of Crist

[Paul M]

Originally Posted by nix

Well I talked to the other Author and he has rights to the mod now from Crist. So he gave me the go ahead to release something. Is that enough?

Seems reasonable to me.

[joeychgo]

Let me suggest something...

Why not a new policy.

If you release a hack - and dont update it to a new version within a set amount of time - then anyone can update or rewrite for the new vB version, provided they give credit to the original author and the original version of the hack.

As an example:
If you release a photo gallery for 3.6x - and 4.0 comes out. And you dont update it or indicate you are in process of updating it, then after say 2 months of the release of the new vb version, then anyone can update the hack to work with the new version, and re release it to work with the new version.

This way, when a hack that people are using wont work with a new version of vB, someone can update it so that it works.

Maybe .org builds in some kind of functionality to make this request -

But this is a problem that should be explored as to how to resolve IMO.

[da420]

^^ Personally, I see a lot of problems that could occur with that. Even though it's great - in theory.

But, this removes ownership of the code from the author to vbulletin.org upon release. I see that causing many problems, and may deter many hacks from being released here at vbulletin.org.