Re: GitHub RFC workflow
| From: | Mike Schinkel | Date: | Wed, 06 Nov 2019 03:00:06 +0000 |
| Subject: | Re: GitHub RFC workflow | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-107768@lists.php.net to get a copy of this message | ||
>
> https://www.vice.com/en_us/article/9kevn7/spain-and-github-are-blocking-an-app-that-helped-protesters-organize
>
> https://github.com/github/gov-takedowns/blob/master/Spain/2019/2019-10-26-GuardiaCivil.md
It would seem to me that if any country decided that downloading and working with PHP were against
the law, it would not matter where we hosted it, GitHub or php.net <http://php.net/>.
If for some reason a country got mad and decided to block GitHub, we could easily set up a mirror at
BitBucket or some other repository and thus allow people from that country to contribute to PHP/
In addition if it became a problem for someone to access discussions, we collectively could use the
GItHub API to write a mirror of discussions so people could read and contribute to support those
people in the "banned country" just as easily as building all infrastructure from scratch
that nobody have thus far found time to get around to build proactively.
So given all those concerns are currently hypothetical — since PHP is not an app for organizing
protests nor is it an advocacy group for a maligned minority — maybe we should just keep our eye
on potential problems so that if potential problems arise we can implement a workaround, but until
then we just use was works best today?
#JMTCW
-Mike