Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106896 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53289 invoked from network); 6 Sep 2019 15:09:22 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 6 Sep 2019 15:09:22 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id B953E2D2033 for ; Fri, 6 Sep 2019 05:43:45 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 ; Fri, 6 Sep 2019 05:43:45 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id m11so12436694ioo.0 for ; Fri, 06 Sep 2019 05:43:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=tfxH3p2NUgh+d9Umk8N/TN72aBioZV1NDaHrrfgFwAk=; b=DNz0Wb5D91nP732iZxb/eKxbbPPKCPz4e7jtRKqBIFbY0cjiNfVpUOKBU7ti6+mc3j avKmKQafPXipom7xjVZ8FQ8VQM7AtGgI1WZhXRe9Og7edy9QCMx2R9pbVU1TAaq7YPVe WkPZfbovVj3/+W1sDtaGyXywGgX20bR4VxC3/H8fqwvNl4G9vMPprw5/Hsyzlo0RWSuX 2ffULrWv4qPURhePJgBCDYPFJFFkGJyBHJiiU5ydQfA/xVnelDubow5+FlRHubcNcNNx oTGrPpNtrDX3J3jMfMenNvQbl4uz3O9HDnCGwtgOsIt5law8TWKTE4tkAOJCkFX5acJI +bkQ== 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; bh=tfxH3p2NUgh+d9Umk8N/TN72aBioZV1NDaHrrfgFwAk=; b=KUbKF3aSz5x/P/J32PBrYVktMPha1Dn2AvJRL1QaFOKbvQ+UjPhID9T++Vvy1/zqAp 0D2hz3ti0gSCfQsAxZbQt1WQ2oh/NrK4ZnIWneKwydzZqIr/jsiEAn6q5jJMnQ8sixK3 6lDj0PdbSX6chP/hJIJNEKLFfV9DCU6B1zHDoHZd4r+9NQqgmZXSK5Wg+iXzAfFVPS+6 +hQMBcHKHmMoDqyh/2Em++H1e7uHxbV7xfpDWW/AHHZfXZKOtIkHqwPdD81L65YYaTvK QpBkmrX02X/+UbJXdUfbnzJynAXTfmkDBBjh5b3aLutiMhhrot4kA262gbMC6C+Kj0ai 0TFA== X-Gm-Message-State: APjAAAXnzc3L61gD8RokzQqjvrKl+tLl7NkaqW2n3Fl/9hzlSA8/NJWZ 1bo8557kzLUQrdsf9mINHQtkVxspLbYNMU0CB8X5WA== X-Google-Smtp-Source: APXvYqx6phtjQYShxfJhSFj/9evUjcwCEwH5gTAFT2EKSYJ8BvIN+v7JE+lj/Ohn+wgZDLMixjYoxHRTTO4Q8bJ8ReQ= X-Received: by 2002:a5e:c301:: with SMTP id a1mr10349618iok.1.1567773824045; Fri, 06 Sep 2019 05:43:44 -0700 (PDT) MIME-Version: 1.0 References: <1686643.PblvKQRnJp@mcmic-probook> <190b7291-812e-4337-bd09-950dc30c655a@Spark> <2157489.0uZv62oTo4@mcmic-probook> In-Reply-To: Date: Fri, 6 Sep 2019 13:43:32 +0100 Message-ID: To: Internals Content-Type: multipart/alternative; boundary="000000000000ded6200591e1c9f6" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Union Types v2 (followup on github usage) From: rowan.collins@gmail.com (Rowan Tommins) --000000000000ded6200591e1c9f6 Content-Type: text/plain; charset="UTF-8" On Fri, 6 Sep 2019 at 12:31, Peter Kokot wrote: > > Plastic analogy - adding "127.0.0.1 github.com" to your /etc/hosts > file shows that developer cannot bring most of the today's (PHP) > projects to any working state without using it. That's what is meant > by inevitable because everything open source today is either on GitHub > and some minor ones scattered around custom Git repos and other Git > hosting providers. > Ah, I see. Yes, having some usage of GitHub is currently pretty much inevitable in that sense. Of course, that may change eventually, just as SourceForge fell out of favour, but that's not something we need to worry about. However, projects over a certain size generally *don't* use it as their main or only discussion platform, which is what we're talking about here. > PHP is already using GitHub. Is it moving to > something else? No, so let's not complicate things more with other > hosting providers now. > The question is not "should PHP ban the use of GitHub for any kind of activity?" it's "should PHP abandon the discussion processes it's been using for most of its history and use GitHub as a discussion forum?". As a code collaboration platform, GitHub is pretty good, but it's not built as a discussion forum, and there are plenty of limitations to using it as one. Regards, -- Rowan Tommins [IMSoP] --000000000000ded6200591e1c9f6--