New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking of projects that are migrating from GitHub (to GitLab, etc.) #41477
Comments
A tool like @r-ryantm is working on could be extended by crawling the web (or by using existing search engines) to find the most likely source for a given package instead of relying on human input to update URLs. That way it wouldn't matter where projects move to, as long as they can be found. |
I think crawling the web for information about packages is hard. It seems like every package does things slightly differently. nixpkgs-update uses Repology to get information about the URLs for sources and it can even change the URL for a |
As a note, we need to be careful with automatically - or even semi-automatically - detecting any kind of repository moves, as we might end up tracking a malicious fork. |
It does not mean bot would switch automatically. I talked about informing with "a message". So far as I look not so many big projects moving. They take timeout. So far from big known projects I found that "Ring project" moved to seft-hosted GitLab (link). But it is so far not in NixPkgs. You can look Twitter at GitLab tracking account @movingtogitlab; and #movingtogitlab but in there many jokes and memes. |
Well, for today this is not needed. |
Issue description
GitLab monitoring is here
This is a meta issue thread about projects migrating their upstream from GitHub to GitLab and other places.
How we can structure tracking of this changes?
It is better if someone with Maintainer authority can close this issue and reopen a thread like this, or maintainers form a unified strategy how we handle this and inform the community.
Folowing @volth in #41448 (comment):
volth:
For example, if GitHub URL becomes unresponsive, something accordingly watch does the same project exists on GitLab. Maybe after call
fetchFromGitHub
fails - launch does it on accordingfetchFromGitLab
(gitlab.com) URL, and output a message "Please look, maybe project migrated to GitLab " that can cover huge part of cases of migration.The text was updated successfully, but these errors were encountered: