> Personally, I don't see any problem with a parser library being GPL. > You can still link it with proprietary code as long as you don't > distribute the result, so it would be fine for research projects or > similar that rely on proprietary components. You can always *use* > GPLd code however you like. If you want to *distribute* proprietary > (or otherwise GPL-incompatible) code that depends on my volunteer > contributions, I'm happy to tell you to go jump off a bridge. >
You'd have an issue with a proprietary application using the wikitext parser as a library? You really find the LGPL completely unacceptable in this situation? Seems like kind of a hardline position to take. That same application could make API calls to MediaWiki, using it in essentially the same way, without the license restrictions. Also, GPL, in our use case, is fairly ineffective. Even if an application makes PHP calls directly into MediaWiki, that application doesn't necessarily need to be GPL, since there is no actual linking occurring. Not all MediaWiki extensions are GPL, for instance. Essentially, this will just limit a C version of the software, which is slightly lame. Meh. If we have a GPL library, I'll just wrap it in a wsgi python library to act as a shim. - Ryan _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
