Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97643 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20788 invoked from network); 9 Jan 2017 22:19:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jan 2017 22:19:10 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.170 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.170 mail-pf0-f170.google.com Received: from [209.85.192.170] ([209.85.192.170:34204] helo=mail-pf0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/23-31343-C5C04785 for ; Mon, 09 Jan 2017 17:19:10 -0500 Received: by mail-pf0-f170.google.com with SMTP id 127so34568951pfg.1 for ; Mon, 09 Jan 2017 14:19:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=haJ8rBPm8facQFG0wcaBjUcYeqp2eLzNyMAG5k0fVMw=; b=rbbnzP9JarSM4EGufb1u3Qt2rsMlRXnOxkkUdpkbpkOR7BaYnSzgaD666R2k2O3wQW cUFPbPJYv7eF/quUI+Zh5d6WzqFKuhUf//Dq/ox6WFkodEUuezZkDZCZIUERNZ8DKXhi jq4H8xFGG0e0RFvDXklyIqrT7kEfBolFplFuKWh2icVh3+PwUwWKnAG0CwilmTlRrq6V kwHkeelvhneVSOpYEHHYSiQu9XitrGs4V8FaYKgtP8clFAqwU90RGpz3qSLk2JtEVYxF 9k+eo+AjNjgBIowNMY42wcPhhBG1pXh3/Yn+CvHf9Y7JrL9n+8PqKIo3sINrxQvrQzN1 CJdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=haJ8rBPm8facQFG0wcaBjUcYeqp2eLzNyMAG5k0fVMw=; b=JMnD1EOlxSHE/r9npaQttWQjFpWy5uO3J90EBBwt1q34SzLKiZwjhHhF+FRpY4K9eo 3KdW5yEvlVmdt3Rg5YE5dj0V2aAHCZ/7+aa59AshgGENLDq3QURvOeNT8UCApwkAKcle sV1dBPsO342JEBWxkQaTx2vA4fo66e/mN6XTvmee8srS3AiSyHRuxxUSuqD7D+NIwJPJ 6xoAUS1FlN/wDkmM0pt4UloeeBN+EKyqekQF4ZXDMgPUhDcMSEJ+UXGRk+xHonMb0I+A BYV3Aiv4HRmJh4DebGesa7dNIfOJkG0X23TWfe1BO6milWMF47tnRSDIUoj7wnM4NaWI +ROQ== X-Gm-Message-State: AIkVDXJuFq2yYJmGRTJv96YU+5ojTZUf+B/NzWldNQgF0CRiWqET0tMfezzK5W0PrTrKVw== X-Received: by 10.84.160.197 with SMTP id v5mr6964467plg.65.1484000346149; Mon, 09 Jan 2017 14:19:06 -0800 (PST) Received: from Stas-Air-1415.local ([204.28.125.162]) by smtp.gmail.com with ESMTPSA id s5sm183408586pgj.19.2017.01.09.14.19.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Jan 2017 14:19:05 -0800 (PST) To: Joe Watkins References: <47370a17-d428-b30d-183b-c1ec96d47872@gmail.com> Cc: Andreas Heigl , Nikita Popov , PHP internals Message-ID: <8307a455-1f57-b289-74cb-71c3a0410c92@gmail.com> Date: Mon, 9 Jan 2017 14:19:04 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bugsnet cleanup From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > The problem with accepting feature requests on bugsnet is that, most of > the time, nobody can implement them because of modern processes. Why not? One can attach pull or write an RFC based on it. Having ticket in bugs.php.net does not prevent it, it just records the need for it. > It's not harmful to us, but it is harmful to the person requesting the > feature, who is probably ignorant of modern processes, and bound to stay > that way until we educate them, or disable feature requests on bugsnet > altogether. We can add comments to those FRs that require RFCs. > I think I would like to see feature requests disabled on bugsnet, > thereby pushing everyone to use the proper channels (github, internals, > RFC's). These channels are not exclusive. In fact, bugs site is the only permanent record for non-RFC requests, and for RFC ones, sometimes significant time passes between idea showing up and RFC being ready, and in that time, we won't have any record of anybody needing this. > What do you think ? I don't think disabling FRs is good. Screening them and noting that some of them will need RFCs to be implemented is good. -- Stas Malyshev smalyshev@gmail.com