Part 2 of the preliminary work required for #27. There's quite a bit of changes (especially with the new entity files) so I wanted to split this PR off on its own before I create the UI for cncf projects.
Approach
Not all landscape items are created equally. There are properties that are common among cncf projects that aren't common for cncf members but they're all treated as landscape items. So I created a new type to differentiate the common properties of different categories.
With the new type for cncf projects, we can include certain properties for the catalog-info of cncf projects without doing any of this business
I've learned that an entity's specific information should be under spec and not metadata so the stuff I put under annotations is now all under spec (plus other new data)
Created a group entity for cncf (since all cncf projects are owned by cncf (if you clicked on one of the projects, it'll complain that group:default/cncf doesn't exist))
Also created a group for contributors. Group doesn't have any members yet but I set it as the owner of landscape3. Eventually we'll create an entity provider for ingesting contributors of landscape3 as users.
TODOs
[x] Let's merge #31 first and I'll rebase and re-generate the new entities
Motivation
Part 2 of the preliminary work required for #27. There's quite a bit of changes (especially with the new entity files) so I wanted to split this PR off on its own before I create the UI for cncf projects.
Approach
specand notmetadataso the stuff I put under annotations is now all under spec (plus other new data)TODOs