Transfer out: django-revproxy #472

The repository has moved to django-commons/django-revproxy, with history and redirects verified. @andruten is the agreed continuing admin, and Commons has accepted RTD access. Tim accepted transfer ahead of the preparation work and opened migration #201. Tim reported the move into the Commons PyPI organization. The November 5 registry independently confirms Commons ownership, direct Owners penguin_brian and seocam, and Jazzband as Maintainer. Tim's inherited Commons publishing role remains unverified.

#203 merged on November 5 at db01e16f. GitHub then rebased #204, #205 and #202, dismissing their approvals. Their diffs are unchanged, and all reported checks passed in the November 5 recheck. Jannis renewed approvals for #204 at 2a42b514 and #205 at 0928208b. Merged #204 and #205 through stack #206 after checking their final heads, approvals and passing checks. Have andruten or another reviewer with write access approve #202 at its current head, then merge when GitHub's review and check requirements are met. Joe's question about removing Django 4.2 from tox is still open and needs a maintainer answer. It did not block the partial merge under the existing review rules. Refresh #201 against master. Keep #201 open until Commons reviews its refreshed migration and final release configuration. Publishing, destination docs and integration checks remain pending.

People

• Project leads: @andruten.
• jezdez: arrange Jazzband's ownership changes and remove obsolete access after the handoff.

TODOs

• Give @andruten repository Admin access. Verified on October 19.
• Confirm andruten requested the Commons move and Tim accepted the repository ahead of the remaining preparation. Before transfer, andruten had repository Admin access and accepted Commons membership.
• Record Tim’s acceptance of the Commons handoff.
• Confirm remaining inherited publishing roles and receiving configuration before final Jazzband cleanup. Commons already owns PyPI and has accepted RTD administration.
• Record Tim's confirmation that the package moved into the Commons PyPI organization.
• Verify Commons PyPI ownership and direct Owners penguin_brian and seocam. Jazzband remains a Maintainer.
• Confirm Tim's inherited Commons publishing role and the agreed receiving access.
• Confirm Commons has accepted RTD access. The current users include djangocommons and andruten.
• After approval, change only the RTD repository URL from https://github.com/jazzband/django-revproxy to https://github.com/django-commons/django-revproxy. Preserve master, version settings and all users. Rebuild latest once and verify the destination checkout and existing documentation. Build 35803609 passed before the transfer, so it does not verify the proposed URL change.
• Merge #203 at db01e16f after andruten's approval. The merged changes match the reviewed diff.
• Renew approvals for #204 at 2a42b514 and #205 at 0928208b after their automatic rebase. The diffs are unchanged and their checks passed.
• Obtain an approval from andruten or another reviewer with write access for #202 at its current head. Recheck its diff, target and checks after the partial stack merge.
• Merge Call to maintain newspapers #204 and Transfer django-cities-light to an org commited to free software hackers #205 through stack #206 after checking their final heads, approvals and passing checks.
• Merge Set up CI for Jazzband project releases for PrettyTable #202 once its current head satisfies GitHub's review and check requirements. Verify Codecov and receiving integration after the Commons move.
• Answer Joe's Django 4.2 tox question as a separate support-policy follow-up.
• Refresh #201 against master and resolve its conflicts for Commons review. Keep it open until the refreshed migration and release configuration are approved.
• Transfer GitHub ownership to django-commons/django-revproxy. Verify canonical ownership, repository history and old-URL redirects. Keep PyPI, RTD and Jazzband website access unchanged.
• Update publishing, CI, required checks, release reviewers and documentation for the receiving owner.
• Verify a maintainer-approved release from the destination. Keep publishing verification pending until that has happened.
• Update contribution guidance, security and conduct contacts, project links and the Jazzband badge.
• Remove obsolete Jazzband credentials and integrations after their replacements work, update the Jazzband directory, and link the completion evidence.

If retirement is agreed, replace the transfer steps with the archive, package ownership and service-retirement checks. Silence does not count as agreement.

Project details

• Repository: https://github.com/django-commons/django-revproxy
• Destination: Django Commons (GitHub transferred, closeout pending)
• Jazzband wind-down board
• Jazzband wind-down plan
• Onboarding: Implement Jazzband guidelines for django-revproxy django-commons/django-revproxy#129