Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116390 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26760 invoked from network); 15 Nov 2021 19:24:15 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Nov 2021 19:24:15 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E42AD1804C4 for ; Mon, 15 Nov 2021 12:19:01 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3301 81.224.0.0/12 X-Spam-Virus: No X-Envelope-From: Received: from ts201-smtpout73.ddc.teliasonera.net (ts201-smtpout73.ddc.teliasonera.net [81.236.60.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 15 Nov 2021 12:19:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telia.com; s=tssemail; t=1637007541; bh=mm/u8/b7PKkilDcwt7kaweLcKw7V1eCD7qSC9ewIMro=; h=Message-ID:Date:MIME-Version:Subject:To:References:From:In-Reply-To; b=SMCQ8HhFIIUg6R8a34Vs9B7ytJcX2G9M62SlWIV13t8fASV2B28da1/AIZ9qkFUlWtz4tAAsjA3JbceAdSjBeTCzEYbvxu9zuJsFDM4ABgbOnBPXOOE2bi4jlO+XeMzWsEHa7k0fElkAooCxLwTPE9hZxwdAgsDoUdrsNFktHULMi5UQ6xUqyz7lHs28SDN7wYv7m5hJsfWrF4Lzqq/5g0k3IwhLOcjr4lPQAmxRyr1df+o4xeG+hakXABki8Z/ZaBt1i1QeOYjeyTSy+LyPpnSt3Hnr9Wl29dUqgVDkjUehC7VMZCpNF42H3irKvWlmRKQtkCIy3lEg27Pn7eGBng== X-RG-Rigid: 6184E14900921054 X-Originating-IP: [213.64.245.126] X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvuddrfedtgddutdekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvffgnffktefuhgdpggftfghnshhusghstghrihgsvgdpqfgfvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomhepuehjnphrnhgpnfgrrhhsshhonhcuoegsjhhorhhnrdigrdhlrghrshhsohhnsehtvghlihgrrdgtohhmqeenucggtffrrghtthgvrhhnpeegudefveeguddviefgffehjeejteevheefgfefteeuuddtlefhgefgteeujeeivdenucffohhmrghinhepphhhphdrnhgvthdpvgigthgvrhhnrghlshdrihhonecukfhppedvudefrdeigedrvdeghedruddvieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedrjedruddungdpihhnvghtpedvudefrdeigedrvdeghedruddviedpmhgrihhlfhhrohhmpehukeelledtieegudejsehpnhgvrdhtvghlihgrrdgtohhmpdhrtghpthhtohepihhnthgvrhhnrghlsheslhhishhtshdrphhhphdrnhgvthdprhgtphhtthhopehnihhkihhtrgdrphhpvhesghhmrghilhdrtghomh X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.7.11] (213.64.245.126) by ts201-smtpout73.ddc.teliasonera.net (5.8.716) (authenticated as u89906417) id 6184E14900921054; Mon, 15 Nov 2021 21:18:58 +0100 Message-ID: Date: Mon, 15 Nov 2021 21:18:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Content-Language: en-GB To: Nikita Popov , PHP internals References: Reply-To: =?UTF-8?Q?Bj=c3=b6rn_Larsson?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [RFC] Migrating to GitHub issues From: internals@lists.php.net ("Björn Larsson via internals") Den 2021-11-02 kl. 15:19, skrev Nikita Popov: > Hi internals, > > The migration from bugs.php.net to GitHub issues has already been discussed > in https://externals.io/message/114300 and has already happened for > documentation issues. > > I'd like to formally propose to use GitHub for PHP implementation issues as > well: https://wiki.php.net/rfc/github_issues > > Regards, > Nikita > Hi, The current proposal is to move all new issues from bugs.php.net to Github except security ones. I think it's important to think a bit on what that means for reporting security issues in the future. I mean, if we leave bugs.php.net to rot in the corner, what are the consequences for reporting security issues? I think that aspect needs to be a bit further analysed like: - Will this move have a negative impact on reporting security issues on bugs.php.net? # Both from a technical and people perspective. - Can one assume that by bugs.php.net having probably even less attention, that reporting security issues will work as is? - Is there an alternative for also handling security issues? Think it would be good if the RFC could analyse that a little, besides saying business as usual for security issues. Regards //Björn L