Believe it or not, I do understand all of these perspectives...
We are faced with an exceedingly difficult task, to take a massive software stack, and not only be able to understand it, but also to be able to maintain it, and be able to effectively add features, fix bugs, and bring the project forward overall.
There are over FOUR MILLION LINES of our own code.. OUR OWN... not counting the 12 other projects we appropriate (MythTV, Asterisk, VDR, Xine, etc.)
We have to shoulder all that burden...
So yes, when someone asks what we need? we need people who will roll up their sleeves and code.
We need people who will get things done if they want them done, It's not at all about thinking that "coding is this magically easy thing to do." IT'S WHAT _HAS_TO BE DONE! PERIOD. End of story. In the end, code is what solves the problems. No, don't get caught up in the chicken-egg argument of attracting attention, it is a red herring here. In the end, that is wishful thinking and ultimately doesn't solve anything, you work with what you have, because in the end, it is what you have. Just know that what you have can change, and you adapt accordingly.
P.R. is a funny thing, it's predicated on selling the strengths of a system while downplaying its weaknesses. This is a good thing to do when the product is ready to sell, or can be put in a position to sell effectively, LinuxMCE is not in this position for several reasons:
* We have licensing issues due to essential core parts of the code being licensed under a license that prohibits commercial distribution with hardware as a complete system. These pieces need to be re-engineered to be GPL compliant, to lift this restriction, while allowing community development to proceed organically.
* We have UI issues to solve, ranging from capabilities (people want zoomy zoomy flashy flashy crispy fast fast zoomzoom), to targets (making sure the UI is present on-screen, and off-screen on popular devices. Orbiter wasn't up to the task. Touch Orbiter was a short term solution proposed by Dianemo to get Orbiter onto more targets. qOrbiter (as it is called now) is the future, as it will solve both of the above issues by providing a cross platform UI with tons of capability in QML, atop the Qt toolkit which is very cross platform.
* We have architectural issues to solve, as the technology in the devices we appropriate gets better, we need to become more dynamic in our handling of these devices, some come, some go, but we need to be able to adapt better than we do.
* We have to improve our install and systems integration. This is an uphill battle that causes cancer, drives men to drinking, and has been known to end loving relationships. It's easy to make things just work, when you're Apple, and you make the hardware, and the software, and people buy your product and afterwards be told, "You do it our way, or not at all." We don't have that luxury.
I can keep going, but I'll stop there...
So please, it's not elitism that I have been perceived to espouse, it's the simple fact that I am frustrated at the sheer tidal wave of entitlement and expectation that has been thrown at me and the rest of the team since we took over in 2008. It's really very simple, if you want it done, you do the coding.