[maemo-developers] How to use extras-testing correctly?

[From: Aniello Del Sorbo]

2009/9/24  <tero.kojo at nokia.com>:
>> -----Original Message-----
>> From: maemo-developers-bounces at maemo.org
>> [mailto:maemo-developers-bounces at maemo.org] On Behalf Of ext
>> Aniello Del Sorbo
>> Sent: 24 September, 2009 12:20
>> To: Gil Quim (Nokia-D/Helsinki)
>> Cc: maemo-developers at maemo.org
>> Subject: Re: How to use extras-testing correctly?
>>
>> I personally think we're taking a wrong approach to the problem.
>>
>> I am not developing for  Apple because of their approval
>> process and their desire of control.
>
> That is a different matter alltogether. One device, one shop, complete control. That has very little to do with a community site like maemo.org and a deevice using debian repositories.
>

I am well aware of that :)
But if I go thru extras-testing (and I really want to!) then it looks
like the Community has the last word on my application.

>> I don't want my application to go through an approval process
>> to reach my users.
>
> No one is forcing you to place your app in extras. However it is the place most likely to be found by new users.
> Maemo Extras should be of high quality because we will have completely new users to the platform. We don't want to scare them away, simple as that.
>

And that's what I want. But I am the one that decides if my
application has to go from Extras Testing to Extras.
If I decide badly, the Users will uninstall my app and file bug via AM
and eventually it'll be pulled out from Extras.
Only high quality apps remain.

>> I think that the developer HAS the last work on whether or
>> not her application is ready to be promoted to Extras.
>
> The developer has the last word; just don't promote from testing.
>

But I do want to go through testing. That's why I am proposing this.

>> But I like the idea of my application being tested and I'd
>> love to get feedback from the final users.
>> Android has a nice approach, I think the application goes
>> straight to Market and when a user removes it, she's being asked why.
>
> I don't think so, please provide a reference.
>
I don't have any. I do know that if you uninstall an app, it asks you why.
I have an Android phone.
I know that.

>> I learned that the extremes are almost never the best choice.
>> Thus, I would like to see is a mix of Apple idea of "testers"
>> and Google Android "uninstallation survey".
>>
>> Here's my proposal:
>>
>> We leave Extras-Testing as it is, with votes, comments, bug
>> reports an so on (or improve it, as you wish).
>> But then it's only the developer that decides, based on that
>> feedback, if or not to promote the application to Extras.
>
> Which is how it works, except you need ten thumbs up.
>

Exactly what I am trying to remove.
I choose.
But based on those 9 thumbs up.
I need to be wise of course, but I choose.

>> When the application gets promoted to Extras, people will
>> start using it.
>
> Yes, extras-testing for testing, -devel for development, extras for prime time.
>

/me nods

>> If there's a major bug, the user will uninstall the application.
>
> Certainly.
>

/me nods

>> The Application Manager should ask the user, as Android
>> Market does, WHY she uninstalling the application.
>> Of course she may choose not to give any feedback.
>> One of the choice she has is "Uninstalling because of a bug"
>> and she can fill in the bug if she wish so.
>>
>> This bug goes straight to bugzilla for that application and
>> we should count them and decide on two limits: a soft
>> threshold and a hard one.
>>
>> Soft threshold:
>> if the application goes below this soft limit a yellow flag
>> is raised (how to handle it, it's another topic).
>>
>> Hard threshold:
>> if the application goes below this hard limit a red flag is
>> raised and application pulled from Extras.
>
> Look, if you want to remove stuff, it's better to do it early than late. The assumption is that someone will submit bad code, then the better option is to take it out before it hits peoples devices. Not after it's gotten to the public.
>

My point is exactly this. I think it's the opposite.
The decide what my application does, the users decide if it is good.
No one in between.
Extras Testing IS very good for.. testing.

>> This way the Developer has full control of when and how she
>> wants her application to reach the public.
>> The Community has some control of which applications should
>> be removed.
>
> Which is there already. When you get the ten votes on testing, you get notified and can choose to ignore it or promote when you feel like it.
>

If I don't get those, may be because few people care, I am stuck in Testing.
And this reminds me of Apple approval process.

I like the whole Extras Testing idea, but I have to choose if I want
to go to Extras nonetheless.
Of course I wan't promote my app if there are showstoppers, but it's up to me.

If I have to go straight to Extras, I will do that, but I'll miss the
opportunity that Extras Testing gives me.
And that's a shame.

Aniello