We knew that you guys would really dig open source but we didn’t expect such a positive response. Within a single week, our open source blog post got more than 200k views! And even on GitHub, which seems to be the place for open source these days, .NET Core jumped at the top of the trending GitHub repositories for last week.
We also have seen a tremendous activity in our social channels, specifically Twitter, blog comments and our Facebook site. I’ve seen very few negative comments – the overwhelming majority of the feedback was congratulations and genuine excitement.
But that’s not all – we’ve also received and accepted 20 pull requests from the community. The first one was from Adam Ralph who fixed a test break. We also received some substantial contributions such as performance improvements to immutable collections.
Some of the contributions were requests for API additions, such as async overloads for XDocument. We’re still figuring out the process for reviewing public API additions. As you know, we still very much care about interoperability between .NET Framework and .NET Core. Thus, we need to be mindful about the fact that we may need to port API additions back to the .NET Framework – which we know isn’t exactly cheap or easy. However, at the same time we don’t want to slow down .NET Core too much. After all, we’ve created this new stack so that we can release more often. So we need to strike a good balance here.
Microsoft GitHub presence
In case you haven’t you should check the Microsoft GitHub landing page:
We’re entertaining the idea of integrating charts like the one above into this site so that you can get a live view. What do you think?
We’re currently focusing on a few key areas:
Contribution processes. We’ve just finished setting up a public CI server on AppVeyor. We’ve also started a wiki that contains developer information. The next steps include a public roadmap and more specific information around how we review your pull requests.
More libraries. We’re heads down extracting the libraries from our internal engineering system so that we can put it on GitHub.
Cross-platform. We’re engaging with Miguel and the Mono community to take our stack cross-plat. This is currently blocked by not having enough libraries out there but it’s coming soon.
Runtime. Some of you might be eager to read the GC or the JIT code. You probably have to wait until early next year.
Please don’t hesitate to give us feedback. My team is still learning on how to play in an open source world so we’re heavily depending on you, our community, to tell us whether we’re heading in the right direction or not.