Today, I'm happy to announce that MiniProfiler for .NET, StackExchange.Redis, protobuf-net, and Sign Service are joining the .NET Foundation!

MiniProfiler for .NET

MiniProfiler for .NET is a simple but effective mini-profiler for ASP.NET (and Core) websites.

StackExchange.Redis

StackExchange.Redis is a high performance general purpose redis client for .NET languages (C# etc). 

protobuf-net

protobuf-net is a contract based serializer for .NET code, that happens to write data in the "protocol buffers" serialization format.

Sign Service

Sign Service aims to make it easier to integrate Authenticode signing into a CI process by providing a secured API for submitting artifacts to be signed by a code signing cert held on the server. It uses Azure AD and Azure Key Vault's HSM for security. We've been using Sign Service for years behind the scenes to code sign many of our .NET Foundation projects, this is just making it official.

Welcome!

Here's the February edition of the .NET Foundation newsletter! Every month, we'll give you a quick overview of the .NET Open Source landscape, including top project news, events, community links and more.

This month's newsletter includes:

  • Update on Open Membership and Elections
  • Information on Visual Studio 2019 Local Launch Parties
  • News from .NET Foundation member projects
  • .NET Meetup news

As always, these are available both on our blog and via e-mail: Sign up to get the .NET Foundation Update via e-mail


.NET Foundation Update: Open Membership and Elections

We recently announced that the .NET Foundation is moving to Open Membership and governance, with blog post series to explain:

This month, we've begun accepting our first batch of .NET Foundation Voting Members and onboarding them to our new .NET Foundation Members site. We also clarified that .NET Foundation that the contributor requirement for membership isn't just code, it includes things like speaking and community organizing. If you've been putting off applying, apply today!

Today, we announced the kickoff of our first .NET Foundation elections! Any Voting Member is eligible to campaign for a board seat. The campaign period runs from February 28 - March 21, followed by a one week voting period ending March 28 at 12 PM Pacific time. More information about the elections is available on our election website.

We're going to continue posting more information about membership and board elections on our blog, and you can watch the @dotnetfdn Twitter account for updates as well. If you have any questions about membership, running for the board, or joining as a corporate sponsor, don't hesitate to contact us at contact@dotnetfoundation.org.

Apply for .NET Foundation Membership


.NET Foundation Project Updates


Windows Template Studio goes 3.0!

Windows Template Studio 3.0 has been released, with lots of great features including:

  • Code now generates as a multi-project solution. This will enable better reuse and separation of code logic. This now will output a UWP project and .NET Core project.
  • Support adding new projects on right click
  • Horizontal Navigation View is replaced the Pivot navigation pattern.
  • Update MVVMLight to use .NET Standard library
  • Bug fixes

DNN-Connect 2019 Announced

DNN-Connect was announced and will be held in Champery Switzerland, June 6-9.

Steeltoe 2.2 RC1

Steeltoe 2.2 RC1, and has been released, and should be generally available mid-March.


Visual Studio 2019 to be released on April 2, 2019


Visual Studio 2019 is almost here! Join us online on April 2 starting at 9 AM Pacific Time for demos and conversations centered around development with Visual Studio 2019, Azure DevOps, and GitHub. Join a local launch event in your city or help organize one for your community.

Learn more and save the date! > https://launch.visualstudio.com

The .NET Foundation helped partner with our local Meetups to host these local events, check out the worldwide reach!


New, Fancy Site for .NET Presentations


We've upgraded our .NET Presentations repo with a pretty new site with an easy to remember URL: https://presentations.dotnetfoundation.org. It also has some new updates, including an all new Blazor workshop (complete with drone delivered pizzas!). Take a look!


Meetups

Our .NET Foundation sponsored .NET Meetup Pro groups continue to grow! Here are some quick stats:

  • 255 Groups (+6)
  • 52 Countries
  • 165K Members (+8K)

We've also started sending newsletters to Meetup organizers, including some links for some free swag for their groups. If your meetup hasn't joined yet, you can right here.


Connect with the .NET Foundation online

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

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.


Remember to Subscribe!

Please sign up to get the .NET Foundation Update via e-mail. Don’t worry, we want to keep these short, interesting, and low-noise, so we won’t overload your e-mail.

Here's the January edition of the .NET Foundation newsletter. Every month, we'll give you a quick overview of the .NET Open Source landscape, including top project news, events, community links and more.

This month's newsletter includes:

  • Update on Open Membership, Corporate Sponsorship, and Elections
  • News from .NET Foundation member projects
  • .NET Meetup news

As always, these are available both on our blog and via e-mail: Sign up to get the .NET Foundation Update via e-mail


.NET Foundation Changes: Open Membership, Elections, and Corporate Sponsors

At the Microsoft Connect event in December, we made announced that we are moving to open membership, governed by a community elected board of directors. Here's an update on what we've been up to with that.

This month we published a series of blog posts explaining things in more detail:

Beth and Jon also spoke on the .NET Rocks podcast to explain what the .NET Foundation does, why it matters to every .NET developer, and how you can get involved. We've had a lot of response: lots of membership applications, several inquiries into running in the board elections, and some additional companies interested in becoming sponsors. Yay!

While we originally announced we'd be starting elections in January, we've decided to push them back to mid-February. These are our first elections, and we want to be sure we do it right. We also want to allow some more time to communicate clearly how the campaign process works, and to make sure we've gotten the word out to all prospective board members. We really want to make sure we've got a board that represents our entire community, and we'd love your help to spread the word to those you think should consider running (and think about running yourself, of course!).

Apply for .NET Foundation Membership

We're going to continue posting more information about membership and board elections on our @dotnetfdn Twitter account for updates as well. We're targeting election campaigns kicking off the second week of February. If you have any questions about membership, running for the board, or joining as a corporate sponsor, don't hesitate to contact use at contact@dotnetfoundation.org.


.NET Foundation Project News

DNN Summit (Feb 19-23)

DNN Summit is just a few weeks away, and .NET Foundation Executive Director Jon Galloway will be presenting the keynote. There are still tickets available, come join us in Denver!

Steeltoe: Modernize .NET Apps for a Microservices Architecture

Great article by David Dieruf discussing Steeltoe and modernizing .NET Apps in The New Stack.

NUnit .NET Core 3.0 Support

The 'dotnet new nunit' template has been updated for .NET Core 3.0. (Specify `--framework` to use other frameworks.) Thanks halex2005!

Cake: v0.32.0 release, and a look back at 2018

The Cake team posted about v0.32.0, and included some fun stats on 2018: 11 releases of Cake, hundreds of PRs from over fifty individual contributors, hundreds of issues raised and closed, and millions of downloads. Congrats!

ReactiveUI

The ReactiveUI team has been busy this month! In addition to several bugfix releases on the 9.x line, the team released two previews of 10.0.0, with support for WPF and WinForms under .NET Core 3.0.


Meetups

Our .NET Foundation sponsored .NET Meetup Pro groups continue to grow! Here are some quick stats:

  • 249 Groups (+6)
  • 51 Countries
  • 157K Members (+7K)

We've also started sending newsletters to Meetup organizers, including some links for some free swag for their groups. If your meetup hasn't joined yet, you can right here.


Connect with the .NET Foundation online

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

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.


Remember to Subscribe!

Please sign up to get the .NET Foundation Update via e-mail. Don’t worry, we want to keep these short, interesting, and low-noise, so we won’t overload your e-mail.

We recently announced some big changes to the .NET Foundation, and one of the biggest is that we’re moving to a community elected Board of Directors. We're expanding the board from three to seven members, with one single seat appointed by Microsoft and the remaining six elected by the community. This structure will help the .NET Foundation scale and better serve the .NET ecosystem.

If you’re passionate about open source .NET, we’d like you to think about running in the elections! This post will explain the details, and hopefully get you to consider it, or maybe encourage someone else to.

This post is the third in a series:

What’s Changed?

Since the .NET Foundation was created, we’ve had three board members, all appointed by Microsoft. We’re changing that to seven board members, only one appointed by Microsoft. The remaining six are voted in by the community in yearly elections.

What does the .NET Foundation Board Do?

The board completely runs the .NET Foundation. They decide how the money is spent, what projects join the foundation, what the Executive Director (that’s me) does, what programs the foundation will run or be involved with, what events we’ll sponsor. The board runs the foundation.

Who Can Run for a Board Seat?

Any voting member can run for a board seat. That’s anyone who’s contributed to a .NET Foundation project and applied for membership.

Who Should Run for The Board?

Well, we need seven people to run the show. We’d love to see seven people with different viewpoints and experiences. We’d love to see a lot of diversity! We’d love to see people who represent different development backgrounds and concerns – not just .NET open source veterans, but people who speak for students, startups, new developers, corporate developers. We’d love to see folks who speak for different platforms, operating systems, web, desktop, games, IoT. We’d love to see people we haven’t thought to ask. The board is seven people instead of one because we need more viewpoints.

If you’ve had long conversations on Twitter, at conferences, or with developer friends about the way .NET open source ought to be, you’ve got an important viewpoint, and this is where you can make that change.

What’s Expected of Board Members?

The board actively manages the foundation and gets involved in new initiatives. Here’s what that looks like:

  • Monthly meetings with the board and executive director to keep up with what’s going on and set plans
  • Review and approve requests for new projects to join

Form committees and get stuff done! Committees are an area where you can really have a personal impact on things you really care about. This will include some general committees for businessy things (like membership and elections), as well as some special purpose committees that are up to you (maybe student outreach, Meetups, game development on .NET, diversity, conferences, etc.). We have a budget and a community that wants to get involved, so it’s not about you signing up for a lot of work here, it’s mostly about vision, planning and organizing.

I’m Interested in Running, But I’m Not Sure I Can Do It…

If in doubt, go for it!

If you’re feeling unqualified, remember that we’re looking for a board that represents a lot of backgrounds, and that includes experience levels. The important thing is that you’ve got a passion for .NET open source and are willing to show up to make it a better place.

If you’re worried about the time commitment – well, it’s true, we need you to be available and to put in the time. I’m not expecting a major time commitment – probably 4-6 hours a month, and most of it can be over e-mail and on your own schedule.

If there’s something preventing you from joining the .NET Foundation as a voting member to be eligible to run in the election, talk to us! Our previous post on joining as a voting member hopefully explains why contributions or dues shouldn’t get in your way.

How Do Campaigns and Elections Work?

We’ll be announcing more details in the next post, and kicking off the one-month campaign and election period on January 28. But here’s the high level:

  • We’ll be running a simple campaign mini-site using GitHub pages and pull requests. Candidates will submit a campaign statement as a markdown file pull request and can link off to other information if they want (e.g. video, podcast interviews, projects, etc.).
  • We’d love to see community discussion wherever it happens – Twitter, forums, etc. – following the standard code of conduct.
  • In the last week of the election cycle, voting members will cast their votes. We’re using the Single Transferable Vote methodology on the OpaVote system.
  • The board serves for one year, after which you can choose to run for reelection.

Interested? Watch for our next post with specifics on the elections process, and feel free to ping us at contact@dotnetfoundation.org with questions.

We recently announced some big changes to the .NET Foundation: Open Membership and a new Corporate Sponsor program. We’ve talked a bit about the Open Membership changes, but haven’t said a whole lot about the Corporate Sponsor program other than welcoming Pivotal, Progress Telerik and Insight as launch partners. Let’s dig into some specifics: what’s changing, why, and why your company should consider getting involved.

This post is the second in a series:

What is the .NET Foundation?

Let’s start with the basics since they help explain why we see broad corporate sponsorship as an important part of evolving the foundation: The .NET Foundation is an independent, non-profit organization, created in 2014 to foster open development and collaboration around the growing collection of open source technologies for .NET. It serves as a forum for commercial and community developers alike to strengthen the future of the .NET ecosystem by promoting openness, community participation, and rapid innovation.

What we announced

The .NET Foundation is changing to an open membership model. This includes the following:

  1. Any contributor to .NET is eligible to become a member.
  2. All members can participate in annual board member elections. Members can both run for election for the Board of Directors and vote in the annual elections.
  3. We're expanding our current Technical Steering Group to a Corporate Sponsor Program.

We’re inviting the .NET community to take an active role in guiding and supporting the .NET Foundation, and that includes both individual open source developers and businesses that depend on .NET open source. We think it’s really important to involve corporate sponsors as a key part of this change for three reasons.

First, for the .NET Foundation to really be independent and community run, it needs to be independently funded. In the past, we’ve depended on (greatly appreciated!) donations from Microsoft. Going forward, we’ll be funded by Corporate Sponsorships and Member Dues. Microsoft’s donation as a Corporate Sponsor will now be a relatively small percentage of our funding.

Secondly, Corporate Sponsorship really expands what the .NET Foundation can do – not just by having a bigger budget, but by being able to make long term plans based on annual dues payments.

Third, Corporate Sponsorship will directly involve the .NET corporate world in the .NET open source ecosystem, which is important! We’ll have input from companies that depend on .NET open source, we’ll be able to tackle some hard problems like how companies can be involved in sustainable community run open source projects.

Why should you join as a Corporate Sponsor?

So far we’ve talked about why we want companies to join. Now let’s explore why a company would want to join: what’s in it for you?

  1. First and foremost, because open source .NET is important to your business; a healthy open source .NET community helps you. Sponsoring the .NET Foundation is your best opportunity to ensure that the worldwide .NET open source developer base grows to their full potential.
  2. Corporate sponsors get a seat on the Advisory Council. We understand that a healthy .NET open source ecosystem includes input from everyone, and that definitely includes businesses who depend on .NET.
  3. Annual invitation-only summit for corporate sponsors.
  4. Co-marketing: e.g. we'll show your logo in our keynotes, you can use our logo on your public material.
  5. Direct contact with the .NET team.

Why change the TSG to a Corporate Sponsor Program?

We recognize that many companies have significant business interests in the future growth and health of the .NET ecosystem, across a variety of business models - platforms, developer tools vendors, consultancies, as well as businesses in other verticals that depend on .NET to run their websites, line-of-business applications, infrastructure, etc. We've had repeated requests from businesses that don't directly fit into the TSG model to join the foundation and get involved. Creating a Corporate Sponsor Program with annual dues will allow the .NET Foundation to have much greater impact and make long-term investments in the .NET community.[JG1]

How will sponsor contributions be spent?

Historically, we have spent money on things like:

  • Technical support services for member projects (e.g. code signing certificates, build servers, cloud hosting, etc.)
  • Event sponsorship (.NET Conf and .NET Conf Local events, third party conference sponsorship, open source project hackathons)
  • Meetup (user group) sponsorship (we sponsor 250 Meetups in 50 countries around the world)

Going forward, the Board of Directors will decide how best to spend contributions. Our current Board of Directors and Advisory Council are really excited about the potential to expand what we've been doing, as well as to launch some new activities to serve as a catalyst for the .NET open source community, such as:

  • Speaker grants: Now that we've built out a global network of local Meetups, we can help them get great speakers. Meetups provide new developers with an easy way to learn, make contacts in their local community, and develop into leaders and speakers if they so choose. Speaker grants help both provide great content and support the Meetup speakers by providing them more opportunities to speak.
  • Event sponsorship: We've helped sponsor the annual .NET Conf virtual conference and contributed to some small local events, but corporate sponsorship could allow us to put on in-person events, event tours to Meetups, larger hackathon events, and more.
  • Outreach: With a shared goal of growing the .NET developer base, we have many options to pursue - education, non-traditional venues (e.g. Twitch and online streaming), global and diverse markets we've missed historically, etc.
  • Open Source Evangelism to the Corporate Developer: .NET has a huge developer base, but too few are actively engaged in contributing to .NET and the .NET open source libraries they rely on. We'd love to see a dedicated speaker tour focused on educating and connecting enterprise developers with open source. We could bring some top .NET open source project leaders to local and corporate Meetups and show them how to get involved, as well as how contributing to .NET open source benefits them and their companies.

Really, this is just a start - there is tremendous explosive potential in the huge, worldwide .NET developer base that sadly underutilized. We'd love to engage that, and we'd love for our corporate sponsors to both lead the charge and get the credit for it.

Sponsor levels and dues

After reviewing the various software foundation levels, we've decided to ask for pretty inexpensive dues:

  • Large Company (> $10M revenue per year): $50,000 annually
  • Medium company ($3M - $10M revenue per year): $25,000 annually
  • Small company (< $3M annually): $10,000 annually

Most important, you should see .NET Foundation sponsorship as something that benefits you in three clear ways: you help build the .NET open source ecosystem, you can have a direct impact on the future of .NET, and you can market your products and services to the .NET community.

If you’re interested in learning more about the sponsorship program Got questions? Get in touch: contact@dotnetfoundation.org