[Lizard King]

Originally Posted by Brad

While a lot of modifications don't require it; I've been ranting for years about the fact that we need "project webpages" like they have on sourceforge. For anyone that isn't up to speed with what I'm talking about see; http://sourceforge.net/projects/sierra-php/ for an example.

Some key things I've been wanting to see for awhile;

- Ability to upload/host multiple copies of the software. I know this is possible with the current attachment system but I'd like to see something more user friendly (like having them listed by version number).

- Sub-forums for modifications. The main ones we need; Support, Bug reports, General Development.

- Ability to browse a modifications source code before downloading it. Hosting the modifications in a repo system. (I'll get to this in a second).

- Ability to have an "FAQ" on our modification's page.

- A way to update users outside of sending e-mails and editing threads. We need a way to post news about our modifications.

Going back to storing modifications in a repo; It'd be neat if I could download and install modifications directly from my admincp (*hint*).

I agree that modification pages can be improved. Supplying each modification a page of its own is a good idea but i honestly dont think it is possible to handle this while allowing comments and bug reports on same place. That why it may not be possible.

My main reason for suggesting this is directly related to vBulletin.org's Coder ranking system. https://vborg.vbsupport.ru/vborg_mis...eleases&type=1 follow this link and you'll see what i mean. nearly 90% of this releases are duplicate of even 3.6 version nearly. This way coders double or triple their release and install number.

I personally donot release anything at vb.org for various reasons but people depend on coder rankings for paid modifications which may mix their mind up.

Danny's tag solution may work or custom fields can be used such as coders can choose which versions the mod will work with.

This is also a problem on coders side since he needs to support the product in two different threads.