<html><body><div dir="ltr">Fair. Still my view. Did not know they are niw separate. It started thiugh as one and the basic decisions were made when one was part of the other. </div><div dir="ltr"><br></div><div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">Having access to all our modules and using the labour of everyone and then creating a separate ecosystem with special modules we can not use is in my eyes very bad behaviour. </div><div id="ms-outlook-mobile-body-separator-line" dir="ltr"><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;"></span></div><div id="ms-outlook-mobile-signature" dir="ltr"><br></div><div id="ms-outlook-mobile-signature">It might be acceptable from the license point of view, it is not acceptable to me from any other point of view. </div><div id="ms-outlook-mobile-signature" dir="ltr"><br></div><div id="ms-outlook-mobile-signature">Peter</div><div id="ms-outlook-mobile-signature" dir="ltr"><br></div><div id="ms-outlook-mobile-signature">Sent from <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div><div> </div><div id="mail-editor-reference-message-container" class="ms-outlook-mobile-reference-message"><hr style="display: inline-block; width: 98%;"><div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif;"><b>From:</b> sword-devel <sword-devel-bounces@crosswire.org> on behalf of David Haslam <dfhdfh@protonmail.com><br><b>Sent:</b> Monday, June 30, 2025 2:57 pm<br><b>To:</b> sword-devel mailing list <sword-devel@crosswire.org><br><b>Cc:</b> David Instone-Brewer <davidinstonebrewer@gmail.com>; Jamie Jamieson <jamie@critos.co.uk><br><b>Subject:</b> Re: [sword-devel] Script to find a best fit v11n</span><div style="font-family: Calibri, sans-serif;"> </div></div><div dir="auto">Hi Peter,</div><div dir="ltr"><br></div><div dir="auto">STEP Bible is formally & organisationally separate from Tyndale House, Cambridge.</div><div dir="ltr"><br></div><div dir="auto">It has been so for several years.</div><div dir="ltr"><br></div><div dir="auto">David</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div>On Mon, Jun 30, 2025 at 14:52, Peter von Kaehne <<a href="mailto:On Mon, Jun 30, 2025 at 14:52, Peter von Kaehne <<a href=">refdoc@gmx.net</a>> wrote:<blockquote><div dir="ltr" class="protonmail_quote">
Step Bible is to my mind the reason not ever to go LGPL. The sole reason STEP has the ESV and a dozen other modules we don’t have for us is a weird double encryption inside STEP we do not have access to. And Tyndale House behaves badly in terms of negotiating on everyone’s behalf. my view.
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div dir="ltr" class="protonmail_quote" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Peter
</div><div dir="ltr" id="ms-outlook-mobile-body-separator-line"><br>
</div><div id="ms-outlook-mobile-signature">
Sent from
<a href="https://aka.ms/o0ukef">Outlook for iOS</a>
</div><div class="protonmail_quote">
</div><div class="ms-outlook-mobile-reference-message" id="mail-editor-reference-message-container"><hr style="display: inline-block; width: 98%;"><div dir="ltr" id="divRplyFwdMsg"><span style="font-family: Calibri, sans-serif;"><b>From:</b> sword-devel <sword-devel-bounces@crosswire.org> on behalf of David Haslam <dfhdfh@protonmail.com><br><b>Sent:</b> Monday, June 30, 2025 2:40 pm<br><b>To:</b> sword-devel mailing list <sword-devel@crosswire.org><br><b>Subject:</b> Re: [sword-devel] Script to find a best fit v11n</span>
<div style="font-family: Calibri, sans-serif;">
</div></div><div dir="auto">
Does anyone know whether STEP Bible uses JSword as is, or a modified form of JSword ?
</div><div dir="ltr"><br>
</div><div dir="auto">
Asking in view of Arnaud’s observation about LGPL.
</div><div dir="ltr"><br>
</div><div dir="auto">
Kind regards,
</div><div dir="ltr"><br>
</div><div dir="auto">
David
</div><div dir="ltr"><br>
</div><div id="protonmail_mobile_signature_block"><div>
Sent from
<a href="https://proton.me/mail/home">Proton Mail</a> for iOS
</div></div><div dir="ltr"><br>
</div><div dir="ltr"><br>
</div>On Mon, Jun 30, 2025 at 14:32, Arnaud Vié <
<a href="mailto:On Mon, Jun 30, 2025 at 14:32, Arnaud Vié <<a href=">unas.zole+avie@gmail.com</a>> wrote:
<blockquote><div dir="ltr" class="protonmail_quote">
It might be a silly question, but can't we just consider changing the libsword license to something more permissive to allow such use cases, without overthinking about GPL compatibility issues ?
<br>
</div><div dir="ltr" class="protonmail_quote">
It is quite uncommon for open source libraries to use GPL nowadays, as it's very restrictive by nature. GPL remains mostly for "complete" applications - libraries tend to rather use LGPL, Apache 2.0 or MIT license (depending on the level of protection they seek), to favour wide usability.
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div dir="ltr" class="protonmail_quote">
It is to be noted that JSword is published under LGPL, which allows other apps to use it without constraints as long as it's not being modified.
<br>It would be enough for the current use case, and it would make sense for libsword and jsword to be aligned.
</div><div dir="ltr" class="protonmail_quote">
Personally speaking, I'd favour something more permissive like the Apache 2.0 license, which basically allows any usage or modification of any kind, but requires people to preserve the initial copyright notice and notify of significant changes.
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div dir="ltr" class="protonmail_quote">
Of course, publishing under a new license can only be done by the current rights holder, which according to the libsword LICENSE is the "CrossWire Bible Society", as an organisation.
</div><div dir="ltr" class="protonmail_quote">
Does Troy have the full power of decision on the topic ?
</div><div dir="ltr" class="protonmail_quote">
Troy, what do you think of publishing libsword under a more permissive license ?
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div dir="ltr" class="protonmail_quote">
Regards,
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div dir="ltr" class="protonmail_quote">
Arnaud
</div><div dir="ltr" class="protonmail_quote"><br>
</div><div class="protonmail_quote"><br>
</div><div dir="ltr" class="gmail_attr">
Le lun. 30 juin 2025 à 14:43, Matěj Cepl <
<a href="mailto:mcepl@cepl.eu">mcepl@cepl.eu</a>> a écrit :
<br>
</div><blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204);"><div class="gmail_quote">
On Mon Jun 30, 2025 at 4:55 AM CEST, Aaron Rainbolt wrote:
<br>> From what I understand as someone who isn't a lawyer but has done
<br>> licensing audits for applications in Ubuntu and Debian, you'll only
<br>> run into issues if you publish *built binaries* of your code.
<br>
<br>That technically may be true, but it is a stupid idea. You don’t
<br>do open source software, which nobody can package and distribute.
<br>
<br>And apparently FSF doesn’t agree with my analysis:
<br>
<a href="https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility" rel="noreferrer">https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility</a>
<br>
<br>So, my only advice is to relicense your new program under GPLv2
<br>and send FSF to … Apparently, you will be in the distinguished
<br>company of Linus Torvalds and many others.
<br>
<br>Best,
<br>
<br>Matěj
<br>
<br>--
<br>
<a href="http://matej.ceplovi.cz/blog/" rel="noreferrer">http://matej.ceplovi.cz/blog/</a>, @mcepl@en.osm.town
<br>GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
<br>
<br>For those of you who think we are descendents from those cavemen
<br>who stood and fought with dinosaurs, you must be nuts, we are
<br>descendents from the ones who ran like hell to live.
<br>
<br>_______________________________________________
<br>sword-devel mailing list:
<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer">http://crosswire.org/mailman/listinfo/sword-devel</a>
<br>Instructions to unsubscribe/change your settings at above page
<br>
</div></blockquote></blockquote></div><p class="protonmail_quote">_______________________________________________<br>sword-devel mailing list: sword-devel@crosswire.org<br>http://crosswire.org/mailman/listinfo/sword-devel<br>Instructions to unsubscribe/change your settings at above page</p></blockquote></div></body></html>