GitLab support

[CLOVIS-AI]

Is your feature request related to a problem? Please describe.
My libraries are hosted on GitLab.com. They are published to Maven Central like any other library, and their scm URL is set to their GitLab page like you request.

Describe the solution you'd like
Include libraries that are hosted on GitLab instead of GitHub (provided they follow all other requirements for this project).

Additional context
Example project: https://central.sonatype.com/artifact/dev.opensavvy.pedestal/backbone

[IgnatBeresnev]

Thank you for submitting the very first issue :)

I plan to add support for GitLab, but at a noticeably later stage. At the moment, GitLab accounts for less than 3% of all scm urls, with 95% being links to GitHub, so I want to focus on it first: build features, fix bugs and iterate quickly without having to support two different APIs at the same time (GitHub alone is bad enough as it is). Once the website has the majority of the features I have in mind (so closer to the stable release), I'll add support for GitLab. Thankfully, it's very similar to GitHub, and the backend's architecture allows it (there's an abstraction on top of repositories)

[CLOVIS-AI]

Would it be acceptable to relatively soon add GitLab-based projects in the list, even if most of the data isn't filled in? Just so they appear in search results. All the other data can be missing with a ‘GitLab projects are not fully supported yet, see #1’ message. For example, you could fill the data you have from the Central metadata, and leave everything else empty.

It's unlikely you'll ever be able to support all VCSs, so this ‘degraded mode’ will always remain useful in the future.

I do still hope GitLab will be supported fully later, but I much prefer being on the list to the opposite, even if there are less available features.