public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Magnus Hagander <[email protected]>
To: [email protected]
Subject: Re: Web code license
Date: Fri, 17 Mar 2006 10:13:10 -0000
Message-ID: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9583@ratbert.vale-housing.co.uk> (raw)
> -----Original Message-----
> From: Magnus Hagander [mailto:[email protected]]
> Sent: 17 March 2006 10:03
> To: Dave Page; [email protected]
> 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
view thread (4+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Web code license
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9583@ratbert.vale-housing.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox