How to handle reusable component repos?

[mbland]

Before we'd talked about having the parent: field being the only thing in a child project's .about.yml file, but I can see the use in having projects like about_yml and team_api being children of other projects yet having their own team, stack, type, etc. And in particular, something like library, infrastructure or component might make sense as a new type value.

Thoughts?

cc: @arowla @monfresh @jmcarp @wslack

[mtorres253]

This is talking about shared software components. 1 How do we model the relationship to the original project (e.g. about_yml is a child of team_api) handled by #8 2 How do we label it so that users know whether it is reusable for example as a library, infrastructure, or a component.

This is informational right now, so that the project details and relationships can be displayed correctly to an end user

We can act on this story now, and we need to do more research on #8