Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114311 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 55713 invoked from network); 9 May 2021 13:23:54 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 9 May 2021 13:23:54 -0000 To: internals@lists.php.net References: <3faab631-f7ec-8fd8-1a62-26b3b241f676@gmail.com> Date: Sun, 9 May 2021 14:31:09 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: <3faab631-f7ec-8fd8-1a62-26b3b241f676@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: Bugsnet From: marandall@php.net (Mark Randall) Message-ID: On 09/05/2021 09:05, Stanislav Malyshev wrote: > I don't see how we could "just move" if all our bug handling would be > wired into Github. I can easily see how we could move a repo to any > provider that supports git - git is a generic platform, Github is just a > frontend. But there's no alternative frontend for Github Issues that we > could just copy the data into - you move, you lose your existing system. > There are probably import tools on some platforms, but the processes, > assignments, etc. - all will have to be re-developed, even if we could > re-use the raw data. If Github does something so outrageous that a move is required, it is unlikely to just be PHP that is affected. Such an eventuality would be all but certain to result in a huge cross-community effort to develop automated migration tools. Tools such as github already have integrations that allow migrating Github data into their own formats. I personally am not at all worried about having bugs on github.