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

License violation #315

Closed
CarlSchwan opened this issue Dec 25, 2021 · 10 comments
Closed

License violation #315

CarlSchwan opened this issue Dec 25, 2021 · 10 comments

Comments

@CarlSchwan
Copy link

Hi 👋

I wanted to let you know that it seems Microsoft forked this repo and changed the license to the MIT license in their fork and are claiming to have copyright to this repo (Copyright (c) Microsoft Corporation.)

microsoft@ad69bcc

INAL but this seems to be a copyright violation.

@aloisdg
Copy link

aloisdg commented Dec 25, 2021

Related to grpc_bench

@6uhrmittag
Copy link

For reference, the current Hacker News discussion: https://news.ycombinator.com/item?id=29683471

It's worth noting that some comments suspect it to be a misconfigured bot action.

@madscientist42
Copy link

madscientist42 commented Dec 25, 2021

The problem I happen to have with that take? That this was all the way into the beginning of the year. Bot? Perhaps. Inexcusably SLOPPY, even for proprietary software practices? YEP.

PLEASE, folks, don't just excuse what is something the Courts (because you're required to do due dilligence on things like, "bots," doing this) would deem as a WILLFUL ACT OF INFRINGEMENT. If the shoe were on the other foot, you'd have hoards of lawyers descending upon you before you could even remotely sort it out...if you even could.

@jeffwilcox
Copy link

We've reverted the incorrect LICENSE files in the repository and are going to look through the other forks where this may have happened. I wrote the bot code that's misbehaving and feel horrible about this.

@madscientist42
Copy link

You had this lurking for almost a year...not really acceptable enough to say, "sorry" by and of itself.

@madscientist42
Copy link

If Microsoft had that happen to THEM...do you think they'd just say, "It's all okay...it's fixed now"?

@CarlSchwan
Copy link
Author

Thanks for the update @jeffwilcox

@ghost
Copy link

ghost commented Dec 25, 2021

你们所有开源作者,应该 向微软道歉,你们侵犯了微软的权利,你们在开源代码的同时,居然胆敢写上自己版权所有?还得麻烦微软亲自帮你们一一改正过来。
给你们一天时间,快自己主动改成微软。
所有github项目,版权归微软所有。
烦请所有开源项目,早日改邪归正,不要迷途不返。

@dmccollough1
Copy link

You had this lurking for almost a year...not really acceptable enough to say, "sorry" by and of itself.

Exactly this. Do proper code and repo reviews.

@michaelrsweet
Copy link
Member

OK, folks, I think this discussion has reached a natural conclusion. FWIW, as the original author of all this code I am not offended and am happy that things have been fixed in the MS forks.

@OpenPrinting OpenPrinting locked as too heated and limited conversation to collaborators Dec 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants