[fat-apple]

Thanks for your feedback! As with many in the industry, we are trying our best to figure this out.

Our intention is to be really transparent with how we build and price software, which is why our commercial features will also be public in our repo, but commercially licensed. Transparency is critical in our opinion.

This is the model we’ve seen work for other highly impactful software projects.

We’ve created a ticket to track our addition of commercial code to our repo: https://github.com/opstrace/opstrace/issues/319

[sneak]

Ahh. The commonly used "open source" term is a synonym in practice for "free software", so if you are a proprietary software vendor that is source-available but calling it "open source" (when really, it's not) is a different type of misleading.

Don't call source-available proprietary software "open source", or say that you'll "always be open source" if you're just going to be source-available for parts.