RE: TWiki cookbook / licences

Noel Welsh wrote:
> I'm impressed with the ease that this has been done.
> It looks nice, works well, and the webhop URL is great.

I was impressed too.  I've set up twiki for clients, but mostly for in-house
docs where we've never bothered to customize it at all.

The one problem I'm aware of at the moment is that the code snippet
inclusion mechanism I used seems to slow certain things down dramatically
(previewing & saving edits, or viewing revision history).  I'll be looking
for a fix or an alternative.

> The only thing that should be done is mentioning the
> licence we use, preferrably at the bottom of every
> page (and an additional reminder on the edit page
> would be good).

OK.  Which license?  LGPL for now?  See below.

> The case against the FDL is:
>
> http://home.twcny.rr.com/nerode/neroden/fdl.html
...
> Clearly the cookbook isn't a library under this
> definition.  However it can still be an "other
> program".  So I think using the LGPL isn't a problem.

If it makes more sense to use the GPL rather than the LGPL for
documentation, perhaps the documentation could be licensed as GPL, with a
note that all source code is also separately licensed under the LGPL.

In fact, if the source code is made available as a separate package, that
package could be licensed as LGPL, while documentation and its embedded
source is GPL only.  There wouldn't even be any need for a note about it,
except for informational purposes.

Anton



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click