Re: How can we submit code patches that implement our (pending)patents?
От | Andres Freund |
---|---|
Тема | Re: How can we submit code patches that implement our (pending)patents? |
Дата | |
Msg-id | 20180726195102.er4buj7vpcgnyk2m@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: How can we submit code patches that implement our (pending) patents? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: How can we submit code patches that implement our (pending) patents?
|
Список | pgsql-hackers |
On 2018-07-26 09:51:54 -0400, Tom Lane wrote: > Chris Travers <chris.travers@adjust.com> writes: > > What about adding an extra line to the license that indicates that the > > copyright owners also give all patent licenses which are both in their > > power to grant and also needed for exercise of the copyright license and > > require that new code contributions use this license with the extra clause. > > There's been an awful lot of discussion in this thread that supposes that > we can change the Postgres license. Let me just point out very clearly > that no such thing is going to happen. There will be no changes, no > additions, no alternate licenses, period. To change the license, we'd > need the agreement of all current and past contributors, which is a > completely impractical thing even if there were fairly wide consensus > that a particular change is a good idea. Which there isn't. That's obviously not going to happen. But there is the less crazy alternative of dual licensing new contributions going forward, with a licence that's TPL compatible. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: