[KW802]

Originally Posted by Cap'n Steve

I'm actually in this situation right now. I took over a hack (with permission) and released a new version. However, the old thread is still there and it can't be updated because no one seems to be able to get ahold of the original author.

What I'd do is create a vb.org license that applies to all submitted hacks and basically states that if you're inactive for a certain period of time, others can take over your hack as long as they include you in the credits.

Only problem with this is that then the risk is that there could be multiple people claiming ownership of hack so all of a sudden there are multiple versions of the same hack.

Personally I like the basic idea of this thread but if a system was put into place I'd prefer that's a clean break.... that hack XYZ by user John Doe is transferring the overseeing of it to user Jane Doe; that way there is still only one version of the hack and it's clear who has taken over development of it.