[Project]: Classifications

### Project Name (1 - 3 words)

Classifications

### Description

This still needs quite a bit of work to better define the scope of this project before starting.

Questions:
* How can we automate the work to draw boundaries around classifications (what is a project?)
* How do we classify things using data, rather than using intuition?

Examples:
* what repositories should we include in a project? (can we know this without asking a maintainer?)
* what stage is the project in? (growth, stability, decline)

Notes: A range is better than nothing. May only be solved by large scale modeling.

### Related Links

Some interesting work on classification that the folks at Microsoft and the Centers for Medicare and Medicade Services are working on is related to this question and probably serves as a good starting point for this project. https://sched.co/1aBPX

Note that we also have a [Project Scope Template doc](https://docs.google.com/document/d/13iLNDfqJ8nuwBGEyJuFutcT7KRNT6JwFrSlJN_5f4o4/edit) that you can use to think about the project details if you find it useful (not required).

### How would you like to be involved in this project?

I am interested in this project, but do not plan to work on it myself

### Additional Notes.

_No response_

Start by reviewing the linked classification work and the Project Scope Template, then use the issue's questions to define what a project and its lifecycle classifications should include. Done means the project has an agreed scope and a documented, data-based classification approach rather than open-ended research questions.

Written by the indexing model from the issue text.