It sounds easy on the surface, but what if the bug is not confirmed and cannot be reproduced? What if it is a duplicate and someone else has already reported it, or we already spotted it internally and fixed it? What if the bug report is regarding a code-level comment block that needs to be updated - does that count? We don't typically treat such things as "bugs" since it doesn't affect the quality of the software, however it can be helpful for developers and we would generally "fix" the problem. It would be extremely hard to keep up with and account for the many, many nuances of what does and does not qualify as a bug.
If bug can't be reproduced then it's not a bug as simple as that.
Anything wrong spotted by end user which requires change in IPS software anywhere = bug. That's just my opinion. And off course if comments in code need to be update then it's not a bug ..Just create new status: Comment Update.. so those will never be counted in confirmed bug reports.
I thought IP.Content is powerful so please excuse me if this suggestion is not possible since I am not an expert in php/sql. Wouldn't be possible to create a custom script which pulls out number of confirmed bug reported by user in a xx period amount of time?
What you guys are doing right now is.. heavily depending on end users to report most of the bugs and then same old story.. Oh we have released beta .. feel free to test it. No I don't need to test if someone can purchase anything from store or not.. It's basic feature and it should work out of the box for Nexus.
If you are facing a problem with the software, please be sure to submit a ticket so that the issue can be addressed.
I do always but it's no fun when user PM's me after each Nexus update that they can't purchase anything. Since last 3 nexus release that's what I am doing. Creating support tickets and that's annoying. Each time same reply and then wait begins when Mark fixes it or tells me patch available in next release.
We've reviewed your request and unfortunately, it is going to require further investigation. I've escalated your ticket, and it will be addressed as quickly as possible. Because of the advanced nature of your request, please note that it may take longer than usual to fully address your concern. I apologize for this delay and appreciate your patience.
We've done similar things in the past. Our experience has been we get a flood of people who get the beta for the perks and then never use/report anything.
I believe we will have a program for 4.0, which will undergo extensive testing throughout the process due to the massive overhaul.
Why not just give the benefits after/once they have reported 50 confirmed bug reports / period of xx amount of time? Normally QA engineers make at least 30$/hr and above.. so giving out 25$ gift coupon for someone reporting 50 bugs in your software is not big deal and I believe is fair trade. You save on QA's which I believe did horrible job on each Nexus release. Each Nexus release is mess compare to other add-ons. Sometimes front end doesn't work and other time no one can buy products from store. Even in new release i am having issue where users can't buy anything from store. What's the point of store/Nexus where users are unable to buy the things? I believe at least this show stopper bugs should be ironed out before release.
Posts, namely hundreds of thousands or millions+. This is how most big board things qualify on other sites.
No offense to any big board admins.. but i have seen some so called big boards with million posts and they have thousands or even say 1,00,000 posts with stupid topics.. Ex being "Let's count to million" or "Lets start countdown" etc etc... and their u go with min 20,000 posts per topic..
Now some admins don't encourage those things on their forums.. and some also keep pruning members with zero post every 3-6 months. What my point is just higher post count doesn't mean board is big.
More or less, I have seen couple of good linux sys admins who don't run any board but still provide help around the forums. Ex: being Garry.
First IP.Portal then IP.Shoutbox, then probably IP.Tracker and then prolly IP.Converge.... All good things doesn't last forever. I am glad we have people like Michael who took the shoutbox and is providing updates and fixes.
After all it's all about $$ so can't blame IPS either.
Actually, someone could use sprites right now in their custom skin if they wanted to. Note that I'm not aware of any custom skins that do, but that doesn't mean skinners can't.
May be they are not using it because it's not in default skin? If it's available in default skins and once admins will see page loading or speed difference, they will ask for it and based on demand skinners will provide it? May be skinners are not providing it since it's not in default skin? dunno..
What I do with the default IPB skin is add in some CSS3, for example the maintitle's can be easily converted into a CSS3 gradient.
Can you please post how to in resource section so newbie people like me can follow ?
I for one use stock skin and if provided with sprites I will use it. I have seen plenty of forums using IPB default skin. Now, if someone needs to use their own skin, they get 2 options. Either they can add their own sprites or just use images.
If the option to use sprites is available admins will use it.. if it's not available how someone is going to use it to begin with? And who knows once sprite are added, skin coders will also provide sprite skins? may be they will charge extra for it but i guess it will be available.