What to do, what to do...
Well this thread is more of less just meant to be more of a fact finding mission on what needs to be addressed and make UBBDev a the community it once was.
This is just food for thought and really a over view without going in to heavy detail (other wise I would be competing against War & Peace)
First I would change the terminology around a bit on what this site promotes. Hacking is a term that has a misnomer and goes back in to the hay days or exactly what it means. I tend to say "modification" or "modifying" when I post and think over all it would be an easier "sell" to the end users to come by and see what can be added with little work and really no experience in programming.
Next is the need to keep the current developers. While they each have their own modifications, I think it might be beneficial to move the current set of modifications in to a UBBDev pool/repository. It seems to be the same modificaitons over and over with nothing really new or exciting. Can't blame anyone as IP seems to be releasing versions fast and ferious and just porting to the next version is alot of work. By creating a pool this will allow those with more time to not only port the modificaitons but to also add on features. Of course proper credits will have to be maintained through documentation of the modification.
New blood. There seem to be fewer and fewer developers as time goes on. People move on, have other interests, etc. How about the current developers start a scripting forum/learning center/workshop where it starts with the basics and a user would need to sign up and works around time frames (i.e. first course runs x amount of weeks and no one can join until it is over and the next one starts) The developers can then share their knowledge and maybe poeple like me can then start scripting and contributing more to the community. Homework can be handed out to be able to judge where each person is in their grasp of UBB & scripting. I knw this would take alot of time and energy but it can be done over a period of time with a particular course being spread out over days or a few weeks depending on complexity. I know for one, I would like to be able to do this and I know I have seen others post wishing they could also help out.
Then there is a need to a dedicated database of all modificaitons ever made or that can still be found. Just linking them to the developers release thread is not enough. There needs to be a framed table with the file and as much of a description as possible (i.e. finished, still needs, should add, etc)
There also needs to be a resource list as to sites that are helpful with knowledge or things that can help run your site easier. I am starting a list for the next e-zine but I am sure many of you have your favorites. Care to share sie you have found helpfull?
UBBDev might want to consider breaking in to 3 distinct areas. 1. Stock current release of UBB so poeple can see what it is and how it works. Should also include ability to see the admin control panel but locking things so they can not be changed to effect board access or uptime. 2. Current beta release with the same things as #1. 3. A modified UBB with all the bells and whistles of the known released modificaitons. Developers sites come and go as the developers move on. Seeing how a particular modification works is key sometimes prior to installing it.
Welp whether good or bad there are my thoughts. Feel free to add or rebuke. But something needs to be done to kick start this place back into high gear as lately it has been a ghost town.
