All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@suse.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Re: bug tracking?
Date: Tue, 20 May 2003 12:34:13 +0100	[thread overview]
Message-ID: <3ECA12B5.3050903@superbug.demon.co.uk> (raw)
In-Reply-To: <3EC98C71.4090904@boosthardware.com>

Patrick Shirkey wrote:
> Takashi Iwai wrote:
> 
>>
>> i'm familiar with bugzilla (not as an adamin but as a user :) and am
>> satisfied almost with it.  it's enough powerful.
>> but bugzilla has many configurations and we'll need to find out the
>> fitting one for our purpose.
> 
> 
> I'm looking at it now. The first thing that jumps out at me is that all 
> users have to login to make a submission online.
> 
> IMO that will make it less likely for people to submit reports. However 
> the rest of the system is very slick so I'm not sure what direction to 
> take. There doesn't seem to be a way to turn of the login as it seems to 
> be crucial to making sure the system works.
> 
I would tend to disagree with you here. I think that it is vital that 
the person submitting the bug does log in, and has a verified email address.
My reason for this is in the answer to the following question from the 
developer: -
1) I think I have fixed the bug, can you please try this patch and tell 
me if it works.

Now, if the person who reported the bug just logged the bug report 
anonymously, the developer might never know if they have fixed the 
problem or not, so the developer is probably unlikely to try to fix it 
in the first place.

Cheers
James



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  reply	other threads:[~2003-05-20 11:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  6:07 [Fwd: Re: [Jackit-devel] OSS Backend] Patrick Shirkey
2003-05-15  8:58 ` Takashi Iwai
2003-05-15  9:21   ` bug tracking? Jaroslav Kysela
2003-05-15  9:37     ` Takashi Iwai
2003-05-15 10:12       ` Patrick Shirkey
2003-05-15 12:53         ` Takashi Iwai
2003-05-20  2:01           ` Patrick Shirkey
2003-05-20 11:34             ` James Courtier-Dutton [this message]
2003-05-20 13:25               ` Patrick Shirkey
2003-05-20 14:11             ` Takashi Iwai
2003-05-20 14:51               ` Erik Inge Bolsø
2003-05-20 16:16                 ` Patrick Shirkey
2003-05-20 16:46                 ` Paul Davis
2003-05-20 16:02               ` Patrick Shirkey

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=3ECA12B5.3050903@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    --cc=pshirkey@boosthardware.com \
    --cc=tiwai@suse.de \
    /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.