Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122222
MIME-Version: 1.0
References: <1705874211.14975.ezmlm@lists.php.net> <CABVsiphJTtEx_UVJx40c2jO7mfvFXQUJftLxQBub1x85ONQp=A@mail.gmail.com>
In-Reply-To: <CABVsiphJTtEx_UVJx40c2jO7mfvFXQUJftLxQBub1x85ONQp=A@mail.gmail.com>
Date: Mon, 22 Jan 2024 14:30:22 +0100
Message-ID: <CAPyj-LBpts3+yUmUmuNJ=bpqavF92L3akvBpjLtfV1_NRYsGXA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: Wiki Access request
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Carlos

You should now have access to the /internals sub-pages.

On Mon, Jan 22, 2024 at 11:38=E2=80=AFAM Barel <barel.barelon@gmail.com> wr=
ote:
>
> I didn't know that there was a list of tech resources listed in the
> "CONTRIBUTING.md" file. I have been researching resources that have
> information about PHP internals and have found a lot, more than twenty. I
> can think of three possibilities:
> - List them all in the contributing document but this can be a bit
> overwhelming as, like I said, the number of resources available is big

Feel free to share this list here, on GitHub or otherwise. I'm
skeptical whether throwing partially outdated resources at people is
actually helpful.

> - Add a new page in the Github repo with all these links and link to that
> page from the contributing page
> - Keep the list in the wiki and link to that page from the contributing p=
age

One of the reasons I'd like to move off of the wiki for these things
is that there is no review process. We highly value volunteer work,
but trusting new contributors to blindly make changes to official
guides is obviously somewhat problematic.

I'd prefer to make CONTRIBUTING.md the "official list" for now. This
file is allowed to be long. And as mentioned, I suspect that the list
of 20+ items may be trimmed.

Ilija