| From: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Nico Williams <nico(at)cryptonector(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How can we submit code patches that implement our (pending) patents? |
| Date: | 2018-07-27 18:07:31 |
| Message-ID: | CAN-RpxC34ue4XFvE2dB5UUryfy6HaSFmQ_BKi0HoFGU78_OVJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 27, 2018, 19:01 Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-07-27 11:15:00 -0500, Nico Williams wrote:
> > Even assuming you can't change the PG license, you could still:
> >
> > - require disclosure in contributions
>
> That really has no upsides, except poison the area. Either we reject
> the patch and people doing so can reasonably be expected to know about
> the patents, making further contributions by them worse. Or we accept
> the patch, and the listed patents make the commercial offerings harder,
> further development more dubious, readers can reasonably be concerned
> about being considered do know about the patents in independent
> projects.
>
What about just requiring a patent license that grants all rights necessary
to fully enjoy the copyright license? That avoids the need to change the
license fomally. And it would just clarify that we expect that patents do
NOT change the license. Not that I expect there would be takers....
>
> Greetings,
>
> Andres Freund
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-27 18:12:06 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Previous Message | Chapman Flack | 2018-07-27 17:59:12 | Re: How can we submit code patches that implement our (pending) patents? |