Re: AGPL

Emiliano Heyns <[email protected]> Sun, 13 Apr 2003 09:02:33 +0200
Newsgroups gmane.comp.java.xwt.general
Message-ID <[email protected]>
Adam Megacz wrote:

> Hrm, the AGPL is incompatible with the GPL.  Is this going to be a
> problem?

I don't see why. The app would be in contact with the widget lib and the
engine, but http://www.xwt.org/faq.html#license says:

> The XWT Standard Widget Library [LGPL] The XWT Standard Widget
> Library is a collection of XWT source files which provides standard
> widgets such as menus, scrollbars, checkboxes, etc. The XWT Standard
> Library is licensed under the GNU Library Public License [LGPL]. This
> is not the same as the GNU General Public License [GPL]. You are free
> to write closed-source XWT applications which interface with and use
> the standard library. However, if you modify or extend the library
> itself, you must relicense those modifications under the LGPL.
> Additionally, the widget library grants an exception from the
> "obnoxious relink clause" in the LGPL.

"Modify or extend" is a bit grey-area, I think. If I write my own theme, 
wven if it only has visual alterations (colors, bitmaps), I'm extending 
the widget set. Must this theme now be lgpl?

Anyhow, since I'm not planning on doing this, this doesn't concern me. 
Yet. The app I want to propose at work to replace with an XWT app *will* 
have to be themed to the house colors, so it then does become a concern. 
  Will this become a problem for me?

> The XWT Engine [GPL] The XWT Engine itself is Copyrighted by Adam
> Megacz, and is licensed to the public under the GNU General Public
> License. If you modify the engine, or link it with any other code,
> you must release the modifications/code under the GPL. It is
> important to note that running an XWT application within the engine
> does not constitute linking, so the XWT engine can be used to deploy
> closed-source applications. However, if you wish to create a
> closed-source port of the engine to another platform (such as an
> embedded device), you would need to acquire a special license from
> Adam Megacz.
> 
> Various libraries that XWT uses

And since I'm not changing the engine, I would think I'm clear here too.

And the backend xmlrpc server I'm writing is totally separated.

If there's a problem with AGPL for XWT apps, there will also be a
problem for any proprietary apps people may want to write with XWT.

Emile


_______________________________________________
http://lists.xwt.org/listinfo/dev