Rename from Django Community to Django Commons

.github/ISSUE_TEMPLATE/admin-request.yml

@@ -1,7 +1,7 @@
 name: Admin request
 description: Have a question, concern or request for the admins?
 labels: ["Admin request"]
-assignees: 'django-community/admins'
+assignees: 'django-commons/admins'
 body:
   - type: textarea
     id: admin-request

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: Have an idea you'd like to discuss with other members?
-    url: https://github.com/orgs/django-community/discussions
+    url: https://github.com/orgs/django-commons/discussions
     about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/new-member.yml

@@ -1,12 +1,12 @@
 name: New member
-description: Become a new Django Community member with the following form.
+description: Become a new Django Commons member with the following form.
 labels: ["New member"]
-assignees: 'django-community/admins'
+assignees: 'django-commons/admins'
 body:
   - type: markdown
     attributes:
       value: |
-        Thanks for expressing interesting in joining Django Community!
+        Thanks for expressing interesting in joining Django Commons!
   - type: textarea
     id: why-join
     attributes:
@@ -25,8 +25,8 @@ body:
     id: terms
     attributes:
       label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/django-community/membership/blob/main/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/django-commons/membership/blob/main/CODE_OF_CONDUCT.md)
       options:
-        - label: I agree to follow Django Community's Code of Conduct
+        - label: I agree to follow Django Commons's Code of Conduct
           required: true
 

.github/ISSUE_TEMPLATE/transfer-project-in.yml

@@ -1,19 +1,19 @@
 name: Transfer project in
-description: Transfer a project into Django community with the following form.
+description: Transfer a project into Django commons with the following form.
 labels: ["Transfer project in"]
-assignees: 'django-community/admins'
+assignees: 'django-commons/admins'
 body:
   - type: markdown
     attributes:
       value: |
-        Thanks for expressing interesting in adding your project to Django Community!
+        Thanks for expressing interesting in adding your project to Django Commons!
 
