How are we doing in the repo? -- spot check

[danmoseley]

It's midyear between our surveys and we'd like to hear from you how we're doing.

<edit - removed link>

If you are reading this, we'd welcome your input. There's only one question so it should take just seconds. But we'd also welcome your suggestions in the optional text box as well.

-- dotnet/aspnetcore maintainers

[danmoseley]

As I noted in the runtime repo equivalent of this issue, if you're less than happy we'd particularly appreciate some comments in the box!

For some reason they have far more responses so far than we do in this repo. We'll leave this up for a week or two -- hoping to get enough that it's statistically comparable with the spring. How are we doing in here relative to February?

[danmoseley]

cc @dotnet/aspnet-community-triagers in case any of those folks wish to do it and haven't. :)

[danmoseley]

I've closed the survey now. Here's a summary of the results. We measure satisfaction with an aggregate called NSAT (net satisfaction) that is between 0 and 200 and anything over 100 is good. Below is the result for aspnetcore. Note there were only 10 responses so there's an error bar of 15 or so here. Results are pretty similar to dotnet/runtime.

NSAT	NSAT (spring 2023)	NSAT (spring 2022)	NSAT (spring 2021)
140	108	124	102

There were several suggestions in text, not enough for common themes - each of these is one respondent

1. "Split Blazor into it's own repo. The number of issues, PRs, and discussions around Blazor drowns out anything else. I think the frontend community could use it's own space."
2. "I'd like to not feel so stupid when asking a (what seems to others to be an obvious) question. And I'd like to think I'm not wasting their time. "
3. "More opportunities for community/external contributors to help out would be nice, e.g. more "Help Wanted" issues, opportunties for regular community contributors to get more involved (within reason)"
4. "Hot reload and fast compilation for Blazor WASM should be a priority. Development on a large scale application becomes very hard."
5. "Publish a roadmap of new features / focus for the next release. Similar to what EF Core does."

Feel free to add any other thoughts below -- these are good suggestions for us all to think about. Thank you so much to the folks that filled this out.

[danmoseley]

for this one

"I'd like to not feel so stupid when asking a (what seems to others to be an obvious) question. And I'd like to think I'm not wasting their time. "

It's really important to me that we have a community here that doesn't make anyone feel that way. It'd be great if anyone feels comfortable sharing examples of this, either here or to the email in my profile. We'd like to make changes if we can to do better.

[danmoseley]

for this one

"Split Blazor into it's own repo. The number of issues, PRs, and discussions around Blazor drowns out anything else. I think the frontend community could use it's own space."

@mkArtakMSFT could you respond to this one with your thoughts? - I'm guessing this has come up in the past. Breaking into two repos while it make make communities more cohesive would bring numerous disadvantages as well, such as new codeflow edges. It is always a tension between these things.

[mkArtakMSFT]

"Split Blazor into it's own repo. The number of issues, PRs, and discussions around Blazor drowns out anything else. I think the frontend community could use it's own space."

Blazor is part of ASP.NET Core and it's integrated into the framework so much, that it makes no sense (neither its feasible) to move it out into a separate repo.