Determine what to do about personal projects

In our discussions with GitLab, they have us under the Open Source license. This license does not allow personal or private projects. I discussed with them why we have some private projects, and they verified that even though we have these, we should continue to use this license.

When I did the seat audit, I determined through an attempt to understand their rules, that we had approximately 148 users that counted as "Seats". However, when we activated Ultimate, the admin interface was complaining that we were over our allocated license limit. After further analysis, it was discovered that I had not included the Owner role for personal projects in this count. As a result, the license seat number is much lower than what the User statistics in the admin interface show (there is approximately 550 additional seats counted there). These additional seats are due to personal projects, where people are Owners.

I noted this to GitLab folks, and asked them how this might affect things, and asked for guidance for how to handle this. They said that they are happy to work with us on figuring out what these projects are or if they could be made open source/public/licensed, and suggested to check back with them in about 3 months before the license expires to come up with a solution.

However, making these personal projects public, wont change the 'Owner' and thus the seats, and probably most of these are public already?

We likely have quite a few of these personal projects that are no longer active, and could be reduced through some careful auditing and cleanup.

This may require thinking outside of the box about how we handle users, personal projects, and forking process.

@anarcat also noted that there is an issue with people being able to fork repositories. Its possible that is because those people are 'external' users, and they'd have to be promoted to be able to do this.