[Feature]: Support for Non-MSFT owning .NET runtime category

[tonyqus]

Related Problem

I'm working on the plan of creating a community-owned .NET runtime. But I may need nuget.org's support to provide extra categories for non-MSFT-owned .NET runtime such as Open .NET 8 (ONET8), Open .NET 9 (ONET9) and so on. The concept is similar to OpenJDK.

I understand it may be hard for you to understand why we need a community-owned .NET runtime. The major reason is to increase the diversity of .NET runtime and make the market more booming than ever before.

Some board member in .NET foundation did mention that Microsoft owned .NET runtime can be safer since MSFT hires a few FTE to work on it. But a community-owned .NET runtime can help other big giant companies accept .NET runtime much easier.

Let me know your thoughts about this. Thank you!

The Elevator Pitch

Create new runtime categories for the community-owned .NET runtime

Additional Context and Details

No response

[erdembayar]

^ @OliaG
Could you please chime in here?

[erdembayar]

@tonyqus
FYI: I believe you can still publish community led .NET runtime even without dedicated category. If you have any concern please let us know.

[tonyqus]

Thank you for keeping this ticket open and willing to discuss this topic.

I believe you can still publish community led .NET runtime even without dedicated category. If you have any concern please let us know.

True. But the problem is that with the development of the new community version, .NET 10 and Open .NET 10 can be very different in APIs. Then it may cause compatibility issues if nuget.org doesn't provide categories to tag different .NET runtime versions.

The plan is that the open .NET runtime will fork from .NET v8.0.13 tag of .NET runtime repo and then start the new development with the community's help.

[erdembayar]

Thank you for keeping this ticket open and willing to discuss this topic.

I believe you can still publish community led .NET runtime even without dedicated category. If you have any concern please let us know.

True. But the problem is that with the development of the new community version, .NET 10 and Open .NET 10 can be very different in APIs. Then it may cause compatibility issues if nuget.org doesn't provide categories to tag different .NET runtime versions.

The plan is that the open .NET runtime will fork from .NET v8.0.13 tag of .NET runtime repo and then start the new development with the community's help.

Do you have examples of any packages that have already been created? We could start a discussion on creating a new category if there is a considerable number of packages with custom runtime that already exist. Without seeing actual examples, it's too early to plan and implement. What we see in actual implementation and our assumptions could be different.