WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] make mkpatches broken

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] make mkpatches broken
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Tue, 19 Apr 2005 17:14:23 -0700
Cc: Paul Larson <plars@xxxxxxxxxxxxxxxxxxxx>, kmacy@xxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 20 Apr 2005 00:13:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3C4C@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3C4C@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707
Ian Pratt wrote:

Several of the the team are of the strong view that requiring users to
create an account and login to submit a bug means that many bugs don't
get submitted out of laziness.

That does happen, and it would be nice to make it as
easy as possible.

I guess the simplest hack would just be to change the bugzilla login
dialogue such that it tells people to login with an acount called 'bug'
password 'bug' if they don't want to create a real account.

Right. Note that the bugzilla account also requires an email.
Further communication with the submitter then occurs through
this email (more info, status, etc). This avoids the need for
the submitter to include contact information in the bug report.

You would need to set up a dummy email or redirect the anonymous
bug reports to a mailing list. You might have to deal with hit
and runs (i.e. submissions, with submitters never checking the
report/list again). This was a significant disadvantage to
anonymous submissions.

Perhaps you manage by incorporating both in the bug handling
business:
        - a bugzilla with accounts for those who are
          motivated, and will follow up with testing of
          patches etc..
        - a mailing list to report bugs on for those
          who don't want to take the trouble to login
          (a mailing list that allowed non-submitter posts).
          You then have the option of having someone
           enter that report in the bug database if desired..
          This could be xen-devel, for that matter.


thanks,
Nivedita



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel