public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: [email protected]
To: [email protected]
Subject: Re: [HACKERS] Collaboration Tool Proposal
Date: Thu, 26 Feb 2004 18:57:05 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>



Peter Eisentraut wrote:

>Josh Berkus wrote:
>  
>
>>The question is, do we need BZ right off or should we try GForge's
>>lightweight tool first?    Personally I find that BZ is a little
>>intimidating to new users, particularly for searching on issues; as a
>>result it tends to lead to a lot of duplicate filings.
>>    
>>
>
>I think we had previously decided that we will not allow a random user 
>off the street to file bug reports into whatever system we end up 
>using.  I see it primarily as a bug *tracking* system, not a bug 
>*reporting* system.
>
>  
>

I don't recall that there was a consensus about that. The difference 
between BZ's "unconfirmed" and "new" states is that the latter means it 
has been triaged. See http://bugzilla.mozilla.org/bug_status.html .

I certainly don't think we should impose such a restrictive rule on 
every project that we might host on a GForge installation.

cheers

andrew

view thread (62+ messages)  latest in thread

reply

Reply instructions:

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

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: [HACKERS] Collaboration Tool Proposal
  In-Reply-To: <[email protected]>

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

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox