[DOC-LICENSE] Re: Publishing an alternative PHP documentation website

[email protected] Thu, 5 Sep 2024 17:14:25 +1000
Newsgroups php.doc.license
Message-ID <[email protected]>
--Apple-Mail=_6865C165-28FA-42B7-9415-20CF8CC36F1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hello PHP documentation team,

I am reaching out to find out if you would, based on the licensing, =
grant me permission to publish my own version of the PHP documentation =
hosted on my own server / domain and have it publicly accessible.

I=E2=80=99ve built a new website generator, i.e., a new phd. It does not =
use any of the phd codebase. The generated website does contain the same =
wording used throughout the php.net website as it is consumes the =
open-source PHP documentation manual (https://github.com/php/doc-en). It =
would, however, have a different design and feature set. Nothing is =
copied from the current php.net <http://php.net/> website, e.g., =
styling, graphics, logo, etc.

The generator will be completely open source.

If I=E2=80=99m understanding=C2=A0the license correctly =
<https://creativecommons.org/licenses/by/3.0/>, it says I am free to =
=E2=80=9CAdapt =E2=80=94 remix, transform, and build upon the material =
for any purpose=E2=80=9D as long as I follow the attribution guidelines, =
which I believe leaving the license and copyright content in should do.

Of course, I don=E2=80=99t want to cross any lines, so I thought it =
would be better to reach out and make sure I=E2=80=99m not =
misunderstanding anything.

Thanks,
Tim.=

--Apple-Mail=_6865C165-28FA-42B7-9415-20CF8CC36F1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">Hello PHP =
documentation team,<div><br></div><div>I am reaching out to find out if =
you would, based on the licensing, grant me permission to publish my own =
version of the PHP documentation hosted on my own server / domain and =
have it publicly accessible.</div><div><br></div><div>I=E2=80=99ve built =
a new website generator, i.e., a new <i>phd.</i>&nbsp;It does not use =
any of the phd codebase. The generated website does contain the same =
wording used throughout the php.net website as it is consumes the =
open-source PHP documentation manual (<a =
href=3D"https://github.com/php/doc-en">https://github.com/php/doc-en</a>).=
 It would, however, have a different design and feature set. Nothing is =
copied from the current&nbsp;<a =
href=3D"http://php.net/">php.net</a>&nbsp;website, e.g., styling, =
graphics, logo, etc.</div><div><br></div><div>The generator will be =
completely open source.</div><div><br></div><div>If I=E2=80=99m =
understanding<a =
href=3D"https://creativecommons.org/licenses/by/3.0/">&nbsp;the license =
correctly</a>, it says I am free to&nbsp;<i>=E2=80=9CAdapt&nbsp;=E2=80=94 =
remix, transform, and build upon the material for any =
purpose=E2=80=9D&nbsp;</i>as&nbsp;long as I follow the attribution =
guidelines, which I believe leaving the license and copyright content in =
should do.</div><div><br></div><div>Of course, I don=E2=80=99t want to =
cross any lines, so I thought it would be better to reach out and make =
sure I=E2=80=99m not misunderstanding =
anything.</div><div><br></div><div>Thanks,</div><div>Tim.</div></body></ht=
ml>=

--Apple-Mail=_6865C165-28FA-42B7-9415-20CF8CC36F1F--