Results 1 to 1 of 1

Thread: Why we won't implement your suggestion

  1. #1
    Join Date
    Aug 2007
    Location
    Utah, USA, Earth, Milky Way
    Posts
    7,502
    Blog Entries
    3

    Default Why we won't implement your suggestion

    Catchy thread title eh? This is more to inform you why we MAY not implement your suggestion(s).

    First, let's be clear that your suggestions are VERY welcome and often suggestions help us improve the forums. There are a lot of very good suggestions that don't get implemented however, and this is an attempt at an explanation as to why.

    We've chosen to implement vBulletin (http) and Typhoon (NNTP) software for these forums. Most of the suggestions received are for the web interface so would impact vBulletin. You also need to know that the servers reside in the Novell Data Center which has many benefits such as fail over, disaster recovery, monitoring etc. but it severely limits who has access to test and implement changes.

    vBulletin issues sofware updates regularly....once every one or two months. When these updates are installed, it will look at the template files (the "style" or look and feel) and if they haven't been customized, it will update them. If they have been customized, it won't update them but tell us to do them manually. One "style" is made of many template files. To update the old "openSUSE Default" style (customized) took 4-8 man hours for a relatively minor update and 36-48 hours for a major update. When we updated to vBulletin version 4, we did as little customizing of the default template for this reason. Human resource to do these updates is very limited so we want to have as little customization as we can get away with. Human resource to build and implement additional functionality into the system is almost non-existant and would cause even more work come update time.

    The bottom line is if we get suggestions that are easy to implement with little to no customization we're more likely to do them than suggestions that require some developement and/or require additional modifications to our templates......even if they are really, really, really, really good suggestions. Don't take it personally if we don't implement your suggestion.

    In regards to our authentication system, session timeouts, etc., we use what is standard for the openSUSE project. The system is the same one used on the wiki and other login areas. It makes for a unified authentication experience across the sites.

    One last thing. We seem to always get requests for us to enable a thread to be marked SOLVED like some other distro forums do. One of the problems here is that things evolve so what was solved a year ago may be a totally different issue/resolution now. We like to leave all our threads open so people can add content or question the resolution at any time. Also, "Solved/Unsolved" is something that is misleading and causes users to think "hey, this problem is kinda like mine, so the solution must apply". More seasoned users know that every problem is likely to have its own nuances and differences, and a solution for one user isn't likely to be a solution for another.

    Anyway....there you have it. I hope it doesn't discourage you from making those good suggestions because sometimes we can find a good hack addition to vBulletin that we can install or otherwise find some way to do it without headaches.
    Last edited by kgroneman; 06-May-2015 at 11:27.
    My computer always used to beat me at chess, but it is no match for me since I changed the competition to kick boxing

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •