Policy on unsupported hacks?

[joeychgo]

That might not be the best way of doing it - im sure it could be tweaked - but I dont see how that would stop people from releasing hacks -

Hack ownership wouldnt be removed. What im saying is that if you write a hack for 3.0 - but its unusable on 3.6 - then you own the hack for 3.0 and have first rights to update for vuture versions of vB. But if you dont update and give no indication of intention to update, and the hack is unusable for current versions of the software, then someone else can make it usable so long as they give you credit as the original creator.

Basically - if you release - then ignore - someone else can recreate so its usable for new versions of vb.