News

Microsoft Goes to China for Open Source Collaboration

China, meanwhile, continues to develop its own China Operating System (COS).

Microsoft is expanding its open source collaboration efforts overseas, with a special emphasis on the cloud.

Microsoft Open Technologies Inc. has opened an office in Shanghai, China.

China officials offered statements of support for the facility in Microsoft's announcement, issued today. The opening of the new facility signals that Microsoft will be investing in, and providing support to, the local open source communities in the country. The new office, called "Microsoft Open Technologies Shanghai Co. Ltd.," will be staffed with engineers and standards experts focused on interoperability between proprietary Microsoft products and open source software developed in China.

"Our new subsidiary will offer more flexibility to iterate and release open source software created in China, participate in existing open source and open standards efforts and collaborate with the community of open source developers in China," said Jean Paoli, president of Microsoft Open Technologies, in a released statement.

One focus particularly called out for the China subsidiary is facilitating interoperability between open source software and Windows Azure. Microsoft had announced back in May that it was expanding its Windows Azure cloud-computing services into China and other countries in that hemisphere. Microsoft is partnering local Shanghai-based 21Vianet to deliver the Windows Azure services.

Meanwhile, the Chinese government is proceeding apace to foster its own Linux-based China Operating System (COS) to compete with operating systems from Microsoft, Apple and Google that are used in the country, according to a CNET report. The COS development effort comes on top of China's earlier collaboration with Canonical to develop a state-sponsored Ubuntu OS for use in China.

Microsoft Open Technologies is a wholly-owned Microsoft subsidiary that was formed almost two years ago. Microsoft's had its collaboration efforts in place with open source software projects for years before creating Microsoft Open Technologies. However, the subsidiary apparently was created to help speed up those collaboration efforts.

Microsoft Open Technologies currently works with various Apache open source projects, such as Apache Cordoba and Apache Qpid. It also works with open source communities, such as JQuery, Node.js and WebKit, among others. It contributes its interoperability efforts to standards organizations, including DMTF, ECMA, IETF, OASIS, W3C and ISO/IEC. Such collaboration efforts mark a more recent phase for Microsoft, which has been sued by companies precisely for not enabling product interoperability with Windows.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube