Skip to content
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

Investigate source code repository providers and package registries for potential tooling sources #4

Open
SensibleWood opened this issue Feb 11, 2022 · 0 comments
Labels
data Issue relates to the tooling data collected from data sources investigation required Go do some work to assess what to do next

Comments

@SensibleWood
Copy link
Collaborator

User Story

As a user of tooling data I want to gather tooling data from all significant source code repository providers

Detailed Requirement

The current data sources tend to focus - not necessarily intentionally - on GitHub. It would be great to expand the search to take in - for example - Gitlab, Bitbucket, npm, etc to gather new tools, data sources, and additional metrics (note the APIs.guru openapi3 source already tapped into some sources).

Research and analysis therefore needs to be undertaken to work out:

  • What sources are readily available.
  • How to normalise them across what we already have.
  • What opportunities there are to tempt tooling providers to publish their tools (through tagging etc.) so we can consume.

This should all be collated in a Google Doc (or similar) so the work can then be broken down into issues.

@SensibleWood SensibleWood added the investigation required Go do some work to assess what to do next label Feb 11, 2022
@SensibleWood SensibleWood added the data Issue relates to the tooling data collected from data sources label Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Issue relates to the tooling data collected from data sources investigation required Go do some work to assess what to do next
Projects
None yet
Development

No branches or pull requests

1 participant