Hi,<br><br><div class="gmail_quote">On Mon, Mar 8, 2010 at 7:30 PM, Attila Csipa <span dir="ltr"><<a href="mailto:maemo@csipa.in.rs">maemo@csipa.in.rs</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Monday 08 March 2010 18:43:02 Graham Cobb wrote:<br>
> It must be made clear to testers that giving a thumbs down (or up) MUST<br>
> always be on the basis of their own, direct observation. It would be<br>
> unacceptable for a tester to give a thumbs down "because Attila has already<br>
> given a thumbs down and added a comment" as it is possible that you had<br>
> made a mistake, or it is possible that the developer has added a comment<br>
> which explains why the thumbs down was incorrect in this case.<br>
><br>
> As long as each tester personally verifies that they can see that the<br>
> problem is there, and it is a showstopper, then it seems a reasonable<br>
> optimisation.<br>
<br>
</div>Again, keep in mind that the issue here was with the bugtracker non-<br>
compliance, and that *IS* something that can be instantly verified (and I<br>
certainly don't expect anybody to t-down without making sure that a listed<br>
error actually exists - not that I'm that big of a factor in the testing-squad<br>
to expect anything from anybody :). In fact, if you take a look at my votes<br>
you'll see that I did not t-down mikkov's Kobo package even though many others<br>
did exactly because it was unclear to me whether it was offending the<br>
bugtracker rule or not.<br>
<br>
To reiterate an important point with the bugtracker issue - IMHO it should be<br>
editable from the packages user-interface (just like screenshots), and the<br>
XSBC field just used as a last-resort manual override. Think about it this way<br>
- the only way to change a bugtracker link is to force thousands of people to<br>
download the SAME package again (even if we forego the whole -testing issue),<br>
just so that a different link would appear on the <a href="http://maemo.org" target="_blank">maemo.org</a> site ? MASSIVE<br>
overkill.<br>
<br>
And that's a two birds with one stone, right there - that would mean<br>
bugtrackers are no longer blockers, i.e. testers thumb down, the author fixes<br>
it in the package interface and the testers change it to thumbs up and it can<br>
be promoted, everybody happy, no quarantine or tester time wasted.<br></blockquote><div><br>I totally agree with that approach, something similar to what Mikkov suggested. <br>At least I don't see any use for the bugtracker outside the <a href="http://maemo.org">maemo.org</a> domain(package interface&downloads), or I'm missing something here ? is there real value to have it embedded in the package ? any future plans for that ?<br>
<br>Best regards,<br><br>-- <br>Valério Valério<br><br><a href="http://www.valeriovalerio.org">http://www.valeriovalerio.org</a><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Regards,<br>
<font color="#888888">Attila<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br><br clear="all"><br><br>