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

From Tsunakawa, Takayuki
Subject RE: How can we submit code patches that implement our (pending)patents?
Date
Msg-id 0A3221C70F24FB45833433255569204D1FA2A21C@G01JPEXMBYT05
Whole thread Raw
In response to Re: How can we submit code patches that implement our (pending) patents?  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: How can we submit code patches that implement our (pending) patents?
Re: How can we submit code patches that implement our (pending)patents?
Re: How can we submit code patches that implement our (pending)patents?
List pgsql-hackers
From: Craig Ringer [mailto:craig@2ndquadrant.com]
> I'm assuming you don't want to offer a grant that lets anyone use them for
> anything. But if you have a really broad grant to PostgreSQL, all someone
> would have to do to inherit the grant is re-use some part of PostgreSQL.

Your assumption is right.  No scope is the same as no patent; it won't help to defend PostgreSQL community against
rivalcompanies/communities of other DBMSs.  Or, I think we can set the scope to what OIN states.  Fortunately, anyone
canjoin OIN free of charge.
 


> I guess there's a middle ground somewhere that protects substantial
> derivatives and extracts but stops you using some Pg code snippets as a
> freebie license.

Are you assuming that developers want to use PG code snippets for non-PostgreSQL or even non-DBMS software?  I believe
thataccepting patented code from companies would be practically more useful for PostgreSQL enhancement and growth.
PostgreSQLis now a mature software, and it can be more corporate-friendly like other software under Apache License.
 


Regards
Takayuki Tsunakawa




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
Next
From: Larry Rosenman
Date:
Subject: Re: peripatus build failures....