All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Paul Larson <plars@linuxtestproject.org>,
	kmacy@fsmware.com, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: make mkpatches broken
Date: Tue, 19 Apr 2005 17:14:23 -0700	[thread overview]
Message-ID: <42659EDF.2030502@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3C4C@liverpoolst.ad.cl.cam.ac.uk>

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

  parent reply	other threads:[~2005-04-20  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 23:56 make mkpatches broken Ian Pratt
2005-04-20  0:05 ` Jeremy Katz
2005-04-20  0:14 ` Nivedita Singhvi [this message]
2005-04-20  0:21   ` Nivedita Singhvi
  -- strict thread matches above, loose matches on Subject: below --
2005-04-19 22:25 Ian Pratt
2005-04-19 23:37 ` Nivedita Singhvi
2005-04-19 18:38 Paul Larson
2005-04-19 18:51 ` Kip Macy
2005-04-19 19:10   ` Paul Larson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42659EDF.2030502@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=kmacy@fsmware.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=plars@linuxtestproject.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.