Hi,<br><br><div class="gmail_quote">On Mon, Mar 8, 2010 at 9:21 PM, Graham Cobb <span dir="ltr"><<a href="mailto:g%2B770@cobb.uk.net">g+770@cobb.uk.net</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 15:29:51 Valerio Valerio wrote:<br>
> since some developers aren't taking seriously the QA rules and there's a<br>
> lot of room for different interpretations in some cases, like the validity<br>
> of the bugtracker fields, the Testing Squad decided to write some<br>
> additional rules to clarify dubious situations:<br>
> <a href="http://wiki.maemo.org/Bugtracker" target="_blank">http://wiki.maemo.org/Bugtracker</a><br>
<br>
</div>I disagree with this rule:<br>
<br>
These bugtrackers link are considered NOT valid:<br>
<br>
* General links that do not lead to a dedicated page (e.g.<br>
<a href="http://talk.maemo.org" target="_blank">http://talk.maemo.org</a> or <a href="https://bugs.maemo.org" target="_blank">https://bugs.maemo.org</a>)<br>
<br>
There should not be restrictions on the type or location of a bugtracker to<br>
use. Any URL at which you can provide the bug report information should be<br>
acceptable. For example, in the GPE apps I point to the upstream bugtracker.<br>
There is no need to point to a page because this is all about GPE. The user<br>
will probably want to search, they may know which GPE component they should<br>
report it against (e.g. one of the applets or libraries, not necessarily the<br>
component they actually installed) and, if not, they can choose the product<br>
itself when they enter the bug report and I will reassign it as necessary.<br>
<br>
Other upstreams may have completely different bugtrackers which work<br>
differently.<br>
<br>
I really don't even see any problem with just pointing to t.m.o or b.m.o.<br></blockquote><div><br>What about <a href="http://www.google.com">www.google.com</a> ? seems the same for me :).<br><br>That could work if that project has a product at bugzilla or a specific thread at TMO(generaly they don't have), but don't you think it will be hard to find ?<br>
That will only leads to general confusion among the newcomers and a lot of bugs filled in the wrong products at bugzilla.<br><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> <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>
By all means give advice that it MAY be helpful to provide a bugtracker link<br>
with a product name, and is particularly recommended when using b.m.o. And/or<br>
particularly for applications with large numbers of users. But it is not a<br>
showstopper. Leave it up to the developer.<br>
<br>
It is marginal as to whether a bugtracker should be required at all. I think<br>
it should, because it is easy and extremely helpful to the user, but only if<br>
it is left up to the developer what form it takes. If a developer wants to<br>
use something different from normal then that is fine. All we should require<br>
is that they have had to explicitly do something.<br>
<font color="#888888"><br>
Graham<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
maemo-community mailing list<br>
<a href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-community" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-community</a><br>
</div></div></blockquote></div><br><br clear="all"><br>