I created a service for my own needs based on BCU but worried about license compliance status

[zbalkan]

Hi,

This question is specific to @Klocman. I created a service for a minor problem: Win32_Product WMI class is a headache and for Group Policy WMI filters, it is unusable. The alternative is to use the path name of a known, static file, yet not every application is suitable for that.

For instance, I want to apply a Group Policy to the computers if only Chrome is installed, I should write something like this:

Select * from Win32_Product where Name like "Chrome"

But that is a huge headache. Some say Win32_Product is evil and MS actually says you should use something else like this or this.

Their suggestion is mostly using registry and write a MOF class based on them. And BCU shows us the registry is not always accurate. Other alternative is using a static path to a file -like full path to chrome.exe- to check. But not all paths are static. It is -almost- impossible to track user-scope installed MS Teams due to crazy path convention.

Then I decided to write my own WMI provider, a class with just enough properties. To publish it I started using Winget but at this point it is a hell to work with. Then I moved to BCUninstaller. I had to copy a part of the jungle to get a couple of bananas. But it works.

Now, I want to make it public though it needs refactoring. There are many unused methods, and possibly unused classes will appear after removing unreferenced methods. Before making it public, I want to get a review if the way I structured and documented are enough to comply with the Apache 2.0 license of BCU.

For a review I can make it publicly available for a while. I am not sure I can share while it is private.

What is next then?

[Klocman]

As long as you are going to publish the source and credit this repo or me then I don't see any issue with it.

[zbalkan]

Great. I'll clean up and make the repo public. Thanks for the heads up.