<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Tuomas,</p>
<p>Yes, Crossway has decided to ask us again to stop distributing
the ESV. We deal with new people there all the time and
explaining to them how we work and our "family" of applications,
and that open source software does not mean open source Bibles, is
a challenge. For the past 10 years, we have tried to get the ESV
distribution off of our server onto Crossway's server into their
own SWORD remote module installation repository, so as to not
require from CrossWire a license from Crossway (and all Crossway
requires of a license, including a nominal annual fee, renewing
the contract, providing regular download stats, etc.). Crossway
has expressed desire to do this in the past, which we hoped would
happen soon and hadn't been paying their licensing fees in the
hopes that they would take over their own distribution, but they
have never follow through with this. The most recent person in
charge of digital licensing has now sent us a bill for $1400 for
past licensing dues and is sending mixed signals:</p>
<p>"Crossway does not wish to have you do this [distribute from
CrossWire servers] with our content, as we have our own servers.
We also do not want to make your software or the data files that
work with our [sic: your?] software available on Crossway's site,
as we have our own proprietary API, apps, software, and systems."</p>
<p>...<br>
</p>
<p>"Crossway is not interested in granting you a license to
distribute the ESV from your server, nor do we wish to distribute
your data files and software from our site."</p>
<p>...</p>
<p>"If in the days to come you wish to use the ESV again, we would
welcome a new proposal from you regarding your desired use."</p>
<p><br>
</p>
<p>I sent the new distributions rights "VP" all the threads of
discussion we've had over the past 18 year with Crossway. I am
sure it was probably too much to be useful, but have quoted
relevant sections of those discussions. It all comes down to the
fact that we have 2000+ Bibles available for our tools. For no
other Bible do we have to pay an annual licensing fee or regularly
deal with demands from some new person in charge of digital rights
to cease distribute of their text when someone from our community
emails them and asks about their new SWORD frontend having access
to the ESV. It has become exhausting.<br>
</p>
<p>I am sad it has come to this,</p>
<p>Troy<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 6/4/19 11:44 PM, Tuomas Airaksinen
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACK9v-nHuvREpxbQEY47CEVuiOegQ_YaQzfyrpx9PeZPQ22Ndg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi,
<div><br>
</div>
<div>And Bible user notified me that popular ESV module has
disappeared and I checked that it indeed is not listed in AB
module listings at the moment. What happened?</div>
<div>
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">T: Tuomas</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
</body>
</html>