Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Web code license
Date: Fri, 17 Mar 2006 11:03:16 +0100
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA3515D@algol.sollentuna.se>
Thread-Topic: [pgsql-www] Web code license
Thread-Index: AcZJqT5bdjusHjWyT+evEj3UA8h8AgAAGI3gAAAR+hA=
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Dave Page" <dpage@vale-housing.co.uk>,
	<pgsql-www@postgresql.org>

> > So...
> >=20
> > I'm looking at putting in the code for the "new techdocs" in cvs=20
> > sometime soon, and realised I forgot this question :)
> >=20
> > The code uses tinymce (http://tinymce.moxiecode.com/) for visual=20
> > editing.
>=20
> There's a coincidence - guess what I've been hacking about=20
> all morning!

:-)


> > This is LGPL code. My question is, should this be added to=20
> cvs (with=20
> > appropriate license files etc, of course), or should it be kept=20
> > outside (like the PEAR components we rely on for example).
>=20
> It should be kept outside I think - perhaps under /files so=20
> it's nicely seperated.

/files/ is in cvs.=20
/files/ is what I had in mind when I said "in cvs". :-) Certainly not
sticking it inside the framework code.

//Magnus