[maemo-developers] No subject

From:
Date: Fri Feb 19 10:21:36 EET 2010
ll, there are probably lots of more people who add extras-testing and even =
extras-devel to their devices and test random applications from there, but =
can&#39;t bother to vote the <a href=3D"http://maemo.org" target=3D"_blank"=
>maemo.org</a> website. I can see several reasons for this.<br>

<br>
1) extras-testing voting is well hidden in maze of the website<br>
2) Once you find the place, you get an ugly list (especially if viewed with=
 n900):<br>
<a href=3D"http://maemo.org/packages/repository/qa/fremantle_extras-testing=
/" target=3D"_blank">http://maemo.org/packages/repository/qa/fremantle_extr=
as-testing/</a><br>
There is no correlation with packages you have actually installed on your n=
900, so you need to browse around to actually find what to vote for.<br>
3) the website kicks you out randomly<br>
<br>
etc. no wonder we don&#39;t get many testers..<br>
<br>
If we want to insist on quality on 3rd party applications, we should start =
by having good UX design and QA on the <a href=3D"http://maemo.org" target=
=3D"_blank">maemo.org</a> website too...<br>
<br>
But I think perhaps the website is the wrong place anyway. a &quot;extras-t=
esting-assistant&quot; application in extras that allows you to add/remove<=
br>
extras-testing to application manager, shows a list of packages installed f=
rom extras-testing and gives you a chance to thumb up/down.<br></blockquote=
><div><br>I&#39;m completly agree. As far as I see many users testing an ap=
plication (see the response/thanks on t.m.o) but a very small group of this=
 votes up/down.<br>
I think having an application to help people who testing rating/comment/wha=
tever on a packaged would be more efficient and making the test process goe=
s up quickly, instead of require to go to the website, looking for the pack=
age and so on.<br>
=A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid =
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Oh, And I also suggest cutting down the requirement for _upgrades_. For upg=
rade, the test checklist should be:<br>
<br>
[ ] No regressions observed (everything that worked on previous version sti=
ll works)<br>
[ ] New functionality/bugfixes work as advertised<br>
<br>
And cut down the delay to 5 days with 5 votes.<div><div></div><div class=3D=
"h5"><br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href=3D"mailto:maemo-developers at maemo.org" target=3D"_blank">maemo-devel=
opers at maemo.org</a><br>
<a href=3D"https://lists.maemo.org/mailman/listinfo/maemo-developers" targe=
t=3D"_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><=
br>
</div></div></blockquote></div><br>

--001636025ff0ba888104815beede--
More information about the maemo-developers mailing list