Now that it's been announced to the Arena community developers I can discuss the news: CCV has decided to branch away from the Arena core code base.
It's difficult for me to talk too much about this situation, since I'm pretty close with Jon and David, and I've got friends over at the Arena HQ in Tennessee. I've also been involved in the Community Developer Board for the past two years, so I've been able to listen in on many of the discussions between CCV and Arena. I think it's probably safe for everyone to assume that there is at least some blame (not even sure blame is the right word) on both sides. Also, based on some things I've heard, both sides believe they will be unshackled a bit by the breakup. Undoubtedly not having to worry about each others changes will eliminate some additional work they've both been having to deal with, but I personally believe this will probably come at a cost.
Regardless of the reasons that brought CCV and Arena to this point, what will this mean to Arena?
Originally this was going to be the end of the post and I was going to initially refrain from giving my opinion. But after several days of reflection I've decided to be the first to chime in...
I think without proper guidance and strong, decisive leadership there is a danger that Arena could become what many other older ChMS products became: dull, convoluted, complicated, and bloated. But I think there is definitely hope...
Yes, CCV originally created what we now call Arena ChMS. They are the masterminds and designers behind most of what it is today. We all have David and Jon to thank for this. And the guys at Arena definitely made it a product and added various regular features and many administrative features. As much as I'd like to think that CCV has been directing the future of Arena/Arena-features, you could make a case that this really has not happened as much over the past 2 years. I do believe the relationship they shared allowed CCV to influence the overall product to a degree and a continued commitment to that relationship could still have a similar effect. Even so, CCV's branching will eventually mean that their modules** will not be compatible with any of our Arena installations.
I believe the key to Arena's future is what the community does. It's the community that makes Arena unique.
When I read Joel's recent post I was reminded of this fact. Thanks Joel! What other ChMS system allows you to pick between three different check-in solutions? As more developer churches come aboard and create more solutions/modules, we all win. However, now more than ever - the community's role must increase. And it's not necessarily easy or free. It will mean more focused, thoughtful discussions. More energy spent on packaging and documenting your modules for others. More communicating and coordinating with others. More of everything.
Trust me -- it takes time and energy. If you do not put in the time, it will not just happen automatically.
Will the community rise to the challenge? I believe it will.
[The other great news is that Arena has finally established a single person to be the Product Manager -- and it is Mark White. I'll cover this in another post.]
** Jon and David tell me they will actually still do some development on the standard Arena product too -- if not during their work week, on their own free time. And so they will still be part of the community. So, be on the lookout for some of this great stuff because I recently got a glimpse of some of it.