Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57494 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50527 invoked from network); 24 Jan 2012 23:11:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2012 23:11:57 -0000 X-Host-Fingerprint: 70.66.157.226 S010600e04c5031f8.pk.shawcable.net Received: from [70.66.157.226] ([70.66.157.226:13006] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 55/40-47393-BBA3F1F4 for ; Tue, 24 Jan 2012 18:11:55 -0500 Message-ID: <55.40.47393.BBA3F1F4@pb1.pair.com> To: internals@lists.php.net Date: Tue, 24 Jan 2012 15:11:52 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 70.66.157.226 Subject: Change bug tracker "bogus" to "not-bug"? From: frozenfire@php.net (Justin Martin) 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 is 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