Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> > We can't, because we can't revoke Berkeley's copyright. But in
> > practice there's hardly any difference anyway.
>
> Just out of curiosity, are the docs covered by the B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> We can't, because we can't revoke Berkeley's copyright. But in
> practice there's hardly any difference anyway.
Just out of curiosity, are the docs covered by the Berkeley copyright?
I know the code originally came from there, but did our current
[EMAIL PROTECTED] wrote:
>
> As the copyright owner, "The PostgreSQL Global Development Group," has
> the right to license the documentation any way they see fit.
The PGDG has never asked for copyright assignments from contributors (as
I gather the PHP folks do), so the copyright to Postgres is co
Mark Woodward wrote:
> Then, what you are saying, is that anyone could come along and create
> a paper trail calling themselves "The PostgreSQL Global Devlopment
> Group," and claim ownership.
No, the point is that we want to stick at least *some* copyright notice
in the code, so people are advis
"Mark Woodward" <[EMAIL PROTECTED]> writes:
>> In my mind the real reason we stick "Copyright PGDG" in the sources is
>> just as a prophylactic against someone putting their own copyright on
>> the files and then trying to prevent anyone else from using the code.
>> Effectiveness of this measure re
> "Mark Woodward" <[EMAIL PROTECTED]> writes:
>> Sorry, that's not true. At least in the USA, any entity that can be
>> identified can own and control copyright. While it is true, however,
>> that
>> there can be ambiguity, an informal body, say "anarchists for stronger
>> government," without char
"Mark Woodward" <[EMAIL PROTECTED]> writes:
> Sorry, that's not true. At least in the USA, any entity that can be
> identified can own and control copyright. While it is true, however, that
> there can be ambiguity, an informal body, say "anarchists for stronger
> government," without charter or in
> Mark Woodward wrote:
>> As the copyright owner, "The PostgreSQL Global Development Group,"
>> has the right to license the documentation any way they see fit. For
>> PHP to sub-license the documentation, it legally has to be transfered
>> in writing. Verbal agreements are not valid.
>
> The Postg
Mark Woodward wrote:
> As the copyright owner, "The PostgreSQL Global Development Group,"
> has the right to license the documentation any way they see fit. For
> PHP to sub-license the documentation, it legally has to be transfered
> in writing. Verbal agreements are not valid.
The PostgreSQL Glo
> Peter Eisentraut wrote:
>> Mark Woodward wrote:
>> > I would say that "The PostgreSQL Global Development Group" or its
>> > representatives (I'm assuming Tom, Bruce, and/or Marc Fournier) just
>> > has to give something written, that says Christopher Kings-Lynne of
>> > "your address, city, count
Peter Eisentraut wrote:
> Mark Woodward wrote:
> > I would say that "The PostgreSQL Global Development Group" or its
> > representatives (I'm assuming Tom, Bruce, and/or Marc Fournier) just
> > has to give something written, that says Christopher Kings-Lynne of
> > "your address, city, country, etc
> Mark Woodward wrote:
>> I would say that "The PostgreSQL Global Development Group" or its
>> representatives (I'm assuming Tom, Bruce, and/or Marc Fournier) just
>> has to give something written, that says Christopher Kings-Lynne of
>> "your address, city, country, etc" has the right to re-licen
Mark Woodward wrote:
> I would say that "The PostgreSQL Global Development Group" or its
> representatives (I'm assuming Tom, Bruce, and/or Marc Fournier) just
> has to give something written, that says Christopher Kings-Lynne of
> "your address, city, country, etc" has the right to re-license or
>>>Uh, but that's what the BSD license allows --- relicensing as any other
>>>license, including commercial.
>>
>> The point remains that Chris, by himself, does not hold the copyright on
>> the PG docs and therefore cannot assign it to anyone.
>>
>> ISTM the PHP guys are essentially saying that th
Uh, but that's what the BSD license allows --- relicensing as any other
license, including commercial.
The point remains that Chris, by himself, does not hold the copyright on
the PG docs and therefore cannot assign it to anyone.
ISTM the PHP guys are essentially saying that they will only take stu
Bruce Momjian writes:
> Bruno Wolff III wrote:
>> Just because the licenses are compatible, doesn't necessarily mean you
>> can safely sign over the copyrights for documentation that you don't hold.
>> If PHP holds the copyright they can relicense the documentation later under
>> a license that ma
Bruno Wolff III wrote:
> On Tue, Mar 15, 2005 at 08:34:14 -0500,
> Bruce Momjian wrote:
> >
> > Uh, but that's what the BSD license allows --- relicensing as any other
> > license, including commercial.
>
> If that were true, than why not have the code public domain? Ismn't there
> credit info
On Tue, Mar 15, 2005 at 08:34:14 -0500,
Bruce Momjian wrote:
>
> Uh, but that's what the BSD license allows --- relicensing as any other
> license, including commercial.
If that were true, than why not have the code public domain? Ismn't there
credit information that is supposed to be kept?
-
Bruno Wolff III wrote:
> On Tue, Mar 15, 2005 at 06:08:48 -0500,
> Mark Woodward <[EMAIL PROTECTED]> wrote:
> > > I'm currently adding support for the v3 protocol in PHP pgsql extension.
> > > I'm wondering if anyone minds if I lift documentation wholesale from
> > > the PostgreSQL docs for the
On Tue, Mar 15, 2005 at 06:08:48 -0500,
Mark Woodward <[EMAIL PROTECTED]> wrote:
> > I'm currently adding support for the v3 protocol in PHP pgsql extension.
> > I'm wondering if anyone minds if I lift documentation wholesale from
> > the PostgreSQL docs for the PHP docs for these functions. F
On Tue, 15 Mar 2005, Christopher Kings-Lynne wrote:
I'm currently adding support for the v3 protocol in PHP pgsql extension.
I'm wondering if anyone minds if I lift documentation wholesale from the
PostgreSQL docs for the PHP docs for these functions. For instance, the
fieldcodes allowed for PQ
> I'm currently adding support for the v3 protocol in PHP pgsql extension.
> I'm wondering if anyone minds if I lift documentation wholesale from
> the PostgreSQL docs for the PHP docs for these functions. For instance,
> the fieldcodes allowed for PQresultErrorField, docs on
> PQtransactionStat
I'm currently adding support for the v3 protocol in PHP pgsql extension.
I'm wondering if anyone minds if I lift documentation wholesale from
the PostgreSQL docs for the PHP docs for these functions. For instance,
the fieldcodes allowed for PQresultErrorField, docs on
PQtransactionStatus, etc
23 matches
Mail list logo
