vb.org feature request: Show number of open bugs in mod description

[Ideal Web Tech]

Originally Posted by Paul M

Most of the mods are products, the rest are almost all in a small number of seperate files. I think we only have about six actual vb file edits. The thing that takes all the time is templates, over 30 templates are customised.

Thats why I got tired of offering more then just 1-2 styles as my site I can easily customize an ungodly amount of templates.

[Brandon Sheley]

it would be nice to see vb.org use the project tools, but it sounds like a lot more work for mods

[Alfa1]

I know this is an old thread. But my request to show the number of open bugs in the OP, would still be a very good enhancement for vb.org

Additionally, it would also very useful to have a way to see open functionality requests. For example: I doubt that anyone knows what functionality requests are open for any of the modifications that have hundreds of discussion pages.

As IB / vb.org admins are currently looking into improving the site, I'd like to bring this under your attention.

[Paul M]

As previously said, it would be impossible until such time as we have a proper system for recording bugs, same for suggestions. As before, the preferred method would be PT, even tho its not an official product anymore.

[Alfa1]

So basically vb.org needs Project Tools functionality but combined with the modification thread functionality.

[Paul M]

Correct.

[ragtek]

Something like http://www.vbulletin-germany.org/showthread.php?t=4354 ^^
On vbulletin-germany.org the "bigger add-ons" have a own project were the authors can track the bugs,tracks, etc...

[Paul M]

Presumably they are manually created, rather than some auto system.

It may be that we have to start off like that. The problem is defining which products are allowed a "project". No matter what criteria you set, someone will get upset that their product doesnt qualify.

[Marco van Herwaarden]

We had something in place for the bigger projects. Currently only ibProArcade is still marked as a larger product. We currently do not add new projects to this anymore as the biggest problem here was that if a project did not qualify anymore (abandoned for example) we couldn't merge all the threads made in such a sub-forum back into a single thread like all other regular modifications.

[ragtek]

Originally Posted by Paul M

Presumably they are manually created, rather than some auto system.

It may be that we have to start off like that. The problem is defining which products are allowed a "project". No matter what criteria you set, someone will get upset that their product doesnt qualify.

Yes, i know what you mean and i'm 100% with you.
Not every add-on would need this.

Maybe something like this:
The author could have a checkbox where he can "ask for a project" in the 2. form on releasing a add-on.
So if he thinks that his add-on is "big and have potential" he can set it to yes, then the mods on vb.org can decide if it's ok or not and then they can "allow" it and a project will be created automaticaly.