Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WhiteSource is called Mend #55

Open
winterrocks opened this issue Sep 5, 2023 · 1 comment
Open

WhiteSource is called Mend #55

winterrocks opened this issue Sep 5, 2023 · 1 comment

Comments

@winterrocks
Copy link

Replace WhiteSource with Mend

https://github.com/OpenChain-Project/Reference-Material/blob/master/Adoption-Preparation/Model-Provisions/openchain-standards-model-provisions.0.5.md#q4do-you-use-any-software-tools-or-services-to-assist-with-open-source-license-compliance-for-example-black-duck-scancode-white-source-fossology-sw360

WhiteSource changed their name to Mend already some time ago and I'm suggesting that on this Q4 we'll use Mend instead of WhiteSource

Additional context
Let's use the current name. Of course we could list many other tools too, but it says "For example" so there is no need to list dozens of tools.

@andrewjskatz
Copy link
Member

Good point. I'm not sure that the Mend.io has much name recognition yet, and this whole space is subject to constant changes of name and ownership, so I'm tempted to delete the reference entirely. Black Duck still seems to be called Black Duck, even within Synopsys. References to FOSSID/Snyk, Palamida/Revenera/Flexera would just be confusing as well, I think. I do want to keep at least one proprietary name in there, however, to ensure that there is no implication that we are only interested in open source tools as the answer to this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants