Thanks Bernd, you make some very good points, including this one:

· Interoperability of CF deployments on an API level is an
important property, at the level of what’s exposed to a developer using CF;
I’m not sure that interoperability on the “platform operations” level has
the same priority at this point in time with many of the underlying
infrastructure pieces moving quite rapidly

In Chip's first response to Dr Nic he said, 'the certification process for
offerings isn't about experimentation in the ecosystem. It's about
consistency across the distributions.'. This struck me as interesting
because I always thought there was a strong, implicit connection between
certification and the ecosystem. CF certification is a powerful concept
that benefits both user and vendors. If you turn up the dial on
certification requirements you improve consistency, but the inevitable
trade off is a reduced space for competition and ecosystem growth.

Your point here about timing is, I think, particularly astute. The
Foundation finds itself faced with a similar decision to that of a central
bank trying to decide when to raise interest rates. The CF user experience
is sacrosanct, but the timing of whether to introduce mandatory BOSH for
deployment is crucial given the existence of non BOSH-based vendors, the
size of the CF ecosystem, overall industry context and pace of change at
the infrastructure layer.


Regards,
Dan Young - CEO
EngineerBetter Ltd <http://www.engineerbetter.com/> - The UK Cloud Foundry
Specialists
@dan0young <http://www.twitter.com/dan0young>
+44 (0)7783 397092 <+447783397092>