4 ms·

YMMV (and this is my personal view, not necessarily Google's), but in general you want to have resources associated with active owners. Otherwise when Bob leave

YMMV (and this is my personal view, not necessarily Google's), but in general you want to have resources associated with active owners. Otherwise when Bob leaves, and his zombie solo project which you no longer have any control over gets pwned, you're going to have an even bigger problem.

naasking 10y ago
No one's denying that orphaned projects are a problem, but if deactivating an e-mail has downstream effects like this, you'd expect a warning or something before permitting account deactivation.
- stickfigure 10y ago
  How would you expect to receive this warning?
  - gselva 10y ago
    In my case, where the email was hosted in Google apps, it would have been helpful if Google apps had checked with GCE before allowing email deletion. After all, this is one of the situations where being within Google Eco-system should have been a good thing.
    - naasking 10y ago
      Agreed. Or force the user to have two registered e-mails in a GCE account at all times, unless they're explicitly deleting it. Doing things implicitly with no warning is simply terrible UX.