Yes, and I've seen this. I even commented in your post about it that I like the idea.

Here's my problem: Looking at that there is nothing I can just grab and "do". It's all theory, great theory mind you - but with nothing tangible to actually work on right now.

RPM packaging? Qt? Usability? ... On what? An integrated reporting system - GREAT - integrated into what?

I mean.. currently we have a shells only barebones image released for MeeGo .. but not much else to "integrate" anything into.. there's just nothing there.

So yes - as soon as there is something I can actually grab and do .. I'll be more than happy to help any aspect of MeeGo that I can.. (skills are an expert in system administration/security, some QT development experience (by no means an expert, but I learn quick), and some RPM package management (again, I learn quickly)).

Making pretty pictures, and activating or engaging a community are not in my lists of stuff I do. I watch you do that.. and then I giggle because people suck .

(I think you do an amazing job at community projects Tex.)

My problem is: What I need is someone to point at me and go "You, Install MeeGo on (qemu, n900, whatever) - load software X, and see if you can fix bug Y".. And I'd be off.

Crawling through bugs.meego.org picking things out that I might be able to fix only to then realize it got fixed by an "internal" dev.. meh. I'll wait till there's a more stable base to work from. (Yes, I know, browsing bugs.meego is a perfectly legitimate way to help meego, I'm just somewhat on the lazy side right now and don't know the whose who of every corner of MeeGo).

Anyway: I do love your ideas in that Article Tex, but unfortunately I just don't see anything I can help with yet until things are a little more tangible.