Summary
The is_foundation boolean field on PCC v2 project records returns false for every project checked, including projects that are clearly foundations: The Linux Foundation, CNCF, ASWF, FINOS.
Observed behaviour
{ "name": "The Linux Foundation", "is_foundation": false }
{ "name": "Cloud Native Computing Foundation (CNCF)", "is_foundation": false }
{ "name": "Academy Software Foundation (ASWF)", "is_foundation": false }
{ "name": "FINOS", "is_foundation": false }
PCC clearly distinguishes foundations from sub-projects in its UI and data model, but the field doesn't reflect this.
Impact
Any caller using is_foundation to filter or categorise projects will silently treat all projects as non-foundations. The field is currently unusable.
Location
PCC v2 · get_project · search_projects — is_foundation field
Severity
P3 — field is present but always wrong; workarounds exist (checking legal_entity_type, parent_uid, etc.)
Suggested fix
Populate is_foundation correctly in the v2 API response. If the determination logic needs updating to match the current data model, document the intended semantics of the field.
Reported by Stephan Ebers — found while building NPS survey automation against the LFX APIs.
Summary
The
is_foundationboolean field on PCC v2 project records returnsfalsefor every project checked, including projects that are clearly foundations: The Linux Foundation, CNCF, ASWF, FINOS.Observed behaviour
{ "name": "The Linux Foundation", "is_foundation": false } { "name": "Cloud Native Computing Foundation (CNCF)", "is_foundation": false } { "name": "Academy Software Foundation (ASWF)", "is_foundation": false } { "name": "FINOS", "is_foundation": false }PCC clearly distinguishes foundations from sub-projects in its UI and data model, but the field doesn't reflect this.
Impact
Any caller using
is_foundationto filter or categorise projects will silently treat all projects as non-foundations. The field is currently unusable.Location
PCC v2 ·
get_project·search_projects—is_foundationfieldSeverity
P3 — field is present but always wrong; workarounds exist (checking
legal_entity_type,parent_uid, etc.)Suggested fix
Populate
is_foundationcorrectly in the v2 API response. If the determination logic needs updating to match the current data model, document the intended semantics of the field.Reported by Stephan Ebers — found while building NPS survey automation against the LFX APIs.