4 ms·

The repo is still online and is official [1], so Google doesn't really seem to care about its existence. [1] https://developers.google.com/workspace/drive/api/

by whstl 4mo ago

The repo is still online and is official [1], so Google doesn't really seem to care about its existence. [1] https://developers.google.com/workspace/drive/api/samples https://developers.google.com/workspace/drive/api/samples

magicalist 4mo ago
It's a fair point that it's still up, though looking just now for two minutes there are at least some issues with auth[1] which would make me really not trust it. It was just speculation about what could be bad enough if they really did have permission to release it, but the OP is being so cagey below now I'm just wondering if they got release permission but misrepresented what they would be releasing or something. > and is official [1] FWIW no idea what you're trying to point out on that page unless you mean the one link to a different project in the same github org indicates the org is official, but that never seemed in doubt in this thread of comments. [1] https://github.com/googleworkspace/cli/issues/780 https://github.com/googleworkspace/cli/issues/780
- whstl 4mo ago
  If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository.
  - frollogaston 4mo ago
    Maybe at this point it's even more disruptive to delete it since people are using it. There's a real reason to not want someone to release an official-looking CLI when you're already doing an actual official one for the same thing. Idk if the firing was justified since he supposedly followed process and had manager approval, but that's only one side.
    - whstl 4mo ago
      Google doesn’t even care to tell its side. HR/Legal very often will give bullshit reasons for termination, since their main job is to shield the company from lawsuits anyway.
  - magicalist 4mo ago
    > If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository. Unclear what you're referring to here. Was it "misrepresented what they would be releasing"? If that's the case, I disagree that the repo still existing is on its face evidence against that theory. It could be a perfectly fine tool, but if you lie on a release checklist, depending on what you lie about, it's easy enough to imagine a fireable offense. There are multiple ways that "it's easier to ask forgiveness" can backfire if there are legal things or organizational things you are knowingly avoiding. Again, this is just speculation. I wouldn't personally fire someone for releasing a library that got popular, but its also speculation to suggest that's the only reason he was fired.
    - whstl 4mo ago
      It's either a problem to have this released or not. Google doesn't seem to care this is in an official repo. > its also speculation to suggest that's the only reason he was fired That's the reason given by Google. The implication here is that Google is lying about this whole thing for ass-covering reasons. People here are up in arms because someone potentially misrepresented a tool that Google itself doesn't even care to remove, while Google HR and legal are possibly lying to damage someone's livelihood.

by whstl 4mo ago

magicalist 4mo ago

It's a fair point that it's still up, though looking just now for two minutes there are at least some issues with auth[1] which would make me really not trust it. It was just speculation about what could be bad enough if they really did have permission to release it, but the OP is being so cagey below now I'm just wondering if they got release permission but misrepresented what they would be releasing or something. > and is official [1] FWIW no idea what you're trying to point out on that page unless you mean the one link to a different project in the same github org indicates the org is official, but that never seemed in doubt in this thread of comments. [1] https://github.com/googleworkspace/cli/issues/780 https://github.com/googleworkspace/cli/issues/780

whstl 4mo ago
If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository.
- frollogaston 4mo ago
  Maybe at this point it's even more disruptive to delete it since people are using it. There's a real reason to not want someone to release an official-looking CLI when you're already doing an actual official one for the same thing. Idk if the firing was justified since he supposedly followed process and had manager approval, but that's only one side.
  - whstl 4mo ago
    Google doesn’t even care to tell its side. HR/Legal very often will give bullshit reasons for termination, since their main job is to shield the company from lawsuits anyway.
- magicalist 4mo ago
  > If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository. Unclear what you're referring to here. Was it "misrepresented what they would be releasing"? If that's the case, I disagree that the repo still existing is on its face evidence against that theory. It could be a perfectly fine tool, but if you lie on a release checklist, depending on what you lie about, it's easy enough to imagine a fireable offense. There are multiple ways that "it's easier to ask forgiveness" can backfire if there are legal things or organizational things you are knowingly avoiding. Again, this is just speculation. I wouldn't personally fire someone for releasing a library that got popular, but its also speculation to suggest that's the only reason he was fired.
  - whstl 4mo ago
    It's either a problem to have this released or not. Google doesn't seem to care this is in an official repo. > its also speculation to suggest that's the only reason he was fired That's the reason given by Google. The implication here is that Google is lying about this whole thing for ass-covering reasons. People here are up in arms because someone potentially misrepresented a tool that Google itself doesn't even care to remove, while Google HR and legal are possibly lying to damage someone's livelihood.