3 ms·
No one is saying there's anything wrong with releasing your code under the BSL. What's wrong is that you're lying and claiming you're open sourcing your code.
by azdle 3y ago
No one is saying there's anything wrong with releasing your code under the BSL. What's wrong is that you're lying and claiming you're open sourcing your code.
- tedivm 3y agoAt this point it's hard not to think that they're purposefully ignoring this. It doesn't matter how many times I say that I don't care about their license, just their messaging, and yet we've got at least three employees from Sentry completely ignoring that and acting as if we don't think they have a right to license their own software. It's a straw man that lets them ignore the actual issue people have.
- ssddanbrown 3y agoThey've been like this before with Sentry, when I've raised their sketchy use of open source. I have some example queries/responses in this issue: https://github.com/ssddanbrown/Open-Source-Confusion-Cases/issues/7 https://github.com/ssddanbrown/Open-Source-Confusion-Cases/i... The repo readme has other examples of sketchy cases of open source and licensing usage. This aspect (of why not just use a different term) often gets ignored. Sometimes folks say they're using it "to prevent confusion to users since they would have heard about open source" which is always an ironic self-involved viewpoint to see.