From: | Richard_D_Levine(at)raytheon(dot)com |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Fw: License question |
Date: | 2005-10-04 20:04:24 |
Message-ID: | OFE17F95C9.F4833E1B-ON05257090.006DA8A4-05257090.006E444A@ftw.us.ray.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Aaron,
If you are new to free software, it is best to familiarize yourself with
the different types of licenses, and especially with the concept of
copyleft:
http://www.fsf.org/fsf/licensing
BSD, LGPL, and GPL are all very different animals, and representative of
many of the licenses used in FOSS. For the type of work you do, a GPL
license might be bad, because your clients pay you to develop software, and
then you have to tell them they must contribute their new software back to
the opensource community. BSD is probably better for your needs, and what
PostgreSQL uses.
----- Forwarded by Richard D Levine/US/Raytheon on 10/04/2005 02:57 PM
-----
pgsql-general-owner(at)postgresql(dot)org wrote on 10/04/2005 02:19:05 PM:
>
> > This brings me here. I have heard of PostGreSQL, so it’s not new to me.
> > But all this licensing is. And maybe you can help get some
clarification
> > for the MySQL licensing too.
> >
>
> You can do anything you want with PostgreSQL. You can close source it,
> you can sell it, you can rename it.
>
> You just can't sue us if something goes wrong.
>
> No charge.
>
> Sincerely,
>
> Joshua D. Drake
>
>
>
>
> > We will not be selling the database software. We may install it for
> > them, though. In fact, most of the time, we will be the ones to install
> > it, and we charge for that time. Our customers are very aware that we
> > did not write it, nor are we selling it. Even if they are to purchase
> > SQL Server, they are the ones to purchase it directly, not us. We
> > purchase the connectivity kits that we use to connect to the database,
> > and then pass that cost on to the customer. It is purchased in their
> > name with their information. We do not charge extra or tack on any
fees.
> > We do it this way so that no screw ups are made… The connectivity kit
is
> > the one that connects to the database; we connect to the connectivity
> > kit through our software.
> >
> > Knowing all this, what do we need to purchase, what can we do and what
> > can’t we do? It’s hard getting a straight answer from anyone that is
why
> > I am here. If we can’t do it, we won’t. If we can save our customers
> > some money while getting them really good options and software, we
would
> > like to do that. But on the same token, we don’t to do anything unfair
> > or illegal.
> >
> >
> > Thank you for your time.
> >
> > Aaron
> >
> >
> >
> > ---------------------------(end of
broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > choose an index scan if your joining column's datatypes do not
> > match
> --
> Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
> PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Welty, Richard | 2005-10-04 20:12:16 | Re: License question[VASCL:A1077160A86] |
Previous Message | Markus Schulz | 2005-10-04 20:04:06 | selfmade datatype in C and server-crash |