Perhaps you can add in something about backups? There seems to be quite a few apps which are not adding themselves to the backup system.

Good point, need to search for appropriated docs.

As a recommendation yes, as a rule no, since we need several months of discussion before that

I've split this discussion off from the bugtracker link thread, as these posts weren't on-topic in there but raise a point worthy of further discussion.

Definitely a recommendation, yes - I'm not sure that backups are appropriate for all applications anyway. I think that the backup configuration has just been fallen off the radar for most developers, so a reminder (and pointer to any documentation) would definitely help.

If no objections are raised against this proposal, I'd like to see it become a SHOULD reasonably quickly. It shouldn't block promotion, but it should be an encouraged practice for applications where it makes sense.

Then, if registering for backup is thought critical enough to be a MUST, I think the date for that should be announced well--as in "months"--in advance to give developers time to plan for it. Also, exceptions to the rule should be allowed, of course. Items like the 2G/3G/Both applet shouldn't have their states backed up and restored, and I'm sure there are plenty of other, similar examples.

EDIT: Rob1n beat me to it.

http://wiki.maemo.org/Documentation/...up_Application if I understood you correctly. Programs using GConf get this functionality thrown in for free.

Note that this documentation is incomplete / out of date for Fremantle. See bug 6250 for details (and 6178 for background).

Glad I haven't used it then; the standard set of files in /etc/osso-backup/applications constitutes as "documentation" for me.