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.
> 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.
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.
Idk if the firing was justified since he supposedly followed process and had manager approval, but that's only one side.