Picture this: Your company is ticking along nicely, making use of a reliable and well-engineered piece of software to support some important business process, when suddenly it becomes apparent that all is not well in the project’s developer community. A fork is in the cards, and the very future of the project hangs in the balance.
Before we get to the crucial questions of whether a fork is really such a bad thing and what a CIO should do when faced with one, let’s first be clear about what we’re talking about.
