public inbox for [email protected]
help / color / mirror / Atom feedWeb code license
4+ messages / 2 participants
[nested] [flat]
* Web code license
@ 2006-03-17 09:57 Magnus Hagander <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Magnus Hagander @ 2006-03-17 09:57 UTC (permalink / raw)
To: pgsql-www
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. 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).
I personally think it should be added to cvs, because that makes life a
lot easier. But given the discussions lately about the license for the
graphics, I figured it's much better to bring it up here before
actualyil doing anything :)
Unlike the license on the graphics, LGPL should be "enough compatible"
with BSD for our use, I beleive. And the site will still work without
it, you just don't get visual editing.
Thoughts?
//Magnus
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Web code license
@ 2006-03-17 10:02 Dave Page <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Dave Page @ 2006-03-17 10:02 UTC (permalink / raw)
To: Magnus Hagander <[email protected]>; pgsql-www
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Magnus Hagander
> Sent: 17 March 2006 09:58
> To: [email protected]
> Subject: [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.
Regards, Dave.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Web code license
@ 2006-03-17 10:03 Magnus Hagander <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Magnus Hagander @ 2006-03-17 10:03 UTC (permalink / raw)
To: Dave Page <[email protected]>; pgsql-www
> > 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.
//Magnus
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Web code license
@ 2006-03-17 10:13 Dave Page <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Dave Page @ 2006-03-17 10:13 UTC (permalink / raw)
To: Magnus Hagander <[email protected]>; pgsql-www
> -----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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2006-03-17 10:13 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-17 09:57 Web code license Magnus Hagander <[email protected]>
2006-03-17 10:02 Re: Web code license Dave Page <[email protected]>
2006-03-17 10:03 Re: Web code license Magnus Hagander <[email protected]>
2006-03-17 10:13 Re: Web code license Dave Page <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox