Autumn 2024 repo health check

[mkArtakMSFT]

It's time for an end-of-year survey for our repository and we'd like to hear from you how we're doing.

From the last survey we've learned that getting ASP.NET Core API Reviews streamed live is something many of you want to see. Well, that's a work in progress, and we plan to start streaming these from early next year (hopefully from February).

How are we doing? As before, we'll post the aggregated results when we close the survey. This is an anonymous, 2 question survey. (Also posted in several other repos, each have their own survey so you can answer more than one.)

https://www.surveymonkey.com/r/5CS8T9W

[danmoseley]

mentioning our wonderful community members who help keep our issues and PR's healthy -- @david-acker @egil @gfoidl @hishamco @Kahbazi @marinasundstrom @martincostello

I hope y'all can do the survey as well -- each repo has its own survey link so you can do more than one.

[danmoseley]

Meant to circle back with the results earlier, but here they are. First, NSAT.

We measure happiness with the repo in Net Satisfaction, which varies from 0 (very bad) to 200 (very good). dotnet/aspnetcore dropped significantly in NSAT during 2024 as shown in this graph, but remained over 100. With 22 responses this should be fairly accurate. Compare dotnet/runtime which consistently is 120-130 and dotnet/aspire which debuted at 113. Across dotnet repos we're now about in the middle.

Comments in answer to "if we could do one thing to improve your experience in the repo what would it be" were on these themes:

• Slow issue resolution and lack of transparency in the planning process.
• Ask for more attention to issues. Some instances of issues being closed without sufficient explanation or discussion.
• Community PR's open for too long without review
• Bots closing too aggressively in some cases including at the weekend.

(There was also an ask for more real-life code examples - Blazor and OpenID was called out, which should now be covered.)

There was appreciation for the community triager team which now has 6 members. These folks help make this community better. We intend to invite some more members soon, based on folks we've seen consistently being present and helpful in the community.

For planning, we do publish a roadmap early in the cycle and respond to discussions of it. We held planning discussions in many community standups

• ASP.NET Community Standup - ASP.NET Core planning kickoff for .NET 10
• ASP.NET Community Standup - Contributing to the ASP.NET Core Repo
• Blazor Community Standup - Blazor .NET 10 Planning Discussion
• ASP.NET Community Standup - Security & Auth .NET 10 planning discussion
• ASP.NET Community Standup - .NET 10 Server & APIs Planning Discussion

We'd welcome suggestions for how we can include the community in better ways. In the transparency theme, but not planning per-se, we began live streaming API reviews so the community can provide comments on the spot.

For bots, we have several, defined in yml files in this repo here and here. We don't have any metrics we're driving with them 😄 . They are designed to keep issues fresher, for example, if we've asked for more information a week ago without response, we'll close the issue. We fixed the one that was doing this at the weekend to only work weekdays. We're open to discussion of tuning how they work in the repo Discussions.

For PR throughput - this is noted. I don't have a good answer for this at the moment.

Other feedback welcome in Discussions. We'll have the next survey in May, 6 months after this one was held, and we'll see whether any of this has helped.