This repository contains all the information for administrators to manage Django Commons packages.

• New member
• Team change
• New repository admin
• New project
• Remove project

1. Review new issues/application at https://github.com/django-commons/membership/issues/
2. If they are not a real human or not reasonably trustworthy, close the issue, asking for more information they are a human and not a spambot. You can explain that by being a member, they can impact repositories immediately.
3. Add the user's GitHub username to the members collection in the terraform/production/org.tfvars file.

     members = [
       # ...
       "new_user"
     ] 

4. If they requested to be on specific repository team(s), in the terraform/production/repositories.tfvars file, add them to the members collection.

     repositories = {
       "[REPOSITORY]" = {
         # ...
         members = [
           # ...
           "new_user"
         ]
       }
     }

5. Create a pull-request to main branch. This will trigger terraform to plan the changes in the organization to be executed. Review the changes and make sure they align with the request.
6. Merge the pull request. This will trigger terraform to apply the changes in the organization.

1. If they are not a real human or not reasonably trustworthy, close the issue, asking for more information if they are a human and not a spambot. You can explain that by being a member, they can impact repositories immediately.
2. For the requested repository's team(s), in the terraform/production/repositories.tfvars file, add them to the members collection.

     repositories = {
       "[REPOSITORY]" = {
         # ...
         members = [
           # ...
           "new_user"
         ]
       }
     }

3. Create a pull-request to main branch. This will trigger terraform to plan the changes in the organization to be executed. Review the changes and make sure they align with the request.
4. Merge the pull request. This will trigger terraform to apply the changes in the organization.

1. Confirm with all existing admins that they approve changes to the repository admins or committers.
2. If there's disagreement, close the issue and ask for the admins to come to a consensus
3. For the requested repository's team(s), in the terraform/production/repositories.tfvars file, for the repository's key under repositories, add them to the admins collection for the correct team. There will be two privileged teams for each repository, *-admins and *-committers, the user should be added to the requested team.

     repositories = {
       "[REPOSITORY]" = {
         # ...
         admins = [
           # ...
           "new_user"
         ]
       }
     }

4. Create a pull-request to main branch. This will trigger terraform to plan the changes in the organization to be executed. Review the changes and make sure they align with the request.
5. Merge the pull request. This will trigger terraform to apply the changes in the organization.

1. Check if repository meets inbound requirements.
2. Confirm who will be the admins and maintainers for the repository
3. PyPI project owner must add you (Django Commons admin) as owner in PyPI
4. (TODO: Determine how this works with transferring out of an org and into the Django Commons org)
5. Add repository owner to Django Commons as member (they'll be added to a team later)
6. Share link (https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) with repo owner to transfer repo
7. Wait for repository transferred in
8. Make Terraform changes to add new project
9. Configure environments pypi and testpypi in the repository to enable publishing packages via GitHub Actions
10. For pypi environment, add Deployment protection rule with reviewers as [repo]-admins and enable "Allow administrators to bypass configured protection rules"
11. Under Actions > General > "Fork pull request workflows from outside collaborators", set "Require approval for first-time contributors"
12. Set a calendar event or reminder for 30 days in the future to remove previous repository owner from team

Assuming repository name is repo-name:

1. In terraform/production/respositories.tfvars, add the new repository to the repositories section:

repositories = {
   # ...
   "repo-name" = {
      description = "repo description"
      allow_auto_merge = false # optional, default is false
      allow_merge_commit = false # optional, default is false
      allow_rebase_merge = false # optional, default is false
      allow_squash_merge = false # optional, default is false
      allow_update_branch = false # optional, default is false
      enable_branch_protection = true # optional, default is true
      has_discussions = true # optional, default is true
      has_downloads = true # optional, default is true
      has_wiki = false # optional, default is false
      is_template = false # optional, default is false
      push_allowances = []
      required_status_checks_contexts = [] # optional, default is []
      template = "" # optional, default is ""
      topics = []
      visibility = "public" # optional, default is "public"
      skip_team_creation = false # Optional, default is false => create 3 teams for the repository
      admins = [] # Members of the repository's admin and repository teams. Have admin permissions
      committers = [] # Members of the repository's committers and repository teams. Have write permissions
      members = [] # Members of the repository team. Have triage permissions
   }
}

1. Confirm there's agreement amongst current project maintainers to move project out of Django Commons
2. Add new Owner(s) to project in PyPI
3. Transfer GitHub repo to new owner or Org
4. Wait for repository to be transferred out.
5. Remove all Django Commons members from PyPI project (except any that are staying on from step 2)
6. (TODO: Determine how to handle transferring a PyPI project out of an organization)

1. Remove the repository from the repositories section in terraform/production/respositories.tfvars
2. Remove the parent team and child teams for the repository from the teams_repositories and teams_repositories_privileged sections in terraform/production/teams.tfvars
3. Create a pull-request to main branch. This will trigger terraform to plan the changes in the organization to be executed. Review the changes and make sure they align with the request.
4. Merge the pull request. This will trigger terraform to apply the changes in the organization.