Community Development Features...
 

Allow modification authors to appoint others to work on their code in a true community development method. The original author would become project manager and could allow others to submit work. That submitted work would bubble up to the top in the form of new releases, fixes and other changes.

This is a good idea, i actually already walk around with such ideas for a long time now. But if it has to be done in a good way, then this is not so easy.

But with vB4 the whole modification process will be rewritten, so we can keep this in mind and see if we can add this to the list.

I LOVE this idea ;)

I'll be patiently waiting for vb.org to upgrade to vB 4.0 AND implement!

(I know it might be a while but a great idea regardless ;))

Id love to get involved in this. Sounds like something that would get more people involved. And this also gave me a great idea for my next forum project. lol wow cant believe i came up with something "different" and original for a forum concept.

This would be even better if Project Tools could be worked in somehow...

And PT certainly has been discussed. :)

Bare in mind that if by some reason a disgruntled member where to pull his/her scripts from the org which happens and who's agreed for the re-use of his/her code wouldn't have any right over hybrid copies of scripts or takeovers if they agreed on this.

This feature should be an opt in rather than an opt out option.

Most people who have been around for years won't allow the re-use of their code so I think they would see the potential cons that could arise from allowing others to work on your code.

Hasn't this been discussed before, and even talked about being implemented before, and even the use of PT to keep track of it all?

Pretty sure it always got shot down due to lack of time, or whatever

I don't remember anywhere it got "shot down". vBulletin.org is certainly going to be upgraded in the future - and as Marco has mentioned above, things are going to be re-jigged.

Excellent idea, and would allow 'addons' and 'translations' to be included in the release and no longer have to be their own individual threads (which happens, and is in my opinion overkill).

I assume that "lite" and "free" releases that have a paid alternative offsite, will have to be excluded from this list.