There are many people at Nokia and in the community interested in the status of cool projects aiming to be ready for prime time the day Maemo 5 goes to the hands of real users. These cool projects include the Fremantle Stars but also any other open source project with committed developers behind.

Please have a look at http://wiki.maemo.org/Fremantle_Star...her_great_apps and fill the information relevant to your project. Suggest or just apply any improvements in that table in order to help everybody know how are you going and what do you need.

If you play this little game you might get more contributors willing to help in the success of you project, including Nokia and its marketing arm.

Hate to thread-jack, but it's related somewhat... What about projects that are quite Fremantle-oriented (both software-wise and hardware class) but have a terribly low profile ? For example I can't say (with a clear conscience) my app rocks in it's current state or that it has a million supporters as it's not really N810 friendly (i.e. needs GL to be snappy, has a large Qt dependency...).

I added my application to the list; yes, I'm vain

I'm not sure I understand that page correctly. Should we add our apps to the list of "Proposals for Fremantle Stars" or should we add them to the table at the top? If it's the table what does "bugs.m.o" and "downloads" stand for? Is bugs.m.o different from bugs in garage?
Also, does the "testing" repository already exists?

bugs.m.o = bugs.maemo.org = your bug tracker. Unless I got it very wrong

Yes it is, bugs.m.o is the official bugzilla platform for the maemo project and some other remarkable projects (e.g. Canola), is administrated by the maemo bugmaster(Andre).
The tracker in garage is a different system (part of the gforge project), and is administrated by the project owners.

Thanks! So is it somehow a new requirement to have the tracker on bugs.m.o? What would be the advantage? My bugs are currently on garage.

attila77, in case of doubt just list your project in the table, make all the steps to have it ready for end users (package in extras, Downloads page) and let others decide on how much they want to contribute and promote.

Projects willing to get special attention from the community and Nokia are invited to keep their status in the TABLE. If developers use this table and keep up to date, it may become a very useful reference for the Maemo 5 pre/post launch marketing activities.

"Downloads" means you have a proper page at http://maemo.org/downloads

maemo-testing doesn't exist yet, as far as I know. We start needing it, yes. This goes connected to the fact that we need the agreement and the tools to decide when a package can move from devel to testing. The discussion was started in the maemo-developers list but I'm not sure about the current status. Hopefully a task commited for the next sprint.

It's a recommendation to track your bugs in bugs.maemo.org. The Bugsquad team can provide more details on the reasons. I haven't found actually any place explaining to developers why, so perhaps all we have until now are mail/forum discussions.

Well, a few reasons. First, any project of a certain size needs bug tracking. It helps you, and it helps your users. Second, if you've already got a tracker (Garage, elsewhere) you should consider moving Bugzilla since it's centralized (most users reporting bugs go to b.m.o to do so) and a vastly better tracking platform than GForge. Third, b.m.o comes with its own support staff of administrators and triagers who will be able to pick up some of your bug maintenance workload.

Is there any place where we should request a new product in b.m.o for our apps or we should contact Andre directly ?