Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57496
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F1F3ACB.9070909@oracle.com>
References: <55.40.47393.BBA3F1F4@pb1.pair.com>
	<4F1F3ACB.9070909@oracle.com>
Date: Tue, 24 Jan 2012 23:16:47 +0000
Message-ID: <CAKxcST_=9F09+MPrNb6gijQ-0ke3PXbSRgVPjoTwqSc9H2iAGg@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Change bug tracker "bogus" to "not-bug"?
From: dragoonis@gmail.com (Paul Dragoonis)

On Tue, Jan 24, 2012 at 11:12 PM, Christopher Jones
<christopher.jones@oracle.com> wrote:
>
>
> On 01/24/2012 03:11 PM, Justin Martin wrote:
>>
>> Hello,
>>
>> With some frequency, I find bugs which are not "bogus", so much as they
>> are reported based on a misunderstanding. Usually this happens for
>> documentation problems, where someone has misunderstood what the
>> documentation says, or hasn't read the documentation
>> thoroughly enough.
>>
>> I'd like to propose simply changing the term "bogus" to "not-bug". This
>> would more politely and clearly indicate the nature of the way the bug i=
s
>> being closed, in addition to the comment that one ordinarily leaves.
>>
>> Those I've spoken to in php.doc agree. Any objections?
>>
>> Thank you,
>> Justin Martin
>>
>
> I'm +1 on this. =A0It's time for a new, more collaborative approach.

Sure, I'll +1 on this. The "bogus" implies "RTFM, bitch", which isn't
professional at all :-)

>
> Chris
>
> --
> Email: christopher.jones@oracle.com
> Tel: =A0+1 650 506 8630
> Blog: =A0http://blogs.oracle.com/opal/
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>