The 2nd question ("What if development would be the core of a wider area around collaboration?") reflects a good thought and is almost reality but has a limited scope. What is the non-development part of the community? Feedback? Translation? Artwork? Users helping users? Maybe, but this is not an all to revolutionary concept for open platforms.

I'd be very, very reluctant to accept the 2nd proposal (opening maemo.org for closed-source projects). To be honest, mostly I'm rejecting it because it feels wrong, maybe even dangerous. Maybe it's because with closed source projects we have to assume they follow their own agenda. They keep things secret. They take from the community, but they don't give back. Even with the one project you refer to for "releasing soon, often, listening to feedback" - how would it help having such projects on an open developer platform? They get their feedback anyway and by their closed nature, they're not able to contribute anything to the community. (In fact, I still wonder why they're closed at all and simply don't trust the whole thing too much.)
To put it short, I'm afraid closed projects wouldn't be equal players on maemo.org. They might benefit while not giving back. I think it's much more important to have a place where developers of free code can bundle their forces, a place that enables them to do better and do more.