Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107751 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12816 invoked from network); 3 Nov 2019 02:41:39 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 3 Nov 2019 02:41:39 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 864E22CC48C for ; Sat, 2 Nov 2019 17:30:25 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Sat, 2 Nov 2019 17:30:24 -0700 (PDT) Received: by mail-wr1-x442.google.com with SMTP id s1so13220635wro.0 for ; Sat, 02 Nov 2019 17:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iFleB1ZMRIqmQ19fMLSuVedN40m8mVOfvYqREmA/BPU=; b=Pn04nd4bMo3Hd+D6+xRkjxtEkG2AgND62uOwvJQwwzdx2wGDBrl2s6SdvW+CRbDjTi XdAuKwjvN9ArQB7RYOhMG5sLqfzZ0Pc9jwoWiE+FE7MJvIVUswGGfiSJBygTsxZyiiJe 3tcdXV65Dm4+0t+BLnh2zNPJvLwkffkWMm8FsQlWV/x53m1q3S0YyXiDUlbjJnFYzbRk VG4xYsyCw+We6OiWJmrREjkg+XzyYK5S/cetV91XBEDd55Coi6nSuQCZ21YmycI5qzqu R8oApmPoaVCLrDGFlNIOGZGSYii3vLnmXs2DLUbg3RZ+hILjTg5A5CMN5jB1Y+NvzbNk jgag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iFleB1ZMRIqmQ19fMLSuVedN40m8mVOfvYqREmA/BPU=; b=gO2wiycP3z61BCq6Oy9UowdXGzxuZp5l/7sGZBm04hGfkzrY+CvdUhUq5AeMspsUf+ gS8XwEqMB+aNEUseCBcyjWlvU4dA3sUBYuJ0oTTSAPYS/ruIxVqlenIR2rhHoNk0ImO0 HSnrhKIXICuXpVcg/KwRanBuAHSvoomv4ihk2vyIIa1XH2tb+FTgshufvw1c4CUNIraU rrt/IKY6k7qwGkTaPtZOMewX16OjPo/DN6SjKSx/5Phs547H5AcKDcOUrwZtcuHRXkNP qVl3yhNisj42dFwNC2e8SAYxa/42w4t6GQX4jEu7JBM0LwMvku8J6YGGf1BylxfSwwtK Dakg== X-Gm-Message-State: APjAAAXtd178ksvv/W9HdG+tyfoadeoYyd1s3qiYT9q5LMe7tiwpl1xw 22eM/yMkUc5Zc7aAFzj2IBRoYBd43hf53EwZ3GrgHw== X-Google-Smtp-Source: APXvYqxveYax/nAZRcMf3AYqmQgtsmNdDHvyqXRO73ziiuAjmEly6Y6Kd41mGIrAYpLOD3ym3udDrC+8NWzQledDdpQ= X-Received: by 2002:adf:f4c9:: with SMTP id h9mr12546294wrp.354.1572741023170; Sat, 02 Nov 2019 17:30:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 3 Nov 2019 01:30:12 +0100 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: Joe Watkins , Nikita Popov , PHP internals Content-Type: multipart/alternative; boundary="000000000000029ca60596664ea4" X-Envelope-From: Subject: Re: [PHP-DEV] GitHub RFC workflow From: kontakt@beberlei.de (Benjamin Eberlei) --000000000000029ca60596664ea4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 2, 2019 at 9:03 PM Johannes Schl=C3=BCter wrote: > On Sat, 2019-11-02 at 19:40 +0100, Joe Watkins wrote: > > I would like to question the reasoning behind wanting to "own" the > > RFC content: We don't require any such thing for any other kind of PR > > although we say we require a patch on bugsnet, we actually don't > > require it. So, I have a hard time telling the difference between a > > PR for an RFC and a PR for a bugfix or enhancement. > > > > Can anyone tell the difference ? > > In a bug fix or enhancement the relevant information is in the patch, > which in the end lives in php-src.git. If a patch isn't self- > explanatory it probably needs an RFC as reasoning. That reasoning shall > live in a central place to be found by future generations. > Outside pull requests don't live in php-src.git, because they are provided by different remotes and these are not as far as I see mirrored back in any way to php.net git. So the question Joe poses is right, pull request descriptions and all their comments are currently only available on Github. I also question the "we must own everything" rule, as its highly unlikely Github will not suddenly remove all php-src data and they provide an API to backup or migrate data if we ever want to do something else. > And some historic context (do with it what you want :-) ) on why > php.net instead of GitHub: When we moved to git I (among others) pushed > for using our own infrastructure we control, and not binding the > process to an external entity. PHP has seen other platforms like > sourforge come and go and migrated from CVS, to svn, to git so other > platforms coming and going and versioning systems come and go is > likely. While GitHub under current Microsoft probably is more likely to > stay than the young startup from years back. :-) > (that aside from GH requiring accounts on that platform, eventually > blocking countries etc.) > > johannes > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --000000000000029ca60596664ea4--