This response to this is exactly the sort of to and fro that doesn't help budding developers from caring about the project.
I'd also like to get my hands on new maemo code, especially if I'm going to be using features that are upcoming -- Apple /does/ provide seed releases to developers. I'm honestly just 'developing' by writing some python glue, but its likely I'll do more in the future. Making this 'harder' and less accessible through hiding stuff from developers until its released is not helping. Getting cranky about it through blogs and/or mailing lists isn't going to help either, too.
And re: ubuntu (and by some extension debian) working with developers on issues critical to follow-on development (in my case systems integration at the time) was not met with a 'one way' channel. I had /no/ problems working with developers of both projects (I am a Debian Developer) and fix problems right on the spot so things were working for release. Harnessing developers is hard. Harnessing outside developers is harder.
[I may have the following wrong, but it is my perspective]
My experience with Maemo is that much of the development is nokia driven. New code (ie: diablo) doesn't quite make it into any sort of firmware loadable onto any maemo-supported devices because nokia developed firmware includes non-free stuff. There is no really installable image aside from what nokia builds as far as I can tell, so the way maemo.org is setup it blurs the distinction between maemo and nokia. Sure, I installled the SDK on a machine, but it definately wasn't anywhere near the 'same' as my tablet. It was a very basic framework for developing apps on that can happen to run on the tablets. Palm at least had full-test-environments to run apps under that didn't feel so utilitarian.
The Debian/Ubuntu/Canonical situation is more clear. Debian packages 'stuff'. Ubuntu takes 'stuff' and denotes some of it as part of their 'main' distribution for support by the Ubuntu core team. Canonical makes money by taking Ubuntu work (and funding it) and adding support contracts and OEM customization for pay. Canonical supports Ubuntu by deploying a novel project management system, launchpad. I don't see these easy-to-delineate boundaries with Maemo/Nokia.
Maemo is the platform that Nokia uses to build up a set of software for use on the tablets, but much of the software is kept close to keep a competitive advantage. Developers are inconvenienced because of this management decision to hold back significant parts of the 'secret sauce' until firmware image release. Ubuntu/Canonical does not do such a thing. Sure, you can't go to LKML and ask when Ubutnu is getting Bug XYZ fixed -- but I can just plug a comment into launchpad or contact a developer on IRC and see if its on their radar. Likely I will even be able to start a dialog with developer on the issue, something substantive that helps Ubuntu harness my thoughts on the issue rather than telling us to go away.
