Microsoft announced a new interoperability approach, opening up previously secret specifications and protocols to open source developers (and heroes), providing a covenant not to sue them for development or non-commercial distribution of implementations of these protocols.
Am I a visionary? by osse
The Open Source Interoperability Initiative is just started, and the EU seems skeptical on Microsoft sharing plans, as is Red Hat, while Groaklaw recaps us on Microsoft’s promises. ArsTechnica reports that the EU investigation seems to have played a role, stating that Microsoft may not be up for yet another fight with regulators.
Besides the ballot resolution meeting, I doubt Microsoft is changing everything so that it can stay the same. Beyond any possible speculation of the real meaning of the non-commercial covenant, Microsoft today is probably giving up with its vertically integrated corporation approach.
The Microsoft’s de-verticalization has begun, Microsoft opening its interfaces and APIs will allow applications to be hooked more easily its products. This is a huge change, and it will affect the IT market at large. Before exploiting it further, and how and if it will impact on the open source market, a little background.
One of the most promising value of open source software is that its licensing enables coopetition. The neologism refers to a market situation in which two or more organizations compete and cooperate simultaneously. The non-rivalrous nature of software distributed under an OSI compliant license is the basis on which cooperation among open source firms can take place.
The Observatory of European SMEs, given the importance of High-tech SMEs in Europe , analyzed success factors and among them the role of networks:
Studies dealing with barriers to networking and co-operation in the area of high-tech SMEs identify a number of
reasons hampering the formation of networks among these enterprises. Many of these factors are the same as for SMEs in general, e.g. different objectives and expectations among partners and differences in enterprise culture. Also, the lack (or the importance respectively) of a ‘co-ordinator’, e.g. a larger leading firm or an agency, is relevant for the networking among high-tech SMEs, too. [..] small and large high-tech enterprises seem to have different motives to engage in networking: for high-tech SMEs the main motivator is to achieve (quick) access to markets and credibility. Hence, networking is seen to be a ‘necessity’ for high-tech SMEs. In contrast, for large high-tech firms the reasons to engage in networks include primarily access to competitive R&D and technology. [..] These fundamentally different approaches imply that smaller firms are rather oriented towards short term and concrete results. SMEs want projects to have a quick path to market and achieve returns as quickly as possible. However, networking often requires a lot of time-consuming communication and efforts before actual results are achieved and benefits are not visible immediately. But SMEs have difficulties in allowing time and delays for different processes and exchange of information. A further consequence is that SMEs prefer to form one to one collaborations rather than collaborations between groups of enterprises.
Open source consortia and other “loosely coupled†organizations among open source firms could definitely play an important role to foster communities, but as a matter of fact they suffer from above mentioned limitations.
Despite the recent rise of interest toward coopetitive alliances, effective coopetition doesn’t occur too often. Strategic-business literature lack of descriptions explaining how organizations should manage a coopetitive relationship, and how they in practice manage to compete and cooperate with other organizations.
How co-operation and competition could possibly merge together to form a strategic interdependence among firms, eventually giving rise to a coopetitive system of value creation?
ZEA Partners experience shows the importance of the creation of an intermediate organization, providing rules and regulations, aiming to secure the long term survival of the association. ZEA Partners is on duty to resolve conflicts, and considering that fields of expertise are not complementary, one of the most important reason to become a ZEA partner is definitely to get a more formal status. Organizations within ZEA Partners are willing to cooperate on activities that are far away from applications that could generate an income:
It is knowledge that is not close to an application, and that means that it is knowledge that can easily be shared.
Therefore OS firms sharing the same knowledge can easier co-operate through customer distance (i.e. the closer to the customer, the more competition). The rules and regulations that an intermediate organization could issue don’t include licensing to manage the coopetitive relationship.
But the concept of competition might include relationships with suppliers and customers, rather than restrict coopetition only to relationships among cooperating firms that compete in the same market and want to reach the same customers.
Customers asking for not differentiating IT solutions or not competing (e.g. public administrations), could take advantage of the possibility to share with suppliers assets like source code and also blueprints to implement such technologies. Allowing them to reuse by other customers might turn to be a viable strategy to obtain enhancements and discounts.
Suppliers on the other hand can take advantage of customers’ ability to set user requirements and through blueprints can turn their customers in testimonials, reporting about such best practices.
Now, how does the Open Source at Microsoft fit into the picture?
Microsoft recently launched another initiative, the NXT partner program geared towards Open Source ISVs. The program is aimed at providing open source ISV with information to make it easier to develop and sell open source software on Windows. Microsoft NXT partner provides ISV with a range of services, ranging from marketing support to technical advice, including also business model definition and channel delivery plans.
All in all the Microsoft NXT partner program, the Open Source Interoperability Initiative and the just started Forge New Powers to me seems to be part of a general strategy. As a matter of fact there is a lot of free and open source software deployed on Windows, and Microsoft is refocusing on fostering value creation also partnering with open source firms.
I wouldn’t be surprised if Microsoft will eventually give rise to a coopetitive system of value creation in the next future, helping IT firms to exploit the role of networks, as none else could possibly will to do.
Am I a visionary?
Technorati Tags: open source microsoft, microsoft, open source interoperability, NXT, open source hero, Forge New Powers, commercial open source, open business
Open Source Piracy? No thanks! by mrs.reed
A beautiful Long Tail by 
priaterus and 
Social Responsibility by 
Open Source: our potential? by 
Roberto Galoppini, 
Invitation by 
Peter Vescuso 7:55 pm on August 19, 2008 Permalink
While the appeals court decision is certainly an important move for software creators, and one that organizations should review carefully, it should not scare people from using open source within development. More and more companies that are using open source code are doing so in the right way, so that licensing and other obligations are met. Black Duck sees the court decision as more of a wake up call to software development organizations without a proper open source use policy in place, rather than an industry-shifting milestone.
Open source is becoming an increasingly important and strategic component of today’s software development process – enabling faster and more cost effective product evolution. Underscoring its importance, Gartner recently found that 47% of the companies surveyed say they are using code from external sources. A large number of these organizations have well-established policies for open source use and adoption that take into account license obligations. The combination of proprietary and open source software has created a hybrid software development model that definitely requires careful attention to licensing – but can be managed.
Developers and their organizations should have a clear understanding of what’s inside their software components, no matter how seemingly insignificant, in order to avoid legal, financial and business ramifications. Open source code analysis is not about policing developers or prohibiting use, it provides a clear, concise and efficient way to track open source use and license restrictions- a necessity of doing business in a world in which software development is an open field.
-Peter Vescuso, Black Duck Software