Map repos to projects, communities, and foundations

Individual repos are often part of larger projects, which is not always obvious (nor necessarily automatable). But having some rough mapping of repo1, repo2 -> are part of an obvious software project could be useful, even if incomplete.

Similarly, how projects/repos change over time is related to the project's status: is it a couple of JS developers hacking? Is a project part of a consistent and governed community or GH Organization? Is a project part of a FOSS Foundation with documented governance, IP policies, and the like?

Adding metadata structures that can be used to create these mappings is the first step. Some projects are then easily associated, with GH Organizations, or with a handful of FOSS Foundation URLs that are self-declared to house projects at their organization.

I'd love to provide organizational input to this kind of mapping from the Foundations metadata directory. For example, what field(s) should be listed under a FOSS Foundation Schema entry in the directory, to provide attestations of affiliations with repos, projects, or root paths?

Additionally, is there enough research interest - and implementation interest - to map both repo <-> project relationships, and also map repo|project <-> foundation relationships? For example the ASF as a foundation might have data like this, that explicitly attests these other items are governed at the ASF:

```.yaml
ghorgs:
- https://github.com/apache/

repoRoots:
- https://github.com/apache/
- https://svn.apache.org/repos/asf/

projects:
- https://whimsy.apache.org/public/committee-info.json # ['committees']

# Individual projects may also have repo attestations that could be scraped
```

For reference:
https://github.com/Punderthings/fossfoundation/blob/main/_data/foundations-schema.json