Re: [RFC] Union Types v2 (followup on github usage)
| From: | Côme Chilliet | Date: | Thu, 05 Sep 2019 11:27:10 +0000 |
| Subject: | Re: [RFC] Union Types v2 (followup on github usage) | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106874@lists.php.net to get a copy of this message | ||
Le jeudi 5 septembre 2019, 12:50:48 CEST Joe Watkins a écrit :
> > Because the PHP project should avoid depending on a privately owned centralized service
> > for its technical discussions
>
> This is obviously your opinion, but you haven't actually told us why this
> is the case, and it's not at all obvious.
I thought it was obvious, sorry.
So, the problem is PHP have no control over github, and cannot know how it will evolve.
GAFAM organizations have closed people accounts before, sometimes without giving reasons.
I think PHP project should not let other organisations choose who can or cannot participate in PHP
development.
> > should not encourage (some would say force) people to use such platforms.
>
> In any case it's not a choice for the contributor, internals chooses the
> medium and the contributor has to use it. Whether we force them to use a
> mailing list from last century or something from this century makes no
> difference with regard to choice for the contributor.
With a mailing list the contributor can choose its email server and email client. He does not have
to agree to term of service of a third party.
https://tosdr.org/#github
With github, internal chooses to delegate to github, and github (currently microsoft) chooses who
can take part in the discussion and how the discussion works. (they can change the platform tomorrow
and internal won’t be able to do anything about it).
Côme