DefCore: What OpenStack Devs Need to Know

As DefCore has become more established over the past year or so, I’ve started getting more questions from project developers and PTL’s. In most cases, they’re interested to know whether things they’re thinking about doing in their projects are “ok from a DefCore perspective” or would be “ok from an interoperability perspective”. In some cases they’re basically just giving a quick (and appreciated!) heads-up and sometimes they’re generating terrific discussions. So before we go on, let’s take a quick timeout to give a some kudos to developers and PTL’s that are now more than ever thinking about interoperability early on when making technical decisions–that is fantastic.

DefCore Misconceptions Part 2: Debunking Advisory Status

DefCore isn’t a new creature in the OpenStack community: it’s been in discussion since at least 2013. However it was only earlier in 2015 that adherence to DefCore Guidelines became a requirement for products that want to use the OpenStack name and OpenStack Powered logo. As a result, a lot more people are now interested in DefCore than in the past. As we’ve started receiving a lot more feedback about DefCore, it’s become apparent that there are a few misconceptions out there from folks who are new to DefCore.

DefCore Misconceptions Part 1: Leading vs Trailing Indicators

DefCore isn’t a new creature in the OpenStack community: it’s been in discussion since at least 2013. However it was only earlier in 2015 that adherence to DefCore Guidelines became a requirement for products that want to use the OpenStack name and OpenStack Powered logo. As a result, a lot more people are now interested in DefCore than in the past. As we’ve started receiving a lot more feedback about DefCore, it’s become apparent that there are a few misconceptions out there from folks who are new to DefCore.