Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106924
MIME-Version: 1.0
References: <CAF+90c8EvfFPqjRJjJ3T-qTfLiWn7aZzCrGpk7R3yNFLT1qWjQ@mail.gmail.com>
 <3425415.rOq7SuEVWJ@mcmic-probook> <CA+kxMuRtmhd6ZJ+OtQ99B+-C+8zxe1uYgOZQczKWXT1ykEy1yg@mail.gmail.com>
 <2411051.U6HbW7jRvI@mcmic-probook>
In-Reply-To: <2411051.U6HbW7jRvI@mcmic-probook>
Date: Tue, 10 Sep 2019 10:02:41 +0100
Message-ID: <CALKiJKrOxjk4zqBmTmD3oTOTHYFDeF7gv5DSKgp-CuXTYArYTg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000063a6d205922f2ba6"
Subject: Re: [PHP-DEV] [RFC] Union Types v2 (followup on github usage)
From: rowan.collins@gmail.com (Rowan Tommins)

--00000000000063a6d205922f2ba6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 10 Sep 2019 at 08:37, C=C3=B4me Chilliet <come@opensides.be> wrote:

> > >  PHP have no control over github, and cannot know how it will evolve.
> > >
> > >  (they can change the platform tomorrow and internal won=E2=80=99t be=
 able to
> do anything about it).
> >
> > Those are hypothetically problems. But they do not appear to be
> > currently problems.
>
> The fact that PHP has no control over github is current, this is not
> hypothetical.
>


The idea that the platform will change overnight in a way that makes it
unusable by the project is hypothetical.




> It=E2=80=99s not the same when the project can act to fix it and when the=
 project
> is powerless.
> If github blocks someone from commenting we cannot do anything about it.
>


Are you aware of any heavy-handed moderation on github, or is this, again,
a hypothetical problem?

As you will see from my other responses on this thread, I'm not totally
sold on github in particular, but I can see pros and cons more generally:

- our own systems, fully in our control, but used by nobody else, and
managed by a handful of volunteers
- or: a well-established third-party system, which could change in
unpredictable ways, but is widely used, and supported by hundreds of paid
staff

Even the mailing list relies on third-party software; I presume it gets
updated regularly, and those updates could include changes in functionality
we disagree with. There is a pragmatic decision to be made between building
absolutely everything from scratch, and trusting some third parties, with
contingency plans if that trust proves ill-founded.

Regards,
--=20
Rowan Tommins
[IMSoP]

--00000000000063a6d205922f2ba6--