Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113997
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>
 <CAOwTYAvgpOqmw2w2f-LjykzVDRs_1Hackj=FQMJfthD5xtG1Ow@mail.gmail.com> <AM9PR09MB502894C4DE1F3AEE2274A145AE749@AM9PR09MB5028.eurprd09.prod.outlook.com>
In-Reply-To: <AM9PR09MB502894C4DE1F3AEE2274A145AE749@AM9PR09MB5028.eurprd09.prod.outlook.com>
Date: Thu, 8 Apr 2021 11:21:15 +0200
Message-ID: <CAOwTYAsn2N8avPVTfMaXU_qvN3U1fuoq4N13G76917VHTtFCaQ@mail.gmail.com>
To: Sergey Panteleev <sergey@s-panteleev.ru>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005f54a905bf72921c"
Subject: Re: [PHP-DEV] wiki.php.net upgrade
From: krakjoe@gmail.com (Joe Watkins)

--0000000000005f54a905bf72921c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

First, thanks for taking the time to do that.

I don't think we have a staging capability for the wiki.

I don't think it's likely that anyone will review the pull request.

I would suggest that you request access to commit to the wiki, and then
email systems to get access to the wiki machine.

Someone else may have better or more specific suggestions for you.

Cheers
Joe

On Thu, 8 Apr 2021 at 11:16, Sergey Panteleev <sergey@s-panteleev.ru> wrote=
:

> Hi there!
>
> Oops .. for some reason an empty message came, try again =3D(
>
> I prepared an upgrade to the last release [1].
> I tested locally, it seems ok.
>
> Can we test it in the production environment, but not yet release it?
>
> [1] https://github.com/php/web-wiki/pull/15
>
> =E2=80=94
> wbr,
> Sergey Panteleev
>
>
> From: Joe Watkins <krakjoe@gmail.com>
> Date: Thursday, 8 April 2021, 11:23
> To: Stanislav Malyshev <smalyshev@gmail.com>
> Cc: PHP internals <internals@lists.php.net>
> Subject: Re: [PHP-DEV] wiki.php.net upgrade
> 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
> >
> >
>

--0000000000005f54a905bf72921c--