<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 07/28/2010 05:29 PM, Adam Williamson wrote:
<blockquote cite="mid:1280338152.2038.21.camel@adam.local.net"
type="cite">
<pre wrap="">In general I think we could just say that the best approach is to write
strictly factually about how to report bugs upstream, as opposed to
trying to codify the reasons why someone might choose to do so.
</pre>
</blockquote>
Actually instruction how to file bugs upstream should be under
components page or components group page on the wiki. <br>
<br>
So for an example if working with Gnome upstream bugzilla the
instruction to do so should be on a page under
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
fedoraproject.org/wiki/Desktop.<br>
<br>
Those instructions need to be on a step by step bases usage along
with explanation of the different bug workflow upstream has in their
bugzilla vs ours and also explanation on what's the difference
between upstream bugzillas vs bugzilla.redhat.com to avoid confusing
reporters using our bugzilla and theirs, that is if upstream is
using mozilla bugzilla to track their bug reports ( which is far
from being the generic case ). To give you an example bugs status on
bugs filed against components in Red Hat and bug status on bugs
filed against component in Fedora do not have the same meaning
behind them and are treated differently even thou they are using the
same bugzilla instance together. <br>
<br>
JBG<br>
</body>
</html>