!http://www.jivesoftware.com/skin/images/spark-skin-sshot.gif! The Spark Skinning Service has been a hot topic here at Jive for the past couple of weeks. The service is not yet ready to serve up customized builds of Spark 2.5 (it will be ready late May) and it turns out that one small change to the service will make it much easier to keep the Skinning Service up to date with the latest Spark release. What's the change? Removing the ability to change the color of Spark. So in the interest of staying in sync with Spark releases, we'll be removing this functionality.
We have also decided to stop selling Spark Skinning as a stand-alone service. Instead, it will only be available as part of Openfire Enterprise Edition. Current customers of Spark Skinning will not be affected. If you have a subscription to the service already it will continue to work until the current subscription runs out, and there is an upgrade path to Openfire Enterprise to keep the functionality after that time.
Spark Skinning is being phased out as a stand-alone service for a couple of reasons. First and foremost, the changes to Openfire Enterprise pricing substantially lower the barrier for small deployments while maintaining value-based prices for larger deployments. The second reason is that the amount of administration required to keep two sets of Spark Skinning accounts functioning smoothly became too onerous. Simplifying to a single account type will help considerably.
As always, let me know if you have any thoughts about Spark Skinning or these changes.
matt
Hmm... personally, I dislike the per-user pricing structure of Enterprise, simply because it kills OpenFire as an alternative for ejabberd in everything but small-scale enterprise IM. For example, if you are in some school, or doing some small community website, but somehow you need a monitoring and/or logging functionality, you have two options:
- Since these things usually have an average of 1000 users (let's say: some schools might have 10000 users, some communities might have only 2-300), spend 15 000 $s per year just on jabber - not recommended, if you don't have income.
- Use a jabber server which has archiving / monitoring functionality built-in at no cost, and try to make it authenticate against your current architecture.
Personally I think there's a lot of space between the two which is needed to fill, not to mention that OpenFire has a far more conveninient interface than anything else in jabber server market I know of.
I think that there are organizations what would pay for an easy setup, but not that price, simply because it's based on user number, not about efficiency / utilization.