This used to be an EE issue, but it became a valuable conversation about what to do with users on GitLab.com so I moved the issue to gitlab-com/infrastructure#841.
This is now the feature proposal for implementing it.
It was an old issue, that used to be a feature proposal on EE.
But that issue turned into a discussion about what limits we will enforce on GitLab.com, so I moved it to infrastructure and then it was no longer an EEfeature proposal.
Sorry, I know that is confusing, does it make sense?
@dewetblomerus Is your proposal for this to be an evolution of https://gitlab.com/gitlab-org/gitlab-ee/issues/559, adding a "Total project size limit" to users that is enforced on top of the per-project ones? Would that only apply to their personal projects, or also projects in groups they own?
We have had a user create a group on GitLab.com and then use scripts to create over 600GB of projects in that group. So we do need this to also count the projects in groups that a user owns.
I can see how this might be bad for large organizations wanting to use GitLab.com, but I think the best way to cater for that is to one day add paid extra storage as an add-on.