Similiar to docker-library-transitioner GitHub org (see docs upstream), this organization serves as an intermediary regarding repository ownership changes between us and old/new repository owners.

Anyone can request repository ownership transfers for their GitHub projects to Recap Time Squad as long as:

• At least maintained for the past 3 months. Otherwise, we'll either reject or archive the request to recaptimedev-archive namespace.
• Open-source project under one of either OSI-Approved, FSF-endorsed, or that meets Debian Free Software Guidelines, or on the Fedora Software License List.
  • Open core projects are a bit of an edge case because we also need to worry about the business side of them (since we're fiscally sponsored under a non-profit).
• While squad members can transfer their projects here, their requests must be reviewed due to the high risk of accepting them, especially on CI secrets.
• Hosted on their namespace. If your open-source project is managed via a separate GitHub/GitLab/sourcehut namespace, please invite our administrative account first, and continue to step 2 for non-squad members.

We recommend not forking a new repo back into the old namespaces to ensure that URL redirects will work magically.

1. File an access request so that we can provision access to the intermediary organization.
2. Move your project to this repository once we provisioned access. Then file a RFC for change of maintainership in order for us to have a look onto it.
3. Once we confirmed that we have the enough resources/bandwidth to maintain it, we transfer repo ownership to its new home and close the RFC issue for you. There'll be few more paperwork you need to fill up for legal reasons, but we don't require a copyright license assignment to be signed just to transfer the repo to us (following the sprit of the Linux DCO).

You can transfer directly to either recaptime-dev or one of our other orgs if you prefer (currently, both public and private repos are allowed to be transferred, so be careful of transferring your private repos):

If you got the You don’t have the permission to create public repositories on recaptime-dev error similar to the screenshot below, please check instructions for non-squad members. Either another squad member with admin privileges (or authorized to use our administrative account) should invite you to the organization where you desire to transfer the repo.

We're sad to let you go, but we understand your decision as a maintainer to part ways. To make this transition smooth, make sure to reach out to your contact (or one of our Squad Leads or IT admins) for help with infra cleanup and off-boarding.