Speaking of licensing issues, I've always wondered why Sword was licensed under the GPL license. Is there a specific purpose for being specifically GPL? To me if would be benifical for the library to be LGPL or a less restrictive license. I mean the purpose of the code is to make the bible available and is specifically designed in that respect. I believe the GPL restricts use of this purpose.
<br><br>For example, say I am a commercial company and I put out a device and publish an api to my UI. Some random hacker comes around and implements a sword program with that API and distribute the program freely. This generally is only possible if the company decided to open source their entire UI, which frequently might not be the case. In fact, the GPL restricts what components can be linked into a program.
<br><br>There are probably more issues then I am thinking of here, but to me I would give the code away and hope people used it to make the bible available to more people.<br><br>Keith Preston<br><br><br><div><span class="gmail_quote">
On 7/16/07, <b class="gmail_sendername">Eeli Kaikkonen</b> <<a href="mailto:eekaikko@mail.student.oulu.fi">eekaikko@mail.student.oulu.fi</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sword library source code has some licencing issues. Different files<br>have different licence statements. They should be reviewed and<br>corrected.<br><br>The problem is mostly theoretical because nobody really cares - the
<br>library is under GPL and that's that. But there may arise issues later<br>with GPL 3. Some of you may already know that GPL 2 and 3 are NOT<br>compatible. That may sound weird but that's how it is. The only thing
<br>which makes them compatible is the copyright notice which is not part of<br>the licence. If it reads "relased under GPL v 2 or later" it's<br>compatible. If it reads "released under GPL" it is unclear. If it reads
<br>"released under GPL; see the attached licence" and the GPL v 2 is<br>attached it is technically GPL 2 only and not compatible with version 3.<br><br>Inside Crosswire this is not important because we don't sue ourselves
<br>because of inconsistency. But if and when we use other libraries inside<br>Sword library and when the frontend projects use many different<br>libraries this may become an issue.<br><br>Most probably we want the Sword licence to be "under GPL v. 2 or any
<br>later version" to secure the widest compatibility possible. Even after<br>that the library or the frontends can not use two libraries of which one<br>is under GPL2 only and the other GPL3 only.<br><br> Yours,<br>
Eeli Kaikkonen (Mr.), Oulu, Finland<br> e-mail: <a href="mailto:eekaikko@mailx.studentx.oulux.fix">eekaikko@mailx.studentx.oulux.fix</a> (with no x)<br><br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br>