Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1398478091.5681.8.camel@guybrush>
References: <F014D0B8-EEC6-4B55-82D7-A2B2E26B70B4@googlemail.com>
	<1398478091.5681.8.camel@guybrush>
Date: Fri, 25 Apr 2014 23:26:35 -0700
Message-ID: <CAKOpQSyiP0638r=i81O6uxHt408ro9t6PjWmoEpEggndyYw=_A@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Kevin Ingwersen <ingwie2000@googlemail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013a0894f5324b04f7ec29db
Subject: Re: [PHP-DEV] License question
From: kris.craig@gmail.com (Kris Craig)

--089e013a0894f5324b04f7ec29db
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 25, 2014 at 7:08 PM, Johannes Schl=C3=BCter
<johannes@schlueters.de>wrote:

> On Sat, 2014-04-26 at 01:22 +0200, Kevin Ingwersen wrote:
> > Hey!
> >
> > I am not very good with English - its my second language, German my
> > first - so I wanted to ask about something that has to do with
> > redistribution.
> >
> > Currently, in my project I am configuring PHP and then compiling it,
> > plus a few extensions (v8js, yar, uv, pthreads, PHP-CPP) to a set of
> > static libraries (libphp5.a, libtsrm.a, libzend.a, libphp-v8js.a, =E2=
=80=A6).
> > In the end process, this is all combined, together with other
> > libraries, into a dynamic library.
> >
> > This project is not public yet, since I dont know if:
> >
> > - I can actually link PHP into my dynamic library without tripping on
> > any licensing?
> > - That applies to all extensions using the PHP license?
> > - I have to redistribute anything else but the headers? (of course, a
> > copyright notice to php plus original headers of the main library and
> > extension swould be distributed all together, excluded would be the
> > actual binaries/utilities, phar, php, php-cgi, etc.)
> >
> > Would be great to know if I can work it that way or not! :) Because
> > the least I want is to run against a wall=E2=80=A6 o.o
> >
>
>
>   1. Redistributions of source code must retain the above copyright
>      notice, this list of conditions and the following disclaimer.
>
>   2. Redistributions in binary form must reproduce the above copyright
>      notice, this list of conditions and the following disclaimer in
>      the documentation and/or other materials provided with the
>      distribution.
>
> and
>
>   6. Redistributions of any form whatsoever must retain the following
>      acknowledgment:
>      "This product includes PHP software, freely available from
>      <http://www.php.net/software/>".
>
> sound relatively clear. I'm not really getting whether you distribute
> source or binaries. In general providing that licenses in some "about"
> dialog or referring to it from your README or whatever should be fine.
> If you can describe in more detail I assume that group@qhp.net (I'm no
> member there can't speak for them) will help you ..,. but mind if you
> really go into legal issues: Ask two lawyers and you receive three
> answers. ;-)
>
> johannes
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Where does the group alias go to, anyway?

--Kris

--089e013a0894f5324b04f7ec29db--