Everything

php

wiki.php.net upgrade

php.internals

Stas Malyshev

5 years ago

Hi!

Given that we're upgrading and updating our infrastructure, maybe it's
time to update the wiki.php.net wiki too? I count five upgrade warnings
there now, and I am not sure, but I think we could assume there were
some bugfixes in it since 2017.

--
Stas Malyshev
smalyshev@gmail.com

Sebastian Bergmann

5 years ago

Am 08.04.2021 um 08:01 schrieb Stanislav Malyshev:

> Given that we're upgrading and updating our infrastructure, maybe it's
> time to update the wiki.php.net wiki too? I count five upgrade warnings
> there now, and I am not sure, but I think we could assume there were some
> bugfixes in it since 2017.

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.

Stas Malyshev

5 years ago

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

Joe Watkins

5 years ago

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:

Сергей Пантелеев

5 years ago

Сергей Пантелеев

5 years ago

Hi there!

Oops .. for some reason an empty message came, try again =(

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

—
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:

Joe Watkins

5 years ago

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:

Niklas Keller

5 years ago

Hey Sergey,

I've tried the same yesterday, but the auth plugin does no longer work for
me. I get a 404 after trying to sign in.

2692 files changed, 35365 insertions(+), 102210 deletions(-)

Dokuwiki changed a lot in the latest release, e.g. namespacing and
refactoring quite a bit. I'll need to have a look at the plugin.

@Stanislav Malyshev <smalyshev@gmail.com>: We're only one release behind,
the other three yellow bars are about release candidates. However, Dokuwiki
might not be PHP 8 compatible, yet, at least the latest release only says
it fixes PHP 7.4 compatibility.

I'd be open to replace the wiki with a Git repository and markdown. I
prepared that a long time ago by writing a Dokuwiki -> Markdown converter.

The main challenges I see are:
- Voting
- Voting access for people without VCS account

Voting could probably be moved into main.php.net (except for people without
a VCS account, but we could probably approve an account there without any
further access?)

Best,
Niklas

Am Do., 8. Apr. 2021 um 11:16 Uhr schrieb Sergey Panteleev <
sergey@s-panteleev.ru>:

Сергей Пантелеев

5 years ago

Hmm…

> I've tried the same yesterday, but the auth plugin does no longer work for me. I get a 404 after trying to sign in.

Can you also check the .htaccess file?

IMO, it should fail on /start page without additional settings.

I deployed for the test here: https://wiki.s-panteleev.ru/

—
wbr,
Sergey Panteleev


From: Niklas Keller <me@kelunik.com>
Date: Thursday, 8 April 2021, 13:15
To: Sergey Panteleev <sergey@s-panteleev.ru>, Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] wiki.php.net upgrade
Hey Sergey,

I've tried the same yesterday, but the auth plugin does no longer work for me. I get a 404 after trying to sign in.

2692 files changed, 35365 insertions(+), 102210 deletions(-)

Dokuwiki changed a lot in the latest release, e.g. namespacing and refactoring quite a bit. I'll need to have a look at the plugin.

@Stanislav Malyshev<mailto:smalyshev@gmail.com>: We're only one release behind, the other three yellow bars are about release candidates. However, Dokuwiki might not be PHP 8 compatible, yet, at least the latest release only says it fixes PHP 7.4 compatibility.

I'd be open to replace the wiki with a Git repository and markdown. I prepared that a long time ago by writing a Dokuwiki -> Markdown converter.

The main challenges I see are:
- Voting
- Voting access for people without VCS account

Voting could probably be moved into main.php.net<http://main.php.net> (except for people without a VCS account, but we could probably approve an account there without any further access?)

Best,
Niklas

Am Do., 8. Apr. 2021 um 11:16 Uhr schrieb Sergey Panteleev <sergey@s-panteleev.ru<mailto:sergey@s-panteleev.ru>>:
Hi there!

Oops .. for some reason an empty message came, try again =(

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

—
wbr,
Sergey Panteleev


From: Joe Watkins <krakjoe@gmail.com<mailto:krakjoe@gmail.com>>
Date: Thursday, 8 April 2021, 11:23
To: Stanislav Malyshev <smalyshev@gmail.com<mailto:smalyshev@gmail.com>>
Cc: PHP internals <internals@lists.php.net<mailto:internals@lists.php.net>>
Subject: Re: [PHP-DEV] wiki.php.net<http://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<mailto:smalyshev@gmail.com>> wrote:

Niklas Keller

5 years ago

Hey all,

the wiki is up to date now with the help of @Sergey Panteleev
<sergey@s-panteleev.ru>. :-)

Sorry for the upgrade downtime being slightly longer than intended.

Best,
Niklas

Stas Malyshev

5 years ago

On 4/8/21 7:44 AM, Niklas Keller wrote:

> Hey all,
>
> the wiki is up to date now with the help of @Sergey Panteleev
> <mailto:sergey@s-panteleev.ru>. :-)

Thank you both!

--
Stas Malyshev
smalyshev@gmail.com

Stas Malyshev

5 years ago

Hi!

> Nobody has updated the wiki in several years, despite warnings, and two
> very public breaches of security that we know about.

I think it's just because nobody has focused attention to it. As you
see, once it was focused, it has happened.

Thanks,

--
Stas Malyshev
smalyshev@gmail.com

Mark Randall

5 years ago

On 08/04/2021 19:38, Stanislav Malyshev wrote:

> I think it's just because nobody has focused attention to it. As you
> see, once it was focused, it has happened.

This is usually referred to as shutting the stable door after the horse
has bolted.