Hacker News Reader

Comment by dak1 | Hacker News Reader

This is a teachable moment for a young student. Let's avoid crucifying them.

We've all made mistakes, most of us were just fortunate enough that it didn't end up as the top link in Hacker News.

It might have not been a mistake at all. The thread shows a comment by a more senior Google employee asking for clarification as there is no infringement he can see.

I may be in the minority that agrees with you here.

Giving constructive feedback / discussion that may lead to GCP supporting the OP's project may be a better way than going directly to "I'm going to get my lawyers involved".

From the current discussion it also looks like some people don't even agree that this repo steals from the OP.

This is a teachable moment for the guy who posted the comment, not the intern, since the repo isn't even a fork of his stuff and he comes off like a petulant asshole that would have been better served trying to solve this issue through some more direct line of communication as a first step. At the very least it would have saved him the embarrassment of being so publically wrong.

Yeah, blame should be placed on whoever did the code review, but this is probably something the intern learned/got away with in school.

Yes. I don't know what the rules for making code public are at Google, but where I work we are incredibly cautious.

I would have thought Google would have been far more cautious.

If you look at the repo it's not clear at all if there is an issue. It's certainly not a fork of a repo. It actually includes gemstash as a dependency [1] which is a really weird thing to do if it was actually a copy of gemstash.

https://github.com/GoogleCloudPlatform/google-cloud-gemserve...

If there is a lack of caution I think it's on @indirect's side.

Or the original allegation is totally baseless, which appears to be the case. You should have investigated the issue before insinuating the accused is a serial plagiarizer.

We've all made mistakes - but I highly doubt that we've all stripped away an inconvenient license from software that we've forked.

Well. When your mistake involves stealing other peoples work (yes, I equate "using without proper attribution" and "changing the license" with stealing), I think a few crosses and nails are in order.

Reply on news.ycombinator.com