DefCore doesn't threaten anyone, it merely adds compliance tests and a future date when they're expected to pass to be able to qualify to continue using the related trademarks. It's also open to discussion/participation from all parts of the community including deployers/operators/providers to provide feedback on whether compliance with new requirements is reasonable or even feasible. It's the OpenStack community's answer to ensuring increasing levels of interoperability between independent deployments over time, and as an interoperability bug this is a good fit for such process.
DefCore doesn't threaten anyone, it merely adds compliance tests and a future date when they're expected to pass to be able to qualify to continue using the related trademarks. It's also open to discussion/ participation from all parts of the community including deployers/ operators/ providers to provide feedback on whether compliance with new requirements is reasonable or even feasible. It's the OpenStack community's answer to ensuring increasing levels of interoperability between independent deployments over time, and as an interoperability bug this is a good fit for such process.