|
|
|
|
|
by bragh
1687 days ago
|
|
Usually projects like this are meant to be used together with Office 365 or for extending Microsoft ecosystem. Straight from the README, but maybe there are other limitations: "This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship." |
|
That's just a trademark clause for Microsoft logos and brands. The Fluid Framework itself is MIT licensed [0] and doesn't require exposing any of those logos/brands when you use it, so the framework itself is fairly open for usage.
I think the main thing that would slow down adoption for Fluid is that the only "production" backend is an Azure service, which isn't part of the open source Fluid Framework. Other open source backends[1] aren't recommended for productions. Until there are some open source ones, I'd assume adoption will be limited to folks in the Azure ecosystem.
[0]: https://github.com/microsoft/FluidFramework/blob/main/LICENS...
[1]: https://fluidframework.com/docs/deployment/service-options/