Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125340
Date: Wed, 28 Aug 2024 12:09:48 -0400
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Message-ID: <2C8593BC-48FC-4D24-AEB6-0C76CE937C72@getmailspring.com>
In-Reply-To: <819bcfbb-b747-4ed1-a878-bf5a8e00935e@app.fastmail.com>
References: <819bcfbb-b747-4ed1-a878-bf5a8e00935e@app.fastmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Using and Mentioning
 Third-party Packages in PHP Documentation and Web Projects
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="66cf4bcc_643c9869_13757"
From: john@coggeshall.org (John Coggeshall)

--66cf4bcc_643c9869_13757
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



On Aug 28 2024, at 9:34 am, Larry Garfield <larry@garfieldtech.com> wrote:
>
> I don't think I'd support a list of "popular" frameworks, but mentioning Composer, Xdebug, and PHPUnit seems a requirement for a useful modern tutorial.

Can you explain your position more here, what exactly is your concern (if I captured it in my previous email -- why do you think I'm off base to say we're over-estimating the importance)?
> Admittedly, the docs team is very under-resourced right now and even the reference section has not-small holes, making maintaining even more types of documentation a potential challenge. That's something the Foundation could possibly help with. But that's not the topic at hand: The topic at hand is just "look, we should be able to mention Composer, Xdebug, and PHPUnit, OK?" On which I very much am in agreement.
That's not the topic at hand -- the topic at hand is adopting the principle that:
"The web and documentation projects within the PHP Project can use or document the existence of third-party PHP projects as part of their roles in supporting the overall PHP community. Such use does not represent endorsement of those third-party projects by the PHP Project."
So that would include frameworks, etc. alongside composer, phpunit, etc.
--66cf4bcc_643c9869_13757
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div class=3D=22gmail=5Fquote=5Fattribution=22>On Aug 28 2024, at=
 9:34 am, Larry Garfield &lt;larry=40garfieldtech.com&gt; wrote:</div><bl=
ockquote><div><br><div>I don't think I'd support a list of =22popular=22 =
frameworks, but mentioning Composer, Xdebug, and PHPUnit seems a requirem=
ent for a useful modern tutorial.</div></div></blockquote><div><br><div>C=
an you explain your position more here, what exactly is your concern (if =
I captured it in my previous email -- why do you think I'm off base to sa=
y we're over-estimating the importance)=3F</div><br><blockquote>Admittedl=
y, the docs team is very under-resourced right now and even the reference=
 section has not-small holes, making maintaining even more types of docum=
entation a potential challenge. That's something the =46oundation could p=
ossibly help with. But that's not the topic at hand: The topic at hand is=
 just =22look, we should be able to mention Composer, Xdebug, and PHPUnit=
, OK=3F=22 On which I very much am in agreement.</blockquote><br><div>Tha=
t's not the topic at hand -- the topic at hand is adopting the principle =
that:</div><br><div>=22The web and documentation projects within the PHP =
Project can use or document the existence of third-party PHP projects as =
part of their roles in supporting the overall PHP community. Such use doe=
s not represent endorsement of those third-party projects by the PHP Proj=
ect.=22</div><br><div>So that would include frameworks, etc. alongside co=
mposer, phpunit, etc. </div></div>
--66cf4bcc_643c9869_13757--