feat: Purge sources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 87
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
User Story
As the a maintainer of the tooling repository
I want to ensure the dataset is of suitable quality
And only contains the tools that are relevant
So I can provide reasonable data to the community
Detailed Requirement
Currently we catalog many repositories that contain boilerplate code and do not change again.
We need to have a shelf life for such projects and purge them from the dataset after a given period of time. Needs to be qualified by other metrics e.g. code complexity?
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
No files, tests, or entry points are named in the issue, so first locate the dataset and the process that publishes or refreshes it. Define the shelf-life and qualifying metrics for inactive boilerplate repositories, then verify that entries failing those criteria are removed from the dataset without purging relevant tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, openapi
- Domain
- data, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100