| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Amonson, Paul D" <paul(dot)d(dot)amonson(at)intel(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, "Shankaran, Akash" <akash(dot)shankaran(at)intel(dot)com> |
| Subject: | Re: Proposal for Updating CRC32C with AVX-512 Algorithm. |
| Date: | 2024-06-12 18:08:02 |
| Message-ID: | 1507251.1718215682@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Amonson, Paul D" <paul(dot)d(dot)amonson(at)intel(dot)com> writes:
> I had our OSS internal team, who are experts in OSS licensing, review possible conflicts between the PostgreSQL license and the BSD-Clause 3-like license for the CRC32C AVX-512 code, and they found no issues. Therefore, including the new license into the PostgreSQL codebase should be acceptable.
Maybe you should get some actual lawyers to answer this type of
question. The Chromium license this code cites is 3-clause-BSD
style, which is NOT compatible: the "advertising" clause is
significant.
In any case, writing copyright notices that are pointers to
external web pages is not how it's done around here. We generally
operate on the assumption that the Postgres source code will
outlive any specific web site. Dead links to incidental material
might be okay, but legally relevant stuff not so much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-06-12 18:08:31 | Re: race condition in pg_class |
| Previous Message | John H | 2024-06-12 18:05:33 | Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions |