feat: Source repositories from alternative git forges

[reobin]

Motivation: vimcolorschemes/vimcolorschemes#376

Possible sources:

• gitlab
• Sourcehut
• Codeberg
• Bitbucket

[letorbi]

Hi @reobin, I am the maintainer of the Modern Borland colour scheme and am currently migrating from GitHub to Codeberg for the reasons mentioned above. However, the fact that vimcolorschemes.com is not supporting any other platforms than GitHub is holding me back. Therefore I'd like to help to get support for other platforms working.

The other issue is marked as "research needed". Could you outline, what information is actually required and what roadmap for the implementation you would prefer?

[reobin]

Hi @letorbi ! Thanks for reaching out.

The good thing is that removing your repository from Github won't remove it from https://vimcolorschemes.com, but it will stop getting updates. That is, unless you mirror the repository updates from it's main source to Github. If that's ok with you, then there's no need to hold back moving away from Github.

About what's needed for me to work on sourcing multiple forges, at this point, it's more about implementation details (which sources, API docs, etc.), and less about investigating. Still, there's work to do, and I wouldn't expect this change to be done very very shortly.

[letorbi]

Thanks for your feedback. Mirroring the repo is actually an acceptable interim solution for me, but I'd like to move completely from GitHub in the long run.

Even though I cannot implement support for all possible forges, I could start on a PR that enables Codeberg as a second source besides GitHub. Would you merge such a PR, if it meets your coding standards?

[reobin]

@letorbi Contributions are very welcome. I wouldn't say the codebase is 100% prepared for it. It was very much built with Github in mind, but that can be refactored to have a generic service that each commands uses, or whatever else helps. Don't hesitate if you have more questions. 🙏