Re: How can we submit code patches that implement our (pending) patents? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: How can we submit code patches that implement our (pending) patents?
Date
Msg-id 27889.1531230429@sss.pgh.pa.us
Whole thread Raw
In response to RE: How can we submit code patches that implement our (pending)patents?  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Responses RE: How can we submit code patches that implement our (pending)patents?  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Re: How can we submit code patches that implement our (pending)patents?  (Nico Williams <nico@cryptonector.com>)
Re: How can we submit code patches that implement our (pending)patents?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
"Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com> writes:
> From: Nico Williams [mailto:nico@cryptonector.com]
>> ... But that might reduce the
>> size of the community, or lead to a fork.

> Yes, that's one unfortunate future, which I don't want to happen of
> course.  I believe PostgreSQL should accept patent for further
> evolution, because PostgreSQL is now a popular, influential software
> that many organizations want to join.

The core team has considered this matter, and has concluded that it's
time to establish a firm project policy that we will not accept any code
that is known to be patent-encumbered.  The long-term legal risks and
complications involved in doing that seem insurmountable, given the
community's amorphous legal nature and the existing Postgres license
wording (neither of which are open for negotiation here).  Furthermore,
Postgres has always been very friendly to creation of closed-source
derivatives, but it's hard to see how inclusion of patented code would
not cause serious problems for those.  The potential benefits of
accepting patented code just don't seem to justify trying to navigate
these hazards.

            regards, tom lane


pgsql-hackers by date:

Previous
From: 今井 良一
Date:
Subject: Re: Locking B-tree leafs immediately in exclusive mode
Next
From: Ashutosh Bapat
Date:
Subject: Re: BUG #15212: Default values in partition tables don't work asexpected and allow NOT NULL violation