Investigate source code repository providers and package registries for potential tooling sources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 87
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current data sources and the APIs.guru OpenAPI3 source, then investigate repository providers and package registries such as GitLab, Bitbucket, and npm. Document available sources, normalization against existing data, metrics, and ways providers could publish tools; completion is a consolidated Google Doc or similar that can be split into follow-up issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100