| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Sean Chittenden <sean(at)chittenden(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: plPHP -- sort of an announcement.. but not commercial |
| Date: | 2003-08-04 20:48:58 |
| Message-ID: | 11328.1060030138@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> From what I read:
> Products derived from this software may not be called "PHP", nor
> may "PHP" appear in their name, without prior written permission
> from group(at)php(dot)net(dot) You may indicate that your software works in
> conjunction with PHP by saying "Foo for PHP" instead of calling
> it "PHP Foo" or "phpfoo"
> No. We don't need to do that. We couldn't call it PHP Procedural
> Language but Procedural Language for PHP (plPHP) is ok.
However, your code is not "derived from" PHP, is it? It's a glue layer
that allows PHP to be attached to Postgres (or vice versa if you prefer).
It's not clear to me that you're bound by any of their copyright
conditions, since you aren't planning to ship any of their code in your
tarball.
It'd probably be polite to contact them and let them know that you want
to call it plphp because "plfoo" is the standard name for a Postgres PL
based on language "foo". It's hard to believe that they'd object.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-08-04 20:54:29 | Re: what is null |
| Previous Message | Richard Welty | 2003-08-04 20:40:46 | varchar, text and cidr |