{"id":1636,"date":"2018-11-02T17:57:56","date_gmt":"2018-11-02T22:57:56","guid":{"rendered":"http:\/\/coevolving.com\/blogs\/?p=1636"},"modified":"2018-11-09T12:21:37","modified_gmt":"2018-11-09T17:21:37","slug":"optimism-for-open-sourcing","status":"publish","type":"post","link":"http:\/\/coevolving.com\/blogs\/optimism-for-open-sourcing\/","title":{"rendered":"Optimism for open sourcing"},"content":{"rendered":"<p>The <a href=\"#humphries-2018-ibm\">October 2018 acquisition of Red Hat by IBM<\/a> gives me hope.\u00a0 Both IBM and Red Hat have been champions in promoting open sourcing behaviours.<\/p>\n<blockquote><p><em>Open sourcing<\/em> is an open innovation behaviour related to, but distinct from, open source as licensing.\u00a0 [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0chap. 1, p. 1].<\/p>\n<p>The label of <em>open sourcing<\/em> frames ongoing ways that organizations and individuals conduct themselves with others through continually sharing artifacts and practices of mutual benefit.\u00a0The label of <em>private sourcing<\/em> frames the contrasting and more traditional ways that business organizations and allied partners develop and keep artifacts and practices to themselves.\u00a0 [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0sec. 1.2, p. 5].<\/p>\n<p>The label of <em>open source<\/em> is most readily recognized from software development. An open source license allows free use, modification and sharing.\u00a0\u00a0<em>Open sourcing<\/em> is a norm where the resources of system internals, e.g. artifacts and practices, are shared in a community beyond the originators.\u00a0\u00a0<em>Private sourcing<\/em> is coined as a norm where the resources of system internals are reserved within a privileged group.\u00a0 [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0sec. 1.3, p.6]<\/p><\/blockquote>\n<p>This deal continues a socio-economic trajectory by IBM &#8230;<\/p>\n<ul>\n<li>starting in 1993 with the Lou Gerstner expectation of &#8220;open, distributed user-based solutions&#8221; after the Chantilly meeting [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0sec. 2.3.1, pp. 55-56];<\/li>\n<li>with the 1998 IBM open sourcing with Apache while private sourcing Websphere [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0sec. 2.3.2, pp. 56-59], and<\/li>\n<li>with the 2000-2001 investment of $1 billion in Linux [<a href=\"#ing-2017-open\">Ing (2017)<\/a>\u00a0sec. 2.3.3, pp. 59-62].<\/li>\n<\/ul>\n<p>IBM&#8217;s 2018 acquisition of Red Hat can be compared with the <a href=\"https:\/\/www.nytimes.com\/2009\/04\/06\/technology\/business-computing\/06blue.html\">2009 IBM withdrawal of a $7 billion offer for Sun Microsystems<\/a>. That was followed immediately by an announcement of\u00a0<a href=\"https:\/\/abcnews.go.com\/Technology\/story?id=7395780\">Oracle to buy Sun for $7.4 billion<\/a>. Years later, it was revealed in court that &#8220;Oracle didn\u2019t buy Sun just to sue Google but to keep it away from IBM&#8221;.<\/p>\n<blockquote><p>[Oracle CEO Safra Catz] explained that Oracle bought Sun because so much of Oracle&#8217;s own product was based on Sun&#8217;s Java, and they were concerned about what would happen if someone else acquired Sun.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Oracle: Did you buy Sun because you wanted to file a copyright lawsuit against Google?<\/p>\n<p>Objection. Overruled.<\/p>\n<p>Catz: No, we did not.<\/p>\n<p>&mdash; sarah jeong (@sarahjeong) <a href=\"https:\/\/twitter.com\/sarahjeong\/status\/732293338720673792?ref_src=twsrc%5Etfw\">May 16, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>By someone else, she later clarified, she meant that Oracle &#8220;was afraid&#8221; IBM would buy Sun [<a href=\"#bort-2016-oracle\">Bort (2016)<\/a>].<\/p><\/blockquote>\n<p>For Oracle, their acquisition was a financial play, with Larry Ellison in 2012 declaring that &#8220;<a href=\"https:\/\/www.wired.com\/2012\/05\/larry-ellison-sun\/\">Sun Buy Paid for Itself, Now We Crush IBM<\/a>&#8220;.\u00a0 In the lawsuits brought by Oracle against Google, Larry Page said that &#8220;a lack of cooperation between tech partners was holding back progress&#8221;.<\/p>\n<blockquote><p>Page blamed a &#8220;focus on negativity and zero-sum games&#8221; for the industry&#8217;s failure to achieve its full potential.\u00a0 [&#8230;.]<\/p>\n<p>Page named the tech giant Oracle as one of the roadblocks to faster progress. &#8220;Money is more important to them&#8221; than having any kind of cooperation, he said [<a href=\"#rushe-2013-googles\">Rushe (2013)<\/a>].<\/p><\/blockquote>\n<p>In December 2016, Oracle was reported to have <a href=\"https:\/\/www.theregister.co.uk\/2016\/12\/16\/oracle_targets_java_users_non_compliance\/\">ramped up audits of Java customers, chasing them for payment<\/a>, six years after open sourcing had effectively ended.\u00a0 By September 2017, an industry analyst declared that &#8220;<a href=\"https:\/\/meshedinsights.com\/2017\/09\/03\/oracle-finally-killed-sun\/\">Oracle Finally Killed Sun<\/a>&#8220;.<\/p>\n<p>With IBM and Red Hat, philosophies on open sourcing are organizationally better aligned.\u00a0 Red Hat and IBM started an <a href=\"https:\/\/www.redhat.com\/en\/about\/press-releases\/press-ibmalliance\">alliance on enterprise solution in 1999<\/a>\u00a0on x86-based servers, later extended to POWER and z Systems.\u00a0 By 2009, an industry consensus viewed that &#8220;in the long run, Red Hat will have to be subsumed into a large company &#8212; most likely IBM&#8221; [<a href=\"#dignan-2009-is\">Dignan (2009)<\/a>].\u00a0 In the open source ecosystem, the IBM and Red Hat have both taken leadership positions, amongst other companies playing mostly to a lesser degree in the same field.<\/p>\n<blockquote><p>The deal is a good fit for many reasons &#8230;.<\/p>\n<p>Oracle has to hate this deal. Oracle\u2019s Linux (the kernel part) is based on Red Hat. This will definitely cramp Oracle\u2019s style. Most cloud providers resell Red Hat software, so now IBM will be getting money on their business. IBM could be in the position Microsoft has been for the last 30 years. For every PC made Microsoft got money.<\/p>\n<p>Microsoft will hate this deal. Amazon will, too. [<a href=\"#cringely-2018-red\">Cringley (2018)<\/a>]<\/p><\/blockquote>\n<p>Since the <a href=\"https:\/\/www.kernel.org\/doc\/html\/v4.18\/process\/license-rules.html\">Linux kernel is licensed under the GNU GPLv2<\/a>, IBM is free to charge for the software &#8230; just as everyone else is free to charge for the software.\u00a0 There is, however, more money beyond the operating system, in middleware, hardware and services.\u00a0 Companies who have only embraced open sourcing grudgingly may have to learn new tricks.<\/p>\n<p>Reviewing history at IBM, this company has <a href=\"https:\/\/www.ibm.com\/investor\/strategy\/acquisitions.html\">a long history of acquisitions<\/a>\u00a0that have been successful.\u00a0 Following a counterfactual, IBM is absent on a 2016 list of &#8220;<a href=\"#zdnet-2016-cisco\">worst tech mergers and acquisitions<\/a>&#8220;, that includes:<\/p>\n<ul>\n<li><a href=\"#zdnet-2016-cisco\">#17<\/a> Cisco &amp; Linksys<\/li>\n<li><a href=\"#zdnet-2016-cisco\">#16<\/a> Apple &amp; Lala<\/li>\n<li><a href=\"#zdnet-2016-facebook\">#15<\/a> Facebook &amp; Instagram<\/li>\n<li><a href=\"#zdnet-2016-facebook\">#14<\/a> Zynga &amp; OMGPOP<\/li>\n<li><a href=\"#zdnet-2016-facebook\">#13<\/a> Myspace &amp; News Corp.<\/li>\n<li><a href=\"#zdnet-2016-novell\">#12<\/a> Novell &amp; Unix<\/li>\n<li><a href=\"#zdnet-2016-novell\">#11<\/a> Borland &amp; Ashton Tate<\/li>\n<li><a href=\"#zdnet-2016-caldera\">#10<\/a> Microsoft &amp; Danger. Inc.<\/li>\n<li><a href=\"#zdnet-2016-caldera\">#9<\/a> Caldera &amp; SCO<\/li>\n<li><a href=\"#zdnet-2016-hp\">#8<\/a> Hewlett-Packard &amp; Palm<\/li>\n<li><a href=\"#zdnet-2016-hp\">#7<\/a> Oracle &amp; Sun Microsystems<\/li>\n<li><a href=\"#zdnet-2016-hp\">#6<\/a> Northern Telecom &amp; Bay Networks<\/li>\n<li><a href=\"#zdnet-2016-hp\">#5<\/a> Google &amp; Motorola<\/li>\n<li><a href=\"#zdnet-2016-hp\">#4<\/a> HP &amp; Autonomy<\/li>\n<li><a href=\"#zdnet-2016-nokia\">#3<\/a> Nokia &amp; Microsoft<\/li>\n<li><a href=\"#zdnet-2016-nokia\">#2<\/a> AOL &amp; Time Warner<\/li>\n<li><a href=\"#zdnet-2016-hp\">#1<\/a> HP and Compaq<\/li>\n<\/ul>\n<p>On the contrary, a 1998 article provides a case study of IBM and Lotus working together in post-merger integration.<\/p>\n<blockquote><p>What follows are some of the key tenets that I.B.M. followed.<\/p>\n<ul>\n<li><em>Don&#8217;t drag your heels and don&#8217;t look for bargains.<\/em> [&#8230;.]<\/li>\n<li><em>Get the right people to run the show.<\/em> [&#8230;.]<\/li>\n<li><em>Insure autonomy, avoid layoffs and don&#8217;t send in an army of invaders.<\/em> [&#8230;.]<\/li>\n<li><em>Understand the real cultures, not the outside perceptions.<\/em> [&#8230;.]<\/li>\n<li><em>Don&#8217;t damage the acquired company&#8217;s credibility with customers and business partners.<\/em> [&#8230;.]<\/li>\n<li><em>Go beyond peaceful coexistence to successful cross-pollination.<\/em> [&#8230;.]<\/li>\n<li><em>Hold the champagne.<\/em> If the two companies have learned anything, though, it is that success is a hard thing to hold on to, especially in the high-tech sector.\u00a0 [<a href=\"#rifkin-1998-post\">Rifkin (1998)<\/a>]<\/li>\n<\/ul>\n<\/blockquote>\n<p>This was reinforced in a 2009 interview with the IBM executive who oversaw $15 billion in acquisitions of 70-plus companies since 2004.<\/p>\n<blockquote><p>&#8230; successful integration requires taking the time to align the acquired company and the leadership of the parent company on the goals of the acquisition. That clarifies roles, responsibilities, and priorities, so the team can execute the vision of the merger. [Moni Miyashita, Managing Director of Mergers and Acquisitions Integration at IBM] explains that the integration needs to be \u201cfocused on value,\u201d rather than on check lists such as suppliers, IT, and office space. [&#8230;.]<\/p>\n<p>To guide the process, IBM has dedicated \u201cintegration executives\u201d whose full-time jobs are to lead the integration and make sure the activities and results of the merger stay on track. Miyashita says integration executives must have world-class project management skills, a deep understanding of the parent company, and enough clout to be effective and influential with all organizations.<\/p>\n<p>[&#8230;.] What makes a strong leader in this case? Miyashita says, \u201cYou need savvy business people who know how to relate to all levels of people.\u201d A leader needs to ensure continuity of the acquired business, work with all groups supporting the integration into the parent company, be able to drive change with both companies, and execute the business case expectations. What\u2019s more, a leader must be ready to lead.<\/p>\n<p>As for performance management, Miyashita emphasizes it\u2019s important to have formal tracking on the acquisition\u2019s performance, so there\u2019s clear accountability and attention to lessons learned. At IBM, this includes monthly checkpoints and more extensive quarterly reviews. \u201cIt\u2019s a very formal process,\u201d Miyashita says. \u201cIt\u2019s important to have the focus from the top. Having the CEO and CFO focused on our acquisition success ripples down to every deal.\u201d\u00a0 [<a href=\"#huang-2009-how\">Huang (2009)<\/a>]<\/p><\/blockquote>\n<p>Citing leadership and performance management as central to integration shouldn&#8217;t be surprising for managing any business.\u00a0 Does the new world of commercial enterprises actively participating in open sourcing communities change anything?<\/p>\n<p>The research published in <a href=\"http:\/\/openinnovationlearning.com\/online\/\"><em>Open Innovation Learning<\/em><\/a> is theory-building.\u00a0 Three descriptive theories (in three paradigms) and three normative theories (in one paradigm) are developed.<\/p>\n<p>What should IBM and Red Hat do to continue their track record of success? Three normative theories prescribe <em>open innovation learning<\/em>, extending practices that are already in place in both companies:<\/p>\n<ul>\n<li>In a paradigm of <em>co-responsive movement<\/em>\u00a0[<a href=\"#ing-2017-open\">Ing (2017)<\/a> chap.9], IBM and Red Hat should build on their trajectories of:\n<ul>\n<li>(a) Innovation learning <em>for<\/em>, paying attention to:\n<ul>\n<li>(i) <em>Proto-learning<\/em>, continuing operational excellence on current offerings (e.g. Linux) with existing customers and the open source community, as they had previously;<\/li>\n<li>(ii) <em>Deutero-learning<\/em>, extending existing offerings (e.g. <a href=\"https:\/\/www.redhat.com\/en\/blog\/red-hat-and-cloud-native-computing-foundation\">Kubernetes and the Cloud Native Computing Foundation<\/a>\u00a0and <a href=\"https:\/\/techcrunch.com\/2018\/03\/31\/red-hat-looks-beyond-linux\/\">Openstack<\/a>) with incremental improvements; and<\/li>\n<li>(iii) <em>Trito-learning<\/em>, cocreating new offerings (e.g. <a href=\"https:\/\/www.coindesk.com\/red-hat-eyes-blockchain-for-tracking-when-customers-use-the-cloud\/\">blockchain<\/a>, the <a href=\"https:\/\/developers.redhat.com\/blog\/2018\/03\/06\/introduction-istio-makes-mesh-things\/\">Istio service mesh<\/a>, and technologies still in infancy) with open sourcing participation; and<\/li>\n<\/ul>\n<\/li>\n<li>(b) Innovation learning <em>by<\/em>, weaving their ongoing efforts though:\n<ul>\n<li>(i) <em>Learning-by-doing<\/em>, combining the knowledge bases on <a href=\"https:\/\/www.ibm.com\/us-en\/marketplace\/redhat-support\">support services<\/a> that previously were separated;<\/li>\n<li>(ii) <em>Learning-by-making<\/em>, <a href=\"https:\/\/www.redhat.com\/en\/about\/development-model\">sharing<\/a> both improvements and setbacks on code developed between the companies, and in open source repositories; and<\/li>\n<li>(iii) <em>Learning-by-trying<\/em>, experimenting in <a href=\"https:\/\/www.redhat.com\/en\/blog\/what-weve-learned-two-years-red-hat-open-innovation-labs\">open innovation labs and &#8220;offboarding&#8221;<\/a> into real products; and<\/li>\n<\/ul>\n<\/li>\n<li>(c) Innovation learning <em>alongside<\/em>\u00a0in agencing strands, with:\n<ul>\n<li>(i) <em>Polyrhythmia entangling eurhythmia<\/em>, meshing\u00a0<a href=\"https:\/\/www.forbes.com\/sites\/brookmanville\/2016\/01\/28\/red-hat-redux-the-open-ish-organization\/\">Red Hat&#8217;s Open Organization<\/a>\u00a0culture with IBM&#8217;s global, industry-aligned customer relationships;<\/li>\n<li>(ii) <em>Regenerating entangling preserving<\/em>, balancing the forward looking investment of <a href=\"https:\/\/www.pcmag.com\/feature\/363939\/the-biggest-tech-mergers-and-acquisitions-of-all-time\/\">$34 billion in Red Hat<\/a>, against the <a href=\"https:\/\/www.thestreet.com\/markets\/ibm-adds-4-billion-to-share-buyback-plan-confirms-dividend-after-red-hat-deal-14762497\">suspension of buybacks of common shares in 2020 and 2021<\/a>; and<\/li>\n<li>(iii) <em>Less-leading-to-more entangling more-leading-to-more,<\/em>\u00a0recognizing <a href=\"https:\/\/investors.redhat.com\/ir-resources\/investor-faqs\/how-many-employees-do-you-have\">12,600 Red Hat employees<\/a> as new to IBM, while IBM has been <a href=\"https:\/\/www.statista.com\/statistics\/265007\/number-of-employees-at-ibm-since-2000\/\">shrinking<\/a> (from 434,246 ending 2012, to 366,600 ending 2017).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>What would signal a successful integration of Red Hat into IBM?\u00a0 Ex-post validation would require diligence in measuring (supporting or disproving) three <em>descriptive<\/em> theories on <em>open sourcing while private sourcing<\/em>:<\/p>\n<ul>\n<li>1. A descriptive theory of <em>quality-generating sequencing<\/em>\u00a0[<a href=\"#ing-2017-open\">Ing (2017)<\/a> chap. 6] sees open sourcing while private sourcing as entailed by three patterns:\n<ul>\n<li>(a) <em>Program envisioning<\/em> enables <em>elevating common standards<\/em> that are (i) worth backing; (ii) enable an offering superior to alternatives, and (iii) anticipates non-exclusive projects.<\/li>\n<li>(b) <em>Program realizing<\/em> enables <em>doing well by doing good<\/em> where (i) a combination of commons and private interests outweighs independent action, (ii) the strategic bet is superior to alternatives; and (iii) the project shows momentum and continues to attract participants.<\/li>\n<li>(c) <em>Program elaborating<\/em> enables <em>cultivating perennial platforms<\/em> so that (i) platforms can be elevated with emerging standards; (ii) maintenance updates and chargeable upgrades can extend relevance; and (iii) tangible evolution.<\/li>\n<li>This theory is developed under a paradigm of <em>architectural problem seeking<\/em>, i.e. synthesizing IBM and Red Hat into a unified system that enables capabilities that the separate parts cannot.<\/li>\n<\/ul>\n<\/li>\n<li>2. A descriptive theory of <em>affordances wayfaring<\/em>\u00a0[<a href=\"#ing-2017-open\">Ing (2017)<\/a> chap. 7] sees open sourcing while private sourcing as entailed by three patterns:\n<ul>\n<li>(a) <em>Enskilling<\/em> collective work by enabling <em>access to the smartest people<\/em> (i) at the frontier of knowledge; (ii) for basic functions and advanced features; and (iii) as modular for re-assembly to tasks at hand;<\/li>\n<li>(b) <em>Equipping<\/em> a community to <em>practice until they can&#8217;t get it wrong<\/em> (i) with professional resources to volunteer initiatives; (ii) complementing capital investment over grassroots activities; and (iii) sharing processes and materials as readily available; and<\/li>\n<li>(c) <em>Legitimating<\/em> an initiative to being <em>on the right side of history<\/em> (i) encouraging emerging directions towards open standards; (ii) associated with an identity with values attracting affiliation; and (iii) maintaining credibility collectively and individually.<\/li>\n<li>This theory is developed under a paradigm of <em>inhabiting disclosive spaces<\/em>, i.e. IBM and Red Hat coordinating on private sourcing initiatives for specific commercial opportunities, while continuing to participate actively in open sourcing activities.<\/li>\n<\/ul>\n<\/li>\n<li>3. A descriptive theory of <em>anticipatory appreciating<\/em>\u00a0[<a href=\"#ing-2017-open\">Ing (2017)<\/a> chap. 8] sees open sourcing while private sourcing as entailed by three patterns:\n<ul>\n<li>(a) <em>Judging material reality<\/em> as finding viability for <em>the commercial beyond non-profit institutions<\/em> with (i) customers embracing chargeable commercial extensions beyond non-chargeable platform; (ii) features and pricing distinct over competitors; and (iii) voluntary contributors welcomed;<\/li>\n<li>(b) <em>Judging formal value(s)<\/em> as <em>growing a bigger pie better than slicing a smaller pie<\/em>, with (i) an industry champion seeing investments as commercially viable; (ii) a target segment of customers sustainable; and (iii) finding works worth perserving into perpetuity; and<\/li>\n<li>(c) <em>Judging efficient instrumentality<\/em> in <em>stratifying concierge levels above mainstream excellence<\/em>, with (i) distinctive chargeable features; (ii) offerings resonating with customers; and (iii) volunteers continuing to contribute to the commons.<\/li>\n<li>This theory is developed under a paradigm of <em>governing subworlds<\/em>, i.e. IBM and Red Hat organizing sets of practices for commercial taskscapes of customers receiving value for money, and in collaborative taskscapes of contributing developers where time and efforts are pooled.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>The above theories aren&#8217;t meant to suggest that other theories couldn&#8217;t be built.\u00a0 Multi-paradigm theory building leads to exploring alternative explanations and prescriptions to phenomena.<\/p>\n<p>Practically, open sourcing while private sourcing has proven to be a viable way of doing business since the mid-2000s.\u00a0 The IBM acquisition of Red Hat has been anticipated as an eventuality by many, yet hasn&#8217;t been appreciated in the frame of open innovation learning.<\/p>\n<h3>References<\/h3>\n<p><a id=\"bort-2016-oracle\"><\/a>Bort, Julie. 2016. \u201cOracle Didn\u2019t Buy Sun Just to Sue Google but to Keep It Away from IBM, CEO Says.\u201d <em>Business Insider<\/em>. May 16, 2016. <a href=\"https:\/\/www.businessinsider.com\/oracle-bought-sun-because-of-ibm-not-google-2016-5\">https:\/\/www.businessinsider.com\/oracle-bought-sun-because-of-ibm-not-google-2016-5<\/a>.<\/p>\n<p><a id=\"cringely-2018-red\"><\/a>Cringely, Robert X. 2018. \u201cRed Hat Takes over IBM.\u201d <em>I, Cringely<\/em>. October 29, 2018. <a href=\"https:\/\/www.cringely.com\/2018\/10\/29\/red-hat-takes-over-ibm\/\">https:\/\/www.cringely.com\/2018\/10\/29\/red-hat-takes-over-ibm\/<\/a>.<\/p>\n<p><a id=\"dignan-2009-is\"><\/a>Dignan, Larry. 2009. \u201cIs an IBM Purchase of Red Hat Inevitable?\u201d <em>ZDNet<\/em>. May 15, 2009. <a href=\"https:\/\/www.zdnet.com\/article\/is-an-ibm-purchase-of-red-hat-inevitable\/\">https:\/\/www.zdnet.com\/article\/is-an-ibm-purchase-of-red-hat-inevitable\/<\/a>.<\/p>\n<p><a id=\"huang-2009-how\"><\/a>Huang, Gregory T. 2009. \u201cHow to Integrate an Acquired Company: Lessons from IBM.\u201d Xconomy. January 5, 2009. <a href=\"https:\/\/www.xconomy.com\/seattle\/2009\/01\/05\/how-to-integrate-an-acquired-company-lessons-from-ibm\/\">https:\/\/www.xconomy.com\/seattle\/2009\/01\/05\/how-to-integrate-an-acquired-company-lessons-from-ibm\/<\/a>.<\/p>\n<p><a id=\"humphries-2018-ibm\"><\/a>Humphries, Matthew. 2018. \u201cIBM Acquires Red Hat for $34B.\u201d <em>PCMAG<\/em>, October 29, 2018. <a href=\"https:\/\/www.pcmag.com\/news\/364649\/ibm-acquires-red-hat-for-34b\">https:\/\/www.pcmag.com\/news\/364649\/ibm-acquires-red-hat-for-34b<\/a>.<\/p>\n<p><a id=\"ing-2017-open\"><\/a>Ing, David. 2017. <em>Open Innovation Learning: Theory Building on Open Sourcing While Private Sourcing<\/em>. Toronto, Canada: Coevolving Innovations Inc. <a href=\"https:\/\/doi.org\/10.20850\/9781775167211\">https:\/\/doi.org\/10.20850\/9781775167211<\/a>. <a href=\"http:\/\/openinnovationlearning.com\/online\/\">http:\/\/openinnovationlearning.com\/online\/<\/a><\/p>\n<p><a id=\"rifkin-1998-post\"><\/a>Rifkin, Glenn. 1998. \u201cPost-Merger Integration: How I.B.M. and Lotus Work Together.\u201d <em>Strategy+Business<\/em>, July 1, 1998. <a href=\"http:\/\/www.strategy-business.com\/article\/18930\">http:\/\/www.strategy-business.com\/article\/18930<\/a>.<\/p>\n<p><a id=\"rushe-2013-googles\"><\/a>Rushe, Dominic. 2013. \u201cGoogle\u2019s Larry Page Says Oracle among Those Holding Back Tech Industry.\u201d <em>The Guardian<\/em>, May 15, 2013. <a href=\"https:\/\/www.theguardian.com\/technology\/2013\/may\/15\/google-larry-page\">https:\/\/www.theguardian.com\/technology\/2013\/may\/15\/google-larry-page<\/a>.<\/p>\n<p><a id=\"zdnet-2016-cisco\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: Cisco and Linksys; Apple and Lala.Com.\u201d ZDNet. September 20, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-acquisitions-cisco-linksys-apple\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-acquisitions-cisco-linksys-apple\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-facebook\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: Facebook and Instagram.\u201d ZDNet. February 8, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-acquisitions-cisco-linksys-apple\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-facebook-instagram\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-caldera\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: Caldera and SCO, Microsoft and Danger.\u201d ZDNet. February 10, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-caldera-and-sco-microsoft-and-danger\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-caldera-and-sco-microsoft-and-danger\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-novell\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: Novell and Unix, Borland and Ashton-Tate.\u201d ZDNet. February 9, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-novell-unix-borland-ashton-tate\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-novell-unix-borland-ashton-tate\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-hp\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: HP and Autonomy, Google and Motorola, and More.\u201d ZDNet. February 12, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-hp-and-autonomy-google-and-motorola-and-more\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-hp-and-autonomy-google-and-motorola-and-more\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-nokia\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: Nokia and Microsoft, AOL and Time Warner.\u201d ZDNet. February 13, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-nokia-and-microsoft-aol-and-time-warner\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-nokia-and-microsoft-aol-and-time-warner\/<\/a>.<\/p>\n<p><a id=\"zdnet-2016-hp\"><\/a>ZDNet Editors. 2016. \u201cWorst Tech Mergers and Acquisitions: HP and Compaq.\u201d ZDNet. February 15, 2016. <a href=\"https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-hp-and-compaq\/\">https:\/\/www.zdnet.com\/article\/worst-tech-mergers-and-acquisitions-hp-and-compaq\/<\/a>.<\/p>\n<p><a href=\"http:\/\/openinnovationlearning.com\/online\/\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full\" src=\"http:\/\/coevolving.com\/images\/Ing_Open-Innovation-Learning_Theory-building_cover_20171115_noback_640x416.png\" alt=\"Open Innovation Learning book cover\" width=\"640\" height=\"416\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The acquisition by IBM of Red Hat brings together two companies that have been leading in open sourcing while private sourcing for almost 20 years.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[21,11,14],"tags":[489,370,490,491,487,180,488],"class_list":["post-1636","post","type-post","status-publish","format-standard","hentry","category-governance","category-innovation","category-technologies","tag-acquisition","tag-ibm","tag-merger","tag-open-sourcing","tag-oracle","tag-red-hat","tag-sun-microsystems"],"_links":{"self":[{"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts\/1636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/comments?post=1636"}],"version-history":[{"count":17,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts\/1636\/revisions"}],"predecessor-version":[{"id":1653,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts\/1636\/revisions\/1653"}],"wp:attachment":[{"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/media?parent=1636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/categories?post=1636"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/tags?post=1636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}