PDA

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

Alfa1
07-15-2007, 05:03 PM
It would be handy if the modification opening post that lists details about the modification like:
Supported, Installer included, Uses Plugins, Template changes, Additional files, would list how many bugs reports are open.

I gather this can be done by either give users the functionality to mark their post as a bug report or to use Jelsoft's project tools.

I see that many post on vb.org's mod section ask the same question, if the modification works well and if there are any open bugs.

IMHO project tools could greatly enhance vb.org. Not only with bug reports per mod, but also feature requests per mod.

What do you think of this?
Paul M
07-15-2007, 07:46 PM
We don't have bug reports atm, so there is no number we could display.

As for project tools, yes, we will be looking at them, but remember, vb.org is not run by full time staff, we all have real jobs and have to fit this into our spare time.
Alfa1
07-15-2007, 11:21 PM
We don't have bug reports atm, so there is no number we could display.
I know. That's exactly why I am requesting it.

As for project tools, yes, we will be looking at them, but remember, vb.org is not run by full time staff, we all have real jobs and have to fit this into our spare time.
You must be very busy with this site. Many thanks for the effort you all put into it.
Phalynx
06-30-2008, 01:40 PM
I'm also interested in having project tools installed here with a project for every bigger modification. What is "bigger"? Maybe with at least 200 installs.

Currently I have many modification but only spare time to give real support. A project in project tools would be great to collect bugs, suggestions in one place. A thread is only limited to this.

A single Forum for bigger modifications has not succeeded. Is ibProArcade the only modification that can be listed in "Premium Modifications"?
Paul M
06-30-2008, 03:42 PM
The idea of Premium Modifications was abandoned quite some time ago, there were a number at one time, but ibProArcade is the only one still in active use, hence why it still exists.

As for project tools, yes it would be nice, but not likely for a long time yet (for the original reason given). The next "big" thing we will be doing is the upgrade to 3.7, and thats still quite some time away atm.
Phalynx
06-30-2008, 06:12 PM
That's really pity as it would enhance vb.org a lot. Let's see what the future brings...
nexialys
06-30-2008, 07:26 PM
the future will bring a site upgrade, and i hope there is less and less features plugged-in... because the site is actually loaded with so much features it takes months to upgrade... this is the anti-thesis ofthe ease of upgrade advertised by Jelsoft...
King Kovifor
06-30-2008, 09:47 PM
I wouldn't say that. It is just the custom modifications take a while to ensure everything works.
nexialys
06-30-2008, 10:48 PM
that's what i say... having all your modifications switched to products --- like 95% of the other coders who have upgraded their mods... would make this site more reflective of how vBulletin is able to handle upgrade and updates...

one thing would be to provide the coders here with the hacks you have no time to upgrade so we can work them out... it would help you out a lot, and would show everybody that this community work together instead of competing for no use.
Paul M
06-30-2008, 11:16 PM
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.
Ideal Web Tech
07-01-2008, 05:12 AM
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
07-01-2008, 05:25 AM
it would be nice to see vb.org use the project tools, but it sounds like a lot more work for mods
Alfa1
11-18-2009, 06:20 PM
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
11-18-2009, 10:43 PM
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
11-18-2009, 11:39 PM
So basically vb.org needs Project Tools functionality but combined with the modification thread functionality.
Paul M
11-19-2009, 08:31 AM
Correct. :)
ragtek
11-19-2009, 08:36 AM
Something like http://www.vbulletin-germany.org/showthread.php?t=4354 ^^
On vbulletin-germany.org the "bigger add-ons" have a own project (http://www.vbulletin-germany.org/project.php) were the authors can track the bugs,tracks, etc...
Paul M
11-19-2009, 08:42 AM
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
11-19-2009, 09:01 AM
We had something in place for the bigger projects. Currently only ibProArcade (https://vborg.vbsupport.ru/forumdisplay.php?f=170) 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
11-19-2009, 09:01 AM
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.