Transfer an organization?

[ehmatthes]

Hi! First of all, thank you for creating this. It's a fantastic idea, clearly builds on prior efforts in this area, and looks like it's off to a great start.

Is there a mechanism for transferring an organization in? I don't have a specific org in mind, but I'm thinking of all the open projects I've seen that are structured as orgs because the project consists of more than one repo.

I am not aware of support for nested orgs, but maybe teams could be used to implement support for an org? Transfer all the repos from the org, then make a team that has access to those specific repos?

[tim-schilling]

Hi Eric, thanks for reaching out. Currently I have an issue template for "Transfer project in" available at: https://github.com/django-commons/membership/issues/new/choose (new issue on the membership repo). The playbook an admin/organizer will follow can be found in the controls repo here

[ehmatthes]

This all looks good. As a side note, the ARCHITECTURE post is exactly what I was looking for this past week, so I appreciate the inclusion of that.

[tim-schilling]

I didn't have anything in mind for handling an org transferring an entire suite of projects. I think it'd be best to treat them individually since I don't expect to have sub-organizations in Django Commons. Or at least not right now. Until the org has its legs underneath it, it should approach things in the most simple, repeatable manner.

[ehmatthes]

Sounds good! Thanks for getting this off the ground!