[flagged]
I reported it to Twitter as violation of it terms with relevant category.
Twitter said naming people Pussy is fine.
Fired by Google for creating the Google workspace CLI
261–270 of 472 posts
Re: Fired by Google for creating the Google workspace CLI
#262Interesting that people here seem so sympathetic to the fired guy. Wouldn’t you kind of expect to be fired if you release a project under your employers name that’s not even associated with them and hasn’t been cleared? Working for them actually makes it worse because people could look up your name and would see that you actually work for google. It’s kind of obvious that this is a bad idea, right?
Yeah I'm struggling to believe that this person who worked at Google for 7 years was surprised by this outcome. Google has very clear processes for contributing to open source as an employee. I'm skeptical that this person never navigate to go/opensource (not remembering exactly the link, but it might literally be that) and read the policies there in that amount of time... This is not even an endorsement of those pol…
He worked for devrel under Osmani. These guidelines and processes do not apply to them, last I checked.
Re: Fired by Google for creating the Google workspace CLI
#263Earlier quoted context omitted.
> 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?
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?)
Would you like them
in a house?
Would you like them
with a mouse?
Re: Fired by Google for creating the Google workspace CLI
#264Earlier quoted context omitted.
You are assuming that it was "personally" releasing something and that the process wasn't followed.
You continue to dance around this question on this post - did you or did you not follow Google's open source approval process[1]? Did you have an approved Ariane/Launcher2 entry? 1: https://opensource.google/documentation/reference/releasing/...
Yes
Re: Fired by Google for creating the Google workspace CLI
#265Earlier quoted context omitted.
Pretty sure that the agreement that Google employees sign (a "contract") when hired reflects exactly that. At least at did when I joined (I left > 3 years ago, speaking here only for myself...)
Is it legal (or moral) for an employer to keep you from being a board member of a dog rescue or a glove repair company without review?
The answer is not that it matters, but as a matter of financial and legal controls they need to know and approve. Do they care? They probably are delighted, but also want to get all the paperwork set up to avoid problems.
The space this comes from is the legal undue influence side where they need to give notice to shareholders about potential conflicts of interest, and it needs to be in the form of having a clear positive audit trail that they have told people to follow a clear policy with no grey area so that any deviation is an accident not willful failure to get people to tell them.
Re: Fired by Google for creating the Google workspace CLI
#266Earlier quoted context omitted.
Where are you getting the information that this project hadn't been cleared? That seems like a big assumption, and I don't see anything in the linked tweet, or the replies, or any of the linked pages that supports it. Unless I missed something?
He's being intentionally vague and combative in his statements. I think it's fair to assume there was a process issue when even as he admits he was "grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories". Clearing up the issue would take a single comment that all the correct processes were followed. The fact he hasn't said as much is the elephant in the room…
There is a two "calendar" launch process for OSS at Google, one "calendar" is org specific, the other OSS. I followed the process and each of the bits were flipped in the same way I had always done it.
Re: Fired by Google for creating the Google workspace CLI
#267Put aside whether this was justified or not, or the potential Streisand effect or PR damage (or vice versa). What signal is this sending to the young Google engineer who wants to build the next Gmail? Even if this violated every internal policy, firing someone who created something that people actually want is sending a very disturbing message (internally and externally).
Also, is this somehow relate to Addy Osmani’s recent departure from Google? (Was it in sympathy, was it a retaliation as this was “the tweet that got OP fired”?)
Re: Fired by Google for creating the Google workspace CLI
#268Earlier quoted context omitted.
To clarify, I was on the Google Workspace Developer Relations team, the majority of my work was that exact OSS release process. It is not clearly documented and always changing. You can read some of it here, https://opensource.google/documentation/reference/releasing/... , but like I said it is always changing. Relevant: https://www.theregister.com/software/2023/01/27/what-is-goog...
Something in the explanation is missing here. It's still not clear to me from any of the provided context whether you got approval to release this. At least from my understanding of your role, if you had approval and used an official google repository, you would not get fired for merely publishing code that accesses a documented API through documented endpoints. Hence many people are wondering if you released this wi…
There was a Ariane/Launch with bits flipped including the eng bit from my manager.
Re: Fired by Google for creating the Google workspace CLI
#269Earlier quoted context omitted.
To clarify, I was on the Google Workspace Developer Relations team, the majority of my work was that exact OSS release process. It is not clearly documented and always changing. You can read some of it here, https://opensource.google/documentation/reference/releasing/... , but like I said it is always changing. Relevant: https://www.theregister.com/software/2023/01/27/what-is-goog...
Straight from that page: >This includes side projects that have not gone through IARC, even for DevRel engineers. So did you do this "Launcher2" or "Ariane" thing and get the approvals? If so, it seems your ass would be covered. If not... I can sympathize that the process seems convoluted and could particularly bite a DevRel accustomed to more autonomy. One would hope Google would do the whole blame free retrospectiv…
Yes there was a launch with eng bit flipped by manager.
Re: Fired by Google for creating the Google workspace CLI
#270Earlier quoted context omitted.
To clarify, I was on the Google Workspace Developer Relations team, the majority of my work was that exact OSS release process. It is not clearly documented and always changing. You can read some of it here, https://opensource.google/documentation/reference/releasing/... , but like I said it is always changing. Relevant: https://www.theregister.com/software/2023/01/27/what-is-goog...
Maybe I'm misunderstanding, but it really sounds like you knew the policy in depth, and even contributed to the design of the policy, but when it came to your pet project you ignored it by skipping the release process? Am I missing something?
Wasn't ignored or skipped.