You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrate FOSS projects under nexB organization on GitHub to aboutcode-org on GitHub.
How This Feature will help you/others
Transferring ownership of AboutCode projects on GitHub from nexB to aboutcode-org will demonstrate to the community our FOSS for FOSS commitment with the projects in a FOSS organization on GitHub instead of commercial entity.
This will facilitate displaying individual projects on the new aboutcode.org site. We will also revisit the plan to better index the docs for AboutCode projects: #129
GitHub should create automatic redirects following their docs: All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL.
There could be some issues with integrations and their tokens, including:
PyPI deployment
Azure DevOps
GitHub Actions
Read the Docs
Slack
Others?
There could be some issues with migrating permissions and collaborators in the new organization.
@chinyeungli Per Philippe, please plan to migrate the Fork repos to aboutcode-org. Philippe said that we need them in general to be co-located with the other projects and some of them have nexB updates.
Short Description
Migrate FOSS projects under nexB organization on GitHub to aboutcode-org on GitHub.
How This Feature will help you/others
Transferring ownership of AboutCode projects on GitHub from nexB to aboutcode-org will demonstrate to the community our FOSS for FOSS commitment with the projects in a FOSS organization on GitHub instead of commercial entity.
This will facilitate displaying individual projects on the new aboutcode.org site. We will also revisit the plan to better index the docs for AboutCode projects: #129
Possible Solution/Implementation Details
GitHub published docs on how to transfer ownership between organizations: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
GitHub should create automatic redirects following their docs:
All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL.
There could be some issues with integrations and their tokens, including:
There could be some issues with migrating permissions and collaborators in the new organization.
Example/Links if Any
More documentation on transferring a repo owned by your org: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-organization
Can you help with this Feature
I can help with some testing but this would require someone with advanced git (and git troubleshooting) skills.
Actual repos to migrate
This list is sorted so we start with a few smaller, less critical repos to validate the move process:
The text was updated successfully, but these errors were encountered: