Ignore Approach and Implementation

User Story

As a user of tooling-related data I want to ignore anything that appears to be boilerplate code, unmaintained or archived.

As a maintainer of tooling-related data I want to reduce the amount of queries run against projects that appear to be boilerplate code, unmaintained or archived.

Detailed Requirement

Given the "coarse-grained" nature of the data collection approach there is a great deal of opportunity for "dross" to clutter up the tooling dataset. Some examples:

• Tools removed from sources.
• Dead repositories with no history or anything particularly interesting about them.
• Repositories with zero stars that have not changed in eons.
• Repositories that are tagged but not actually anything to do with OpenAPI.

We therefore need to decide on:

• The policy for ignoring this stuff.
• An implementation in the gulp build to sift it out.

Start with the issue's examples of boilerplate, unmaintained, archived, and unrelated repositories, then inspect the gulp build where filtering is requested. Define the policy for ignoring these entries and identify how the collection queries are assembled. Done means the policy is documented and the gulp process sifts out the agreed categories before unnecessary project queries run.