Re: [RFC] [Discussion] Using and Mentioning Third-party Packages in PHP Documentation and Web Projects
On Thu, Sep 26, 2024, at 5:13 AM, Tim Düsterhus wrote:
> Hi
>
> Am 2024-09-25 01:45, schrieb Jim Winstead:
>> It has taken me longer than initially anticipated to circle back to
>> this, but I intend to open the voting on this RFC on Thursday
>> (2024-09-26T16:00:00Z or so) unless there are any other changes that
>> anyone would like to propose.
>>
>> The RFC again: https://wiki.php.net/rfc/web-and-doc-use-not-endorsement
>
> Thank you. I've used your reminder as the opportunity to catch up with
> this thread after my vacation.
>
> I'm likely going to vote “no” on your RFC, because I do not believe that
> your proposed statement of principle makes the situation any *less*
> vague. It just makes the situation vague in a different way, because
> there are no guidelines regarding what is acceptable and what is not, as
> also mentioned by others in this RFC's discussion thread.
I am very open to discussing guidelines that anyone thinks would be more acceptable than my
proposal.
I think the closest anyone has come to another suggestion so far is Larry's proposal that
individual deviations from the currently-unspecified policy should be settled by an RFC.
(https://news-web.php.net/php.internals/125284)
The currently unstated guideline is "don't mention third-party tools" and it has been
very inconsistently enforced so we have things like https://www.php.net/manual/en/install.windows.tools.php
and https://www.php.net/manual/en/install.macosx.packages.php.
We have 250 pages of documentation for a UI extension that hasn't seen any movement in eight
years (https://www.php.net/manual/en/book.ui.php), but the documentation can't mention Composer
because it's the wrong sort of contribution to the PHP ecosystem.
Jim
Thread (31 messages)