| ▲ | financltravsty 7 hours ago |
| This ethos doesn't gel with the old ethos and that's where the disconnect comes from. At one point Google was there to build cool shit and enable people to do it; not extract maximal amount of value and "being Evil" by the values of its time. |
|
| ▲ | davidgay 5 hours ago | parent | next [-] |
| The open source policy described above was in place 16 years ago (I went through it to continue working on some existing projects), and I doubt it was very new then. |
| |
| ▲ | Grombobulous 4 hours ago | parent [-] | | And it's not just about open source, it's about the author of this tool using trademarks and effectively impersonating Google. Judging by the screenshot of the repo, I think most people who download this would think that it's official Google software. | | |
|
|
| ▲ | Arainach 6 hours ago | parent | prev | next [-] |
| Build cool shit and follow the proper release procedures for it. There is a huge difference between something unrelated to your employer on a personal repo, youremployerrepo/api-samples, and calling something "Employer Majorproduct CLI" on an official employer repo which is bound to be confused for an official release. I would have been fired from every employer I've ever worked for of any size for doing something like that - including Google circa 2018. |
| |
| ▲ | DANmode 3 hours ago | parent [-] | | > follow the proper release procedures for it What happens when your thing or nothing close to your thing will ever see the light of day? | | |
| ▲ | no-name-here 3 hours ago | parent | next [-] | | 1. If google said ok but don't release under google’s name/in google’s repo, do that. 2. If google said no this goes against our goals for the product, don't release it if you want to keep working for google? | |
| ▲ | sib 3 hours ago | parent | prev | next [-] | | Is that relevant here, given that Google was creating an official thing quite close to his thing at the same time? (And why are we writing like this?) | | |
| ▲ | gedy an hour ago | parent | next [-] | | Would you like them in a house? Would you like them with a mouse? | |
| ▲ | seanhunter 2 hours ago | parent | prev | next [-] | | Fair to point out, the official google thing, was quite a lot worse than his thing. (I’m quite into the whole “Posting in free verse” idea) | |
| ▲ | DANmode 2 hours ago | parent | prev [-] | | > Google was creating an official thing
quite close to his thing Just link to it. | | |
| |
| ▲ | Arainach 2 hours ago | parent | prev [-] | | None of that is relevant. You're working on things for their employer, they control when and if anything is released. Most of us have worked on projects that were cancelled - even when that happens you don't just release it anyway. |
|
|
|
| ▲ | financltravsty 7 hours ago | parent | prev | next [-] |
| Just a very sad departure from more humanistic values towards "well technically their legal rights take precedence over common good." Especially that he's an "engineer" not a "Googler" or "a person." God what a fall from grace. |
| |
| ▲ | mh2266 5 hours ago | parent | next [-] | | I'd much rather be an "engineer" than a "Googler" (I don't work at Google) or any other corporate cutesy name. No thanks... | |
| ▲ | debo_ 5 hours ago | parent | prev [-] | | I was there in 2005 and we were basically told point-blank that we couldn't open source _anything_ without running it by a manager first. This was at a time where all engineers were basically housed in the main 4 buildings on the north campus, so not yet all that big. Not sure what grace they fell from, but I found it to be a nauseating sanctimonious place even then. | | |
|
|
| ▲ | vachina 5 hours ago | parent | prev [-] |
| Ya we all can build cool shit all day if the world isn’t a litigious bitch. “Actions have consequences” |
