| • The hosts discuss the show's guests, Rich Lander, Emma Landworth, and Varun Gupta, from the .NET Core team at Microsoft.
|
| • The show is a rare occurrence, as it's the first time the hosts have had anyone from Microsoft on the show talking about .NET being open source.
|
| • The guests introduce themselves, discussing their backgrounds and involvement with the .NET team.
|
| • The hosts ask the guests about the shift towards open source, specifically why Microsoft chose to go open source with .NET Core.
|
| • Rich Lander explains that the motivation behind going open source is to reach developers who require open source software, and to make them customers.
|
| • Emma Landworth discusses the "why now" question, explaining that the benefits of open source are particularly evident in cross-platform projects, where open source is a more sustainable way to work.
|
| • Agile delivery and its benefits
|
| • Complexity of a 15-year-old project and the need for agile
|
| • Customer feedback and satisfaction through open source
|
| • Microsoft's shift towards open source and its progression over time
|
| • Leadership change and its possible influence on the shift in strategy
|
| • Open source as a continuation of dev ops and other emerging technologies
|
| • Embracing open source as a key to reaching a broader customer base
|
| • Microsoft's open source strategy and embracing community involvement
|
| • Comparison of Microsoft's approach to Apple's open source efforts
|
| • Challenges in maintaining open source projects and the need for community involvement
|
| • The importance of transparency and trust in open source communities
|
| • The distinction between "open source" and "source open" approaches
|
| • Microsoft's shift towards a "source open" approach and its implications
|
| • The size and enthusiasm of the .NET team involved in open source efforts
|
| • Microsoft has a large team working on the .NET codebase, with around 100 people contributing to the code that will be available on GitHub.
|
| • The initial codebase available on GitHub includes a small number of libraries, including immutable collections, metadata reader, XML, and vector library.
|
| • The reason for focusing on these four libraries is to make open-source development a priority and to be able to build and use the source code themselves.
|
| • The engineering initiative to decouple the built infrastructure from the libraries themselves is underway.
|
| • The entire .NET Core stack, including the runtime, BCL layer, networking, and app model, will be open-sourced over time.
|
| • Additional libraries, such as console and data flow, are scheduled to be added to the GitHub repository in the coming weeks.
|
| • The .NET framework has two stacks: the full framework and .NET Core, with the latter being a fork designed for modularity and deployment on a variety of devices.
|
| • The focus on open-source development includes releasing source code on a regular cadence and taking contributions back from the community.
|
| • Microsoft's dotnet framework is a large, proprietary codebase that ships with Windows and is updated via Windows Update.
|
| • The dotnet framework is so large that it's hard to evolve without breaking existing apps or dependencies.
|
| • Dotnet core is a separate, open-source project that is designed to be app-local and easier to reason about.
|
| • Microsoft has released parts of the dotnet framework that correspond to the dotnet core stack as open source on GitHub.
|
| • The dotnet framework and dotnet core have a compatibility story, allowing libraries to run on either stack.
|
| • Microsoft is committed to keeping a compatibility story between the two stacks.
|
| • The dotnet core project is considered the "real open source strategy" for Microsoft.
|
| • The dotnet framework is not open sourced in the same way as dotnet core, but some components are available as open source.
|
| • Microsoft has a process for evolving the dotnet core project, including releasing new packages and porting innovations back to the full framework.
|
| • Microsoft is open-sourcing .NET Core
|
| • .NET Core is being developed in the dotnet foundation org on GitHub, which is a community-driven effort
|
| • The dotnet org on GitHub is where .NET Core lives, and it's part of the open source community around .NET
|
| • The mono project, a clone of .NET, is also being integrated with .NET Core and is working closely with Microsoft
|
| • The goal of open-sourcing .NET Core is to create a consistent and coherent .NET implementation for all users, and to leverage the community and open source advantages
|
| • The importance of having a single experience across multiple devices and platforms.
|
| • Dot Net was designed to have a single experience on multiple scenarios, but this may not be the best approach.
|
| • The need for reusability of code across devices and platforms.
|
| • The goal of open source to increase the breadth of Dot Net and make it easier for developers to use.
|
| • The current state of Dot Net Core and Framework support, with only Windows supported.
|
| • The plan to open source Dot Net Core, allowing for community involvement and eventual support for Linux and Mac.
|
| • The iterative process of adding Linux and Mac support to Dot Net Core.
|
| • The work being done to make the runtime available on multiple platforms, including a legitimate-based runtime and an ahead-of-time compiled runtime.
|
| • The speaker discusses the concept of .NET Core and its goal of having a unified code base that runs on Linux, Windows, and Mac.
|
| • Microsoft's support for .NET Core and the unification of its community with the Mono community.
|
| • The excitement and potential of open-source projects, including .NET Core, but also the challenges and difficulties that come with maintaining them.
|
| • The importance of team culture and the fact that the .NET Core team is made up of engineers who are truly passionate about open-source development.
|
| • The differences between working on an open-source project as part of one's job versus working on it as a hobby, and the potential for burnout and challenges in the latter case.
|
| • Corporate customers want a Linux version of .NET for their applications
|
| • Azure wants to provide a consistent developer platform for both Linux and Windows Server
|
| • Microsoft's corporate customers are not required to participate in the open source community
|
| • The company will still provide commercial software with Microsoft support
|
| • The open source community can help by providing feedback on the development process and providing contributions
|
| • Discussion of open source development and community feedback
|
| • Introduction of the .NET Foundation, its purpose, and how it brings the .NET community together
|
| • Benefits of community-driven efforts in open source development
|
| • Upcoming podcast episode on the .NET Foundation with guests Varun and Beth
|
| • Microsoft's approach to open sourcing .NET Core and the BCL
|
| • Importance of community involvement in open source projects versus corporate entities
|
| • Future plans for the .NET community and potential collaborations
|
| • Introduction and gratitude to the audience
|
| • Mention of sponsors: Code Ship, Top Towel, and Rack Space
|
| • Appreciation for the sponsors' support
|
| • Farewell and thanks to the opportunity to be on the show |
