Re: possible license violations

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "tom(dot)beacon" <tom(dot)beacon(at)protonmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: possible license violations
Date: 2021-06-04 16:34:01
Message-ID: 20210604163400.GL20766@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings,

* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> On Thu, Jun 3, 2021 at 06:08:42PM -0400, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > On Thu, Jun 3, 2021 at 09:31:15PM +0000, tom.beacon wrote:
> > >> What is the best contact with whom to discuss possible violations of the pgsql
> > >> license?
> >
> > > Uh, good question, and I could not find the answer easily. I would
> > > report it to the owners of the Postgres trademark:
> >
> > > https://www.postgresql.org/about/policies/trademarks/
> > > board(at)lists(dot)postgres(dot)ca
> >
> > A point worth making here is that the Postgres *license* is so lax
> > that it's basically impossible to violate, unless maybe by redistributing
> > the code sans COPYRIGHT file. And even if somebody were doing that,
> > I doubt how much we'd care.
>
> I have received private reports of our COPYRIGHT not being properly
> included in distributions so I am sensitive to those possible
> violations, and I assume the trademark holders would deal with those as
> well.

One of the downsides of attributing the copyrights to an organization
which doesn't exist (PGDG) is that, I would think anyway, it'd make it
rather hard to actually enforce anything regarding copyright.. I'm not
a lawyer though.

Thanks,

Stephen

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laura Smith 2021-06-04 16:47:45 Struggling with EXCLUDE USING gist
Previous Message Atul Kumar 2021-06-04 16:06:49 Re: strange behavior of WAL files