Clarifying / Updating the Repology Automation Project

So I have started adding Repology IDs to linter bears (there are a lot of them, around 80-90)
So for the first evaluation, I am trying to make sure that all the Gem bears' packages are on repology.
I would be adding them to Wikidata which is the fastest way of getting data onto repology.
My main concern is with the application of the usage of the data, so after a bears package is available on the repology, we can fetch data using HTTP requests to Repology API. But exactly what information are we going to use and what decisions would we take based on this information is something I need help with.

Quoting @margobra8
> I think your API calls should be focused on cross-referencing the repositories which host the dependency packages so that they can be liked and referenced recursively. Maybe check the repository URI, the version number so as to decide, in that case, which package to install. You would also need to take into account what to do when a bear requires a specific version of a dependency, but Repology also lists all versions so there should be no problem. I think we should schedule a meeting with all mentors just to see how each one thinks about this and reach a consensus so that we can just steer in the right direction.

I am opening this issue to have a discussion with all the mentors, @jayvdb @margobra8 @underyx @fexpr