[maemo-developers] Extras-testing improvements

[From: Eero Tamminen]

Hi,

Voipio Riku (Nokia-D/Helsinki) wrote:
> I do not represent the general view of my employer or anyone else, just 
> myself. But poor quality applications reflect badly on maemo.org 
> community as well. Do you want to be part of a community which is known 
> for its low quality standards? Notice that the current extras-testing QA 
> requirements are quite low:
> 
> 1. [ ] Bug database exist.
> 
> Annoying, but not hard to add (particularly if you choose a tmo thread 
> instead of bugzilla).
> 
> 2. [ ] Licensing ok.
> 3. [ ] No illegal/dubious content.
> 
> Yep, no piracy is acceptable.
> 
> 4. [ ] Working provided features.
> 
> Yep. crashing apps are bad.
> 
> 5. [ ] No missing announced features.
> 
> If something doesn't work (yet), don't advertize it. Don't dissapoint users.
> 
> 6. [ ] Optification ok.
> 
> Should we start accepting packages that break SSUs ?
> 
> 7. [ ] No performance problems.
> 8. [ ] No power management issues.
> 
> This could be clarified to belong only to always-running apps

If application does things on the background without user requesting
it (like e.g. Maep), that's bad for the performance of the application
on top (the one user is trying to interact with) and for the device
battery life.


App should do only things as response to what user requested.

In the Maep case, it should do things on the background only if it's
requested to track a route, and even then, skip its window updates
to minimize its CPU usage.

Tester can see CPU usage from SSH console with "top"
and screen updates with:
	xresponse -w 0 -a '*'


If there were some easy way for the user to see that bg app is slowing
down things & eating battery, I think letting them to do that would
be more acceptable.  Then it's user's choice to use the badly behaving
(but potentially otherwise very useful) application.  She knows to
close the application when not needing it or low on battery.


 > (such as hildon-desktop plugins).

But for applets in home or statusbar, using CPU when home isn't
visible or leaking memory etc is inexcusable.


> 9. [ ] No known security risks.
> 
> This is a bit sketchy, but certainly allowing things like "default 
> password ssh server" would be very very bad for endusers.

Here's the quality awareness pages for Diablo and earlier:
https://garage.maemo.org/plugins/wiki/index.php?id=253&type=g
http://maemo.org/maemo_release_documentation/maemo4.1.x/node16.html

Didn't find it for Fremantle though.


	- Eero