Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113994
MIME-Version: 1.0
References: <bdaec552-8f1f-6392-2417-2ff9d2fbd5dd@gmail.com>
 <84b6179e-19ab-4325-4933-937205953433@php.net> <6884cd05-7d9e-b4fb-1b2c-02d27863bfb0@gmail.com>
In-Reply-To: <6884cd05-7d9e-b4fb-1b2c-02d27863bfb0@gmail.com>
Date: Thu, 8 Apr 2021 10:23:01 +0200
Message-ID: <CAOwTYAvgpOqmw2w2f-LjykzVDRs_1Hackj=FQMJfthD5xtG1Ow@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000015da6605bf71c21c"
Subject: Re: [PHP-DEV] wiki.php.net upgrade
From: krakjoe@gmail.com (Joe Watkins)

--00000000000015da6605bf71c21c
Content-Type: text/plain; charset="UTF-8"

Any use case we have for content or collaboration is best served by
whomever or whatever is going to secure that content or ability to
collaborate.

Nobody has updated the wiki in several years, despite warnings, and two
very public breaches of security that we know about.

We don't have the people to maintain our own infrastructure, let's stop
pretending we do.

Cheers
Joe

On Thu, 8 Apr 2021 at 08:15, Stanislav Malyshev <smalyshev@gmail.com> wrote:

> Hi!
>
> > If we want to keep using wiki.php.net then, sure, we should update it.
> > We could also migrate the wiki to GitHub.
> >
> > We also already have https://github.com/php/php-rfcs which we could use
> > for RFCs instead of a wiki going forward.
>
> Wiki isn't used only for RFCs, there's more content there than that. I
> personally think wiki serves these use cases much better than Github would.
>
> --
> Stas Malyshev
> smalyshev@gmail.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000015da6605bf71c21c--