News

Microsoft Joins Open Source Initiative

Microsoft, continuing a years-long transformation into a more open company, has joined the Open Source Initiative (OSI) as a premium sponsor.

The non-profit OSI is involved in many aspects of the open source movement, including community building, education, public advocacy and so on. It's probably best known for maintaining the Open Source Definition, which details the criteria for the distribution terms that open source software must comply with.

"The work that the Open Source Initiative does is vital to the evolution and success of open source as a first-class element in the software industry," Microsoft said in a blog post this week. "As Microsoft engages with open source communities more broadly and deeply, we are excited to support the Open Source Initiative's efforts and to take part in the OSI community."

The OSI said Microsoft has a long history of working with the organization, going back some 12 years, but it was probably the release of the Microsoft .NET Framework in 2014 that brought that participation to light for many in the open source community.

The organization also pointed to several other Microsoft open source initiatives, such as: bringing Bash/Linux to Windows 10; expanding support for Linux and open source workloads on the Azure cloud; the open sourcing of Visual Studio Code and Typescript; and many more. Also, Microsoft previously joined the Linux Foundation and frequently partners with other companies on open source projects, including Canonical, Red Hat and SUSE.

Listing the company's GitHub projects, for example, results in 47 pages of different offerings that total well over 1,000 items.

That might seem normal to younger developers who weren't around in the '90s when Microsoft was seen by many as a monolithic, closed, corporate predator that barely tolerated any competition and swallowed up rivals or sought to eliminate them. It even became the target of the U.S Department of Justice, which derided the company for its internal "embrace, extend, and extinguish" strategy of "entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences to disadvantage its competitors."

Now, it's a total team player, with open source initiatives and partnerships galore, a "Microsoft + Open" Web site, an "Open Source at Microsoft" Web site and executives such as Scott Hanselman tasked with furthering open source efforts at the company. Hanselman famously outlined his thoughts on open source and Microsoft haters in the 2014 blog post "Microsoft killed my Pappy."

In this week's post, the company said, "Today's announcement represents one more step in Microsoft's open source journey and our increased role in advocacy for the use, contribution, and release of open source software, both with our customers and the ecosystem at large."

About the Author

David Ramel is an editor and writer at Converge 360.

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