Compatibility/overlap with the OpenFeature Spec/SDK

While checking something completely unrelated today, I stumbled upon this:

• https://openfeature.dev/

Similar to OpenTelemetry, this appears to be a SPEC + SDK standardization effort around the concept of feature flags/toggles. I noticed it already has a .NET implementation as well:

• https://www.nuget.org/packages/OpenFeature

However, its interface is not very "idiomatic" to modern .NET patterns. For instance, it doesn't seem to have native integration with the hosting model and Dependency Injection, while this library here has those.

Looking at the list of known providers for OpenFeature, it doesn't list Microsoft's FeatureManagement there:

• https://openfeature.dev/ecosystem/?instant_search%5BrefinementList%5D%5Btype%5D%5B0%5D=Provider&instant_search%5BrefinementList%5D%5Btechnology%5D%5B0%5D=.NET

Does Microsoft intend to support this spec in a way similar to how it does for OpenTelemetry today? Are there any talks around unifying this FeatureManagement project around the concepts exposed by OpenFeature, perhaps even making it the oficial SDK, or at least the hosting model compatible SDK (like OpenTelemetry.Extensions.Hosting)?

We had some plans to leverage FeatureManagement for our own currently custom feature flags system, but now I'd also want to be able to leverage this standardized OpenFeature SDK as it will be easier to support things such as OpenTelemetry integration in the future if the SDK is standardized.

Start by comparing the OpenFeature specification and .NET SDK with FeatureManagement’s hosting-model and dependency-injection integration, using the linked OpenFeature and NuGet resources. Clarify whether the requested outcome is compatibility, a provider, or unification with the official SDK; done would require a documented maintainer decision and defined integration scope.