It's ironic. Just recently we had a(nother) thread on community software QA that stirred up a lot of emotion here. Now here's something proposed that certainly began with good intentions but does indeed have the potential to create or exacerbate fragmentation.

Here's what I would have rather seen with the time, energy and resources devoted to this: a solution to the software QA problem. Some sort of synergy with maemo rather than overlap and possible competition.

It concerns me when a developer says he's too lazy to create a maemo project, because I have to wonder what else they're being lazy with-- QA, documentation, libraries, etc. If it becomes easier to "manage" a project using this new solution then the result will not only be fragmentation, but further erosion of quality. Rather than enable laziness, we should encourage at least some degree of discipline. I realize that last word seems to fly in the face of FOSS, but without discipline Linux would remain a cool hobbyist plaything, nothing more.

I really, really, REALLY wish the community developers would team more. The resources are there. The need is certainly there. I'm not sure what's kept it from happening like I've seen it happen in similar circumstances. What's lacking? An Internet Tablet Developer School?

Anyway, just my meager 2 cents on the subject. I won't argue much on this one because I know Reggie's heart is in the right place and the last thing I would want to do is rain on his parade.