HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
50% Positive
Analyzed from 751 words in the discussion.
Trending Topics
#google#author#code#removed#since#github#don#https#com#artemis

Discussion (25 Comments)Read Original on HackerNews
Wow, this looks pretty damning. I can't imagine Google seeing this as worth the risks. Is an innocent explanation possible here?
This is normal (specific to pyproject.toml overwriting authors). I am not sure about pyproject.toml conventions but I would have done the same. This is the equivalent of telling you who the maintainers of the project are.
Usually what you see in the code is the retention of Copyright statements on source code and LICENSE with some reference on README.
Maybe it is possible the google engineer didn't understand how open source licenses work, or didn't care since maybe it was supposed to be an internal project first that eventually ended up open sourced?
(I'm interested in what this says about current culture.)
https://github.com/google/artemis/compare/14e02c4c27bc5b3c0d...
Seems legitCredit should be assigned tho.
They're trying to cover it up now
Did you read the post? They originally removed all traces of minitap and its contributors, and only added it back when they were called out.
Yeah, they’re totally being forthright. /s
For the amount of money Google’s engineers are paid, I expect you guys to be able to tell your manager when you’ve used OSS code, since you already have a proven worth to the software engineering ecosystem as a whole… that’s why you’re a googler. If you’re too afraid to make sure attribution is properly documented, perhaps due to your only engineering knowledge centering around basic understanding of VCSs, then perhaps you’re not yet ready for the high-stakes lifestyle of a Fortune 50 Engineer.
(Although I would say it isn't a very good-faith effort to address the issue if they don't put back the author attributions they removed).
That reads like a coverup as open discourse would have admitted a mea culpa and apology.
I predict they will close the issue without discussion, citing this PR as the fix, potentially associating the fix with a less guilty looking duplicate ticket.
I'd like to be wrong but this is what other commercial projects do when they are called out on a shady practice.
They were in clear violation of Apache 2.0
https://en.wikipedia.org/wiki/Don%27t_be_evil
> "but retained it in the last sentence"
I was going to comment on the title's perpetuation of big IPs stealing/theft meme but it turns out that TFA did not use those words.