@Monolith
Those expectations are quite lofty at this stage...to thoroughly understand why you need to have some background of the projects history. You can start by looking at pluto home's ailing website.
Read through the PPL on their website and consider that we are still focusing on freeing ourselves from that license. As a businessman I'm sure you can see how, as long as we're operating under that license, we're basically limping around on one leg, no chance to run until we're free of those shackles. Then go look at our codebase and see just how large and complex it is, you can imagine that with only a handful of us here working to accomplish these things, it takes a considerable amount of time.
Now consider that none of us are paid to do development on this system, I think I can speak for all the developers here when I say we do it because we enjoy it and understand the potential of the system. We all have lives we live outside of this particular hobby, and most of us are also working 40+ hours a week, have families, etc. We're only humans, we can only put in so much time programming, studying, researching, and designing.
That said, I would love to see your expectations of the system met, those are the goals we're all working towards, but your post does not come across as constructive, more like telling us to get our shit together and get busy so that you can profit off of it. I'm going to suggest a few alternative approaches that would be more well received by the community here.
1) Contribute to the codebase and help us help you reach your goals, the few of us here that are actively working on the system are willing to help, you can find that time and time again on the forum, in the IRC channel(s), in TRAC, and on the wiki.
2) Make a donation to a developer who has already made significant contributions toward your goals, a nice gesture to say thanks for the work you've put in so far.
3) Test the system, if you have problems, open a TRAC ticket, yes there are some that have sat stagnant for quite some time, but we do look at them, and we are actively resolving those issues.
4) Help us get better documentation in the wiki. If you solve a problem, search the wiki and add to our existing documentation. If you find something incorrect in the wiki, correct the information.
5) Jump on the #linuxMCE channel on freenode IRC and help users solve problems they may be having and encourage them to provide feedback.
@Everyone who helps us
There's several ways you can help the project achieve those goals without relying solely on us. I want to take a time out and thank everyone in this community who is actively helping, helping doesn't have to be in the form of programming, the short list above are also ways that people help us every day.
With that all out of the way, the software is not perfect, far from it in fact, I think we've all been frustrated with it at one time or another. We find mistakes, we make mistakes, but mistakes are okay because mistakes provide feedback and feedback is how we learn. Without making mistakes along the way, we'll never reach the goal and vision we all have of what this system can be.
@Anyone who wants to see an improvement
I hope this helps explain the reality of the project, and encourages at least one person to grab a shovel and start digging.
-Adam
