Good question! I’m wondering myself. I just posted this comment to Rachel Happe’s post on LinkedIn with the news:
Hard to see the positives for customers — either Jive or Lithium. Lithium just bought code from their biggest competitor. But the Jive-x and Jive-n code bases are nearly identical, so how do you split this baby in half? Which current Jive developers, consultants, and support staff will move to Lithium? Who gets the A-players? Then once they’ve split, you’ll have teams that have worked together for years with common technical expertise working on common code in two different companies. Will they continue to collaborate? What if the best expert for a problem happens to have ended up in the other company? Do the code bases fork?
Will the Jive-x code survive at Lithium? Or is Lithium hoping to convince their new Jive-x customers to move to the Lithium platform? Lithium is missing basic structures that Jive depends on, so there will be data conversion issues as well as retraining issues for community members (meaning cost and aggravation for Jive-x customers as their community members chafe having to learn the new platform and complain about “missing” their favorite Jive-x features.)
And of course what happens to companies that have deployed both Jive-x and Jive-n solutions for their customers and employees? Will the code remain similar? Or fork off in different directions? Will there now be separate contracts, support agreements, and Jive experts in customer’s IT organizations?
Somehow doesn’t seem sustainable long term. Much depends on how the two companies work together and where they each intend to take these inextricably interwoven solutions into the future.