[rvivek]

Oscar, thank you for responding and I'm terribly sorry for the disruption this has caused. I should have taken this more seriously when it sprung up on HN the first time but for whatever reason we just fixed that problem and moved on. This is a serious one and we are working on a strategy that is sustainable.

Meanwhile, if we need to make a monetary contribution for your effort or anything more we could do to promote, what would be the best way to do it? If you'd like to send me an email to discuss further, I'm available at vivek at hackerrank

Thank you & sorry!

[not2b]

If you don't want to utterly destroy your company's reputation and have every company that depends on Python or other critical open source infrastructure boycotting you, you need to stop. Just stop. Don't send out any DMCA notices at all, not unless you encounter a case of infringement so blatant that it is obvious to all. And then make the decision yourself, don't contract it out. The risk of damage to others and blowback to you is too great. You're risking the failure of your company if something like this happens another time after two high-profile cases; damage to your company could be that bad.

And here's the thing: if there's a match between the SymPy Docs and something you consider yours, the copying was quite likely in the reverse direction: the solution you claim copies something out of the SymPy documentation (which is legal, but it isn't yours).

[rvivek]

Yes, agree https://news.ycombinator.com/item?id=31092085

[dmurray]

You agree to

> stop. Just stop. Don't send out any DMCA notices at all, not unless you encounter a case of infringement so blatant that it is obvious to all. And then make the decision yourself, don't contract it out.

?

Sounds great - did you make similar promises last time?