[maemo-developers] [maemo-developers] Maemo alarms ==> retutime
From: Weinehall David (Nokia-M/Tampere) David.Weinehall at nokia.comDate: Mon Aug 7 10:17:51 EEST 2006
- Previous message: [maemo-developers] Maemo 2.0 and AMD64
- Next message: [maemo-developers] Maemo alarms ==> retutime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On mån, 2006-07-31 at 14:17 +0200, ext Nils Faerber wrote: [snip] > OK, where does that lead us now? > > Do I understand this right that you/Nokia have an implementation, right? > And this implementation is still locked in some desk because it is not > ready for production (yet), right? No, it's under active development here, and as soon as it works as expected well pass it through legal checks and unleash it onto the unsuspecting Maemo community. *Muahahaha!* (ehrm). > Well, then I would propose two steps: > > - First, document somewhere what *is* existing concerning alarm with > the current IT2006 edition, no matter how limited it is. This issue has > been a FAQ for almost a year now and it would help to avoid n-th times > asked questions. /mnt/initfs/usr/sbin/retutime --help The retutime tool has been mentioned several times on this list as far I can remember, and trying `--help' doesn't require that big of a leap of imagination, eh? > - Second put that "internal" implementation somewhere so that it can be > enhanced and productised by the community, like e.g. Garage. > If you do not do so I see the danger that the community might not be > willing to wait for a next IT2007 edition which might eventually have > the framework in place (or may not). But instead we might end up with > double effort, i.e. the community develops such a framework, uses it > until you/Nokia release your version and the community version will > become obsolete - very annoying. Well, it all boils down to manpower. It might seem that it's an easy enough thing to just release things into the public and let the community to the rest, but everything has to go through the Nokia legal machinery before this can happen, thus the work needed is pretty significant. At the moment we prefer using our time to make the new alarm framework as good as possible (which will be properly documented). Regards: David -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing?
- Previous message: [maemo-developers] Maemo 2.0 and AMD64
- Next message: [maemo-developers] Maemo alarms ==> retutime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]