| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Clarifications of licences on pgfoundry |
| Date: | 2010-05-18 13:22:02 |
| Message-ID: | 1274188922.28911.2064.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2010-05-18 at 07:32 -0400, Andrew Dunstan wrote:
>
> Simon Riggs wrote:
> > That puts a fairly large hole in recommending that people visit
> > pgFoundry. That either needs to fixed or users will no longer be able to
> > trust PgFoundry.
> >
> pgFoundry is a resource we provide the community. The projects there are
> the responsibility of their individual owners. We are not going to start
> being the license police. I at least have neither the time to do that
> nor any interest in doing it. If people want to use what is on pgFoundry
> then it is up to them to make sure it has whatever licence meets their
> requirements.
Agreed, though that significantly lessens the value of that resource for
everybody. If somebody would like to try to improve that by attempting
to improve or police the licencing, it would be appreciated.
> What we should do is add the PostgreSQL license to the list of available
> licenses and make sure it is the default for new projects.
Good idea.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2010-05-18 13:24:17 | Re: Clarifications of licences on pgfoundry |
| Previous Message | jesper | 2010-05-18 13:11:40 | pg_upgrade - link mode and transaction-wraparound data loss |