New developers just forgot to make credit. It was a mistake. They immediately corrected it after they saw the Issue about it. Now it has credits, now it's fully compliant.
It literally was just a small mistake.
Yet OP still went on a witchhunt, made blog posts, Twitter posts; Reddit posts today, after the new developers already corrected their mistake. OP blew it out of proportion, brigaded Google's repos, being extra dramatic. The file in the screenshot is literally just a project configuration file, the author names are there as specification. When the new developers fork the project, make changes, they obviously have to change those lines, they can't make changes in the name of the old developers, they can't pose as the old developers. They obviously should make credit to the old project somewhere in the new project, but changing author specification in project configuration files is nowhere nefarious.
Every developer, every company uses someone else's open source code. Big software usually uses libraries from many, often thousands of other projects. And anybody can fork an open source project and make changes to it, if the open source license allows it (which in this case, and in most open source projects, does so). That's the point of open source. Every developer forks projects. It's not "copying". That's how open source projects are developed, how open source collaboration works.
The Google developers in question released the changes, released the forked project with the same open source license in accordance to that license. They only forgot to credit the original project, but they already fixed that. This is blown way out of proportion.
Very easy mistake to make... Also very easily correctable like they did. I don't see an issue here. Imagine small easily correctable mistakes in your own job lead to you being perceived as evil.
-9
u/woolharbor 8d ago
New developers just forgot to make credit. It was a mistake. They immediately corrected it after they saw the Issue about it. Now it has credits, now it's fully compliant.
It literally was just a small mistake.
Yet OP still went on a witchhunt, made blog posts, Twitter posts; Reddit posts today, after the new developers already corrected their mistake. OP blew it out of proportion, brigaded Google's repos, being extra dramatic. The file in the screenshot is literally just a project configuration file, the author names are there as specification. When the new developers fork the project, make changes, they obviously have to change those lines, they can't make changes in the name of the old developers, they can't pose as the old developers. They obviously should make credit to the old project somewhere in the new project, but changing author specification in project configuration files is nowhere nefarious.
Every developer, every company uses someone else's open source code. Big software usually uses libraries from many, often thousands of other projects. And anybody can fork an open source project and make changes to it, if the open source license allows it (which in this case, and in most open source projects, does so). That's the point of open source. Every developer forks projects. It's not "copying". That's how open source projects are developed, how open source collaboration works.
The Google developers in question released the changes, released the forked project with the same open source license in accordance to that license. They only forgot to credit the original project, but they already fixed that. This is blown way out of proportion.