What is the recommended way for consumers of OSMF libraries to discover the OSMF?

[matthew-a-thomas]

I'm most familiar with the world of C# and NuGet, so I'll frame my question from that perspective:

For example, I followed the Quick Start guide for Wix, and at no point did any of my tooling (JetBrains Rider, NuGet, dotnet) inform me that I was possibly violating a EULA. Of course, one would reasonably expect me to also read the other documentation pages where OSMF is clearly called out. But it doesn't seem to fit well with the tooling.

Any thoughts on how to approach this as a consumer of possible-OSMF libraries?

Do I just need to be less of a noob with respect to EULAs (as in actually read more of them)? Or is this a gap that tooling can fill?

Thanks for your efforts to fix the OSS funding problem. To be honest it's not something I've thought about much before. But encountering OSMF forced me to read some of the swirling context, and I have to say it doesn't look easy.

[matthew-a-thomas]

You may have already answered my question in the "Which projects do you pay?" section

1. Open each [project file and collect dependencies]
2. Search for [the identifiers online]
3. Click the "Project website" link on the right to be taken to the project.
4. Follow the instructions in the project's README file how to pay the Fee for a project

In which case, yes, I just need to be more diligent.