Welcome to the first of a series: our regular .NET Foundation updates! We’ll be posting these on our blog, but to make sure you don’t miss one, please subscribe to get them via e-mail.

Sign up to get the .NET Foundation Update via e-mail

We’re planning to send these out at the beginning of every month going forward, so that means you should see the February one in just a few weeks. Don’t worry, we want to keep these short, interesting, and low-noise, so we won’t overload your e-mail.

.NET Foundation Updates

Meetups

The .NET Foundation has sponsored a .NET Meetup Pro group and now has over 100 member groups. If you’re looking for a .NET Meetup in your area, this should help you find Meetups that are focused on .NET; if you run a .NET meetup we’ll pay for your Meetup Pro membership.

Please help connect us with other groups you're aware of that haven't joined yet by dropping me a note jon@dotnetfoundation.org or leaving a comment below.​


Open Collective

One issue many open source projects deal with is handling finances in an open source friendly way. We've set up an umbrella organization under Open Collective to make it easier for your projects to accept money (donations, sponsorships, bounties) and to make payments in an open, transparent way. For an example of an open source project where this has worked really well, see the webpack Open Collective: https://opencollective.com/webpack. Open Collective's model is that a parent institution (in this case, .NET Foundation) holds the money for you. This is especially useful for community projects with several owners who don't want to deal with deciding who holds the money and dealing with accounting, reporting to the community, etc.

You obviously have other options, and I'd encourage you to do whatever makes the most sense for your project. For instance, in working with the IdentityServer team, we agreed that Patreon made more sense for them (https://www.patreon.com/identityserver).

If you host a .NET Meetup or run a .NET Foundation project and would like to get set up with Open Collective, e-mail me at jon@dotnetfoundation.org.

CLA System Upgrade

One of the technical services we offer .NET Foundation projects is access to our Contributor License Agreement (CLA) automation system for GitHub pull requests. We’ve recently completed a pretty significant upgrade from our previous legacy system. The new system is build on the open source CLA Assistant  project and is a lot more reliable and easy to maintain. Users will have a better experience since they can just click through in the browser (no need to use DocuSign). Project owners will see less noise on the repo as the CLA messaging is cleanly integrated into the GitHub required pull request review steps and doesn't add status comments to the pull request.

One of the features of the new system is that it's easier to add new projects. We’re still working through getting some new projects onboarded, but it’s a much simpler process now.


.NET Foundation Project News

UWP Community Toolkit

The UWP Community Toolkit was recently updated to v2.1 which introduced new helpers for composition animations and visuals, new DockPanel control, support for new FCU controls and more to simplify and demonstrates common developer tasks building apps for Windows 10. Contributors are always welcomed to submit issues or pull request to add new awesome features.

More information on the new UWP Community Toolkit release is in this announcement post.

BenchmarkDotNet

BenchmarkDotNet v0.10.12 has been released!

There are a lot of improvements in the main .NET benchmarking tool:

  • New TailCallDiagnoser: now you get notifications when JIT applies the tail call optimizations to your methods.
  • Improved MemoryDiagnoser: it has a better precision level, and it takes less time to evaluate memory allocations in a benchmark.
  • Improved DisassemblyDiagnoser: BenchmarkDotNet contains an embedded disassembler so that it can print assembly code for all benchmarks; it's not easy, but the disassembler evolves in every release.
  • Better environment info: when your share performance results, it's very important to share information about your environment. The library generates the environment summary for you by default. Now it contains information about the amount of physical CPU, physical cores, and logic cores. If you run a benchmark on a virtual machine, you will get the name of the hypervisor (e.g., Hyper-V, VMware, or VirtualBox).
  • Better summary table: one of the greatest features of BenchmarkDotNet is the summary table. It shows all important information about results in a compact and understandable form. Now it has better customization options: you can display relative performance of different environments (e.g., compare .NET Framework and .NET Core) and group benchmarks by categories.
  • Other minor improvements and bug fixes

Read more in this announcement post.

Polly

Major new features added to Polly over the last few months include:

Next on the roadmap is enabling policies to emit events which could be streamed (for example by Rx) as telemetry to dashboards.


Community Links and News

The .NET Foundation is on Facebook now. Please like our page! We’ll post regular updates and interesting things happening with .NET to share.

Recently Matt Warren, a .NET MVP, wrote up this pretty interesting post on Open Source .NET - 3 Years Later (http://mattwarren.org/2017/12/19/Open-Source-.Net-3-years-later) . In the post, he highlights the community's involvement in .NET repositories. It’s amazing to see the growth we’ve achieved in just three years. I’m very encouraged by our fantastic community contributing to .NET open source.

The .NET Foundation is also on YouTube. Watch community standups and design reviews as well as code-focused shows and interviews across our multiple playlists.

Youtube

Do you have an interesting piece of news or content related to .NET open source? Let us know so we can include it in next month’s update by posting a comment below.


Remember to Subscribe!

Please sign up to get the .NET Foundation Update via e-mail.

Subscribe

We’re planning to send these out at the beginning of every month going forward, so that means you should see the February one in just a few weeks. Don’t worry, we want to keep these short, interesting, and low-noise, so we won’t overload your e-mail.