"community" in a sense means way more then the proverbial "idiots not on your payroll". In my experience, many companies are in search of a community, but are also under the assumption that they can just create one similar to how they can create a new department within their organisation. Instead, "community" can be regarded to as a bottom-up type of thing, that companies can merely facilitate and create incentive for (rather then exercise their control over what they have and attempt to create something they might not be able to control at all).
So, in response to the point you made, "community developed" could be considered in no way resembling the value of those proverbial "idiots not on your payroll", which, arguably, is the very core competency creating the majority of momentum for "Open Source" as well as "community developed", that will probably never be on anyone's payroll.
My intention is not to argue about "free" or "open" in any sense of either word, different people have beat that drum before.
My intention is more along the lines of making sure that the values, principles and inherent benefits of "free" make it to the list of KSPs of "open". It's the type of KSP that the rather marketable "open" rarely addresses, in my opinion, but rests on heavily, regardless of whether you call it free software or free culture.
"community" in a sense means way more then the proverbial "idiots not on your payroll". In my experience, many companies are in search of a community, but are also under the assumption that they can just create one similar to how they can create a new department within their organisation. Instead, "community" can be regarded to as a bottom-up type of thing, that companies can merely facilitate and create incentive for (rather then exercise their control over what they have and attempt to create something they might not be able to control at all).
So, in response to the point you made, "community developed" could be considered in no way resembling the value of those proverbial "idiots not on your payroll", which, arguably, is the very core competency creating the majority of momentum for "Open Source" as well as "community developed", that will probably never be on anyone's payroll.