| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Travers <chris(dot)travers(at)adjust(dot)com>, 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 17:10:27 |
| Message-ID: | 20180727171026.GT5695@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 27, 2018 at 10:01:40AM -0700, Andres Freund wrote:
> 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. [...]
Sure it does: a) it allows PG to reject such contributions unless they
come with suitable grants, and b) it gives PG users a legal defense
should they ever be sued for infringement on a patent that was not
disclosed to PG at the time of the contribution. (b) is a big deal.
Nico
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2018-07-27 17:16:18 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Previous Message | Andres Freund | 2018-07-27 17:05:18 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |