DevOps has (arguably) a lot of guff, fluff and puff attached to it right now.
We're still not sure if this portmanteau-propelled "coming together" of two core technology disciplines is really one new perfectly formed beast.
Is it Ops that have gotten good at Dev... and so progressed onwards (Ed - that never happens surely?) or Devs that can handle a bit of Ops?
Is it really one person?
Or is DevOps actually a movement, a cultural approach and a method?
So DevOps is actually 2, 4, 8, 16, 32 or 64 people and so on.
While we're ranting... shouldn't we also argue that DevOps has true open source roots?
The argument goes as follows....
DevOps (developer-operations) was born out of the FOSS (Free and Open Source Software) by its very nature because it aims to address the "incongruous nature of integrating traditional LOB applications" with other applications.
This is the view of Paul Greer, chief architect and co-founder at RedPixie -- a British technology firm, which specialises in transforming IT environments.
"DevOps has a lot to do with automating and repeating, a practice that grew significantly with the widespread adoption of free tooling and frameworks that were built by the open source community," said Greer.
"This became popular in the early 2000s with the automation of software builds but now encompasses platform provisioning as well as software deployment," he added.
Greer goes on to argue proprietary tooling may provide some benefits in organisations that have standardised on a single vendor stack, but even these tools would be short lived if they prevented DevOps from controlling other vendors stacks.
"Line of Business application vendors products are changing through open interfaces and cloud based hosting which negate the customer from having to concern themselves with platform provisioning," he concludes.
DevOps is open source, or the pure bits are at least -- the debate continues.