For posterity: nobody has questioned that Reggie's proposal was pointing in the right direction, nor that ITt is a better place for end users than the developer oriented maemo.org. The question was how to avoid developers doing manual publishing twice and the risk of splitting the information in different places + the risk of having an easy upload feature in ITt deviating from the developer effort of having an integrated and quality aware process in maemo.org.

Syndication solves the first part and now we will work on the implementation.

About the 'easy uploads', it is understandable that in a first glance easy=better - however it is not always like this. The easiest is to give candy to children every time they ask for it and use them as a short term incentive to get other things done - but this will ruin their teeth and their motivation to understand why some things need to be done. Easy uploads out of the sight of the maemo community of developers favour at the end all kinds of system weaknesses and mid term bad user experiences. Main reasons provided in my previous posts here and some proofs in user complaints here and there having the root of the problem in app/applet X with a fancy frontend and an involuntarily harmful backend.

All we have learned something with this discussion.

The best way for everybody to propose improvements to maemo.org is http://bugs.maemo.org - product Website. Downloads has its own component and you can make your suggestions there. The right developer will pick it up and you will know in real time what is the progress, being able to discuss further details, vote and bug more.

There are currently eight open bugs of a total of 75 bugs submitted to the Downloads component.

Bugs and tasks like now the syndication thing are pushed through monthly sprints where Niels, Dave, Andre, Karsten, the Nemein and Nokia guys meet and decide what comes next. All this process is open and can be followed and actively influenced and supported via the maemo.org development wiki and mailing list.

I reckon all this is not well documented and publicitized (this is actually one of the tasks in the May sprint). At least now you see that there is no reason to think in Nokia alone planning and developing maemo.org features behind four walls. In fact today the maemo community has as much initiative and power to organize and implement things in the maemo.org website - but the majority of hasn't still realized that.

You can help, pointing to others in the right directions everythime you see complaint X about maemo.org and getting involved yourselves. The maemo.org Downloads discussion here is just one example on how you can help improving things.