Which pretty much brings you back to my wording doesnt it?
"PostgreSQL is licensed under the BSD license, giving maximum
flexibility for both commercial and noncommercial use. This puts our
users in control of how PostgreSQL is deployed in their organizations,
not us, which is how we feel it should be."
We don't get into price (which as Peter pointed out we shouldn't) and
highlight flexibility (which Ned was doing). We also differentiate
between both the commercial companies as well as the dual licensing
folks by reassuring people that they are in control.
Robert Treat
On Thu, 2004-09-02 at 13:46, Ned Lilly wrote:
> Point taken. I guess I would include modification under the general word "use" for purposes of this discussion.
>
> But maybe say "... how the software is used or distributed."
>
>
>
> Peter Eisentraut wrote:
> > Ned Lilly wrote:
> >
> >>The original language I suggested was:
> >>
> >>PostgreSQL is released under a "BSD-style" license, which allows
> >>maximum flexibility for corporate and individual users, with no
> >>license fees regardless of how the software is used.
> >
> >
> > My response still holds:
> >
> >
> >>>>This is an incorrect interpretation of the licensing situation.
> >>>>There are plenty of licenses that are granted free of charge but
> >>>>still leave the recipient without any flexibility. The advantage
> >>>>of the BSD license is the lack of restrictions on modication and
> >>>>distribution.
> >
> >
> >>I think that offers a good contrast to both MySQL and the commercial
> >>competitors.
> >
> >
> > You can *use* MySQL however you want, if you have obtained a legal copy.
> > You just can't modify or distribute it however you want. That is an
> > important distinction. Copyright law does not regulate use at all; it
> > regulates copying. Once you have obtained a legal copy, you can use
> > the software in any way you choose, even if some licenses try to give a
> > different impression.
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