-        Please review the [incoming repository requirements](https://github.com/django-community/membership/blob/main/incoming_repo_requirements.md) before submitting your request.
+        Please review the [incoming repository requirements](https://github.com/django-commons/membership/blob/main/incoming_repo_requirements.md) before submitting your request.
   - type: input
     id: project-url
     attributes:
       label: What's the URL to the project?
-      placeholder: "https://github.com/django-community/django-community-playground"
+      placeholder: "https://github.com/django-commons/django-commons-playground"
     validations:
       required: true
   - type: input
@@ -29,7 +29,7 @@ body:
       options:
         - label: Does the project have tests?
         - label: Does the project have documentation?
-        - label: Has the project adopted Django Community's Code of Conduct?
+        - label: Has the project adopted Django Commons's Code of Conduct?
   - type: textarea
     id: new-maintainers
     attributes:

.github/ISSUE_TEMPLATE/transfer-project-out.yml

@@ -1,7 +1,7 @@
 name: Transfer project out
-description: Transfer a project out of Django Community.
+description: Transfer a project out of Django Commons.
 labels: ["Transfer project out"]
-assignees: 'django-community/admins'
+assignees: 'django-commons/admins'
 body:
   - type: markdown
     attributes:
@@ -13,12 +13,12 @@ body:
     id: transfer-location
     attributes:
       label: Which person or organization is the repository being transferred to?
-      placeholder: "https://github.com/django-community"
+      placeholder: "https://github.com/django-commons"
     validations:
       required: true
   - type: textarea
     id: reason
     attributes:
-      label: Please explain why the project is being transferred out of Django Community.
+      label: Please explain why the project is being transferred out of Django Commons.
     validations:
       required: false

.github/workflows/new_member.yml

@@ -13,7 +13,7 @@ jobs:
       - name: Check if commenter is in the admins team
         id: check_membership
         run: |
-          ROLE=$(gh api -X GET /orgs/django-community/teams/admins/memberships/${{ github.event.comment.user.login }} --jq '.role')
+          ROLE=$(gh api -X GET /orgs/django-commons/teams/admins/memberships/${{ github.event.comment.user.login }} --jq '.role')
           
           if [[ "$ROLE" == "maintainer" ]]; then
             echo "is_team_member=true" >> $GITHUB_OUTPUT
@@ -33,7 +33,7 @@ jobs:
         run: echo "User to invite is ${{ github.event.issue.user.login }}"
       - name: Invite User to Organization
         run: |
-          gh api -X PUT /orgs/django-community/memberships/${{ github.event.issue.user.login }}
+          gh api -X PUT /orgs/django-commons/memberships/${{ github.event.issue.user.login }}
         env:
           GITHUB_TOKEN: ${{ secrets.ORG_CONTROLS_PAT }}
       - name: Close Issue

CODE_OF_CONDUCT.md

@@ -1,5 +1,5 @@
 
-# Contributor Covenant Code of Conduct
+# Django Commons Code of Conduct
 
 ## Our Pledge
 

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 Django Community
+Copyright (c) 2024 Django Commons
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

incoming_repo_requirements.md

@@ -1,11 +1,11 @@
 # Requirements for Incoming Repositories
 
-Thank you for looking at Django Community to help maintain your
-repository! We're here to help however is best for both the project
-and the community.
+Thank you for looking at Django Commons to help maintain your
+repository! We're here to help find what is best for both the
+project and the community.
 
-To see how to transfer a project into Django Community, see
-[How to transfer a project in?](https://github.com/django-community#how-to-transfer-a-project-in).
+To see how to transfer a project into Django Commons, see
+[How to transfer a project in?](https://github.com/django-commons#how-to-transfer-a-project-in).
 
 ## Repository requirements
 
@@ -14,9 +14,9 @@ be transferred in.
 
 1. Tests that run in CI
 2. Maintained documentation
-3. Adopt [Django Community's Code of Conduct](https://github.com/django-community/membership/blob/main/CODE_OF_CONDUCT.md)
+3. Adopt [Django Commons's Code of Conduct](https://github.com/django-commons/membership/blob/main/CODE_OF_CONDUCT.md)
 4. After transferring, switch to [PyPI's "Trusted Publisher"](https://docs.pypi.org/trusted-publishers/)
-   process (see [example in django-community-playground](https://github.com/django-community/django-community-playground/blob/main/.github/workflows/release.yml))
+   process (see [example in django-commons-playground](https://github.com/django-commons/django-commons-playground/blob/main/.github/workflows/release.yml))
 
 ### Tests
 
@@ -37,33 +37,33 @@ is highly recommended, but not required.
 
 ### Code of Conduct
 
-The repository must adopt Django Community's Code of Conduct. It should
-directly link to https://github.com/django-community/membership/blob/main/CODE_OF_CONDUCT.md
+The repository must adopt Django Commons's Code of Conduct. It should
+directly link to https://github.com/django-commons/membership/blob/main/CODE_OF_CONDUCT.md
 
 ## Maintainer requirements
 
 The current maintainers must be willing to hand over control of the
-PyPI project. The Django Community admins team and the
-Django Community's repository admin team specific to this repo will
+PyPI project. The Django Commons admins team and the
+Django Commons's repository admin team specific to this repo will
 accept possession of the PyPI project.
 
 The repository must identify which people will be the new 
 maintainers moving forward. This can contain existing maintainers.
 
 If desired, the current maintainers can temporarily join the
-Django Community's repository admin team to ensure the project's
+Django Commons's repository admin team to ensure the project's
 standards are met during the process. Being on this team gives
 them all the controls they would need to transfer the repository
-out of Django Community, back under their control. After the trial
-period, they may be removed from Django Community's repository admin
+out of Django Commons, back under their control. After the trial
+period, they may be removed from Django Commons's repository admin
 team. Regardless, it's recommended that a project go through the
-formal [transfer a project out of Django Community](https://github.com/django-community#how-to-transfer-a-project-out)
+formal [transfer a project out of Django Commons](https://github.com/django-commons#how-to-transfer-a-project-out)
 process.
 
 ## Funding
 
-This is still in the works for Django Community. If a repository
+This is still in the works for Django Commons. If a repository
 has a prior funding arrangement, that can continue provided any
 future maintainer receives an equal share. Additionally, if Django
-Community defines a formal funding policy, that must be adopted by
+Commons defines a formal funding policy, that must be adopted by
 the repository.