Re: Web code license

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>, <pgsql-www(at)postgresql(dot)org>
Subject: Re: Web code license
Date: 2006-03-17 10:13:10
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9583@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

> -----Original Message-----
> From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> Sent: 17 March 2006 10:03
> To: Dave Page; pgsql-www(at)postgresql(dot)org
> Subject: RE: [pgsql-www] Web code license
>
> > > So...
> > >
> > > I'm looking at putting in the code for the "new techdocs" in cvs
> > > sometime soon, and realised I forgot this question :)
> > >
> > > The code uses tinymce (http://tinymce.moxiecode.com/) for visual
> > > editing.
> >
> > There's a coincidence - guess what I've been hacking about
> > all morning!
>
> :-)
>
>
> > > This is LGPL code. My question is, should this be added to
> > cvs (with
> > > appropriate license files etc, of course), or should it be kept
> > > outside (like the PEAR components we rely on for example).
> >
> > It should be kept outside I think - perhaps under /files so
> > it's nicely seperated.
>
> /files/ is in cvs.
> /files/ is what I had in mind when I said "in cvs". :-) Certainly not
> sticking it inside the framework code.

Alright, the bit where we stick the stuff that comes from different
CVS's like the raw FAQs.

/D

Browse pgsql-www by date

  From Date Subject
Next Message Robert Treat 2006-03-18 15:15:00 Fwd: [webmaster] Kudos
Previous Message Magnus Hagander 2006-03-17 10:03:16 Re: Web code license