Question Will Kunena survive?

Yes, thing are slow after kunena 1.08 is launch. But Kunena is done by volunteer programmers without getting anything in return.

Besides even that. Kunena was only launched recently and already devs are hard at work on making it native. Already with the Doom and Gloom? There's no cause for such speculation this early in the game.

But true. The devs worked HARD to get 1.0.8 out at a frenzied pace at the cost of a lot of personal time and man-hours. If you want assurances Kunena will survive, do your part to help.

I figured this might ruffle some feathers. Sorry about that. Despite the ruffling, it did help assure me that things continue to move forward and involvement is strong. I do feel strongly that lots of communication can only help build the trust and increase the following/support. If everything on the changelogs was compiled into weekly or shorter tweets, then those 270 twitter followers would easily see that this is a very active project and the 270 will probably increase to bigger numbers quickly.

Yes, all of the info is probably in the forums somewhere, but not all of us dig through all the posts. Yes, I would love to help support the project but I don't know squat about code (that's why I like joomla, themes, and kunena). I wish I could send some money but that isn't how this is set up. I pay for jomsocial, jomcomment, myblog, rocketthemes (joomla and phpbb).

I'm not a disgruntled trouble maker. On the contrary, I have a huge interest in seeing Kunena work and grow. I'm just trying to give a different perspective - that of the non-coder who builds an occasional site. I see joomla and associated components eventually becoming the new blogger for casual users. Forums are the obvious weak point for joomla and I think an integrated forum (vs. bridge) is the way to go. I look forward to the great new releases that the Kunena team will provide. All hail Kunena.

waitinginvain,
I think you raised a valid point. I recently had to decide on a forum for my Joomla install. I used Fireboard before. Anyway, it wasn't until I rebuilt my site using J1.5 that I realised just how thin on the ground forum options were for Joomla. I found that fireboard had gone, Kunena had come, SMF was no longer usable with Joomla due to licencing.
Initially, I decided on PHPBB with a bridge but it was way too complex for me.
Anyway, I gravitated back to Kunena and my choice sits firmly with Kunena.

This is why your question IS valid as I am sure it is in the minds of anybody that has investigated the state of available forums recently, it is a little un-nerving.

Don't be scared to ask in the forums. One of the Mods will undoubtadly come back at you with a grizzle, but ignore him, it's just what he does. If anything, that is the way to turn people away from Kunena.

Let's all smile, be happy and use Kunena:woohoo:
:woohoo:

I also felt like this was a reasonable question. I keep checking the blog, twitter, and checking several places within the forum. I think the biggest thing is just communication. I wouldn't have known to check the SVN, but I do know the last blog was on 2/17 and the last tweet on 3/6. I think what everyone wants to see is the Kunena project be very successful and survive, but I think what people fear is a lack of communication. I think that's kinda what happened with Fireboard. No one really knew what was going one because there wasn't allot of communication and pretty soon the project is dead.

I personally, am very thankful for Kunena, I just wish there were more tweets or blog posts stating that 16 bugs were found and squashed but there are 12 more items that need fixed before stable or something to that manor.

For being a Kunena developer I can probably comment on this one:

We worked very hard to get Kunena 1.0 stable out. Basically it meant that two developers: me and fxstein were spending all your spare time to build a stable version. It basically meant sleeping less than 4-5 hours almost every night and forgetting our families and children.

As you may guess that cannot last forever. I was becoming very tired and my wife was not very happy with my new hobby. Being awake all the nights is not good for your job either. So after getting 1.0.8 out, we needed some time to recharge. It didn't mean that the development stopped, but there was a major slowdown.

In general we have a bad issue in this project: because of the sudden popularity we don't have resources to give support and to write new code at the same time. Reading and answering messages takes about 4-5 hours every day. So for core programmers over half of the time goes to support.

We need to solve this major problem. Luckily, there are active users, which help us, but they cannot answer to every problem. Do you have any ideas how to make support more efficient, so that developers can do what they know the best: write new code?